The quotation is accepted. Can delivery act on it?

Consider a fictional equipment supplier making a customised workbench. The customer discussed an upcoming premises move during the sales conversation. The quotation specifies a delivery week. The planner receives that document but does not know whether the bench must also be installed and usable before the move.

Booking a lorry may satisfy the date on the page while missing the outcome the customer expects. Before scheduling, sales and delivery need to clarify what was promised, what the customer will provide and which details remain unsettled. The aim is to make the agreement usable by someone who was absent from the original conversation.

The UK Government Digital Service's Service Standard calls for services that make sense across organisational boundaries. It concerns public services. Applied here as a design principle, it suggests starting from the customer's intended result and working through the responsibilities needed to deliver it.

Forwarding an entire email chain preserves correspondence but leaves the recipient to reconstruct the decision. Create a concise job brief that points to the agreed quotation, drawing and confirmation. Keep those source documents authoritative; the brief should help colleagues find and understand them rather than establish a competing specification.

Separate four kinds of information:

Part of the brief	What the receiving team needs to understand
Confirmed commitment	The agreed outcome, boundaries and document version
Prerequisite	What must be available first and who will provide it
Assumption	What remains unconfirmed and which decision depends on it
Open decision	Who will resolve it, by when, and what work can proceed meanwhile

In the workbench example, access through a doorway might be a prerequisite. The final floor measurement might be an open question. Availability of lifting equipment might merely be an assumption. These should not appear as equally settled facts on a work order.

Ask the people preparing and performing the job which questions they repeatedly have to ask. Use their answers to decide what belongs in the brief. Avoid copying every piece of customer information into every system. Colleagues need relevant context and access to the right source, with responsibility for keeping it current.

Receiving a job and being ready to perform it are different events. Agree a point at which an authorised colleague reviews whether the first activities can safely and sensibly begin. For a familiar order, this may be a quick check within an existing work order. A new configuration or unusual deadline may require a discussion before sales makes a firm commitment.

Record the practical conclusion: which activities can proceed, what must wait and who owns the next action. A missing detail need not stop unrelated preparation. Equally, ticking “received” should not conceal an assumption that affects the entire job.

An internal hold does not rewrite a customer commitment. If the team discovers that an agreed date or outcome is at risk, someone must address that with the customer. Name that responsibility when setting up the handover, so the planner is not left to choose between silence and an unauthorised promise.

Keep the process proportionate. Routine work should move through agreed boundaries without requiring the owner to approve every order. Use experienced colleagues where judgement is needed, and define how someone can get support when the usual specialist is unavailable.

A complete brief is of limited use if the recipient cannot act on it. A planner may need authority to ask the customer for a measurement, rearrange preparation within the agreed window or select an already approved configuration. Changes to scope, price or a promised completion date may require a different decision-maker.

Our article on helping employees make decisions independently explores the knowledge, authority and support behind that autonomy. At a handover, the essential question is whether the colleague can take the next appropriate step without chasing the business owner for background on every job.

Keep sales available to explain the reasoning behind a commitment. Also agree who updates the customer. Someone who has been told “everything is ready” should not then discover that delivery is still waiting for essential information. GDS guidance on joining up service channels includes involving front-line operations staff in service design. For this handover, that means involving the colleagues who will answer the customer's next question.

After handover, the customer may change a dimension or ask for a different installation arrangement. Record what changed, who confirmed it and which preparations now need review. Uploading another drawing is not enough if the workshop is still working from its predecessor.

Start by examining the tools already in use. Can the work order show the current agreement, unresolved questions and responsible colleague? Can someone see that a relevant change has happened? A customer portal may be useful when customers regularly provide details or confirm options, provided those decisions reach the people who must act on them.

Before commissioning software, ask a technical partner to demonstrate one complete scenario: a dimension changes after preparation has begun. Follow the change through confirmation, version history, review and the next customer update. This tests the proposed support against actual work and gives the team a concrete basis for judging it.

Review a small selection of recent jobs together: a straightforward order, one with missing information and one changed after acceptance. Compare what the customer expected with what the receiving colleague could actually know. Use gaps to improve the process rather than to assign blame with hindsight.

Then try the brief on new work. Discuss whether fewer details have to be reconstructed, whether uncertainty becomes visible before scheduling and whether customers receive a consistent answer. Include the effort of maintaining the brief in that assessment. Remove fields that create administration without supporting a decision.

If every order still depends on the owner remembering the original conversation, the next step is organisational. Through business process analysis, IndustrylinQ connects customer commitments with responsibilities and information. That makes it possible to choose a practical change in the way people work, supported by software where it adds value.