The existence of a twenty-page instruction does not mean an officer can quickly find the sentence needed during a task. Conversely, reducing the document to one page by removing exceptions and responsibilities may introduce new uncertainty. A usable task card is more than a polished summary: it helps someone begin a defined activity at the correct point.
Readability is not the same as understanding
Lindhout and colleagues designed an indicator for systematically managing the readability of safety documents. [1] Their paper is not an experiment demonstrating the field effectiveness of a task card. Its useful starting point is to examine usability separately from a document's existence. HSE similarly recommends reviewing the task with its users when designing procedures. [2] The following structure is our practical application of these ideas.
Select one decision point first
Instead of a broad heading such as “entrance security procedure”, choose a bounded activity, such as notifying the relevant department about a scheduled visit. Identify who will use the card, where and under what conditions. Do not combine different tasks merely because they happen at the same desk.
Mark the authority limits, required checks and consultation points in the approved instruction. Do not start shortening the document by deleting them. Technical wording can be made clearer, but editorial decisions should not change the sequence of work or the authority required for approval.
Divide the card into six parts
An initial draft can answer these questions:
- Purpose: What should be clear when the activity is completed?
- Starting condition: What must be available before beginning?
- Steps: What does the officer do, and in what order?
- Stop-and-ask point: Which missing condition prevents independent continuation?
- Contact: Which role should be consulted, through which organisational channel?
- Version: Which dated version of the approved instruction supports the card?
Use specific verbs instead of “take the necessary action”. Explain which role is meant by “inform the relevant authority”. To avoid making the whole card obsolete when a person changes, contact details can be held in a maintained organisational directory referenced by the card.
Ask a user to work through a harmless example
The author can give a representative officer a safe example scenario. Ask the officer to use the card to show where to begin and when to consult someone. Include a user from another shift in the review as well. This is not a memory test or an attempt to embarrass the employee. Its purpose is to discover gaps in the document.
If the officer repeatedly needs verbal clarification, do not dismiss this as inattention. There may be a missing condition, an ambiguous pronoun or two different activities combined in one step. Revise the card and check the same decision point again. Personal information and site details in the example should be fictional or appropriately anonymised.
Fit the layout to the work setting
Squeezing everything onto one page in small print may not improve usability. Consider headings, brief steps and spacing together. Review the printed version as well as the screen display, and check that a colour cue does not lose its meaning in a monochrome copy.
After approval, establish when the card comes into use and how obsolete copies will be removed. The card does not automatically replace the formally approved procedure. Its document owner should resolve any inconsistency before use. At the next review, add a second question beside “was the card distributed?”: can the officer actually find the required decision in it?
