A field guide that behaves like event infrastructure.
The Peer Review build is a working companion for a small, high-context training: agenda, speakers, venue, stay planning, area guidance, and a public Fund Guide that keeps provider references source-backed without overstating what has been verified.
Voice notes are useful only when the privacy posture is honest.
The agenda title opens a session note surface. Attendees can type notes, use browser voice notes when supported, create a PDF on their device, and send a follow-up request. The product stance is simple: give people useful tools while naming the boundary clearly. Simpli-FI Events does not store audio, transcripts, or PDFs unless the attendee submits a follow-up request.
Open agenda→The table is a doorway, not the whole product.
The compact Fund Guide gives one-line scanning for every TLFFRA fund, then routes each fund to its own detail page. The ranking copy now describes the source clearly: PRB total expenses as a percentage of assets, converted to basis points. No vague 'low' label, and no implied advice.
Open fund guide→Every physical place should behave like a place.
Venue, dinner, hotels, and area-guide locations use native map links where the location appears as visible text. It removes the clumsy 'Map' pill pattern and lets the page feel more like a concierge desk than a spreadsheet.
Open venue guide→Speaker profiles need enough polish to be trusted.
The speaker cards include public bio copy, LinkedIn links, a public resource PDF where available, and clickable portraits that open in a larger framed view. The interaction is small, but it makes the page feel cared for.
Open speakers→Verification is a workflow, not a button label.
The Fund Guide now offers an update review request. It does not automatically accept changes or send a public self-service link. Requests go internal first so staff can verify the requester against fund, city, administrator, board, or public-source records.
Open update intake→These snippets avoid private event data and blur example contact fields. Live public pages can show public speaker names, public fund metrics, and public venue information. Private notes, emails, transcript text, sponsor lead data, and update-request details should stay redacted or out of the portfolio entirely.
The portfolio page explains product decisions. The live build remains available for the parts that are already public.