A construction workflow is the path every job takes from the first call to the final payment: the stages, who owns each one, what gets recorded and how you know a stage is done. A job can lose more time between stages than in the work itself, when one person thinks the next step is someone else’s.
The fastest way to see your own workflow is to map one real job you finished recently. This guide shows the stages to use, how to trace a job with real dates, a worked example, and the four problems to look for once it’s on paper.
Why map one job before you fix anything
Ask five people in your business how a job moves from request to payment and you’ll get five slightly different answers. The estimator thinks the office schedules approved jobs. The office thinks the estimator sends the materials list first. The crew lead thinks the office invoices when the crew leaves. Everyone is doing their part, and the job still sits.
A map of one real job replaces opinions with dates. You see exactly where the job waited, for how long and why. That tells you which handoff to fix first, instead of trying to fix “communication” in general.
The stages of a job, from request to payment
Use these nine stages as a starting point. Rename them to match your trade, but keep them in order.
| Stage | Starts when | Done when |
|---|---|---|
| 1. Request | A customer calls, emails or fills in a form | Someone has replied and booked a visit, or said no |
| 2. Site visit | The visit is booked | Measurements, photos and the customer’s goals are written down |
| 3. Proposal | The site visit is done | The proposal is sent |
| 4. Approval | The proposal is sent | The customer signs and, if you take one, the deposit is paid |
| 5. Readiness | The job is approved | Materials are ordered, permits are handled, a crew and start date are confirmed |
| 6. Work | The crew starts | The work in the approved scope is finished |
| 7. Closeout | The work is finished | Punch items, photos, time and costs, and every change are recorded |
| 8. Invoice | Closeout is done | The invoice is sent |
| 9. Payment | The invoice is sent | The money is in the bank |
Change orders run alongside stage 6 and loop back through pricing and approval. Keep them on the map as a side loop rather than a separate stage.
Look at the “Done when” column. Every stage needs one. A stage without a clear finish line is a stage nobody knows when to hand off.
How to map one real job
- Pick one job you finished in the last month or two. A typical one, not your worst disaster. You want to see your normal workflow.
- Collect the dates. Go through emails, texts, the proposal, the schedule, timesheets and the invoice. Write down when each stage started and ended.
- Write the owner for each stage. Who actually did it on this job, not who’s supposed to. If the honest answer is “me,” “whoever had time” or “nobody, it just happened,” write that.
- Write where the information lived. The proposal in email, the schedule on a whiteboard, the materials list on the estimator’s laptop.
- Mark every wait. Any gap between one stage ending and the next starting. Ask what the job was waiting for.
Do it with the people involved if you can. A 30-minute conversation with the estimator, the office and the crew lead over one job’s timeline shows more than a month of guessing.
Example: the approved job that waited nine days
A deck replacement for a three-crew contractor. The dates and details are made up to show the method.
| Stage | Dates | Who did it | Where it lived | Waited for |
|---|---|---|---|---|
| Request | Mar 3 | Owner (on their cell) | Text message | - |
| Site visit | Mar 6 | Estimator | Estimator’s notes and photos | 3 days for a visit slot |
| Proposal | Mar 10 | Estimator | - | |
| Approval | Mar 12 | Customer signed, deposit paid | Email + payment app | - |
| Readiness | Mar 12 → Mar 21 | Unclear | Materials list on estimator’s laptop | 9 days: estimator assumed the office would schedule; office was waiting for the materials list |
| Work | Mar 24–28 | Crew 2 | Whiteboard + crew group text | 3 days for the crew’s next opening |
| Closeout | Mar 28 | Crew lead | Photos in the crew lead’s phone | - |
| Invoice | Apr 4 | Office | Accounting software | 7 days: waiting for the crew’s timesheet and the receipt for extra screws and boards |
| Payment | Apr 18 | Customer | Bank | 14 days, inside the payment terms |
The work took five days. The job took six and a half weeks. Two of the waits had no owner:
- Readiness: nobody owned it. The estimator and the office each thought the other was moving.
- Invoice: it waited on information from the field that nobody had asked for by a set time.
The fix wasn’t a new tool or a new hire. It was two sentences:
- Readiness is owned by the office coordinator. Done when materials are ordered and the start date is confirmed with the customer, within two working days of the signature. The estimator sends the materials list the same day the proposal is signed.
- Closeout is owned by the crew lead. Done when timesheets, photos and every material receipt are in, on the last day of the job.
The four problems to look for
Once your map is on paper, go through it stage by stage and mark these:
| Problem | How it shows up on the map | What fixes it |
|---|---|---|
| No owner | “Unclear,” “whoever,” or the owner’s name on routine work | One named role per stage |
| No finish line | Nobody can say when the stage was done, so nobody knows when to hand off | A “Done when” that can be checked |
| Information typed twice | The same details copied from email to whiteboard to invoice | One place where the job lives |
| Waiting with no date | A gap where the job “was waiting on something” | A time limit on the handoff: “within two working days” |
Count them. The stage with the most marks, or the longest wait, is where you start. Approved work but no schedule goes deeper into the readiness gap.
Write your workflow on one page
Turn what you learned into a one-page map everyone can see. For each stage, write six things:
| Stage | What comes in | Who owns it | Record kept | Done when | Hands off to |
|---|---|---|---|---|---|
| Approval | Sent proposal | Estimator | Signed proposal, deposit receipt | Signed + deposit paid | Office coordinator, same day |
| Readiness | Signed proposal + materials list | Office coordinator | Purchase order, schedule entry | Materials ordered, start date confirmed with the customer, within 2 working days | Crew lead, 2 days before start |
| Closeout | Finished work | Crew lead | Photos, timesheets, receipts, punch items | All in on the last day of the job | Office coordinator for invoicing |
These rows are examples. Write your own. Start with the stages where your map showed a problem; the rest can wait. Put the page where both the office and the crews can see it, and walk through it in your next team meeting.
- Keep it to one page. If a stage needs more detail, that belongs in a checklist for that stage, like a job handoff checklist for readiness. The map is for seeing who owns what and where the job waits.
- One role per stage, not a department and not “everyone”: the person who has the information and the time to move the job forward. If the honest answer is the owner on a routine stage, that’s a stage to hand off. The owner bottleneck guide covers how to find those.
Your next action
- Pick one job you finished in the last month or two.
- Trace it through the nine stages with real dates, owners and where the information lived.
- Mark every stage with no owner, no finish line, double entry or a wait with no date.
- Write an owner and a “Done when” for the two worst stages, and share them with the team.
Free templates: an estimate, a change order and an invoice for the stages on your map are in the contractor templates library.
What to review:
- How many stages have no clear owner or no finish line
- The days between signature and start, and between finished work and the invoice. Map another job next month and compare.
Next lesson: Fix the office–field handoffs, where job information has to cross from the office to the crew.
Where MotionOps helps
In MotionOps, every stage lives on the same job record, so nothing gets typed twice:
- Online & In-person Approvals: send proposals for remote approval, or take a signed approval in person.
- Deposit Payments: collect a deposit before work begins; it’s applied to the final invoice automatically.
- Unscheduled Jobs: every open job without a future appointment in one view, so approved work doesn’t sit.
- Close Work Order: close the job once it’s really done, after checking that the full approved amount is invoiced and the timesheets, expenses and approvals are attached.
- Proposal History: the job’s full record, from the first proposal to every change order and update.
See plans and pricing, or book a MotionOps demo.
Contractor Scaler Hub: Build a Job Workflow From Request to Payment, lesson 1 of 5
- Next lesson: Office–Field Coordination: A Practical Workflow for Multi-Crew Contractors
- Course toolkit: Build a Job Workflow From Request to Payment toolkit (PDF)
- All courses and lessons: Contractor Scaler Hub
