Skip to content

Keeping decisions from getting stuck · 3 min read

Does every request need to wait for your approval?

If work keeps waiting in your inbox, decide which requests need your judgment and which staff could handle with a clear rule.

Start here.

Define who can decide, what information they need and what work must wait. Try that routine in one shared place. Add an approval step to software when it helps staff find waiting requests and carry the decision into the work they need to finish.

  • Start with what someone checks before approving a real request.
  • Name the work that can proceed and the work that must wait.
  • Test absence and changed details before adding an approval feature.

Look at what is waiting for you today

Imagine a small furniture workshop. The owner gets messages asking whether staff can reorder packaging, buy a replacement tool, or promise an earlier delivery. All three wait in the same inbox, even though the packaging is a routine reorder and the delivery promise needs someone to check the production schedule.

Pick a few recent requests and ask what the owner actually checked. Could someone else make the decision using an agreed rule? Did the request sit because information was missing, or because nobody knew who could answer? Solve that question before adding an approval button.

Separate routine decisions from exceptions

Write down which requests staff can handle and which need a decision from someone else. Use the circumstances that change the answer. Packaging might be a routine reorder when the item and quantity match an agreed list. A different material or a larger order could need review.

For each request that needs approval, name what must wait. Staff might be able to prepare the order while holding off on placing it. A customer delivery date might remain a proposal until the production manager confirms it. Show those differences in the record so people know what they can do next.

Give the approver enough to decide

Put the request, its reason and the relevant details together. In the workshop, a replacement tool request could include the item, the price, why the old tool cannot be used and when the work needs it. Ask the approver to try making the decision from that record without hunting through messages.

Decide how to record a yes, a no, or a request for more information. A comment asking for a cheaper option should send the request back to the person who can act on it. Make that next step visible alongside the reason.

Plan for an absent approver and a changed request

Name who can cover a decision when the usual person is away, and what that cover includes. A reminder can draw attention to waiting work. It cannot grant the authority to make the decision. Give staff a clear way to find the covering person when time matters.

If the request changes after approval, decide what must be checked again. In the workshop, substituting a different tool could change both its cost and whether it suits the job. Keep the earlier decision with the request, but make clear that it covered the earlier details.

Try a shared list before choosing a system

Use one place to record the requests, the person deciding and the next action. Try the same ordinary and awkward cases in a supplier demonstration. Ask staff to show which work is waiting and which can proceed.

If the shared list makes the decisions clear and someone checks it reliably, you may have enough for now. Consider a software step when people still miss requests, need to see the decision inside another job, or cannot tell which details were approved. Start with one type of request and review the cases that still needed a phone call.

Three approval tests for the hypothetical workshop
RequestWhat to decideWhat staff should see
A routine packaging reorderCan staff place it under an agreed rule?Whether they can proceed and where to record the order.
A tool request while the owner is awayWho is authorised to cover this decision?The covering person and whether buying must wait.
A different tool after approvalDoes the substitution need another decision?The revised details and a clear current approval state.

Bring one waiting request to a supplier demo

Ask the person who submits it and the person who approves it to walk through the same case.

The decision
What makes this request routine or an exception?
The hold
Which action must wait and who can release it?
The next step
Who acts on a rejection, a question or a revised request?

Planning something with a similar workflow?

Discuss your project with us

A couple of common questions.

Should every purchase need an approval step?

Start with what the decision protects and what staff can reliably handle under an agreed rule. Keep review for the circumstances that need judgment, and make those circumstances clear.

What if the person approving is away?

Name a covering person and define which decisions they can make. Make that arrangement visible to the people submitting requests.

What happens if details change after approval?

Decide which changes require another review. Keep the earlier decision with the details it covered and show the current state of the revised request.

Have something in mind?

Tell us what you want to build or improve. We’ll work out a useful first step together.

Discuss a project