Explore Mossy

Decide where a person should approve the next step

Make approval an explicit part of the work.

All blog posts

Write down the actions with consequences your team wants to review. These may include offering an exception to a customer, approving a booking deposit change or spending money outside an agreed limit.

A review should show the proposed action, the information behind it and the result of waiting. Give the request one owner and let the reviewer approve, return it for more information or decline it.

Decide what happens after each response. Test how the workflow handles a late approval, a duplicate request and a change in the facts before a decision is made. Keep a record of the outcome where the team can find it.

Draw the line around consequences

List routine actions and actions that affect money, commitments or access. An ordinary callback may fit an existing policy, while promising an exception to a deposit rule needs a responsible person to decide. Ask what makes each exception important and what evidence someone would need. A threshold is only useful if the workflow can identify when it applies.

Check that the rule is realistic outside office hours and when the normal approver is away. Give the team an alternative owner or a clear way to hold the request. Tell the customer what is pending and when they are likely to hear back. A request can be recorded without creating the impression the business has already agreed to it.

Give the reviewer a clear choice

A reviewer needs the proposed action, the reason it requires approval and the source information. A request to move a booking with a deposit might include both times, the relevant policy and the customer’s preferred contact route. For an incomplete request, make the gap explicit and give the reviewer a way to return it for more information.

Define what approval means at the point of use. The workflow may be allowed to update a diary after approval, for example, while a customer confirmation should wait until the update succeeds. Keep a record of who approved it and when. Agree how a person can pause or correct an action when conditions have changed.

Test declines, changes and delays

Try a request that expires while waiting for approval. Check whether the system revalidates the facts before applying the decision. A reviewer could approve a time that is no longer available if old information remains on screen. Give the person a clean way to choose another option or send the request back.

Review approval queues during a pilot. Count waiting requests with no owner, repeats caused by missing context and decisions that can already be handled under agreed rules. Use that review to refine the boundary. The point is to reserve people’s attention for the decisions where they add judgement and to make those decisions easier to take.

Separate the decision from its execution

A reviewer can agree a change while the downstream system is unavailable. Keep the decision in the work record and show that the action is still pending. Give someone responsibility for checking whether it was eventually applied and whether the customer needs an update. When reviewers can see both states, they can tell the difference between work that needs judgement and work that needs operational follow-through.

Explore related Mossy features

Cookie preferences

Essential storage remembers your choices. Optional analytics measure site use.