Register the document
Add the document code, title, type, owner, review interval and first file version.
Document control guide
Control policies, procedures and SOPs without losing the trail.
Controlled documents are the files that explain how work should be done. Use document control when you need owners, versions, review tasks, approval history and acknowledgement tracking.
Recommended flow
Send for review
Choose a lead reviewer when the draft needs checking. Their review task and email link them to the workflow action.
Approve for use
Once the review is passed, an owner or admin can approve the version for use and trigger the next review date.
Keep history intact
Upload new versions rather than overwriting approved files. Review, approval and acknowledgement history stays visible.
Controlled document versus evidence
These two record types support different questions.
- A controlled document explains what should happen, such as a policy, SOP, form or template.
- Evidence shows what did happen, such as a completed checklist, certificate, photo, report or minutes.
- Approved versions should not be overwritten because the history may be needed later.
- Evidence can be linked back to the task, document or ISO register it supports.
Review workflow
The cleanest workflow keeps review tasks and document decisions connected.
- The owner is accountable for the document but does not automatically receive a review task.
- The lead reviewer receives one review task and should complete the review from the workflow panel.
- Request changes when a draft is not ready, then upload a revised version.
- Approving for use creates the next scheduled review based on the review interval.
Related guides
Important boundary
Obligary supports organisation and evidence. It does not replace professional judgement.
Use Obligary to manage tasks, owners, reminders, documents, evidence and reports. Your organisation remains responsible for deciding what applies and taking legal, regulatory or certification advice where needed.