Customer-controlled requirements: preserve purchasing power

Write the job and its acceptance method so they remain useful when the supplier changes. The paper’s central idea is that the customer retains the standard while developers, operators and experts compete around it.

Updated

Computraq is preparing for launch. These guides explain readiness and the proposed framework; they do not establish a live service, integration or partnership.

Prepare these inputs

  • Business purpose, permitted data and examples of acceptable work.
  • Known exceptions, review responsibilities and failure consequences.
  • The current cost baseline and rights needed to retain operating knowledge.

Decisions and sequence

  • Separate required outcomes from optional implementation preferences.
  • Define who can revise criteria, review evidence and approve spending.
  • Preserve the requirement, tests and decision history across renewal and migration.

The first useful deliverable

A customer-owned requirement record with versioned acceptance rules and explicit authority.

Failure modes to catch

If only the incumbent can explain or run the test, the customer may retain a document while losing practical supplier choice.

How this follows the paper

Read The Independent Institution, sections 3, 4, 14. The role and sequence above are practical preparation derived from those sections; any newly proposed commercial arrangement still needs its own confirmed terms.

Computraq participation status

Computraq is in prelaunch. This guide interprets the proposed operating model in The Independent Institution; it does not establish current hosting, paid booking, provider integration, partnership or a guarantee of service. Use the paper, original slides and expression-of-interest form to prepare a concrete contribution.

Sources and verification