Policy & procedure software
- What keeping the register current costs
- $6,600
- Reviews a year
- 48
- Hours a year
- 120
Every figure printed on this site is arithmetic on the worked example we publish: a register of 48 procedures reviewed once a year at 2.5 hours each by a reviewer costing $55 an hour, 30% of it overdue today; and 12 processes with 4 procedures each, 60 staff of whom 40% are in scope for any one procedure, at 0.15 hours to read and sign, at $38 an hour. Change any of those on a worksheet and the numbers change with them. Nothing here is a market statistic and nothing is quoted from a third party.
Policy & procedure software is one search term covering two documents that behave differently. A policy says what the organisation requires and changes rarely, usually by a decision somebody senior signs off. A procedure says how a role does the thing and changes whenever the system, the supplier or the team changes, which is often. Managing them identically is why registers rot: the review cycle that suits one is wrong for the other. This page sets out how to treat them differently in the same register.
Open the Procedure management Free to use. No account, no card, no trial clock.
Separate the two, then link them
A policy sits above one or several procedures. Recording that relationship is what lets somebody answer why a procedure says what it says, which is the question that stops arguments about changing it.
Give them different review cycles
Policies rarely need annual attention; procedures frequently need more. A single cycle applied to both means either the policies waste reviewer time or the procedures go stale, and usually both at once.
Approve them at different levels
A policy change is a decision for whoever owns the risk. A procedure change is usually a decision for the person who does the work. Requiring the same approver for both is the fastest way to make procedure updates stop happening.
Attest to what applies, not to everything
On the worked example here, 48 procedures across 60 staff with 40% in scope for any one is 1,152 signatures and $6,566.40 of reading time per full cycle. Sending everything to everybody multiplies that by two and a half and gets less read, not more.
Policy & procedure software: what people ask
What is the difference between a policy and a procedure?
A policy says what is required and changes rarely. A procedure says how a role does it and changes whenever the system or the team does.
Should they be in the same system?
Yes, and linked, so anybody can see which policy a procedure serves. What they should not share is a review cycle or an approver.
How many signatures does a cycle need?
On the worked example, 1,152 across 48 procedures and 60 staff at 40% in scope, costing $6,566.40 of reading time.
Sopvo Pro
Keeping the register, not just the answer
You have the number. Pro keeps the register it describes: every procedure, its owner, its version and who signed for it.
- Keep a copy on your own machine, not just in ours.
- No Sopvo mark on anything you hand to staff.
- Close the tab mid-review and come back to it exactly as it was.
- Your organisation's mark on every printed procedure.
- Every procedure, version and signature out in one file, in one click.
- A new version announced to the people it applies to, from the register.
- Not used here: Sopvo takes no payments on your behalf.
- Not used here: a procedure register has nothing to post to a ledger.
$49per month, whole team
Start Sopvo Pro PricingSopvo Pro is $49 a month and renews automatically each month at $49 until you cancel. There is no minimum term and the price does not change on renewal.
Will it hold your register? Ask us about Policy & procedure software
Tell us how many procedures you have and where they live today.