Risk and Resilience

Procurement Policy Has a Version: Why Old Evaluation Rules Create New Governance Risk

Why procurement templates, thresholds, weightings and tender rules need active version control as policy, law and organisational requirements change over time.

EraNorth Insights · 30 Aug 2026 · 6 min read

A procurement procedure can be followed perfectly and still be wrong if the rule itself is out of date.

The Week 9 source set contains two versions of Tasmanian weighted-tender guidance: an earlier 1999/2006 version and a later 2018 version.

They do not contain identical requirements.

The earlier version describes price weightings generally in the 60–90 per cent range, while the 2018 version shows a lower 40–70 per cent range and introduces a mandatory Local SME Industry Impact weighting for specified procurements.

The review threshold and debriefing-record guidance also differ between versions.

That comparison creates one of Week 9's strongest governance lessons.

Policy has a version.

The Strategic Context

Procurement organisations often rely on reusable assets:

  • tender templates;
  • evaluation spreadsheets;
  • contract clauses;
  • delegated-authority tables;
  • prequalification rules;
  • guidance notes;
  • training material.

Those assets improve efficiency.

They also create a hidden risk.

Once embedded in a template, an old rule can survive long after the policy that created it has changed.

Teams may believe they are following approved procedure when they are actually following an obsolete version.

What Leaders Commonly Misread

The first mistake is treating procurement templates as static documents.

The second is assuming an old government guideline remains current because the underlying principles still sound reasonable.

The third is copying numeric thresholds or weightings without checking their policy date.

The fourth is mixing historical teaching examples with current requirements.

The fifth is updating the policy library but leaving old spreadsheets and local copies in circulation.

Reframing the Issue

Procurement policy should be managed like a controlled technical system.

Every operational artefact should have:

  • owner;
  • version;
  • approval date;
  • review date;
  • source authority;
  • change history;
  • retirement process.

This is particularly important for numeric rules because they are easy to copy without context.

A spreadsheet containing a historical 3 per cent equivalency rule can appear authoritative years later.

Strategic Analysis

The Week 9 sources demonstrate policy drift directly.

The older Tasmanian material and the 2018 material use different thresholds, price ranges and debriefing practices.

That does not mean one source is “wrong”.

It means they describe different policy states.

ERANORTH should therefore not silently reconcile them into one rule.

Instead, the difference itself becomes evidence that currency must be checked.

The same applies to historical South Australian guidance, old tender codes and older legal teaching material.

Executive Trade-offs

Strong version control adds administrative discipline.

It also prevents much larger governance failures.

Organisations with decentralised procurement may resist central template control because local teams want flexibility.

The answer is not necessarily to centralise every decision.

It is to centralise the authoritative source of rules and make local variation explicit.

The enterprise should know which parts of a template are mandatory, recommended or adaptable.

Decision Framework

A procurement-control system should answer:

Authority

What current policy, law or standard supports this rule?

Version

When was the source last updated?

Ownership

Who is responsible for maintaining the template?

Propagation

How are changes pushed into spreadsheets, forms and training?

Retirement

How are obsolete copies removed?

Verification

Which high-risk rules require periodic legal or policy review?

Any historical rule used in the Week 9 material should therefore carry [FACT CHECK REQUIRED] until current authority is confirmed.

From Strategy to Execution

Immediate action: audit high-use tender templates for dates, thresholds, weightings, standards and legal statements.

Medium-term capability building: establish controlled template repositories with version history and named owners.

Long-term strategic positioning: connect procurement-policy changes to training, workflow systems and document generation so obsolete rules cannot remain hidden in local files.

This is especially important as procurement becomes increasingly automated.

Automation can scale a good rule quickly.

It can scale an obsolete rule even faster.

Governance Implication

Version control should extend beyond document repositories into procurement systems. Automated approval workflows, evaluation templates and generated tender packs can continue using obsolete thresholds even after policy has changed unless configuration is updated deliberately.

A strong change process therefore links policy revision to system configuration, training, template release and retirement of superseded material. The organisation should be able to identify which live procurements are affected by a rule change and whether transitional arrangements apply.

This is especially important where teams operate across several jurisdictions or business units with different requirements.

Signals to Monitor

Watch for staff using personal copies of tender templates, multiple versions of evaluation spreadsheets, references to superseded agencies or legislation, unexplained numeric rules and training material older than the policies it describes.

Questions for the Leadership Team

  1. Which procurement documents are authoritative?
  2. Who owns each template?
  3. How do policy changes propagate into operational tools?
  4. Which numeric rules are being used without a current source?
  5. How do we retire obsolete copies?
  6. Could our automated workflows be enforcing outdated policy at scale?

Closing Perspective

Procurement governance is not only about following the process.

It is also about knowing that the process being followed is current.

A controlled organisation manages policy changes with the same seriousness it applies to engineering drawings, financial controls or software versions.

Related article: Legal Precedent Is a Control System, Not a Copy-and-Paste Shortcut

Related article: Procurement Governance: Designing Probity, Authority and Control Without Creating Bureaucracy


About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.