The customer has accepted the quote. The document has been uploaded. The first stage of the project is complete.
Each of those events should allow something else to happen. Yet the next step can sit untouched until someone sends a message, checks an inbox or asks for an update.
Meanwhile, the customer waits. A colleague cannot finish their part. The owner spends another afternoon finding out where things stand.
Work can stall even when everyone is busy and doing their own job well. The difficulty is often the handover: how one person’s completed work becomes another person’s next task.
Automation can help by making those handovers clearer and more dependable. It can bring the right information to the next person, assign an action, and flag unresolved work. The benefit can extend beyond minutes saved on administration to less avoidable waiting across the whole process.
A short task can cause a long delay.
Consider a simple illustrative example. Preparing a new project takes twenty minutes, but the accepted quote waits two working days before anyone starts the setup.
Making the setup five minutes quicker would help. Getting it into the right person’s work queue promptly could address a different, potentially more significant problem.
The business has two things to measure: the effort required to do the task and the time that passes before the task is done.
Those measures should not be confused. Removing a two-day wait does not recover two days of staff time. It may, however, let a project start earlier, give the customer a quicker response, or prevent another team from being held up.
To understand the opportunity, look at the journey through the business as well as the individual tasks. Ask what is waiting, why it is waiting and what that delay prevents.
Why handovers break down
A message saying “this is ready” can leave several questions unanswered.
Ready for what? Who should act? Where is the latest information? Has the necessary approval happened? Is there a deadline?
The gaps tend to fall into four groups:
- Unclear ownership. Several people receive the message, but nobody is explicitly responsible for the next step.
- Incomplete information. The recipient must find missing details or ask questions before they can begin.
- Unclear status. Work is marked “done”, although it still needs review, approval or corrections.
- Poor visibility. The request is buried in an inbox, and there is no dependable way to see what remains outstanding.
These problems can lead to repeated chasing. The person sending the work assumes it has been picked up. The recipient assumes someone else is handling it. A manager intervenes to establish what should already be clear.
A better handover makes the next action easier to understand and begin.
What a useful handover needs to include
Before automating anything, establish what the next person needs. A useful handover should answer five questions:
- What needs doing? State the action rather than simply announcing that something has happened.
- Who owns it? Assign a person, or use a team queue with a clear rule for claiming work.
- What information is needed? Include the relevant details and links to the correct records.
- When is it needed? Use a meaningful due date or response expectation.
- What allows it to move forward? Define any required checks, approvals or missing information.
Automation can then help carry those instructions and records into the next stage consistently.
It cannot settle a disagreement about who should be responsible. That is a business decision to make first.
Three handovers that automation can improve
The following examples show how a process could work. They are illustrative, and the available options depend on the software and information involved.
An accepted quote waits for project setup.
When a customer accepts a quote, the salesperson may consider their immediate task complete. The delivery team still needs an agreed scope, customer details, key dates and instructions about what to prepare.
If those details arrive through an informal email, a project can remain unprepared while people establish what was promised.
An automated handover could create a setup task when acceptance is recorded, attach a link to the agreed quote, and identify the responsible person. It could check for required fields and flag anything missing.
The status should distinguish between “accepted”, “awaiting setup” and “ready to schedule”. Accepting a quote does not automatically mean that capacity has been confirmed or that every starting condition has been met.
This gives the delivery team a clearer starting point and makes unfinished setup visible. A person still confirms the commitments that require their judgement.
A document waits for review.
A customer uploads a document, but the reviewer does not know it has arrived. Alternatively, the reviewer receives an attachment without knowing which project it belongs to or what decision is required.
The document is available. The review is still waiting to begin.
A connected process could create a review request linked to the project and the exact document version. It could identify the reviewer, explain what needs checking and set the appropriate due date.
The outcome matters too. Approval could release the next step. A request for changes could return the work to the relevant person with the reason recorded. An unanswered request could remain visible as pending.
Receiving a document and accepting it are different events. The process should preserve that distinction so work doesn’t start prematurely or remain blocked after review is complete.
A completed task never reaches the next person.
One colleague finishes a draft, an inspection or a preparation task. They update their own record, but the next person only discovers the work is ready during a meeting or after asking.
An agreed completion status could prompt the next task, assign its owner and include the output needed to continue.
However, “complete” needs a shared meaning. If a draft still requires approval, the next step is a review. If the work is approved for release, the next step may be delivery to the customer.
When something is returned for correction, the process should also show who owns the rework and what happens next.
The improvement is a dependable transition between stages, with fewer messages needed to establish what comes next.
Timely prompts should help people act.
Sending more notifications is easy. Making them useful requires thought.
A good prompt tells the recipient what needs attention, why it matters and where to act. “Please review the revised brief for Project A by Thursday; delivery planning is waiting for your decision” provides more direction than “Document updated”.
Routine updates may belong in a shared queue or a daily summary. An urgent exception may justify a direct alert. Not every change needs to interrupt everyone.
Reminders should also reflect the current position. Once an action is complete, stop its reminder. If the work is waiting for customer information, the prompt should target that problem rather than repeatedly telling the reviewer to finish.
If no one responds within the agreed period, the process could bring the outstanding item to another responsible person’s attention. That person can decide whether to reassign it, resolve a blockage or change the priority.
The aim is to make action clearer without creating another stream of messages to manage.
Make the reason for waiting visible
“Pending” is often too vague to guide a decision.
A project waiting for a reviewer, a customer response and an available delivery slot may all appear unfinished, but each needs a different response.
Useful statuses distinguish those reasons. A task waiting for customer information can show what is missing and who is following up. A review awaiting a decision can identify the approver. A project held for capacity can show that scheduling is the issue.
This helps the team focus on what can make a difference. It also makes customer updates more accurate: people can explain what is outstanding rather than saying that the work is “in progress”.
The information still needs to reflect reality. Decisions made in conversations must be recorded if they affect the process. Automation can distribute a recorded update, but it cannot reliably act on an agreement that nobody has captured.
Some waiting has a legitimate cause.
Automation can reduce time lost to missed messages, unclear handovers and repeated checking. It cannot create an available specialist when everyone is fully occupied.
If one reviewer has more work than they can reasonably complete, faster notifications may deliver requests into the same overloaded queue. The business may need to adjust priorities, share responsibility or add capacity.
Some work also needs to wait for a sound reason. A customer may need time to make a decision. A technical check may be essential. Starting before approval could create errors, rework or commitments the business cannot honour.
Understanding the reason for the wait helps you choose an appropriate improvement. A reminder can help with an overlooked request. It will not solve a missing decision rule or an impossible workload.
Measure the handover, not just the message.
A notification being sent tells you that one part of the process ran. It does not establish that the work was picked up or completed.
Choose measures that reflect the problem you want to improve. These might include:
- Time between quote acceptance and completed project setup.
- Time between document submission and a recorded review outcome.
- The number of handovers returned because information was missing.
- Outstanding tasks beyond their agreed response period.
- Time staff spend checking progress and chasing updates.
Compare the result before and after the change. Include the effort needed to review exceptions and fix problems in the automated process.
Ask the recipients whether they now receive work they can act on. A task arriving sooner is useful only if it comes with enough information to proceed.
The business benefit might be earlier project starts, more dependable customer updates or less coordination work. Establish which outcome matters rather than assuming every shorter wait has the same value.
Start with a handover your team already finds frustrating
Choose one recurring transition and look at a few recent examples. When was the first stage finished? When did the next person begin? What happened in between?
Speak to both sides of the handover. The sender may believe the instructions are complete, while the recipient knows which details they routinely have to find.
Agree on the owner, the required information and the conditions for moving forward. Remove unnecessary checks or approvals where appropriate. Then consider how automation could prepare the next action and make unresolved work visible.
For a broader way to compare opportunities, see our guide to Which Business Tasks Are Actually Worth Automating?
A reliable handover lets people spend more time doing the work and less time establishing whose turn it is. That is a practical automation benefit even when the individual tasks still require the same expertise and effort.
If work in your business regularly stalls between people, contact Company Compass to explore where clearer processes and practical automation could help.