BC
Brad CodyAdministrator
Current product→Pipelines and record experience
Reverse spec drafted

Pipeline record creation and editing

Create and edit a Pipeline record using governed fields, standardized controls and the active published workflow.

Observed route/admin/pipelinesFuture Spec 09 →
Current maturityFunctional legacy Lead form not yet governed by the published Pipeline
Evidence confidenceVerified
Last reviewedAugust 4, 2026
Visual evidenceDeferred during UI updates

Current-state summary

New opportunity opens a large Create a new lead modal containing 43 active CRM fields across Core details, Contact, Project, Qualification, Assignment, Matching criteria and Project snapshot. It demonstrates useful standardized controls, separate Client and Project addresses, OpenStreetMap address lookup, alphabetized dropdowns and sensible defaults. However, its stage selector uses the legacy states Matched, Matching, Negotiation, New lead, Proposal sent and Qualified instead of the published stages New intake, Qualification, Client review, Ready to convert, Converted to project and Closed. The form is therefore functional as a legacy CRM form but not yet a genuine dynamic Pipeline Record form.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

ElementCurrent behaviorVerification
Modal identityTitle says Create a new lead and explains separate billing and Project-site addresses.Verified live
Core detailsProject name, Pipeline stage and priority are required. Medium and New lead are preselected.Verified live
ContactCaptures name, email, phone, address, best contact time, time zone, preferred contact and decision-maker status.Verified live
ProjectCaptures separate Project address, location, Project type and square footage.Verified live
QualificationCaptures budget range, estimated value, source, desired start date and furniture spend.Verified live
AssignmentCaptures Designer, next task, internal notes and required Admin owner.Verified live
Matching criteriaCaptures style, specialties, language, timeline, property type, rooms and services.Verified live
Project snapshotCaptures design package, hours, commission rate and hourly rate, including legacy Proper Gallery language.Verified live
Form count and actionsReports 43 active CRM fields and offers Cancel/Create lead.Verified live; submission not executed

User journeys

Current flows

01

Create opportunity

  1. Open New opportunity
  2. Complete required identity and qualification fields
  3. Resolve addresses
  4. Assign owner
  5. Add matching context
  6. Submit
Observed result

All controls reviewed; submission intentionally not performed. Current stage selection would create against legacy values.

02

Edit opportunity

  1. Open a record Overview
  2. Select Edit
  3. Load existing values
  4. Change permitted fields
  5. Validate and save
  6. Project updated summaries and Activity
Observed result

Edit surface evidenced; save and concurrency behavior not tested.

03

Resolve Client

  1. Enter email/name/address
  2. Search existing Clients
  3. Detect possible duplicate
  4. Link or create durable Client
  5. Preserve source attribution
Observed result

Required scalable behavior; duplicate search and durable Client resolution are not visible in the current form.

State model

Current and expected states

New form

Defaults include New lead, Medium, Ontario, Canada, Eastern Time, Full-service, $250–300K, Manual, Brad Mitchell and 15% commission.

Required incomplete

Required labels are visible; inline validation behavior was not triggered.

Address search

Client and Project address fields expose OpenStreetMap suggestion attribution.

Saving

Create submission state, duplicate protection and retry behavior were not tested.

Edit conflict

No version token or concurrent-edit warning is visible.

Product rules

Non-negotiable boundaries

  • The form must be generated from the active published Pipeline version and field schema.
  • A record cannot choose a stage absent from its Pipeline version.
  • Client billing and Project-site addresses remain separately modeled.
  • Required, visible, editable and transition-required are distinct field properties.
  • Dropdowns use shared taxonomies and deterministic alphabetical ordering where order has no business meaning.
  • Currency is stored as amount plus currency and displayed with symbols and separators.
  • Date controls store a canonical date/time meaning and show the applicable time zone.
  • Create is idempotent and duplicate Client/opportunity detection precedes irreversible creation.
  • Internal Notes in a creation form must not bypass the canonical revisioned Notes module without an explicit migration rule.
Dependencies
Published Pipeline versionDynamic form schemaShared field registryTaxonomiesAddress providerClient entity resolutionUser/team assignmentMatching questionnaireCurrency/date componentsActivity and audit events

Known current limitations · 8 mapped

What is missing, broken or unverified

Future Spec 09 owns closure →
  1. Critical: the form stage list conflicts with the published Pipeline.
  2. The title and submit action still say lead rather than Pipeline Record or opportunity.
  3. The 43 active fields appear CRM-configured rather than versioned in the current Pipeline Builder; Record details is still a placeholder.
  4. No Client duplicate detection or link-to-existing flow is visible.
  5. Saved labels such as Full-service (saved) and $250–300K (saved) leak configuration state into user-facing options.
  6. Proper Gallery commission language remains.
  7. Required validation, server errors, partial failure, retry and idempotency were not tested.
  8. Conditional fields, per-stage visibility and permission-based field redaction are not evidenced.

Future alignment

Required evolution

  • 01Replace the legacy Lead modal with the shared Dynamic Form renderer bound to a Pipeline version.
  • 02Separate record creation requirements from later transition requirements.
  • 03Resolve or create durable Client entities without duplicate contacts.
  • 04Support Admin, Designer and Provider general-lead Pipelines through the same form engine.
  • 05Record field provenance, original source and AI/import confidence when fields are populated automatically.

Current baseline

Acceptance record

  • All seven field groups and 43-field count are documented.
  • Standardized address, dropdown, currency and date expectations are recorded.
  • Legacy and published stage lists are explicitly compared.
  • The current form is not described as configuration-driven until the mismatch is removed.
  • Create/edit testing avoids mutating the live opportunity dataset.

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
← Feature inventoryOpen Future Spec 09 →