Home improvement · shared job coordination
Plan the scope — then keep the whole job on track.
The same scope-first planning, plus a shared job checklist so workers and the customer can stay in sync: tasks have dependencies, and when a task is finished the next person would be notified in the private app while the customer sees a calm progress update instead of jargon. For contractors, project managers, and handymen.
Want the deep planning sample? See the 350 kW generator scope-first plan.
Scope first (still the foundation)
A small home addition: backyard guest-suite slab + plumbing rough-in. The plan is still built from the contract and drawings — coordination sits on top of planning, it does not replace it.
Source-of-truth order
- 1. Contract / scope of work — Backyard guest-suite slab + plumbing rough-in (agreed scope).
- 2. Issued drawings / permit set — The plan set the customer's designer/engineer provided.
- 3. Measurements / site conditions — Real pad size, depths, and access.
- 4. Specs / manuals — Fixture + material requirements.
- 5. Photos / notes — Supporting context (lowest authority).
Two views of the same job
Contractor / PM view (internal)
- • Full task list with dependencies and who owns each.
- • Change-order risk flags (internal-only wording).
- • Exclusions, scope gaps, and price/schedule impact.
- • Permit/inspection handoffs and next-trade unlocks.
Customer view (calm)
- • Plain progress: what's done, what's next.
- • Approvals to give, in simple language.
- • No alarming jargon — calm, practical updates.
- • Never the words "change order" (see §4).
Shared job checklist (mock)
Illustrative only — nothing is interactive or saved. Shows status, who owns it, the dependency, and what the customer would see.
| Task | Owner | Status | Depends on | Customer sees |
|---|---|---|---|---|
| Layout + excavation | Crew (2) | ✓ Done | — | Done |
| Underground plumbing rough-in | Plumber | ✓ Done | Excavation | Done |
| Permit / schedule inspection | Office / scheduler | ● In progress | Plumbing rough-in ✓ | We're booking the inspection |
| Rough-in inspection | AHJ inspector | ○ Waiting | Inspection scheduled | Waiting on the city inspection |
| Concrete slab pour | Concrete crew | ○ Waiting | Inspection PASS | Starts after inspection passes |
| Backfill + finish | Crew | ○ Waiting | Slab cured | Final step |
Customer-facing wording (no "change order")
"Possible change order" can make a customer worry it's about charging more. The internal view may flag Change-order risk, but the customer view uses calm, plain language:
Dependency in action (mock notifications)
- 1Plumber completes the underground work and checks the task off. [mock next-step update]
- 2Permit / scheduler would be notified in the private app to schedule the rough-in inspection. [notification preview (static)]
- 3AHJ inspection passes. [mock next-step update: inspection PASS]
- 4Concrete crew is unlocked — would be notified in the private app that they can pour. [notification preview (static)]
- 5Customer sees a calm progress update — no jargon, just what's next. [customer view (static preview)]
These are notification previews — no real alert is sent. In the private app this would notify the right person; that is later, opt-in functionality built with proper consent.
Static coordination preview only. The checklist state, notification previews, worker/customer collaboration, and sharing are illustrative — no real notifications, no accounts/sign-up, no uploads, no backend, nothing saved.
This is not engineering work. Outputs are planning aids based on user-provided contract, drawings, measurements, and qualified professional inputs. Verify all work with the contractor, engineer of record, AHJ, manufacturer instructions, and applicable requirements before real-world use.
Would this help on a real job?
We can hand-build a planning packet for one of yours — no app login, no payment here.