A simple work queue for a small service team: see every accepted job in one place

If accepted work isn't visible in one place, someone is carrying it in their head. When that person is away or busy, jobs can stall without anyone noticing.

This guide is for owners of small service teams whose accepted jobs live in inboxes, chats and people's memories. It shows you how to keep one list of accepted work, with an owner and a dated next action for every job, a clear difference between "waiting" and "blocked", a record of who took over when someone was away, and evidence when a job is closed. It includes blank record cards and a hypothetical job followed from acceptance to closure.

This is ScalePass editorial guidance, not a standard. Adjust it to how your team works.

1. Put only accepted work on the queue

The queue is for work the customer has agreed to and you've taken on. Enquiries are not accepted work.

• Enquiries stay in your enquiry record until they're accepted, declined or closed. Our guide to managing customer enquiries covers that record.
• A job joins the queue when it's accepted, for example when the customer accepts a quote. Use the same job reference you already use, so the queue and your other records match.

Keeping the two apart means the queue only shows work you've committed to.

2. Start with a small set of states

A state says where a job is now. Here's an illustrative starting set. Change the names to fit your team:

• To start: accepted, but work hasn't begun.
• In progress: someone is working on it.
• Waiting on: someone outside the team needs to act first, such as the customer or a supplier.
• Blocked: something stops progress and needs a decision or a fix.
• Done: finished and closed, with evidence.

Fewer states are easier to keep accurate than many. Add one only if the team keeps needing it.

3. Give every open job an owner, a next action and a date

Each open job needs:

• a reference and a short description
• one owner: the one person who moves it next. Not "the team".
• a next action: the specific next step, such as "Confirm start date with the customer", not "in hand"
• a due date for that next action

If one person does everything, the owner column still helps. It shows at a glance what's waiting on you, and makes it easier to hand work over if you ever need to.

4. Keep "waiting on" and "blocked" separate

These look similar but need different responses:

• Waiting on means someone outside the team has to act. The next action might be to follow up by a set date, such as "Chase access details if no reply by Thursday".
• Blocked means something stops progress and needs a decision or a fix, such as a supplier delay. The next action is the decision, and who makes it.

Write down what the job is waiting on or blocked by, in a few words. "Waiting" on its own doesn't tell anyone what to do next.

5. When the owner is away, reassign on the record

When someone is off, their open jobs still need an owner. Reassign each one, and record it:

• the date
• who it moved from and to
• the reason: absence, workload or skills
• a short handover note
• the date the new owner acknowledged it

Until the new owner acknowledges it, the job still belongs to the previous owner. If it's only for a few days, note who is covering and until when.

Absence isn't a blocker. If a job was blocked by a supplier before the owner went on leave, it's still blocked by the supplier afterwards. Changing the owner doesn't clear the blocker, so record the two separately.

6. Close each job with evidence

"Done" should mean something anyone can check. When you close a job, record:

• the date and who closed it
• what shows the work is complete, such as a completion checklist or photos
• how and when the customer accepted it
• what was handed on next, such as to billing, if that's how you work

A closed job stays closed. If the original owner comes back from leave, it doesn't move back to them.

7. Use what you already have, and keep it tidy

You don't need new software. A shared spreadsheet, task list or job tool your team already uses will do, as long as everyone can see the same list.

• Keep customer details on the queue to what's needed. Use the job reference, and keep the full customer record where it already lives.
• Give access only to the people who need it.
• If you want to see the whole route from enquiry to finished job first, our guide to mapping your enquiry-to-delivery process shows how.
• For step-by-step instructions for a particular task, our guide to a small operations handbook shows how to write one.

Once the queue is working, a simple reminder may help, for example for jobs with no next action. Our guide on what to automate first covers choosing and testing one. The queue comes first.

8. Take a short, regular look

Agree a regular time to look at the queue together, such as once a week. Look for:

• jobs with no owner
• next actions past their due date
• jobs waiting longer than you'd expect
• jobs blocked with no decision made
• jobs with an owner who's away and no cover recorded

Fix each one there and then: give it an owner, set a new date, or make the decision.

9. Use the record cards

1. Copy the three blank cards into the tool you already use.
2. Add one queue card for each accepted job, using your existing job reference.
3. Update the card whenever the state, owner or next action changes, and note the date.
4. Use the reassignment card every time an owner changes.
5. Use the closure card when a job is done.

Hypothetical example: one job from acceptance to closure

Hypothetical example only: an invented three-person home-repair business. The people, customer, job and dates are fictional. It is not data or a ScalePass client.

The job is JOB-0142: replace and paint a garden fence for Customer B, following an accepted quote (version 2). Alex and Jordan are fictional team members.

What happened along the way:

• 2 Nov: the job joined the queue when the customer accepted quote version 2. The enquiry was closed in the enquiry record.
• 3 Nov: the job was waiting on the customer for side-gate access details. Access was confirmed on 4 Nov.
• 6 Nov: a supplier delay on the posts blocked the job. Customer B was told the same day.
• 9 Nov: Alex went on leave, so the job was reassigned to Jordan (see the card below). It was still blocked by the supplier: the change of owner didn't clear the blocker.
• 10 Nov: alternative posts were agreed with Customer B, and work resumed.
• 12 Nov: the job was closed with evidence (see the card below).
• 16 Nov: Alex came back. JOB-0142 stayed closed, with Jordan as the closer of record. Alex's other open jobs were returned by recorded reassignment.

The example shows one owner at a time, a dated next action at every open stage, "waiting on" kept separate from "blocked", the absence recorded separately from the supplier blocker, and closure backed by evidence and customer acceptance. It illustrates the method; it isn't a case study.

Common questions

How is this different from my enquiry tracker?

The enquiry tracker holds enquiries until they're accepted or closed. The work queue holds only accepted jobs. A job moves to the queue when it's accepted, and the enquiry is closed.

How many states do I need?

As few as your team can keep accurate. The five here are a starting point, not a rule.

What if one person does everything?

Keep the queue anyway. Owners, next actions and dates still help you see what's due, and make it easier to hand work over if you take on help or need cover.

What counts as done?

Agree it in advance. A useful minimum is evidence that the work is complete and a record of the customer accepting it.

What happens when someone's off?

Reassign their open jobs on the record, with a handover note and the new owner's acknowledgement. Keep any blocker as it was.

ScalePass helps service teams set up a clear way of working in the tools they already use, so it's obvious who owns each job and what happens next. If you'd like help setting up a work queue, see how we approach connected systems.

In short

Put only accepted work on the queue, and keep enquiries in your enquiry record. Give every open job one owner, a next action and a due date. Keep "waiting on" and "blocked" separate. When someone is away, reassign on the record, and don't let a change of owner hide a blocker. Close each job with evidence and the customer's acceptance. Take a short, regular look at what's overdue, stuck or unowned.