The technician has finished the first visit, but the repair needs a part. The supplier's email says it should arrive next week. By Friday, the customer is asking for an update and the office is searching through messages to find out who ordered it.
Consider a small appliance repair business serving Orlando. This is a fictional example, but the coordination problem is straightforward: a job can disappear from the day's schedule while it still needs attention. Marking it "waiting" leaves too much unexplained.
Give each paused job a reason, a person responsible for the next check and a date for that check. You can start in your existing job system or a shared spreadsheet. The useful change is agreeing on what happens while the repair is on hold.
Record what the job is waiting for
Keep the original job reference when a repair needs a return visit. Opening a second, unrelated record makes it harder to connect the part order with the customer's history. If your system requires a separate visit record, link it to the original job.
A small waiting list needs enough information for someone else to act. Include the job reference, the specific blocker, the person following up, the next action and its due date. Add a link to the relevant order or message, plus the date and substance of the last customer update. Keep contact details in the existing customer record where possible.
For example, a fictional Job 218 might say: "Replacement component ordered; supplier has not confirmed dispatch. Jordan to request an update Tuesday morning. Customer told we will check again Tuesday." That gives the office a task even if the supplier has nothing new to report.
If you already use Google Sheets, its dropdown feature lets you define a short set of status choices. Use terms your team can distinguish, such as "supplier confirmation needed," "part in transit" and "ready to arrange visit." Google documents that values outside the list can be rejected or allowed with a warning. A consistent label helps with sorting; it doesn't verify that someone has actually ordered the part.
Separate a supplier estimate from a customer commitment
A projected delivery date isn't a confirmed repair appointment. Store the supplier's expected date separately from your next follow-up date. If no delivery estimate exists, record that plainly and still choose a time to check.
When the part arrives, have the responsible person confirm that it matches the job and that the remaining work can be scheduled. Then agree on the return visit with the customer. Don't let an arrival notification automatically become a booking.
Customer updates can be brief. Say what is known, what remains uncertain and when you will contact them again. If you've promised an update on Tuesday, send it even when the answer is that the supplier hasn't confirmed dispatch. Avoid copying a supplier's tentative date into a firm promise.
Check the waiting list during the working day
Choose a regular review time and a backup person for absences. Review actions due today or overdue, but also look for rows with no owner or no next-check date. Those missing fields can hide a stalled job from an otherwise tidy filtered list.
On a computer, Google Sheets supports saved filter views, so a coordinator can inspect one subset without changing someone else's view. You could keep views for work awaiting supplier confirmation and work ready to schedule. Ordinary shared filters behave differently, so agree on which one the team uses. Start with a manual daily review; a saved view doesn't send a reminder by itself.
For an individual supplier email, Gmail's Snooze can temporarily remove the message from the inbox and bring it back at a chosen time. Treat that as a personal prompt. If a colleague needs to cover the job, the next action must also be visible in the shared work record.
Try the routine before adding automation
Set up a few fictional jobs first: one with an uncertain delivery date, one with a part received and one whose usual coordinator is away. Ask the backup person to identify what needs doing next. Check the view on the devices the team actually uses before relying on it.
Keep the list internal and limit access to people who need it. A filtered view isn't a privacy boundary. Don't share the whole list with a customer or add payment details and household access codes just because there is room in a notes column.
If your current service software already handles parts holds and follow-up tasks, use that workflow instead of maintaining a second list. The spreadsheet approach suits a small, manually reviewed queue; it becomes awkward when parts serve several jobs, multiple people change records at once or coverage depends on reliable reminders. Those are reasons to assess the existing system's capabilities before commissioning an integration. This first step uses tools you already have, without buying an add-on.
The job handoff example shows a related way to keep instructions connected to a service visit. If paused jobs are difficult to pick up again, bring the steps between your first visit and the return appointment. We can discuss where a clearer record would help.