Article
Policies, procedures and work instructions: what’s the difference?
Businesses often put policies, procedures and work instructions into the same folder without much thought. Then someone needs an answer and has to open five files to find it. A simple structure makes the information easier to write, use and maintain.
Start with the policy
A policy sets out what the business expects and why. It gives people a clear position on an important matter, such as workplace safety, privacy or handling customer complaints. Keep it short enough that a manager can explain it without reading from the page. A policy should not try to describe every task.
Use a procedure for the steps
A procedure explains how a piece of work is managed from beginning to end. It should say who does what, what happens next and which records are kept. For example, a complaints procedure might cover receiving a complaint, deciding who investigates it, responding and keeping a record. Write for the person doing the work, not for someone trying to impress a reviewer.
Write a work instruction where detail matters
A work instruction explains one particular task. It may show which settings to use on a machine, how to enter a record or what to check before a job starts. Pictures can help. If a competent person can do the task safely and consistently without a separate instruction, another document may not be needed.
Keep the three levels connected
Give documents sensible names and link a work instruction to the procedure it supports. Decide who owns each document and who may approve changes. Remove duplicate copies from shared folders. Ask a new employee to find a particular instruction: the time they spend searching tells you whether your structure works.
Review what people actually use
An unused document is not made better by a more complicated title. Ask staff which instructions are unclear, where they find conflicting advice and what has changed in practice. Update the source document first, then tell the people affected. Keep older versions out of everyday use while retaining the history you need.
Document Controller is intended to keep an approved current version, retain earlier versions and record which staff have acknowledged a document. Your business still decides what each document should say, who approves it and when it needs changing.
Planned for February 2027: try Document Controller free for 14 days.
This article provides general information only and is not legal or professional advice. Consider your own circumstances and get advice where needed.
More articles
- What an auditor may ask about document control
- How to record staff acknowledgements
- Prepare documents for document control
- Plan your audits before they are due
- Who should approve a work procedure
- How to tell field staff about changed procedures
- How to handle a nonconformance
- Corrective action that tackles the cause
- How to carry out an internal audit
- Make management reviews useful
- Managing risks and opportunities
- How to handle customer complaints
- Choosing and reviewing suppliers
- Keeping calibration records
- Do you need a quality management system?
- Document control for aged care and disability providers
- How often should you review your procedures?
- Moving from paper or shared drives without disrupting work
- Document control for construction and trades
- Inducting new staff on your procedures
- Quality records for manufacturers and engineering firms
- Contractor inductions: what to give contractors and what to record
- Food safety records that hold up in an inspection
- Version control without the chaos