Record Overview
Summary cards, contact details, Project snapshot, matching profile, vision, recent work and actions.
/admin/leads/:idFuture Spec 09 →Current-state summary
The Overview brings the opportunity, Client, commercial estimate, matching inputs, vision, inspiration and recent work into one page. Forest Hill Residence includes complete location/contact context, a $425,000 estimated value, 36% matching-profile completion, six inspiration images and empty recent-work cards. Edit actions are card-scoped, while prior evidence shows one large standardized form spanning core, contact, Project, qualification, assignment, matching and snapshot sections.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Opportunity information | Shows identity, type, stage, priority, Project address, estimated value, source and furniture spend. | Verified live |
| Client Contact | Shows identity, contact methods, billing/location fields, time zone and decision context. | Verified live |
| Project Snapshot | Shows design package, hours, commission, hourly rate and total estimate. | Verified live; values are currently zero |
| Matchmaking completeness | Shows completion percentage, completed-field count and eleven criteria. | Verified live at 36%, 4 of 11 |
| Vision and inspiration | Shows Project narrative, six images, Edit and Add images. | Verified live |
| Recent work cards | Internal Notes, Activity Timeline, Next Steps and Documents & Files show latest content or explicit empty states with links to full tabs. | Verified live |
User journeys
Current flows
Qualify opportunity
- Review opportunity and Client
- Assess value and Project type
- Review matching completeness
- Fill missing criteria
- Set next action
Edit record
- Select a card Edit action
- Open sectioned form
- Use standardized fields
- Validate required values
- Save and refresh summary
Continue into work
- Review a recent-work card
- Select View all or Add
- Open the matching dedicated tab or composer
State model
Current and expected states
Displays formatted value such as $425,000, Ontario or Renovation.
Displays Not provided rather than a blank.
Displays a module-specific empty message and action.
Shows 36% and four completed criteria.
Shows $0 and 0 hrs without explaining whether not configured or truly zero.
Product rules
Non-negotiable boundaries
- Overview values are projections of canonical fields, not separately editable copies.
- Missing and zero are distinct states.
- Client and Project addresses remain separately modeled.
- Currency, dates, addresses and dropdowns use standardized components.
- Sensitive contact and financial fields must respect field-level permissions.
Known current limitations · 5 mapped
What is missing, broken or unverified
Future Spec 09 owns closure →- Zero Project Snapshot values do not distinguish unset from calculated zero.
- Legacy Proper Gallery commission language remains.
- Matching completeness counts presence, but quality/recency rules are not visible.
- No duplicate Client warning is shown on the summary.
- Field-level access variants were not verified.
Future alignment
Required evolution
- 01Drive overview cards from Pipeline/entity profile configuration.
- 02Distinguish missing, not applicable and calculated zero.
- 03Expose readiness blockers for matching and conversion.
- 04Reuse the same standardized summary modules for Admin, Designer, Provider and Client with permission-aware content.
Current baseline
Acceptance record
- Opportunity, Client, Project and matching context are visible.
- Missing values use explicit labels.
- Recent work links to full modules.
- Inspiration and vision are retained on the record.
- Edit behavior uses standardized form controls.
Reverse-spec completeness
Documentation coverage
The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.
Purpose and user outcome
DocumentedRoles and access
DocumentedRoutes and entry points
DocumentedPage and component anatomy
DocumentedFields and displayed data
DocumentedPrimary actions
DocumentedForms and validation
DocumentedStates and transitions
DocumentedEmpty, loading and error states
DocumentedResponsive behavior
PartialAccessibility behavior
PartialActivity and audit events
PartialData sources and persistence
DocumentedNotifications and automation
PartialKnown defects and limitations
DocumentedReusable component dependencies
DocumentedFuture-spec conflicts
PartialVisual and repository evidence
DeferredAcceptance of current baseline
Documented