Skip to content
Kaarne Superstore⌕
Small Business Life

The Order Reference Is Missing. Does the Instruction Tell You What to Do?

Make the missing-order-reference route visible in a working instruction. Capture an approved response and test it with a colleague using fictional examples.

A missing piece in a giant order-reference card leads to a visible review route.

The instruction says “look up the order”, but the customer’s message contains no order reference. A new support colleague reaches the second line and has to stop.

That pause is useful evidence. It shows where the written instruction assumes information the reader may not have, and where the team’s exception rule needs to be made visible.

Name the condition the instruction expects

In a fictional small support team, the normal example begins with a complete order reference. The writer has handled the task often enough to work around an incomplete message instinctively. A new colleague does not know which alternative checks are approved.

State the information needed for the normal route. Then describe how the reader recognises that it is absent or uncertain. Avoid broad wording such as “check the details” when the decision depends on a particular piece of information.

Use fictional records while drafting and testing. The instruction should not become a convenient place to store real customer details.

Document an approved exception, not a clever guess

Ask the responsible person what the team permits when the reference is missing. The route might involve asking the customer for a detail or passing the case to a specified role. It should not be invented by the instruction writer simply to let the example continue.

Write down the permitted action and the point at which the reader should stop or seek help. Keep any unresolved policy question marked as a question until it has been reviewed.

An instruction can be useful even when it ends with a clearly routed review. It does not need to imply that every case can be solved immediately by following the same steps.

Make the exception easy to find

Place the missing-reference route near the step that needs the reference, or provide an unmistakable link to it. A reader should not have to discover an important exception by searching a long appendix after they are already stuck.

Use the words the colleague is likely to search for. A descriptive heading such as “When the order reference is missing” is more discoverable than a private abbreviation known only to the author.

Keep the instruction’s owner and current version visible so the reader knows where to raise a gap or conflicting rule.

Observe a complete and incomplete case

Give a colleague two fictional messages and the draft instruction. Ask them to apply the normal route to one and the approved exception route to the other.

Record what they actually do, including any explanation you provide. If they find the route but interpret it differently, revise the wording or seek a decision from the process owner. Then retest the changed step.

The finished instruction should carry the team’s supported response to an awkward case. Its value is not that nobody ever asks a question; it is that the next person can see which question to ask and where it belongs.

Explore the working instruction

See the related guide: Write the Handover the Next Reader Actually Needs.

For a written practice option, review the Team Knowledge with Matze course overview. It uses written exercises and requires your own review of the working instructions.

Check the course contents and current terms. Affiliate link: Superstore may earn a commission if you buy.

0

Discussion 0

What did this article make you think about?

Join the conversation

Your email address will not be published. Required fields are marked *

Saved articles

Saved in this browser.