A paper on change control authority for enterprise planning platforms

Was what's running approved?

Practitioners running Anaplan at scale report

100 to 400hours a quarter preparing for audit
20 to 30%of the platform team's engineering capacity maintaining the tooling behind it

The approvals were given. The promotions were performed correctly. The time goes to reconstructing a record of something the organization already did right.

When approval and promotion run through one governed workflow, the evidence is a byproduct of the work. The auditor's question becomes a retrieval that takes minutes, not a reconstruction that takes weeks.

Eleven pages · Specific to Anaplan · No form, no email required

Getting the hours back, in seven points

  1. 01Every Anaplan change follows a process. It is manual, it compresses under deadline pressure, and it produces evidence only when someone assembles it.
  2. 02A log answers what changed. An auditor asks whether it was authorized, tested, approved by someone other than its builder, and still matches what is running.
  3. 03Application Lifecycle Management governs model structure reliably. Pages, roles and tenant configuration change where they run, outside it.
  4. 04Three conditions a landscape can test: authorization attached to the change, nothing reaching production outside the path, and what was approved being what is running.
  5. 05Conventional software keeps the approval record outside the system it governs, so the two can be compared.
  6. 06Today the work is done twice, once at approval and again for the auditor. When the evidence is a byproduct of the change, the second time is avoidable.
  7. 07The question an auditor asks once a year is the one a user asks when a page looks different from last week. A landscape that meets the three conditions answers both without assembling anything.