To know where every job stands without calling your crew, you need three things: one list of active jobs that everyone updates, clear rules for when the field and the office update it, and a short weekly review where you look only at the jobs that need attention. With those in place, the check-in calls stop, because the answer is already written down.
This matters most right after you hand off decisions. If the only way to see results is to ask, you’ll keep asking, and the person you delegated to will feel watched. This guide shows how to build the list, set the update rules and run a short weekly review.
Why owners keep checking in
Most check-in calls aren’t about control. They’re about not knowing. When the status of a job lives in the crew lead’s head, the office’s inbox and a text thread, the only way to find out is to call. So the owner calls the crew, the office calls the crew, and the crew spends part of the day answering instead of working.
The same thing happens in reverse. A crew hits a problem at 9 a.m. (a backordered tile, a locked gate, a customer who changed their mind) and it reaches the owner at 4 p.m., because there was no obvious place to put it. Why technicians keep calling the office covers the field side of the same problem.
Step 1: one list of active jobs
Every job that’s been approved and isn’t paid yet goes on one list. Not one per person, not one in the office and another on the truck. One. It can be a shared spreadsheet, a whiteboard the whole team can see, or job software, as long as office and field look at the same thing.
Each job gets six columns:
| Column | What goes in it |
|---|---|
| Job | Customer and job name |
| Stage | Where it is (stages below) |
| Owner | One person responsible for moving it to the next stage |
| Next action | The very next thing that has to happen, in a few words |
| By when | A date for that next action |
| Blocker or decision | Anything stopping it, or a decision someone has to make |
Use the same stages for every job so the list can be sorted:
- Approved: the customer signed, nothing scheduled yet
- Ready to schedule: materials ordered, scope clear, permits handled
- Scheduled: on the calendar with a crew
- In progress: work has started
- Waiting: stopped for a reason (customer, material, inspection, sub)
- Closeout: work done, punch list and final paperwork
- Invoiced: waiting for payment
The rule that makes it work: every job always has an owner and a next action with a date. A job with an empty “Next action” is a job nobody’s moving.
Step 2: decide when the list gets updated
A list that’s updated “when people remember” is out of date by Tuesday. Agree on update triggers: specific moments when someone updates the job.
The field updates when:
- the crew arrives and starts work
- a blocker appears: something missing, wrong or unsafe
- the customer asks for a change
- the day’s work ends: what got done, what’s next
- the job is finished
The office updates when:
- a job is scheduled or moved
- materials are ordered or delivered
- the customer approves something or asks a question
- an invoice goes out or a payment comes in
Write the triggers on one page and walk the team through them. The goal is a habit: something happens on the job, the job record gets updated. If it isn’t on the job, it didn’t happen.
Example: a blocker that never reached the owner
A bathroom remodel. The details are made up to show the method.
- 9:05 a.m. The crew lead opens the boxes: the tile is the wrong color. They add a blocker to the job: “Wrong tile delivered, correct tile due Wednesday.” The job stays In progress, and they move on to the vanity and plumbing work that doesn’t need the tile.
- 9:20 a.m. The office coordinator sees the blocker, calls the supplier, confirms the new delivery date and lets the customer know.
- 9:40 a.m. Moving the tile work by two days is inside the coordinator’s rescheduling limits, so they update the schedule and the next action: “Tile install Thursday, crew 1.”
- Friday. The owner sees it in the weekly review: one blocker, solved, with a note on who handled it and why the job moved.
No calls to the owner. The job lost no time it didn’t have to, and the owner still knows exactly what happened.
Step 3: a weekly review that looks only at exceptions
You don’t need to read every job every week. You need to see the ones that are stuck, late or waiting on you. Set a fixed time, say Friday at 2 p.m., and go through the list in this order:
- Jobs with no owner or no next action. Give each one an owner and a next step before you move on.
- Next actions past their date. Ask the owner of the job what’s in the way.
- Blockers older than two days. Decide who clears each one, and by when.
- Decisions waiting on you. Make them now, or set a date.
- Next week’s starts. Check every job scheduled to start next week is really ready: materials, approved scope, permits, crew, customer confirmed.
Everything that comes out of the review gets an owner and a date, written on the list. Because you only look at exceptions, the review stays short even as the number of jobs grows.
What not to do in the review: go through healthy jobs one by one, fix problems on the spot that someone else owns, or turn it into a meeting about everything. It’s a check, not a status meeting.
What the weekly list looks like
Example rows, made up to show the method. The two rows in bold are what the owner looks at.
| Job | Stage | Owner | Next action | By when | Blocker or decision |
|---|---|---|---|---|---|
| Oak Ave bathroom | In progress | Crew lead 1 | Tile install | Thu | Wrong tile, correct delivery Wed (solved) |
| Pine St kitchen | Scheduled | Coordinator | Confirm cabinet delivery | Mon | None |
| Maple Ct deck | Approved | (none) | (none) | (none) | Nobody owns it |
| Henderson basement | Waiting | Coordinator | Inspection booked | Tue | Waiting on city inspector |
| Lake Rd addition | Ready to schedule | Estimator | Owner to approve the sub’s price | Last Fri | Decision overdue: waiting on the owner |
| Cedar Ln repaint | Invoiced | Coordinator | Payment reminder | Wed | None |
Two exceptions out of six jobs. One needs an owner, one needs the owner. The other four don’t need a phone call at all.
Make it stick
- Answer status questions from the list. When someone calls you to ask about a job, open the list together. If the answer isn’t there, that’s the gap to fix.
- Stop asking for updates by phone. If you need to know, look at the list first. If it’s out of date, ask for the update on the list, not by phone.
- Keep the stages and columns the same. Changing them every week makes the list impossible to scan.
- Have the coordinator glance at the list daily. A short look each morning catches blockers before they wait a week for your review.
Your next action
- Put every active job on one list with the six columns.
- Fill in an owner and a next action with a date for every job.
- Write the update triggers for the field and the office on one page and walk the team through them.
- Run your first weekly review this Friday, exceptions only.
Free tools: the Weekly Job Review spreadsheet flags the jobs that need you this week, and the daily job report (PDF) gives crews the same end-of-day update on one page.
What to review each week:
- How many jobs had no current status, owner or next action
- How many times someone still called to ask for a status that should have been on the list
Both numbers should fall over the first month. The next lesson, Build a 30-Day Delegation Plan, puts everything together: one responsibility, handed over step by step.
Where MotionOps helps
In MotionOps, what the crew records in the field shows up for the office in real time:
- Job Checklists: job-specific checklists, with completed tasks tracked in real time.
- Real-time Overview: see photos, notes, signatures and timesheets as each job progresses.
- Private Field Notes: internal notes from everyone who worked on the same job, in one place.
- Unscheduled Jobs: every open job without a future appointment, so you can review them and add them to the schedule.
- Push & Email Notifications: staff and clients get notified about important appointment and work order updates.
More on the office and field side: office–field coordination for multi-crew contractors and tracking jobs you haven’t scheduled yet. See plans and pricing, or book a MotionOps demo.
Contractor Scaler Hub: Get Out of the Owner Bottleneck, lesson 4 of 5
- Previous lesson: Delegation Matrix for Contractors: How to Delegate Decisions, Not Just Tasks
- Next lesson: 30-Day Delegation Plan: How to Hand Off One Responsibility Without Dropping It
- Course toolkit: Get Out of the Owner Bottleneck toolkit (PDF)
- All courses and lessons: Contractor Scaler Hub
