Shared Product Blueprint

Open House Sign-In

A read-only Product Blueprint created with IdeaMade.

Open house visitor sign-in and follow-up tracker

Open House Sign-In

A public, no-login sign-in form for live open house sessions where visitors share contact details and buyer answers, plus an agent-only back office to create sessions, open and close sign-in, review visitors grouped by session, spot duplicate emails, and track follow-up statuses and private notes.

Users and roles

The people who interact with the product.

Visitor

A prospective buyer who attends an open house and signs in on the public form without creating an account.

  • Sign in quickly at a live open house without an account
  • Share contact details and buyer answers once
  • Keep their details private from other visitors

Agent

The independent real estate agent who owns the open houses and reviews and follows up on visitor sign-ins.

  • Create open house sessions and control when sign-in is open
  • Review visitors grouped by open house
  • Spot repeat sign-ins by the same email

Key workflows

The main paths users take to reach an outcome.

Visitor signs in at a live open houseVisitorCore
1

View live session detailsThe visitor sees the property address and session date and time, or a closed notice when the session is Upcoming or Closed.

2

Submit contact details and buyer answersThe visitor enters full name, email, phone, whether they already work with an agent, buying timeline and interest level, and submits.

Outcome: The visitor's contact details and buyer answers are recorded for the agent to follow up.
Agent reviews and follows up on visitorsAgentCore
1

Sign inThe agent signs in to reach the back office.

2

Create and open a sessionThe agent creates an open house session and sets it Live so the public form accepts sign-ins.

3

Review session visitorsThe agent reviews sign-ins grouped by open house, spots duplicate-email badges and filters by follow-up status and representation.

4

Update follow-up and notesThe agent updates the follow-up status, adds private notes and reviews other open houses attended by the same email.

Outcome: The agent has reviewed visitors grouped by open house and updated follow-up statuses and private notes.

Pages

5 pages in the MVP

Public sign-in formShow the property address and session date and time for a live open house and let a visitor submit contact details and buyer answers without signing in. Upcoming and Closed sessions show a closed notice instead of the form.
Public
Public sign-in form
Sign inLet the agent sign in to reach the back office. Visitors never need this page.
Public
Sign in
Open housesList open house sessions with property address, session date, status and visitor count, and let the agent create a session. Empty state: create the first open house session to start collecting sign-ins.
Signed in
Open houses
Session visitorsList sign-ins for a selected open house with visitor name, working-with-agent flag, interest level, follow-up status and duplicate-email badge, and filter by follow-up status and representation. Empty state: no sign-ins yet for this session.
Signed in
Session visitors
Open house sessionFull nameEmailPhone
Visitor detailShow a visitor's original sign-in answers, follow-up status, private notes and other open houses attended by the same email. Once follow-up status is Closed the original answers are locked while private notes can still be added.
Signed in
Visitor detail

Product decisions

Choices you can confirm directly in the Blueprint.

How should a session move between Upcoming, Live, and Closed, and can it be reopened after closing?ConfirmedHow should a session move between Upcoming, Live, and Closed, and can it be reopened after closing?
Agent manually advances Upcoming to Live to Closed; Closed is final
When the same email submits again for the same session, should the newer entry replace the earlier one, or should both entries be kept with the newer flagged as a duplicate?ConfirmedWhen the same email submits again for the same session, should the newer entry replace the earlier one, or should both entries be kept with the newer flagged as a duplicate?
Keep both entries; flag the newer as duplicate

Assumptions

Items that should be verified before implementation.

The agent manually advances a session from Upcoming to Live to Closed, and a Closed session cannot be reopened.

High impactAccepted

When the same email submits again for the same session, both entries are kept and the newer one is flagged as a duplicate.

Medium impactAccepted

There is a single agent account provisioned outside the app; self-service sign-up for multiple agents is out of scope for this version.

Medium impactAccepted

Each open house session has a public sign-in link the agent shares with visitors; the link shows a closed notice when the session is not Live.

Low impactAccepted