BC
Brad CodyAdministrator
Current productPipelines and record experience
Reverse spec drafted

Record Proposals

Commercial records related to the current opportunity or application.

Observed route/admin/leads/:id?tab=proposalsFuture Spec 06
Current maturityHonest disabled placeholder; commercial module not implemented
Evidence confidenceKnown limitation
Last reviewedAugust 4, 2026
Visual evidenceDeferred during UI updates

Current-state summary

Proposals remains present in the record navigation for roadmap context, but it is now disabled and labeled Coming soon. This corrects the earlier behavior where selecting it silently rendered Overview. No proposal list, status, create action, template, commercial summary or empty state is implemented yet, and the global Admin Proposals destination is also disabled with Coming soon.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

ElementCurrent behaviorVerification
TabProposals is visible, disabled and labeled Coming soon.Verified live
InteractionCannot be selected and therefore cannot replace the current record body with unrelated content.Verified live
Proposal listNot implemented on this surface.Absent live
Create actionNot implemented on this surface.Absent live
Empty stateNot implemented because the module is not enterable.Absent live

User journeys

Current flows

01

Encounter planned Proposals

  1. Review record tabs
  2. See Proposals marked Coming soon
  3. Remain in the current working module
Observed result

Verified honest placeholder behavior.

02

Create and send proposal

  1. Create from template
  2. Add scope/pricing/terms
  3. Preview branded output
  4. Send
  5. Track acceptance
  6. Convert accepted work
Observed result

Future Spec 06 journey; not present.

State model

Current and expected states

Coming soon

Visible and disabled.

Empty

No dedicated empty state yet.

Draft/sent/viewed/accepted/declined/expired

Not represented.

Load failure

Not represented.

Product rules

Non-negotiable boundaries

  • An enabled tab must render its own module or a clear unavailable state.
  • Proposals remain linked to their source opportunity and Workspace.
  • Commercial records use immutable versions after sending.
  • Only authorized viewers see pricing, terms and contact information.
  • Acceptance must be auditable and idempotent.
Dependencies
Proposal serviceTemplate and branding systemPricing/financial permissionsClient/provider identitiesElectronic acceptanceNotificationsProject conversion

Known current limitations · 4 mapped

What is missing, broken or unverified

Future Spec 06 owns closure →
  1. Dedicated proposal content is missing.
  2. No global proposal route is currently available.
  3. No statuses, versioning, approvals, PDFs or acceptance behavior are evidenced.
  4. Coming soon does not provide timing, documentation or an alternate workflow.

Future alignment

Required evolution

  • 01Implement Spec 06 proposal, work-order and invoicing model.
  • 02Provide record-scoped list plus global table from one canonical dataset.
  • 03Support Designer proposals and Provider quotes with configurable branded templates.
  • 04Replace the disabled placeholder only when loading, empty, populated, error and permission states exist.

Current baseline

Acceptance record

  • The tab is visibly disabled and labeled Coming soon.
  • The feature is not described as working.
  • Future states and dependencies are separated from current behavior.
  • A functional release requires a dedicated empty state at minimum.

Reverse-spec completeness

Documentation coverage

The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.

Purpose and user outcome

Documented

Roles and access

Documented

Routes and entry points

Documented

Page and component anatomy

Documented

Fields and displayed data

Documented

Primary actions

Documented

Forms and validation

Documented

States and transitions

Documented

Empty, loading and error states

Documented

Responsive behavior

Partial

Accessibility behavior

Partial

Activity and audit events

Partial

Data sources and persistence

Documented

Notifications and automation

Partial

Known defects and limitations

Documented

Reusable component dependencies

Documented

Future-spec conflicts

Partial

Visual and repository evidence

Deferred

Acceptance of current baseline

Documented