“Sort out the handouts and send the final version” sounds like a task, but leaves the work undefined. Which handouts? Starting from which files? Does “final” mean ready for a manager to review, ready to print, or already approved for distribution? A colleague cannot solve those gaps merely by reading more carefully.
A usable instruction gives the reader a starting point, actions in a workable order and a visible finish. Write those facts before polishing the wording. The aim is not a longer message: it is a procedure someone can follow without supplying missing decisions.
Start with the reader and the outcome
Name the person doing the work and one result they should produce. “Prepare a draft for Salma’s review” is narrower and more useful than “manage the workshop materials.” It tells the writer which actions belong in the procedure and which belong elsewhere.
Next, identify the materials and location the reader needs before starting. Google’s procedure guidance explicitly recommends providing preparation information ahead of time. It also defines a procedure as a sequence of numbered steps for accomplishing a task. [2] If a required file, permission or destination is unknown, resolve it before asking the colleague to proceed; do not bury that discovery halfway through the work.
Write in the order the reader needs
Microsoft recommends numbered lists for multiple-step procedures, complete sentences and imperative verbs, with a brief location phrase first when needed. Google likewise says to state the location before the action. [1][2] “In the working copy, replace the session title” lets the reader find the object before changing it.
Keep each step focused. Microsoft allows short actions in the same interface location to be combined; Google generally recommends one action per step while allowing small sequential menu selections together. [1][2] A short save-and-record action can stay together when it forms one local checkpoint. Copying material, checking its meaning and obtaining approval are different jobs: separating them makes omissions easier to notice.
Avoid unnecessary repetition. Microsoft cautions against an introduction that merely repeats a heading; Google advises referencing repeated procedures rather than duplicating them. [1][2] Brevity should remove redundant explanation, not the file name or location needed to act safely.
These are vendor style recommendations, not universal legal requirements. The procedure card below is our proposed MAJLS structure, not a vendor-mandated form or a claim of certified accessibility.
Before and after
Before: “Sort out the handouts and send the final version.”
After: “Omar, prepare the Workshop A handout draft in Review using the approved brief and Handout v3. Give Salma the draft location and comparison note for review. Do not print or distribute it.”
The shorter rewrite establishes scope. The filled card supplies the actual route through the task.
Proposed procedure card: Prepare the workshop handout pack for review
This entire procedure is illustrative, fictional and proposed. It has not been executed. Workshop A, Handout v3 and Review describe hypothetical existing files and a designated internal folder in a local process; they are not supplied files or application features.
Reader: Omar, preparing materials at operations lead Salma’s request.
One outcome: a workshop handout draft FOR REVIEW, accompanied by a comparison note for Salma.
Starting materials and location: the already approved Workshop A agenda brief; the blank Handout v3 template; the designated internal Review folder; authority to prepare a draft only. Before starting, confirm that the approved brief and template are present and do not conflict. Otherwise stop and ask Salma.
Numbered actions:
- In the designated Review folder, create a working copy of Handout v3 named Workshop A handout draft, leaving the source template untouched.
- In that working copy, replace the session title and session order with the exact values in the approved Workshop A brief.
- Compare the draft with the brief and mark any missing or contradictory item for Salma; do not infer a room, time or speaker.
- Save the draft in Review and record the working-copy name in the internal review note.
- Hand Salma the review note containing the draft location, source brief/template versions and any unresolved items.
Completion evidence: a located draft plus a comparison note identifying what was compared and what remains unresolved. This is not evidence of printing, sending attendees a file or publication approval.
Exception destination and owner: stop and ask Salma if the approved brief or template is missing or conflicting. Salma alone accepts the content and authorizes any later printing or distribution. Omar’s authority ends at preparation for review.
Make optional work and results explicit
None of the card’s actions is optional. If a different procedure contains an optional action, label it “Optional:” at the beginning, as Google recommends. [2] Explain when it is useful rather than leaving the reader to wonder whether skipping it breaks the task.
Where a result helps navigation, describe it after the action. Google distinguishes the action from its resulting reaction. [2] State only a result you know the local process produces; do not invent an automatic notification or software feature. Replace “handle appropriately” with an observable action such as “mark the conflicting item for Salma.”
Use these questions before handing it over
Ask: Who is following this? What single outcome do they owe? Which approved materials and location must exist first? Can they identify the object of every action? What shows preparation is complete? Where does a missing input go, and who decides next?
Then arrange a future colleague walk-through. Ask the colleague to follow the instruction and record their actual stopping points: an unidentified folder, an ambiguous version or a decision the writer assumed. Revise from those observations; do not call this illustrative card tested in advance.
A possible MAJLS-agent role is preparing a draft instruction from approved inputs and flagging a missing step. That role cannot invent policy, access, software capabilities or approval. Clear instructions reduce the need to guess by making those boundaries readable.
