Writing Procedures and Work Instructions: Differences, Structure and a Sample Template

The difference between policy, procedure and work instruction; template sections, writing steps with role–action–time–record, weak and corrected step examples, and the order for verifying in practice.
Technical summary
Technology
ISO/IEC 27001:2022, Annex A 5.37, Clause 7.5, ISMS documentation
Topic
Writing IT and information security procedures and work instructions
Level
Beginner–intermediate
Prerequisites
  • An approved information security policy
  • The process owner and those carrying it out identified
In this article8 sections

A single test shows whether a procedure is good: can an employee doing the job for the first time read the text and finish the job correctly? The most common problem in audits isn’t that there’s no procedure at all. It’s texts that repeat the policy word for word, don’t say who does what and don’t match practice on the ground at all. Below, for IT and information security teams, we give the policy–procedure–instruction distinction, the sections of a procedure template and the rules for writing steps, with examples.

The hierarchy of policy, procedure and work instruction

The three documents answer the same question at different depths. A policy says “what we want and why”. A procedure answers “in which steps, and by whom, does the process run”. A work instruction goes down to “how exactly do I do this job in this system, keystroke by keystroke”. When the hierarchy gets mixed up, two typical failures appear: screen steps are written into the policy so it has to be revised with every system change, or the procedure stays so general that there isn’t a single measurable thing in it.

Feature Policy Procedure Instruction
Question What and why? Who, what, when? Exactly how?
Reader All employees, management Process roles The specialist doing the work
Approval Top management Process owner Team lead / process owner
Frequency of change Low Intermediate High (as the system changes)
Example Access control policy User account lifecycle procedure Work instruction for closing guest accounts in Entra ID

ISO/IEC 27001:2022 doesn’t require a separate procedure for every topic. Clause 7.5 requires the organization itself to determine the documented information it considers necessary for the effectiveness of the ISMS; Annex A 5.37 expects operating procedures for information processing facilities to be documented and made available to personnel who need them. Decide which processes to tie to a procedure with three questions: how risky is the process, how many people run it, and what does an error cost? For the design of the top-level policy, see the information security policy writing guide, and for an overall picture of which documents are really needed, the ISO 27001 documents article.

Sections of the procedure template

Use the same skeleton in all procedures; especially when preparing an information security policy and procedure package, this speeds up both the reader and the auditor. The reader knows where everything is. For most IT and ISMS procedures, these sections are enough:

  1. Document header: document number, version, effective date, author, approver, classification. How version and approval rules are operated is explained separately in the article document control and revision management.
  2. Purpose: one or two sentences. Which risk the procedure reduces, which policy clause it implements.
  3. Scope: which systems, locations and user groups are included; what is deliberately excluded. Don’t write unbounded phrases like “all IT systems”; list the scope.
  4. Definitions and abbreviations: only terms used with a different meaning in this document.
  5. Roles and responsibilities: role names, not people’s names. Each role’s authority in this process.
  6. Inputs and triggers: what starts the process (request record, calendar, alert, HR notification).
  7. Steps: numbered flow; decision points and time targets where needed.
  8. Records: which evidence is kept at the end of the process, where and for how long.
  9. Related documents: the top-level policy, work instructions, forms.
  10. Revision history: version, date, summary of the change.

In the field, the weakest section is almost always “Records”. Yet the auditor can only verify that a procedure is operated from its records. If there’s no record, the work counts as not done. At the end of each step ask “does this step leave a trace?”; the section fills itself.

Writing steps: who, what, when, which record

A working procedure step has four elements: role (who), action (a measurable verb), timing (trigger or deadline) and output (record). If one is missing, the step either can’t be applied or can’t be shown to have been applied.

  • Use the active voice. Instead of “The account is closed”, write “The system administrator closes the account”. The passive voice deletes the responsible person from the text; on the day of an incident, nobody thinks the job is theirs.
  • One step, one action. “Reviews, approves and implements the request” may be the work of three different roles; separate them.
  • Choose a measurable verb. “Follows up”, “pays attention”, “takes the necessary measures” can’t be audited. “Records”, “approves”, “disables”, “reports” can.
  • Write the deadline. Instead of “as soon as possible”, write “by the end of the first working day after the leaving date”. Set a deadline the organization can actually meet; an ambitious deadline on paper turns into a finding at the first audit.
  • Give the exception next to the step. Write in the same place whose approval is needed for a deviation in an emergency or when the system is unavailable.
  • Don’t leave decision points open. Wherever you see “if necessary” in the text, add the criterion for the necessity.

Level of technical detail in work instructions

A work instruction explains how a single step of the procedure is done on the system, and is numbered separately from the procedure. This separation isn’t for nothing: when the management console’s interface changes, only the instruction is revised and the procedure’s approval chain doesn’t have to run again. The test for the level of detail is simple: a team member with permissions on that system who is doing the job for the first time should be able to finish the instruction on their own.

In an instruction containing commands, the command itself, the expected output and a verification step are written together. A command without verification is half a job. A section of an instruction for disabling a leaver’s account in Active Directory looks like this:

# Step 3 – Disable the account (ActiveDirectory PowerShell module)
Disable-ADAccount -Identity "jane.smith"

# Step 4 – Verify: Enabled must be False
Get-ADUser -Identity "jane.smith" -Properties Enabled, Description |
    Select-Object SamAccountName, Enabled, Description

# Step 5 – Write the request number in the description field
Set-ADUser -Identity "jane.smith" -Description "Leaver - REQ-2026-0412"

If you use screenshots, note the console or software version underneath. An outdated screenshot produces more errors than a missing instruction; a specialist looking at an image where the menu has moved changes the wrong setting. Don’t write sensitive information such as passwords, keys or the server IP plan into the instruction; refer to the vault or system where they’re kept.

Weak and corrected step examples

The rows below are steps you may come across in user account lifecycle procedures, with their corrected versions.

Weak wording Problem Corrected wording
Leavers’ accounts are closed. No role, deadline or record The IT support specialist disables the user’s directory and email accounts by the end of the working day on which HR’s leaver notification is received, and closes the request record.
Permissions are checked periodically. Frequency, scope and checker unclear Every application owner reviews the permission list produced by IT every three months, opens change requests within the same week and uploads the signed list to the ISMS folder.
Administrator rights may be granted when necessary. No criterion or approver Administrator rights are granted only on a request approved by the IT manager and for no longer than the period stated in the request; the rights are removed when the period ends.
Backups are tested regularly. “Regularly” can’t be measured, no output defined Every month, the system administrator performs a sample restore from at least one critical system and records the result on the restore test form.

The corrected statements are long. That isn’t a flaw. To manage the length, put the steps into a table or a flow list with “Role | Action | Deadline | Record” columns. Most readers use this table, not the procedure in paragraph form.

Common mistakes

  • Copying the standard’s text: Writing an Annex A control description as a procedure step changes nothing in practice; it’s also problematic from a copyright point of view.
  • Writing a process that doesn’t exist: A procedure describes not the ideal process but the process the organization will actually run. If the target process is different, a transition plan is kept separately.
  • Contradicting the higher-level document: A deadline, approver or frequency in the procedure doesn’t match the value in the policy or another linked procedure. While writing, open the policy clause you’re referring to and compare the values one by one.
  • Not defining the record: Writing “is recorded” without saying where and in what format.
  • Squeezing several processes into one procedure: Putting backup, restore testing and media disposal into a single document makes revision and ownership harder. Three processes mean three owners.

Verifying the procedure in practice

Before publishing, show the procedure is workable with a short verification round. The order of checks is:

  • Read the procedure step by step with two different people who run the process; at each step ask, “is this how you do it today?”
  • Pick a real example from a past period (for example the latest leaver request) and trace whether every record in the procedure was actually created.
  • Compare time targets with real data. A deadline that’s constantly exceeded is either a capacity problem or an unrealistic target.
  • Check that the forms, folders and systems named in the procedure exist and that access permissions are correct.
  • Include this procedure in the sample of the first internal audit after publication.

A deviation found in verification is fixed in one of two directions: either the process changes to follow the procedure, or the procedure is updated to reflect the real and acceptable practice. For how the records the procedure produces turn into evidence, the evidence matrix guide is a good complement. If you want to set up these documents systematically in your organization, we put the template and ownership structure in place together in our corporate IT policies, procedures and work instructions work. Official information about the standard itself is on the ISO/IEC 27001 page.

Frequently asked questions

Do we need to write a separate procedure for every ISO 27001 control?

No. ISO/IEC 27001:2022 requires the organization to determine the documented information it considers necessary for the effectiveness of the ISMS. Risky processes, processes involving many people or where errors are costly are tied to procedures; simple controls can be met by a policy clause or a record template.

Can the procedure and the work instruction be in the same document?

For small processes that change rarely, yes. If the system interface changes often, keep the work instruction as a separately numbered document; the procedure flow stays fixed and only the instruction is updated.

Why use role names instead of people’s names in a procedure?

A person’s name makes the document invalid the day that employee changes and requires a revision with every leaver. When the role name matches the job description, responsibility continues independently of the person.

How do we know a procedure works?

Pick a real example from a past period; trace that every record defined in the procedure was created and the time targets were met. If records aren’t created or times are constantly exceeded, the procedure or the process needs fixing.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles