Product / Workflow architecture
How work moves
The operating map for every handoff connecting Designers, Providers, Clients and The Design Registry—from first application through Project delivery and financial reconciliation.
End-to-end operating model
One network. One connected journey.
Individual modules own their states, but the Project becomes the shared operational centre once work is awarded. No participant should have to reconstruct the journey from separate tools.
Join
Designer or Provider applies
Qualify
Client need becomes an Opportunity
Match
The right participant receives an Offer
Contract
Scope becomes accepted commercial work
Deliver
Project, Items and services move together
Approve
Client decisions release downstream work
Settle
Invoice, payment and records reconcile
Workflow directory
Find the journey you need
Jump to a compact state map. Open any workflow to inspect its trigger, handoffs, decision gates, exception paths and accountable owner.
Entry & conversion
How demand and network participants become governed records.
Project delivery
How the Project coordinates phases, Items, Providers and client decisions.
Commercial & control
How commitments, files and money become immutable evidence.
Collaboration
How people communicate, schedule, execute and account for work.
Status architecture
One record can have several truthful statuses
A Project can be in Procurement, have a blocked delivery Task, an overdue Invoice and an at-risk health signal at the same time. Each state answers a different question and must never overwrite another.
Lifecycle
Where the record is in its business journey
Application Stage · Project Phase · Offer StateOperational
What work is happening right now
Task State · Work Order State · Receiving StateCommercial
What has been offered, owed or paid
Proposal · Invoice · Payment · ReconciliationVisibility
Who may see or act on the record
Internal · Shared · Client-visible · RestrictedHealth
Whether attention or intervention is required
On track · At risk · Blocked · ExceptionHow to read the maps
States, gates and exceptions are different things.
Visual workflow register
Core journeys and exception paths
The state strip is always visible. Expand a map for its operating contract. The first three delivery-critical maps are open by default.
Entry & conversion
3 workflowsWF-01Network entryPartially implementedOpen operating contract ↓Designer and Provider application
Applicant · Registry reviewer · Workspace owner
01Draft02Submitted03Under review04Information requested05Decision recorded06Provisioning07Active
Designer and Provider application
Applicant · Registry reviewer · Workspace owner
WF-02Pipeline conversionPartially implementedOpen operating contract ↓Project Opportunity to Project
Registry · Designer · prospective Client
01New02Qualifying03Ready for matching04Matched05Proposal06Accepted07Converted to Project
Project Opportunity to Project
Registry · Designer · prospective Client
WF-04Network coordinationDefined in specificationOpen operating contract ↓Matchmaking, Offer and Assignment
Registry · Designer · Provider
01Eligibility check02Immutable Match Run03Shortlist review04Offer sent05Response06Award decision07Assignment active
Matchmaking, Offer and Assignment
Registry · Designer · Provider
Project delivery
4 workflowsWF-03Project operationsNext releaseOpen operating contract ↓Seven-Phase Project lifecycle
Designer · Client · assigned Providers · Registry
01Concept02Design03Design Package04Construction Administration05Decorating06Procurement07Installation
Seven-Phase Project lifecycle
Designer · Client · assigned Providers · Registry
WF-06Physical goodsDefined in specificationOpen operating contract ↓Item, purchasing and installation
Designer · Vendor · Storage · Delivery · Installer · Client
01Specified02Client approved03PO issued04Ordered05Shipped06Received07Stored08Delivered09Installed
Item, purchasing and installation
Designer · Vendor · Storage · Delivery · Installer · Client
WF-07Provider operationsDefined in specificationOpen operating contract ↓Provider service delivery
Designer · assigned Provider · Registry
01Requirement created02Quote requested03Quote returned04Offer accepted05Work Order06Scheduled07In progress08Evidence submitted09Complete
Provider service delivery
Designer · assigned Provider · Registry
WF-10Client experienceDefined in specificationOpen operating contract ↓Client review and approval
Designer · Client · authorized approver
01Prepared02Shared03Viewed04Client response05Decision recorded06Downstream work released
Client review and approval
Designer · Client · authorized approver
Commercial & control
3 workflowsWF-05CommercialDefined in specificationOpen operating contract ↓Proposal to payment
Designer · Provider · Client · Finance
01Draft Proposal02Sent03Accepted04Work Order issued05Work completed06Invoice issued07Paid and reconciled
Proposal to payment
Designer · Provider · Client · Finance
WF-11Content governancePartially implementedOpen operating contract ↓File and deliverable lifecycle
Internal team · Project participants · Client
01Draft02Internal review03Approved to share04Shared05External review06Accepted07Archived
File and deliverable lifecycle
Internal team · Project participants · Client
WF-12Platform operationsDefined in specificationOpen operating contract ↓Integration job and reconciliation
System · integration owner · operator
01Queued02Processing03Provider accepted04Result received05Validated06Reconciled07Succeeded
Integration job and reconciliation
System · integration owner · operator
Collaboration
2 workflowsWF-08Work managementPartially implementedOpen operating contract ↓Task, schedule and time
User · Team · Project owner · Provider resource
01Backlog02Open03Scheduled04In progress05Review06Complete
Task, schedule and time
User · Team · Project owner · Provider resource
WF-09CommunicationsPartially implementedOpen operating contract ↓Communication and unified inbox
Admin · Designer · Provider · Client
01Received or composed02Classified03Linked to Project04Assigned05Open06Pending07Resolved
Communication and unified inbox
Admin · Designer · Provider · Client
Future product / Provider operations
Category-specific work.
One shared commercial spine.
Providers should receive enough operational value to run the assigned work inside The Design Registry. Category modules specialize the records, statuses and evidence—not the platform foundation.
Every category inherits the same governed relationship from Project requirement through settlement.
Common Provider foundation
One useful business workspace before specialization.
Every Provider gets the same commercial and collaboration foundation. Category modules then change the dashboard emphasis, records, terminology, evidence recipes and operational states.
Operating blueprints
What changes by Provider Category
Each blueprint now covers the Provider portal, Project relationship, matchmaking profile, automations, AI assistance, performance measures and visibility boundary.
PW-01Future category moduleVendors & Product Suppliers
Products, availability and purchasing
1. Product specified2. Price & availability3. Quote4. PO acknowledged+3 statesOpen full Provider blueprint ↓
Portal anatomy
What this Provider operates every day
Fewer incomplete quote requests and consolidated Designer demand.
Items are the operating object. Vendors see only requested or ordered lines, authorized specifications, quantities, ship-to instructions and deadlines. Updates create Item and Purchase Order events rather than editing approved Project facts silently.
Trade pricing, margin and commercial terms are restricted. Client-facing views receive an authorized selling-price projection, never the Provider's confidential trade data.
How the right Provider is found
- Product categories and represented brands
- Trade terms and minimum order
- Service territory and shipping destinations
- Typical lead times and stock model
- Samples and specification support
- Approved catalogue or API capability
What the platform coordinates
- Alert when acknowledged price, quantity or variant differs from the Purchase Order
- Recalculate Project risk when availability or expected ship date changes
- Create substitution review when an Item is discontinued or backordered
- Notify the receiving destination when a Shipment becomes expected
Where AI removes administration
- Extract structured Product and variant fields from an approved URL
- Compare a quote or acknowledgement against the requested Item lines
- Suggest field mappings from Vendor catalogues without fabricating price or availability
- Provider value
- Fewer incomplete quote requests and consolidated Designer demand.
- Required evidence
- Acknowledgement · expected ship date · tracking · return terms
- Required controls
- Trade-price visibility, territory, minimum order and client-price separation
PW-02Future category moduleMillwork & Custom Fabrication
Measurement, drawings and fabrication
1. Scope received2. Site measure3. Quote4. Work Order+5 statesOpen full Provider blueprint ↓
Portal anatomy
What this Provider operates every day
Controlled revisions, complete scope and fewer fabrication mistakes.
Work is grouped by fabricated assembly, Space, drawing package and Work Order. Approved versions are immutable; superseded drawings remain linked to the exact decisions and fabrication milestones they informed.
The Provider receives only the Spaces, measurements, reference images, Files and contacts authorized for its scope. Client access is limited to approved selections, milestones and decisions.
How the right Provider is found
- Fabrication types and materials
- Service geography and installation capability
- Shop capacity and earliest start
- Project value and complexity bands
- Drawing and engineering capabilities
- Insurance, warranty and references
What the platform coordinates
- Block fabrication until the approved drawing revision and commercial deposit gate are recorded
- Notify reviewers when a new drawing revision is submitted
- Create schedule risk when measurement, approval or material milestones slip
- Create a deficiency Task from rejected completion evidence
Where AI removes administration
- Summarize a room-based scope package and identify missing dimensions
- Compare drawing revisions and surface changed callouts
- Draft milestone updates from approved progress evidence
- Provider value
- Controlled revisions, complete scope and fewer fabrication mistakes.
- Required evidence
- Measurement sign-off · approved drawing revision · progress photos · completion
- Required controls
- Fabrication cannot begin before drawing approval and deposit conditions
PW-03Future category moduleContractors & Specialty Trades
Discrete construction scopes
1. Scope issued2. Site review3. Quote4. Work Order+5 statesOpen full Provider blueprint ↓
Portal anatomy
What this Provider operates every day
Clearer scopes, fewer coordination gaps and faster invoicing.
Construction materials remain distinct from decorating and procurement Items but reuse the Item framework. They support submittals, quantities, alternates, site delivery, installation and evidence.
Providers see their assigned scope and dependencies—not the complete design fee, unrelated scopes or private Client information. Emergency actions remain auditable and time-bound.
How the right Provider is found
- Trade classifications and licences
- Service area and crew capacity
- Construction phase availability
- Project and scope size
- Insurance and safety readiness
- Permit and inspection capability
What the platform coordinates
- Prevent mobilization until site-readiness requirements are satisfied or waived
- Route RFIs to the accountable Designer or Project owner
- Require a Change Order before additional non-emergency work proceeds
- Create closeout Tasks for failed inspections or open deficiencies
Where AI removes administration
- Turn a scope narrative into structured inclusions, exclusions and clarification questions
- Summarize daily updates into Project progress
- Compare Change Order scope against the active Work Order
- Provider value
- Clearer scopes, fewer coordination gaps and faster invoicing.
- Required evidence
- Daily updates · inspection · completion proof · deficiency closure
- Required controls
- Licensing, insurance, site access, permits and safety documents
PW-04Future category modulePhotography
Creative production and usage rights
1. Brief issued2. Scope confirmed3. Scheduled4. Access confirmed+5 statesOpen full Provider blueprint ↓
Portal anatomy
What this Provider operates every day
Complete briefs, coordinated access and reusable rights records.
Photography Jobs attach to a Project milestone or completed Project. Assets inherit explicit audience, licensing and publication permissions rather than becoming globally visible on upload.
Private addresses, access contacts, unpublished work and embargoed assets are disclosed only for the scheduled Job and retained according to policy.
How the right Provider is found
- Architecture, interiors and lifestyle specialties
- Portfolio style and quality
- Geography and travel
- Availability and turnaround
- Photo, video and drone capability
- Licensing and usage models
What the platform coordinates
- Flag incomplete brief, access or release requirements before the shoot
- Notify participants of schedule or embargo changes
- Route uploaded proofs to the authorized selection group
- Apply rights metadata and expiry rules to approved assets
Where AI removes administration
- Generate a first shot list from Project Vision, Spaces and requested channels
- Classify uploaded assets by room and shot type
- Draft captions and alt text within approved usage rights
- Provider value
- Complete briefs, coordinated access and reusable rights records.
- Required evidence
- Shot list · releases · selected assets · rights metadata · final files
- Required controls
- Licensing scope, releases, credits, embargoes and storage policy
PW-05Future category moduleMeasurement & Drafting
Authoritative field records
1. Output selected2. Scope confirmed3. Site visit4. Field capture+4 statesOpen full Provider blueprint ↓
Portal anatomy
What this Provider operates every day
Standard requests, traceable revisions and fewer missing dimensions.
Measurements and drawings feed Concept, Design and Design Package. Issued documents are versioned Project deliverables and can satisfy configured Phase gates.
Site contacts and property access instructions expire after the visit. Draft files remain internal until the responsible reviewer authorizes an issued version.
How the right Provider is found
- Output types and file standards
- Measurement and drafting disciplines
- Service geography
- Accuracy tolerance and responsibility
- Turnaround and revision capacity
- Source-file delivery capability
What the platform coordinates
- Prevent scheduling until access and scope requirements are complete
- Create a review Task when a draft set is uploaded
- Supersede—but never delete—prior issued versions
- Satisfy configured Project Phase gates when an authoritative file is approved
Where AI removes administration
- Check a request for missing levels, Spaces and output standards
- Summarize comments by drawing sheet and revision
- Detect inconsistent room labels or dimensions for human review
- Provider value
- Standard requests, traceable revisions and fewer missing dimensions.
- Required evidence
- Field notes · source files · revision history · approval
- Required controls
- Accuracy tolerances, exclusions, file standards and reliance disclaimers
PW-06Future category moduleReceiving, Warehouse & Storage
Custody, condition and location
1. Expected item2. Appointment3. Received4. Identified+5 statesOpen full Provider blueprint ↓
Portal anatomy
What this Provider operates every day
Faster receiving, documented condition and accurate storage billing.
Receiving changes the canonical Item custody state. Every event records receiver, time, facility, quantity, condition, photographs and Storage Location. Moves preserve the complete location history.
Warehouse users see only operational Item and release data. Client contact details, Project financials and unrelated design files remain hidden unless explicitly required.
How the right Provider is found
- Facility location and service area
- Receiving and storage capacity
- Item types, size and handling limits
- Inspection and photo standards
- Claims and repair capability
- Billing model and insurance limits
What the platform coordinates
- Alert the authorized Project team immediately when condition or quantity exceptions are recorded
- Create a claim or resolution Task from configured damage classes
- Start storage aging and billing from the accepted receiving event
- Block release while an Item is on hold or authorization is missing
Where AI removes administration
- Match an arriving package to an expected Item using label, PO and tracking evidence
- Classify visible packaging or condition issues for receiver confirmation
- Summarize aging inventory and unresolved exceptions
- Provider value
- Faster receiving, documented condition and accurate storage billing.
- Required evidence
- Timestamp · receiver · package photos · condition · location history
- Required controls
- Chain of custody, release permissions, retention and item-level billing
PW-07Future category moduleWhite-Glove Delivery
Dispatch, tracking and proof
1. Release approved2. Manifest confirmed3. Scheduled4. Crew assigned+5 statesOpen full Provider blueprint ↓
Portal anatomy
What this Provider operates every day
Better manifests, fewer site surprises and immediate proof of service.
Authorized live milestones appear on the Designer's install-day view. Delivery evidence and exceptions attach to each Item, preserving the custody handoff into placement or Installation Services.
Exact location is shared only during the active route with explicit workforce policy. Client views receive privacy-safe status rather than unrestricted crew tracking.
How the right Provider is found
- Service area and route coverage
- Fleet, crew and capacity
- Handling and assembly capability
- Item size, value and complexity
- Access constraints and equipment
- Availability, insurance and claims history
What the platform coordinates
- Block dispatch when release, manifest or readiness requirements are incomplete
- Send editable milestone notifications for picked up, en route, arrived and complete
- Expire live location sharing automatically after the authorized route window
- Create item-level damage, failed-delivery or return-to-storage workflows
Where AI removes administration
- Check a manifest for missing access, handling and placement instructions
- Summarize route exceptions into a Client-safe status
- Draft a delivery completion report from signatures, photos and Item outcomes
- Provider value
- Better manifests, fewer site surprises and immediate proof of service.
- Required evidence
- Pickup scan · live status · item proof · signature · exception photos
- Required controls
- Tracking consent, limited retention, privacy-safe visibility and claims
PW-08Future category moduleInstallation Services
Readiness, placement and punch work
1. Install plan2. Readiness check3. Team assigned4. Site protected+5 statesOpen full Provider blueprint ↓
Portal anatomy
What this Provider operates every day
Room-level instructions, reduced downtime and defensible completion.
Installation updates both Item state and overall Project completion. Room-level outcomes remain traceable to the responsible crew, evidence and unresolved punch work.
Installers receive placement, access, safety and Item details for the assigned visit. Broader Client, budget and design-development records remain restricted.
How the right Provider is found
- Installation types and assembly skills
- Crew size and geography
- Item handling capability
- Tools, hardware and equipment
- Availability and Project Phase
- Insurance and completion standards
What the platform coordinates
- Compute install readiness from Item, delivery, site and Task dependencies
- Create punch items instead of silently completing unavailable or damaged Items
- Prevent full completion while required deficiencies remain open
- Release invoice readiness from accepted evidence or an authorized partial-completion path
Where AI removes administration
- Generate a room-by-room install checklist from Project Items and placement instructions
- Summarize blocked Items and required follow-up
- Prepare a completion report from checklists, photos and sign-offs
- Provider value
- Room-level instructions, reduced downtime and defensible completion.
- Required evidence
- Readiness result · room checklist · photos · punch closure · sign-off
- Required controls
- Site safety, property protection, disposal, punch ownership and acceptance
PW-09Future category moduleGeneral Service Providers
Configured reusable service modules
1. Requirement2. Scope3. Quote4. Work Order+5 statesOpen full Provider blueprint ↓
Portal anatomy
What this Provider operates every day
A flexible entry point without allowing ungoverned one-off processes.
General Services compose approved scheduling, Item access, milestone, evidence, location, inspection, sign-off and invoicing modules. They never create an unstructured status field.
Access is generated from the selected modules and Work Package. The Provider receives the minimum Project context necessary for the configured service.
How the right Provider is found
- Configured service taxonomy
- Capabilities and service area
- Availability and capacity
- Evidence and qualification rules
- Commercial model
- References and performance
What the platform coordinates
- Generate state and evidence requirements from approved module recipes
- Register every new event with the Notification Builder
- Escalate blocked milestones using shared service-recovery rules
- Flag a category for governance review when usage becomes frequent or material
Where AI removes administration
- Suggest an approved workflow recipe from the service description
- Identify missing scope, milestone or evidence fields
- Summarize performance patterns for category-governance review
- Provider value
- A flexible entry point without allowing ungoverned one-off processes.
- Required evidence
- Configured from scheduling, milestones, inspection, location and sign-off recipes
- Required controls
- A frequent, material service graduates into a canonical Provider Category
Shared service recovery
Exceptions stay attached to the work.
Every category uses the same recovery contract so a problem becomes a governed resolution—not a lost message or rewritten status.
- 01Issue linked to the Project, Item, Work Order, milestone or payment
- 02Evidence, timestamp and responsible parties preserved
- 03Urgency and Client impact classified
- 04Time-bound owner, Task and editable notification created
- 05Resolution recorded as replacement, reschedule, credit, claim, Change Order or dispute
- 06Outcome and performance effect reviewed with an appeal path
Workflow governance