model

How to Coordinate a Remodeling Jobsite: Crew, Subs, Photos, and Schedule

The subcontract tells a sub what they owe. The jobsite tells everyone what is happening now. Who goes on a job, what to share and what to keep private, how to get dates agreed, and what to do when one slips.

Direct answer: The subcontract tells a sub what they owe. The jobsite tells everyone what is happening now. Put each person on the job when their part needs coordinating, share what they need to do the work, and keep prices, the contract, the customer's contact details and your private notes off it. Ask for dates, and treat a date as set only once both sides have agreed to it. When something goes wrong, call if it's urgent, then post the facts. When an earlier step slips, turn the dates after it back into proposals until it's fixed. A problem found on site is a record first; it becomes a change order only if it changes the scope, price or time.

The assumptions

This model assumes

  • A residential remodeler running jobs with a small crew and a handful of trade subs
  • The sub's scope, price and payment terms live in the subcontract; paying subs is outside this guide
  • The owner's practice: no date counts until both sides agree, subs added when their part needs coordinating, photos private by default
  • The worked week is an illustration, not trade durations or inspection waits
  • Recordkeeping guidance, not legal advice; follow your contract's notice requirements

The model, step by step

1Where it sits

A job runs on several records. Each one is for something different.

The jobsite against the records it gets confused with
RecordWhat it is for
The subcontract, written quote and purchase orderWhat the sub has agreed to do, for what price, on what terms. The formal scope lives here.
The jobsiteWhat everyone on the job needs to coordinate the work: who's on it, the dates, updates, shared photos.
Your lead notesThe business's own record. Private.
The customer portalWhat the homeowner sees and signs.
A change orderA signed change to scope, price or time.
The sub's billWhat you owe the sub.
Group textsFast, but scattered. The record is split across phones and people instead of living with the job.

The jobsite is what everyone on the job sees. The lead is what only the business sees.

Michael C. Stone, a builder and remodeler with more than six decades in the industry and the author of Markup & Profit: A Contractor's Guide, Revisited, puts the sub's obligations in the subcontract: show up on the agreed date and time, follow your work rules, make no side agreements with your client, and handle changes the agreed way, plus a job-specific part saying exactly what the sub is to do. The jobsite doesn't replace that agreement. It is the field history behind it.

2What the job shares

Sorted from always shared to never shared.

What the jobsite shares, and what it never does
InformationThis guide's practice
Job name and addressAlways: everyone on the job sees it
The customer's nameAlways: Clamp shows it to subs
Who else is on the jobAlways
Agreed datesAlways: everyone affected sees the same date
The sub's formal scope and specificationsAlways settled, but in the subcontract, not on the jobsite
Access: gate, lockbox, parking, working hours, rules for an occupied houseUsually, posted in the thread
Photos of the area a trade will work inUsually, chosen for that trade
Site conditions and inspection results that change the sequenceUsually
Delivery and install status the next trade depends onUsually
Plans or selection sheets for one tradeOnly when it helps, and outside Clamp, since Jobsites doesn't share documents
A photo of a hidden conditionWhen it explains a problem
Prices, estimates, the contract, invoices, change ordersNever
The customer's phone or emailNever
Your private lead notesNever, unless you deliberately post one to the jobsite
Sales appointments and follow-upsNever
Anyone else's hours or milesNever

Share what someone needs to do the work. Keep price, sales history, private notes, the customer's contact details and unrelated records off the jobsite.

3How to run it, step by step

The lines below are this guide's examples to adapt, not a script.

Adding a sub"I'm adding you to the Oak Street job so you can see the schedule, jobsite updates and the photos we share for your work. Your scope and price stay in our subcontract. Use the jobsite for dates, field updates and anything we need to coordinate."

That sentence sets the line between the coordination record and the contract record. Add each sub when their part needs coordinating, not every sub on day one. Remove them when their work is done. Their posts and photos stay on the job.

The first post"Oak Street starts Monday. Use the side door, and keep the driveway clear before 8 AM. Plumbing and electrical rough-in are first. Post here if anything on site affects another trade or the schedule."
Asking for dates"Can you do the electrical rough-in on Thursday, October 15? Please confirm or suggest another day, so I can book the inspection and the work after you."

While the item shows Waiting on them, don't tell anyone it's scheduled. Ask once the work is real enough to plan, and before later trades depend on the date. Clamp's email follow-up two days before an unconfirmed date is a safety net. It shouldn't be the first time you chase.

Booking what you arrange yourselfAn inspection, a delivery, or a day for your own crew isn't confirmed through Clamp. You arrange it by phone or online, then add it. Clamp saves an item for yourself, a supplier or nobody as Confirmed straight away, so add it only once it's actually booked.
Moving a date"Thursday no longer works because the work before yours moved. Can you do Friday, October 16 instead? Please confirm or suggest another day."

Propose the new date and get it agreed. Don't quietly change it.

A problem found on site"We found damaged framing behind the wall. Stop at the original scope, and post a photo and what you found. No changed work until we decide whether a change order is required and, if it is, it is signed."

A field problem is a record first. If it changes the scope, price or time, it goes through a change order before anyone does the changed work.

Closing out a trade"Tile is done. Post anything still open before you leave. If your part is complete, I'll mark it done on the schedule."
The Oak Street Bathroom job screen: demolition on Monday, Oct 12 Confirmed, electrical rough-in on Thursday, Oct 15 Waiting on them for Rosa of Diaz Electric, the people on the job, shared photos, and the first jobsite post

Your job screen

The sub's view of the same job: Demo Remodeling asked you for Thu, Oct 15, electrical rough-in, with Confirm and Suggest another day, and Propose your dates below

What the sub sees

The ask from step 3 in Clamp: the job screen shows the electrical rough-in Waiting on them, and the sub sees it with Confirm and Suggest another day. Demo data.

The hard case: a sub confirms, then doesn't showThe electrician confirmed Thursday and doesn't arrive. Call first, because it's urgent. Then post the facts: "Diaz Electric didn't arrive for today's confirmed rough-in. I spoke with Marco at 8:20 AM. He proposed Friday, which is waiting on confirmation. The inspection and close-up stay unconfirmed until rough-in is settled." Once Friday is agreed: "Electrical rough-in moved from Thursday to Friday by agreement. The inspection gets rebooked for the next open day. Close-up and tile wait for it to pass."

That post does more than an angry one would. It records what was confirmed, what happened, who was told, and what it moved. It doesn't decide who owes whom; the subcontract and the facts do that.

4The worked schedule

Illustration only. These dates show the sequence and the communication, not normal trade durations or inspection waits.

One week, as planned (illustration)
DayItemWhoStatus
Mon, Oct 12DemolitionCrewConfirmed
Tue, Oct 13Plumbing rough-inPlumberAsked, then confirmed
Tue, Oct 13Electrical rough-inElectricianAsked, then confirmed
Wed, Oct 14Rough-in inspectionNobody (you booked it with the building department)Confirmed, added once booked
Thu, Oct 15Close-upCrewConfirmed, if the inspection passes
Fri, Oct 16TileTile subProposed, waiting on the inspection and close-up

Wednesday's inspection fails. Don't just push every date a day. Post the failed inspection and what has to be corrected, and add the corrective work to the schedule. Book a reinspection, and add it once it's booked. Move close-up back to proposed, and tell the tile sub their date is no longer agreed. Agree tile again only once the inspection passes and close-up is really ready.

After the failed inspection (illustration)
DayItemStatus
Thu, Oct 15CorrectionsConfirmed
Fri, Oct 16ReinspectionAdded once the inspection is actually booked
Mon, Oct 19Close-upProposed until the reinspection passes
Tue, Oct 20TileProposed until close-up is agreed
A failed step doesn't just push the calendar. It turns the dates after it from commitments back into proposals until it's fixed. Clamp doesn't link schedule items to each other, so this is the guide's rule to follow by hand.
5The rule that protects you

No date counts until both sides have agreed to it in writing.

A date you set and a date someone agreed to look the same on a calendar. They aren't the same. Clamp keeps them apart: an unagreed date stays in Waiting on them or Needs your OK, and becomes Confirmed once the side that still needs to agree accepts it. Something you arrange yourself, like an inspection or a delivery, goes on the schedule only once it's booked. Book inspections and the trades that follow against agreed dates, and treat everything else as a proposal.

This is the owner's practice. It doesn't replace the subcontract: if the agreement says how dates are set or changed, follow it.

6The policy decisions

Decide these before the first sub joins a job.

Jobsite policy, and this guide's practice
DecisionOptionsThis guide's practice
When a sub goes on the jobEvery sub from day one; each when their part needs coordinatingEach when their part needs coordinating, and off when it's done. Their posts and photos stay.
PhotosShare most job photos; private, share what's neededPrivate by default. Share the photos of the area each trade works in.
How far ahead to ask for datesA fixed number of days; when the work is real enough to planNo set number. Ask once the work is real enough to plan, before later trades depend on it. Trade availability, materials and inspections vary too much for one number.
Chasing an unconfirmed dateThe app's email two days before; when it has to become a commitmentWhen the date has to become a commitment for what comes after it. The email is a safety net.
Texts and callsEverything in the thread; call or text, then summarizeUrgent or private things can start by phone or text. Anything that affects the job, the schedule, a site condition or another trade gets a short summary in the thread.
What subs postEverything in the thread; routine in the thread, urgent by phoneIn the thread: done, delayed, a problem or hidden condition, short on materials, a date change. Phone first for safety, emergencies, or anything that stops work, then a summary in the thread.
7Where it goes next

Hours, miles and receipts are logged in Workflow; see time on site and the mileage log. A change in scope, price or time becomes a change order, signed before the changed work. What you owe a sub is handled under the subcontract and the bills process: quotes, purchase orders, bills and payment. See How to Track What a Job Costs Before You Pay It. The posts and photos remain part of the job record after a sub is removed.

A dated, shared jobsite record can help later, because it keeps what was known, proposed, agreed and changed, and when people were told. Write it the way you'd want it read in a dispute: promptly, plainly and factually, without blame. This is the owner's practice. The jobsite thread isn't a daily log, and the record doesn't decide a dispute.

This is recordkeeping guidance, not legal advice: follow the notice requirements in your contract, and have your subcontract reviewed for your state.

8Mistakes

What goes wrong coordinating crew and subs, and what to do instead.

The usual mistakes
MistakeWhat to do instead
Treating a proposed date as scheduledCall it scheduled only once both sides have agreed.
Adding an inspection or delivery before it's bookedAdd it once it's booked; Clamp shows it as Confirmed as soon as it's saved.
Putting every sub on every job from day oneAdd each sub when their part needs coordinating.
Writing a sub's scope only in the threadKeep the scope and specifications in the subcontract or purchase order; use the thread to coordinate.
Sharing every job photoKeep photos private until someone needs them.
Moving a date without the affected person's OKPropose the new date and get it agreed.
Letting a no-show disappear into phone callsCall right away, then post what happened and the new proposal.
Arguing or blaming in the threadPost facts, dates, what it affects and the next step.
Treating a field note as a go-ahead for extra workStop at the original scope; no changed work without a signed change order when the scope, price or time changes.
Waiting for the two-days-before email to chaseFollow up when later trades need the date to be firm.
Giving subs the customer's phone or email to work it out directlyKeep the customer's contact details private.
Posting a safety problem and waiting for someone to read itCall the people affected now, then post what happened.
Expecting the schedule to move later items for youWhen an earlier step fails, move the later items back to proposed by hand.
Settling payment in a jobsite postHandle price, bills and payment under the subcontract and the bills process.

What it means

What this saysKeep the contract in the subcontract and the coordination on the jobsite. Share what each person needs, nothing about money or the customer's contact details. A date counts once both sides have agreed to it, and when an earlier step fails, the dates after it go back to proposals.
No date counts until both sides have agreed to it in writing.

Jobsites in Clamp

Jobsites is a window onto your jobs. On Teams, the owner or an admin adds crew to a job and invites subs by email. A sub joins free. They see the job's name, address and customer name, the people on it, its schedule, shared photos and the shared thread, and never your prices, documents, customer contact details or private notes. Photos stay private until you share them, and your lead notes reach the jobsite only when you choose Also post to jobsite. The shared schedule holds installs, deliveries, inspections and work days. An item for a sub or teammate starts as Waiting on them; they can confirm it or suggest another day, and a suggested date comes back to you as Proposed, for you to confirm or suggest back. A sub can also propose their own dates. Jobsites › Schedule shows every job's dates and flags clashes, and requests and follow-ups go out by email with one-tap Confirm links. Clamp doesn't pay subs, track their insurance or lien waivers, or link schedule items to each other.

Score your Operations system in the contractor business self-assessment, and see how to write and price a change order for what a field problem becomes when the contract changes.

Related

Sources & provenance

  1. Markup & Profit: A Contractor's Guide, Revisited Michael C. Stone (book)
  2. Estimating Construction Profitably Michael C. Stone (book)
  3. How to Write and Price a Change Order Clamp Research
Changes: Oct 5, 2026: Initial publication.; Oct 6, 2026: Linked the new core guides.