Full launch: week of 1 February 2027. Build Partner places are open now

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.

Build Partner programme

Become a Build Partner

Build Partners help shape Document Controller for their industry, at 50% off for 12 months from the day your first card payment goes through: A$150.50/month + GST for 10 full users, instead of A$301/month + GST, and A$9.50/month + GST instead of A$19/month + GST per additional user, for businesses that apply by 31 December 2026. After that, 25% off for as long as they remain paying customers. The Build Partner discount covers the platform licence, the modules you lead and all your users, with no cap on the number of people, and excludes other modules, one-off services, usage charges, other non-subscription charges and Iridium AI Assistant Pro. Build Partners get guided setup and industry alignment with one of our team, their industry pack for the module they lead, as it's released, at their Build Partner discount, first access to new modules and direct input into what we build next.

Build Partner places are for businesses with 10 or more people, and we prefer 20 or more.

Document Controller is coming at launch. A small pilot with up to 3 Build Partners is planned from December 2026, and Document Controller is planned to go on sale from January 2027. We'll confirm your start date when we offer your place.