Enterprise policy management software: the 4 things that change above a few hundred people

Updated

Enterprise policy management software is genuinely different from the small-organisation kind, and it is worth knowing which side of the line you are on before shopping, because the price difference is large and the features that justify it are ones a smaller organisation will never touch. Four things change above a few hundred people. If none of them describes you, you are looking at the wrong shelf, and this page says so plainly.

One: several registers that have to stay separate

Multiple legal entities, countries or business units, each with its own policies and its own approvers, and a group function that needs a view across all of them without merging them. That is a real structural requirement and it is the clearest single reason to buy at the enterprise end.

Two: identity and joiners at volume

Single sign-on, automatic provisioning from the HR system, and attestation obligations that appear when somebody joins a department without anybody creating them. Below a few hundred people this is a spreadsheet somebody checks monthly; above it, it is not.

Three: retention and defensible deletion

How long superseded versions and signature records are kept, and the ability to show a schedule rather than a habit. The National Archives publishes general records schedules for exactly this reason, and a large organisation is usually asked to demonstrate one.

Four: translation and jurisdiction

The same procedure in several languages, with the signature bound to the version the person actually read, and local variants where the law differs. This is where enterprise pricing genuinely earns itself, and where a small tool should honestly decline. Below all four, the worked example holds: 48 procedures, 120 review hours and $6,600 a year.

Questions people ask about enterprise policy management software

When is enterprise software actually justified?

Several separate registers, SSO and automatic provisioning, a retention schedule you must demonstrate, or multilingual versions.

What if none of those describe us?

Then you are looking at the wrong shelf and paying for problems you do not have. A register of 48 procedures is a small tool's job.

Can a small tool grow into it?

Up to a point. Separate registers per legal entity and multilingual attestation are structural, and they are the honest limit.

Sources

Related answers

Keep the register: start Sopvo ProStop guessing which version is current: start Pro