How to manage multiple jobs without losing track

Twenty live jobs is not twenty times harder than one. It is harder than that, because most of them are waiting on something.

Last updated: September 2026

Jobs go missing while they are waiting

Work almost never disappears while you are doing it. It disappears in the gaps: the job that needs a part, the quote the customer has not answered, the visit that was finished last Tuesday and never invoiced, the tenant who has not rung back about access.

Those jobs have one thing in common. Nothing about them is scheduled, so nothing brings them back to your attention. They sit in your memory, and your memory is already running the job you are standing in.

The fix is not working harder or being more organised by temperament. It is making the waiting visible, so the thing you have forgotten is on a list rather than in your head.

The four states that cause the trouble

Every lost job in a small trades business is in one of four states:

  • Waiting on a part. Genuinely paused, and invisible unless the date it is due is written down somewhere you look.
  • Waiting on the customer. A quote sent, an access arrangement, a decision about an extra. Nothing moves until they answer, and nobody is chasing.
  • Done but not written up. The work happened. The photographs are on someone’s phone. The customer thinks it is finished and you cannot invoice it.
  • Done, written up, not invoiced. The most expensive state of the four, and the easiest to sit in for a month.

Notice that only one of those four is about doing the work. The rest are admin states, which is why a busier diary makes the problem worse rather than better.

One list, visible to everyone

The single change that makes the biggest difference is a shared list of live jobs with a status on each one, replacing the notepad, the group chat and the three text threads.

It does not have to be clever. It has to be the only place. The moment there are two lists, the true state of the business is in neither of them, and the person answering the phone is guessing.

What makes a status useful is that it is a small, fixed set of words everyone uses the same way. “In progress” written by four people means four different things. A short list of plain states does not have that problem.

Where Dispatch fits

In Dispatch every job carries one of five statuses: New, Scheduled, Awaiting parts, Completed or Cancelled. Five, deliberately, because a longer list gets used inconsistently within a fortnight.

Awaiting parts takes a date, the date the part is due back, and a job whose date has passed surfaces on the dashboard instead of waiting to be remembered. The dashboard also shows today’s visits, tomorrow’s, jobs needing attention, jobs ready to invoice, outstanding invoices and quotes the customer has not answered, which is the four problem states above turned into six numbers you can look at over a coffee.

The same jobs can be read as a list, as a drag-and-drop board by status, or on a map with filters by status and assignee, so the office and the van can each use the view that suits them. Cancelling a job requires a written reason, which sounds like bureaucracy until the first time someone asks why a job never happened.

The customer side stays attached to the job too: messages about the job, with photographs, sit on the job record rather than in a personal phone, and the thread closes itself when the job is completed.

A ten-minute routine that does most of the work

A list only works if someone looks at it. Two short habits are enough for most small businesses:

  1. Ten minutes in the morning. Read the day’s visits, then read the waiting jobs. Chase one thing from each waiting category: one part, one unanswered quote, one unwritten report, one uninvoiced job.
  2. Five minutes at the end of the day. Every job you touched gets its status and its write-up before the van is unloaded. Not tomorrow, because tomorrow has its own jobs in it.

That is fifteen minutes a day against the several hours a month that reconstruction costs, and reconstruction is the expensive part: the phone call to ask what was agreed, the second visit for a part you already had, the invoice raised six weeks late and queried because nobody remembers.

What to do about a backlog you already have

If you are starting from a genuine mess, do not migrate the mess. Work through the last three months of jobs once, mark everything that is truly finished as finished, invoice anything that should have been invoiced, and write off the two or three that are not worth the argument.

What remains is your real live list, and it is usually smaller than the anxiety suggested. From that point the routine above keeps it small, and the next useful step is deciding how the week gets booked so that jobs arrive on the list already scheduled rather than as a note to book them later.

Questions

Keeping track of jobs: FAQ

Why do jobs get forgotten when the business is busy?

Because forgotten jobs are usually waiting jobs. Nothing is booked for them, so nothing brings them back into view, and a busier diary crowds them further out of mind.

How many job statuses should a small business use?

As few as everyone can use the same way. Dispatch uses five: New, Scheduled, Awaiting parts, Completed and Cancelled. Long status lists get applied inconsistently and stop meaning anything.

How do I stop jobs sitting uninvoiced?

Make finished-but-unbilled work visible rather than remembered. A dashboard tile for jobs ready to invoice turns it into a number you can see instead of a nagging feeling.

Is a whiteboard and a group chat good enough?

It works until two people update different copies of the truth. The problem is not the whiteboard, it is having two lists, because then the real state of the business is in neither.

What about jobs waiting on parts?

Park them with the date the part is due. In Dispatch an overdue awaiting-parts job surfaces on the dashboard, so the supplier who quietly missed a delivery gets chased.

Put the waiting jobs where you can see them

Five statuses, a dashboard that counts the jobs waiting on you, and one record per job that everyone can read.