BC
Brad CodyAdministrator

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.

Registered maps12Across 12 workflow domains
Workflow maps12Canonical product journeys
Partially live5Existing behavior to extend
Next release1Immediate delivery priority
Defined next6Sequenced in future specifications

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.

01Application

Join

Designer or Provider applies

02Pipeline

Qualify

Client need becomes an Opportunity

03Network

Match

The right participant receives an Offer

04Commercial

Contract

Scope becomes accepted commercial work

05Project

Deliver

Project, Items and services move together

06Client

Approve

Client decisions release downstream work

07Finance

Settle

Invoice, payment and records reconcile

Operational centreProjectOne canonical shared record
ClientDesignerProviderRegistry
PipelineTasksItemsFilesCommercialCommunication

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.

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.

01

Lifecycle

Where the record is in its business journey

Application Stage · Project Phase · Offer State
02

Operational

What work is happening right now

Task State · Work Order State · Receiving State
03

Commercial

What has been offered, owed or paid

Proposal · Invoice · Payment · Reconciliation
04

Visibility

Who may see or act on the record

Internal · Shared · Client-visible · Restricted
05

Health

Whether attention or intervention is required

On track · At risk · Blocked · Exception

How to read the maps

States, gates and exceptions are different things.

Primary stateSuccessful outcomeDecision gateException pathHuman handoff

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 workflows
WF-01Network entryPartially implemented
Open operating contract

Designer and Provider application

Applicant · Registry reviewer · Workspace owner

01Draft
02Submitted
03Under review
04Information requested
05Decision recorded
06Provisioning
07Active
Trigger

Application submitted

Successful outcome

Approved Entity and active Workspace

Human handoff

Applicant → Registry reviewer → Workspace owner

Transition gates
01Identity verified02Review decision03Provisioning complete
Exception and alternate outcomes
DeclinedWithdrawnSuspended
Required evidenceAuthorized actorActivity eventEditable notificationException recoveryAudit history
State rule

Application Stage, review decision, Entity status, Workspace status and onboarding status remain separate state families.

Current maturity

Application builders exist; end-to-end approval and provisioning require completion.

Accountable owner

Provider Operations + Product

Open spec 05
WF-02Pipeline conversionPartially implemented
Open operating contract

Project Opportunity to Project

Registry · Designer · prospective Client

01New
02Qualifying
03Ready for matching
04Matched
05Proposal
06Accepted
07Converted to Project
Trigger

Qualified inquiry created

Successful outcome

Canonical Client and Project

Human handoff

Registry → Designer → Project team

Transition gates
01Required fields02Match readiness03Accepted proposal
Exception and alternate outcomes
NurtureClosed — not proceedingDuplicate
Required evidenceAuthorized actorActivity eventEditable notificationException recoveryAudit history
State rule

Stages are configured by a published Pipeline version; conversion creates or links canonical Client and Project records exactly once.

Current maturity

Project Opportunity records and conversion action exist; governed transition rules and legacy cleanup remain.

Accountable owner

Sales + Product

Open spec 09
WF-04Network coordinationDefined in specification
Open operating contract

Matchmaking, Offer and Assignment

Registry · Designer · Provider

01Eligibility check
02Immutable Match Run
03Shortlist review
04Offer sent
05Response
06Award decision
07Assignment active
Trigger

Eligible Project requirement

Successful outcome

Active Project assignment

Human handoff

Registry → shortlisted participant → Project

Transition gates
01Eligibility02Human award03Accepted Offer
Exception and alternate outcomes
DeclinedCounteredExpiredWithdrawnNo award
Required evidenceAuthorized actorActivity eventEditable notificationException recoveryAudit history
State rule

A Match Run recommends; an authorized human awards. Accepted Offers create the Project relationship and minimum access grant.

Current maturity

Future release after Projects, permissions and Pipelines.

Accountable owner

Network Operations + Product

Open spec 10

Project delivery

4 workflows
WF-03Project operationsNext release
Open operating contract

Seven-Phase Project lifecycle

Designer · Client · assigned Providers · Registry

01Concept
02Design
03Design Package
04Construction Administration
05Decorating
06Procurement
07Installation
Trigger

Project created from an accepted opportunity

Successful outcome

Installed, closed and archived Project

Human handoff

Designer ↔ Client ↔ assigned Providers

Transition gates
01Phase requirements02Client approvals03Completion evidence
Exception and alternate outcomes
On holdCancelledCompleted and archived
Required evidenceAuthorized actorActivity eventEditable notificationException recoveryAudit history
State rule

Project Phase is not a task status. Each Phase may be Not started, Active, Blocked or Complete, and templates can define gates without creating a second Project.

Current maturity

The seven-Phase structure is established; operational depth, Items, Budgets and Providers are queued.

Accountable owner

Product + Designer Success

Open spec 07
WF-06Physical goodsDefined in specification
Open operating contract

Item, purchasing and installation

Designer · Vendor · Storage · Delivery · Installer · Client

01Specified
02Client approved
03PO issued
04Ordered
05Shipped
06Received
07Stored
08Delivered
09Installed
Trigger

Project Item specified

Successful outcome

Installed Item with complete custody history

Human handoff

Designer → Vendor → Storage → Delivery → Installer

Transition gates
01Client approval02Condition evidence03Delivery confirmation
Exception and alternate outcomes
BackorderedDamagedMissingReturnReplacementCancelled
Required evidenceAuthorized actorActivity eventEditable notificationException recoveryAudit history
State rule

Selection, purchasing, shipment, custody, condition, delivery and installation statuses are independent so one exception never overwrites the complete Item history.

Current maturity

Item lists exist conceptually; normalized procurement and custody workflows are queued with Projects.

Accountable owner

Project Operations

Open spec 07
WF-07Provider operationsDefined in specification
Open operating contract

Provider service delivery

Designer · assigned Provider · Registry

01Requirement created
02Quote requested
03Quote returned
04Offer accepted
05Work Order
06Scheduled
07In progress
08Evidence submitted
09Complete
Trigger

Project service requirement

Successful outcome

Accepted service evidence and completion

Human handoff

Designer → Provider → Project owner

Transition gates
01Quote acceptance02Work Order03Evidence review
Exception and alternate outcomes
Needs clarificationRescheduleBlockedChange orderDisputed
Required evidenceAuthorized actorActivity eventEditable notificationException recoveryAudit history
State rule

Every Provider uses the shared commercial and Project services, then adds category-specific operational evidence such as receiving, tracking, measurements or revisions.

Current maturity

Generic path is defined; category-specific portals and evidence remain to be implemented.

Accountable owner

Provider Operations

Open spec 07
WF-10Client experienceDefined in specification
Open operating contract

Client review and approval

Designer · Client · authorized approver

01Prepared
02Shared
03Viewed
04Client response
05Decision recorded
06Downstream work released
Trigger

Versioned decision package shared

Successful outcome

Recorded decision and released work

Human handoff

Designer → authorized Client → Project team

Transition gates
01Permitted version02Authorized approver03Decision recorded
Exception and alternate outcomes
Changes requestedDeclinedExpiredSuperseded
Required evidenceAuthorized actorActivity eventEditable notificationException recoveryAudit history
State rule

The approval records the exact version, approver, time and downstream effect; a later revision creates a new decision instead of rewriting history.

Current maturity

Future Client Portal workflow using Project presentations, selections and deliverables.

Accountable owner

Client Experience + Product

Open spec 13

Commercial & control

3 workflows
WF-05CommercialDefined in specification
Open operating contract

Proposal to payment

Designer · Provider · Client · Finance

01Draft Proposal
02Sent
03Accepted
04Work Order issued
05Work completed
06Invoice issued
07Paid and reconciled
Trigger

Approved scope is ready to price

Successful outcome

Paid and reconciled commercial record

Human handoff

Seller → buyer → Finance

Transition gates
01Version acceptance02Work completion03Payment reconciliation
Exception and alternate outcomes
Changes requestedDeclinedCancelledPartially paidOverdueRefunded or credited
Required evidenceAuthorized actorActivity eventEditable notificationException recoveryAudit history
State rule

Accepted commercial versions are immutable. Operational completion, Invoice status, processor payment and accounting reconciliation are distinct states.

Current maturity

Proposal placeholders exist; Work Orders, Invoices and payment state are future releases.

Accountable owner

Finance + Product

Open spec 06
WF-11Content governancePartially implemented
Open operating contract

File and deliverable lifecycle

Internal team · Project participants · Client

01Draft
02Internal review
03Approved to share
04Shared
05External review
06Accepted
07Archived
Trigger

File or deliverable created

Successful outcome

Accepted or archived versioned evidence

Human handoff

Author → reviewer → permitted audience

Transition gates
01Review status02Visibility03Version acceptance
Exception and alternate outcomes
Changes requestedSupersededRejectedWithdrawn
Required evidenceAuthorized actorActivity eventEditable notificationException recoveryAudit history
State rule

File version, review state, visibility and deliverable status remain separate. Links always resolve to the permitted current or historically cited version.

Current maturity

Basic uploads exist; versioning, review, deliverables and visibility governance are queued.

Accountable owner

Product + Project Operations

Open spec 14
WF-12Platform operationsDefined in specification
Open operating contract

Integration job and reconciliation

System · integration owner · operator

01Queued
02Processing
03Provider accepted
04Result received
05Validated
06Reconciled
07Succeeded
Trigger

Signed integration event or scheduled job

Successful outcome

Validated and reconciled canonical data

Human handoff

External system → Registry → operator

Transition gates
01Signature02Deduplication03Reconciliation
Exception and alternate outcomes
PartialRetryingFailedDead letterDisconnected
Required evidenceAuthorized actorActivity eventEditable notificationException recoveryAudit history
State rule

External success does not equal Registry success until the canonical record is validated and reconciled. Every event is signed, deduplicated and auditable.

Current maturity

Integration contracts are documented; connected production accounts and jobs are future work.

Accountable owner

Technology + Integration Owner

Open spec 18

Collaboration

2 workflows
WF-08Work managementPartially implemented
Open operating contract

Task, schedule and time

User · Team · Project owner · Provider resource

01Backlog
02Open
03Scheduled
04In progress
05Review
06Complete
Trigger

Work is created or templated

Successful outcome

Approved time and completed work

Human handoff

Owner → collaborators → reviewer

Transition gates
01Resource capacity02Dependency release03Time approval
Exception and alternate outcomes
BlockedOn holdCancelledReopened
Required evidenceAuthorized actorActivity eventEditable notificationException recoveryAudit history
State rule

Task State, calendar placement, resource booking and time-entry approval are separate. Completing a Task never silently approves its time entries.

Current maturity

Basic Tasks exist; dependencies, Calendar, resources and time tracking are queued.

Accountable owner

Product + Operations

Open spec 12
WF-09CommunicationsPartially implemented
Open operating contract

Communication and unified inbox

Admin · Designer · Provider · Client

01Received or composed
02Classified
03Linked to Project
04Assigned
05Open
06Pending
07Resolved
Trigger

Inbound message or outbound composition

Successful outcome

Resolved, linked conversation

Human handoff

Channel → inbox owner → Project participant

Transition gates
01Identity and route02Project classification03Resolution
Exception and alternate outcomes
SnoozedSpamDelivery failedUnmatchedReopened
Required evidenceAuthorized actorActivity eventEditable notificationException recoveryAudit history
State rule

Conversation status is separate from channel delivery. Internal Notes and tags are never sent externally, and every participant route is permission-checked.

Current maturity

Record Communication tabs and Messages shell exist; unified email, SMS, calling and classification are future work.

Accountable owner

Communications Product Owner

Open spec 11

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.

Shared Provider journey

Every category inherits the same governed relationship from Project requirement through settlement.

01Requirement02Work Package03Match04Offer05Proposal06Work Order07Service08Evidence09Invoice
Offers, Proposals, Work Orders, Tasks, Messages, Files, Invoices and payment visibility are shared modules.

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.

01Workspace & business profile02CRM & own opportunities03Offers & RFP inbox04Proposal templates05Work Orders & changes06Tasks & Calendar07Scoped Messages08Files & evidence09Invoices & payment10Notifications11Reporting12Project access grants

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 module

Vendors & Product Suppliers

Products, availability and purchasing

1. Product specified2. Price & availability3. Quote4. PO acknowledged+3 states
Open full Provider blueprint ↓
01Product specified02Price & availability03Quote04PO acknowledged05Order06Shipment update07Received

Portal anatomy

What this Provider operates every day

Fewer incomplete quote requests and consolidated Designer demand.

01Quote & availability requests02Samples requested, shipped and returned03Purchase Order acknowledgement04Lead-time and expected-arrival changes05Shipments, claims, returns and replacements06Deposit, balance and invoice readiness
Project integration

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.

Access and visibility

Trade pricing, margin and commercial terms are restricted. Client-facing views receive an authorized selling-price projection, never the Provider's confidential trade data.

01
Matchmaking profile

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
02
Automation & notifications

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
03
AI assistance

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
Exception paths
Price varianceBackorderDiscontinuedReturnCredit
Operating scorecard
Quote turnaroundPO acknowledgement timeOn-time shipmentOrder fill rateClaim rateProduct-data freshness
PW-02Future category module

Millwork & Custom Fabrication

Measurement, drawings and fabrication

1. Scope received2. Site measure3. Quote4. Work Order+5 states
Open full Provider blueprint ↓
01Scope received02Site measure03Quote04Work Order05Shop drawings06Approval gate07Fabrication08Install09Deficiency close

Portal anatomy

What this Provider operates every day

Controlled revisions, complete scope and fewer fabrication mistakes.

01Bid invitations and scope packages02Site-measure dependencies03Shop drawing and submittal queue04Material and finish approvals05Fabrication schedule and milestones06Delivery, installation and deficiencies
Project integration

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.

Access and visibility

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.

01
Matchmaking profile

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
02
Automation & notifications

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
03
AI assistance

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
Exception paths
RevisionMaterial changeSite varianceDelayDeficiency
Operating scorecard
Bid turnaroundDrawing approval cyclesRevision countMilestone adherenceDeficiency rateWarranty response
PW-03Future category module

Contractors & Specialty Trades

Discrete construction scopes

1. Scope issued2. Site review3. Quote4. Work Order+5 states
Open full Provider blueprint ↓
01Scope issued02Site review03Quote04Work Order05Readiness check06Scheduled07In progress08Inspection09Complete

Portal anatomy

What this Provider operates every day

Clearer scopes, fewer coordination gaps and faster invoicing.

01Bid and quote requests02Scope, exclusions and allowances03Site schedule and crew assignment04RFIs and submittal approvals05Inspections and milestone updates06Change Orders, deficiencies and closeout
Project integration

Construction materials remain distinct from decorating and procurement Items but reuse the Item framework. They support submittals, quantities, alternates, site delivery, installation and evidence.

Access and visibility

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.

01
Matchmaking profile

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
02
Automation & notifications

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
03
AI assistance

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
Exception paths
ClarificationSite blockedChange OrderSafety stopDeficiency
Operating scorecard
Bid turnaroundSchedule adherenceRFI response timeChange Order frequencyInspection pass rateDeficiency closure
PW-04Future category module

Photography

Creative production and usage rights

1. Brief issued2. Scope confirmed3. Scheduled4. Access confirmed+5 states
Open full Provider blueprint ↓
01Brief issued02Scope confirmed03Scheduled04Access confirmed05Shoot06Post-production07Proofs08Selection09Licensed delivery

Portal anatomy

What this Provider operates every day

Complete briefs, coordinated access and reusable rights records.

01Shoot Offers and estimate requests02Creative brief and shot-list readiness03Calendar, access and styling dependencies04Asset upload and proof delivery05Selections and revision requests06Usage rights, releases and invoice readiness
Project integration

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.

Access and visibility

Private addresses, access contacts, unpublished work and embargoed assets are disclosed only for the scheduled Job and retained according to policy.

01
Matchmaking profile

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
02
Automation & notifications

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
03
AI assistance

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
Exception paths
RescheduleAccess failedReshootRights changeEmbargo
Operating scorecard
Offer responseShoot readinessOn-time deliveryRevision cyclesAsset acceptanceRights completeness
PW-05Future category module

Measurement & Drafting

Authoritative field records

1. Output selected2. Scope confirmed3. Site visit4. Field capture+4 states
Open full Provider blueprint ↓
01Output selected02Scope confirmed03Site visit04Field capture05Draft set06Designer review07Revision08Approved reference

Portal anatomy

What this Provider operates every day

Standard requests, traceable revisions and fewer missing dimensions.

01Site-visit requests02Access and contact readiness03Measurement scope and checklists04Drawing deliverable queue05Quality review and comments06Issued versions and invoice readiness
Project integration

Measurements and drawings feed Concept, Design and Design Package. Issued documents are versioned Project deliverables and can satisfy configured Phase gates.

Access and visibility

Site contacts and property access instructions expire after the visit. Draft files remain internal until the responsible reviewer authorizes an issued version.

01
Matchmaking profile

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
02
Automation & notifications

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
03
AI assistance

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
Exception paths
Access issueField varianceMissing dimensionRevision requested
Operating scorecard
Scheduling lead timeFirst-draft turnaroundRevision cyclesQuality acceptanceOn-time issueMissing-information rate
PW-06Future category module

Receiving, Warehouse & Storage

Custody, condition and location

1. Expected item2. Appointment3. Received4. Identified+5 states
Open full Provider blueprint ↓
01Expected item02Appointment03Received04Identified05Condition captured06Location assigned07Stored08Release authorized09Outbound manifest

Portal anatomy

What this Provider operates every day

Faster receiving, documented condition and accurate storage billing.

01Expected arrivals and appointments02Search or scan by PO, tracking, barcode or Item03Quantity and condition receiving04Damage and unidentified-item resolution05Storage locations, aging and charges06Pull lists, release and delivery readiness
Project integration

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.

Access and visibility

Warehouse users see only operational Item and release data. Client contact details, Project financials and unrelated design files remain hidden unless explicitly required.

01
Matchmaking profile

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
02
Automation & notifications

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
03
AI assistance

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
Exception paths
UnidentifiedDamagedMissing partsQuantity varianceClaim
Operating scorecard
Receiving turnaroundIdentification rateCondition capture completenessDamage rateInventory accuracyStorage aging
PW-07Future category module

White-Glove Delivery

Dispatch, tracking and proof

1. Release approved2. Manifest confirmed3. Scheduled4. Crew assigned+5 states
Open full Provider blueprint ↓
01Release approved02Manifest confirmed03Scheduled04Crew assigned05Picked up06En route07Arrived08Placed09Client sign-off

Portal anatomy

What this Provider operates every day

Better manifests, fewer site surprises and immediate proof of service.

01Delivery Offers and estimates02Manifests and Item readiness03Pickup and delivery appointments04Vehicle, crew and route assignment05Day-of status and item outcomes06Proof, signature, damage and invoice readiness
Project integration

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.

Access and visibility

Exact location is shared only during the active route with explicit workforce policy. Client views receive privacy-safe status rather than unrestricted crew tracking.

01
Matchmaking profile

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
02
Automation & notifications

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
03
AI assistance

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
Exception paths
Access failedDelayDamageRefusedReturn to storage
Operating scorecard
Estimate turnaroundOn-time pickupOn-time arrivalFirst-attempt successDamage rateProof completeness
PW-08Future category module

Installation Services

Readiness, placement and punch work

1. Install plan2. Readiness check3. Team assigned4. Site protected+5 states
Open full Provider blueprint ↓
01Install plan02Readiness check03Team assigned04Site protected05Items placed06Assembly07Quality check08Punch list09Final acceptance

Portal anatomy

What this Provider operates every day

Room-level instructions, reduced downtime and defensible completion.

01Install Offers and scope02Site and Item readiness03Crew, date and room plan04Sequence and dependencies05Installed, blocked and partial outcomes06Punch list, photographs and sign-off
Project integration

Installation updates both Item state and overall Project completion. Room-level outcomes remain traceable to the responsible crew, evidence and unresolved punch work.

Access and visibility

Installers receive placement, access, safety and Item details for the assigned visit. Broader Client, budget and design-development records remain restricted.

01
Matchmaking profile

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
02
Automation & notifications

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
03
AI assistance

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
Exception paths
Item unavailableDamageMissing hardwareSite blockedAdditional work
Operating scorecard
Readiness rateCrew utilizationItems installed per visitBlocked-item ratePunch closureReturn-visit rate
PW-09Future category module

General Service Providers

Configured reusable service modules

1. Requirement2. Scope3. Quote4. Work Order+5 states
Open full Provider blueprint ↓
01Requirement02Scope03Quote04Work Order05Scheduled06Milestones07Evidence08Acceptance09Invoice

Portal anatomy

What this Provider operates every day

A flexible entry point without allowing ungoverned one-off processes.

01Offers and scoped requests02Configurable milestones and schedule03Tasks and deliverables04Location or inspection modules05Evidence and Client sign-off06Change Orders and invoicing
Project integration

General Services compose approved scheduling, Item access, milestone, evidence, location, inspection, sign-off and invoicing modules. They never create an unstructured status field.

Access and visibility

Access is generated from the selected modules and Work Package. The Provider receives the minimum Project context necessary for the configured service.

01
Matchmaking profile

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
02
Automation & notifications

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
03
AI assistance

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
Exception paths
ClarificationRescheduleBlockedChange OrderDispute
Operating scorecard
Offer responseMilestone adherenceEvidence completenessException rateInvoice cycleCategory volume

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.

  1. 01Issue linked to the Project, Item, Work Order, milestone or payment
  2. 02Evidence, timestamp and responsible parties preserved
  3. 03Urgency and Client impact classified
  4. 04Time-bound owner, Task and editable notification created
  5. 05Resolution recorded as replacement, reschedule, credit, claim, Change Order or dispute
  6. 06Outcome and performance effect reviewed with an appeal path

Workflow governance

Every new workflow must answer the same questions.

01Canonical record and owner02Entry event and eligibility03Ordered states and outcomes04Transition authority05Required fields and evidence06Automation and notifications07Exception and recovery paths08Activity and audit events09Visibility by audience10Reporting and service levels