Illustrative demonstration · Fictional member · Synthetic project imagery · No real addresses or people
Coordination services

What Shared Plan coordinates — and what it does not

Shared Plan is the coordination layer for small multi-trade work: it holds the plan, names the parties and keeps the record. It is not a general contractor page and not an anonymous lead marketplace.

What coordination covers

The coordination layer, package by package

Discovery & scoping

A structured assessment turns a goal into a readable scope — what the work is, where it stops, and where regulated work begins.

Work-package definition

The scope is broken into packages, each with exactly one accountable owner. A participant can own several packages; a package is never owned by “the team”.

Sequencing & dependencies

The packages are put in an order everyone works from, with the dependencies made explicit — so trades do not collide.

Per-job participant disclosure

Every business expected on site is named before work begins. Naming a party is disclosure, not the Collective pre-verifying them.

Readable budgets & allowances

Budgets, allowances and change orders carry a version and name the receiving party for each payment. A TBD never silently becomes a charge.

Milestones & approvals

You approve the versioned plan before anything is scheduled, and every later change is recorded — what changed, who approved it and when.

Completion & sign-off

A deficiency review and a readable closeout record end the project with a customer sign-off you can read.

Boundaries

What we coordinate — and what we don’t

We coordinate

  • Coordinating small multi-trade projects across several workstreams
  • Naming and disclosing the parties expected on each job
  • Holding the plan, the budget versions and the decision record
  • Running deficiency review and closeout

We don’t

  • Authorizing regulated trades — Shared Plan never does this
  • Architecture, engineering or permit/code certification
  • Major structural renovation or emergency restoration
  • A “vetted network”, fixed savings or a guaranteed completion date
One shared plan, every party named

One shared plan, every party named

The point of the coordination layer is that accountability stays visible: you can always see who the contracting party is, who invoices and receives each payment, which named businesses are expected on site, and what changed.

Those distinctions are never hidden behind “our vetted network.” If a piece of work is outside supported scope, that is explained before any alternative is proposed.

Start a project brief

Put every moving part on one shared plan.

Share the goal and constraints. Shared Plan confirms fit, then draws a plan with named parties, sequence and budget — for you to approve before anything is scheduled.

Start a project brief