Skip to content
All projects
Illustrative exampleGovernance

Policy and SOP Framework

A document system for a growing company: a clear hierarchy from policy to form, version control for every document, and a RACI that says who does what in each procedure.

Illustrative examplePolicies & SOPsRACIDocument controlExcel
Illustrative example, no company data. It shows the kind of governance deliverable I build, with invented roles, limits and figures.

1Problem

Procedures live in people’s heads and in old emails. Two departments follow two versions of the same process, new employees learn by asking, and nobody can say which document is the current one.

2Data

  • Inputs: process walkthroughs with each department, existing forms and the delegation of authority.
  • Illustrative example, no company data. Document names, codes and owners on this page are invented.

3Approach

  1. 01Define four document levels: policy (the rule), procedure (who does what, in which order), work instruction (how to do one task) and form (the record).
  2. 02Give every document a code, an owner, a version number, an effective date and a review date.
  3. 03Write each SOP in one template: purpose, scope, steps, controls, records and related documents.
  4. 04Add a RACI to each procedure: responsible, accountable, consulted and informed.
  5. 05Keep a document register with status: draft, in review, approved or retired.
  6. 06Set a review cycle, so every document is confirmed or updated on schedule.

4What was built

  • Document hierarchy: policy, procedure, work instruction, form
  • Document register with codes, owners and status
  • Version control: version, effective date, next review
  • One SOP template for every department
  • RACI matrix per procedure
  • Links between each SOP and the approval matrix

5Result

  • One current version of every process, known to everyone.
  • New employees are trained from documents, not from memory.
  • Audits start from a register instead of a search.
Chat on WhatsApp