How to Write Work Instructions (with Examples)

A work instruction tells someone exactly how to perform one specific task. Not a process, not a workflow, not a guideline. One task, with enough detail that the reader gets it right on the first attempt.

Work instructions sit one level below SOPs in the documentation hierarchy. While an SOP describes a complete process from start to finish, a work instruction zooms into a single step within that process and provides the granular detail needed to execute it correctly. For a deeper comparison, see SOP vs Work Instructions.

This guide walks you through writing work instructions in five steps, with three real-world examples.

What Are Work Instructions

A work instruction is a detailed, task-level document. It describes how to perform one specific activity: calibrating a machine, configuring a software setting, assembling a component, or sanitizing a workstation.

Work instructions share three characteristics:

1. Narrow scope. They cover one task, not an entire process.
2. High detail. They include exact values, settings, measurements, and expected results.
3. Operator audience. They are written for the person performing the task at their workstation, not for a manager reviewing the process.

You need a work instruction when a task is complex enough that different people might do it differently, when errors have serious consequences, or when precision matters.

Work Instructions vs. SOPs

The distinction is scope:

An SOP for "Daily Quality Control Setup" might have 12 steps. Step 4 is "Calibrate the digital scale." If calibration involves specific weights, a particular sequence, and tolerance checks, that step gets its own work instruction.

For a full breakdown, read SOP vs Work Instructions: What's the Difference.

How to Write a Work Instruction in 5 Steps

1. Pick a Single Task

A work instruction covers one task. If you find yourself writing about multiple tasks, you are writing an SOP, not a work instruction.

Ask yourself: "Can this be described as a single action with a clear start and end?" If yes, it is a work instruction. If it involves multiple phases, handoffs, or decision points, it is a process and belongs in an SOP.

Examples of single tasks:

• Calibrating a piece of equipment
• Configuring a specific software setting
• Assembling one component
• Performing a specific cleaning procedure
• Running a quality check on a single metric

2. Observe the Task Being Done

Never write a work instruction from memory. Watch someone experienced perform the task while you take notes. Better yet, record it.

During observation, note:

• Every physical action or click, including the ones that seem obvious
• The exact tools, materials, and settings used
• Any preparation steps before the main task begins
• What a correct result looks like at each stage
• What common mistakes look like
• Safety precautions the expert follows (even unconsciously)

If the task is performed on a screen, use Credia's Screen to SOP to record the entire sequence. The AI generates the steps and captures screenshots automatically.

If the task is physical, use your phone to record video or take photos at each stage.

3. Write the Steps in Order

Turn your observations into written steps. Follow these rules:

Start every step with a verb. "Place the 100g calibration weight on the center of the scale." "Select 'Calibrate' from the Settings menu." "Wipe the surface with the sanitizer solution in a left-to-right motion."

Include exact values. Not "Add the cleaning solution" but "Add 30ml of the sanitizer concentrate to 1 liter of warm water (35-40 C)." Not "Wait for it to dry" but "Allow the surface to air-dry for a minimum of 60 seconds."

Describe expected results. After each step or group of steps, state what the reader should see if they did it correctly. "The scale display should read 100.0g with a tolerance of plus or minus 0.1g." "A green checkmark appears next to the configuration field."

Flag warnings before the step. If a step involves a safety risk, irreversible action, or common mistake, place the warning before the step, not after. The reader needs to know before they act.

Keep steps atomic. One action per step. "Open the valve and check the pressure gauge" is two steps. Splitting them prevents errors.

4. Add Visual Aids

For any task involving equipment, physical materials, or software interfaces, visual aids are essential. They eliminate the ambiguity that words alone cannot resolve.

For physical tasks:

• Photo of the correct setup before starting
• Photo of each critical step showing hand position, tool placement, or material orientation
• Photo of the correct result at the end
• Annotated photos with arrows pointing to the specific part, button, or indicator

For software tasks:

• Screenshot of the correct screen before the action
• Screenshot with the relevant field, button, or menu highlighted
• Screenshot of the expected result after the action

For both:

• Side-by-side comparison of correct vs. incorrect (when common mistakes exist)
• Close-up of measurement readings, indicator lights, or status messages

You don't need professional photography. A clear phone photo with an arrow drawn on it communicates more than three paragraphs of description.

5. Validate with the Person Doing the Task

Before publishing, test the work instruction:

Expert review. Have another experienced person read it. They catch missing details, incorrect values, and safety items you forgot to mention.

Newcomer test. Give it to someone who has never performed this task (but has general training for the role). Watch them follow the instruction without help. Every hesitation or question reveals a gap.

Common issues found during testing:

• Steps that assume knowledge the reader does not have
• Missing preparation steps (tools not mentioned, access not set up)
• Values that differ from actual practice (documentation says one thing, reality is different)
• Photos that don't match the current equipment or interface version

Fix every issue. Then test again if the changes were significant.

3 Work Instruction Examples

Example 1: Calibrating a Digital Scale (Manufacturing)

Task: Daily calibration of the XYZ-500 digital scale in the quality lab.

Steps:

1. Verify the scale is on a level, vibration-free surface
2. Turn on the scale and allow 15 minutes for warm-up
3. Press and hold the "Tare" button for 3 seconds until the display reads 0.0g
4. Place the 100g NIST-certified calibration weight on the center of the weighing pan
5. Wait for the reading to stabilize (the stability indicator stops flashing)
6. Verify the display reads 100.0g (acceptable range: 99.9g to 100.1g)
7. If out of range: Press "Cal" > Enter password 1234 > Follow on-screen calibration sequence > Repeat from step 4
8. Remove the weight and verify the display returns to 0.0g
9. Log the calibration date, reading, and your initials in the QC log (Binder 3, Section C)

Visual aids: Photos of the scale display at steps 3, 6, and 8. Photo of the calibration weight placement.

Example 2: Configuring SSO for a New Employee (IT)

Task: Setting up single sign-on access for a new employee in Okta.

Steps:

1. Log in to the Okta Admin Console (admin.company.okta.com)
2. Navigate to Directory > People > Add Person
3. Enter the employee's first name, last name, and company email
4. Set Username to their email address
5. Under Groups, add the following groups based on their department (refer to the Department-Group Matrix document for the correct assignments)
6. Set Password to "Set by admin" and enter the temporary password from the onboarding ticket
7. Check "User must change password on first login"
8. Click Save
9. Navigate to Applications > Assign Applications
10. Select the employee and assign the standard application bundle for their role
11. Click Done
12. Send the welcome email from the onboarding ticket template, including the temporary password and login URL

Expected result: The employee can log in at company.okta.com with the temporary password and is prompted to set a new password. All assigned applications appear on their Okta dashboard.

Example 3: Sanitizing the Prep Station (Food Service)

Task: End-of-shift sanitization of the cold prep station.

Steps:

1. Remove all food items and store in the walk-in cooler (do not leave any items on the station)
2. Remove the cutting boards and place them in the dish pit for washing
3. Mix sanitizer solution: 30ml of quaternary ammonium concentrate per 4 liters of warm water (24-30 C)
4. Spray the entire stainless steel surface with the sanitizer solution, covering all areas including edges and the backsplash
5. Allow the solution to sit for a minimum of 60 seconds (do not wipe immediately)
6. Wipe the surface with a clean, single-use paper towel in one direction (left to right, top to bottom) to avoid cross-contamination
7. Allow the surface to air-dry completely (do not use a cloth to speed up drying)
8. Visually inspect the surface under the overhead light. The surface should be free of residue, stains, and moisture
9. Log the sanitization time and your initials on the daily cleaning chart (posted on the cooler door)

Safety note (before step 3): Wear nitrile gloves when handling the sanitizer concentrate. Avoid contact with eyes. If contact occurs, rinse with water for 15 minutes and notify a manager.

Managing Work Instructions at Scale

Once you have more than a dozen work instructions, organization matters. Work instructions should be:

• Linked from the parent SOP so readers can navigate from the process overview to the task detail
• Searchable so someone can find the right instruction without knowing where it lives
• Version-controlled so you can track changes when equipment, software, or procedures are updated
• Assigned an owner who keeps each instruction current

Credia stores work instructions alongside SOPs in a single knowledge base. Link them together, search across everything, and keep your documentation connected. Start with our SOP templates and add work instructions for the steps that need them. For the complete SOP writing framework, see how to write a standard operating procedure.