Standing RFP requirements: retain the test between bids

Convert repeated procurement discovery into a maintained customer-owned standard. The paper uses RFQs and RFPs to explain the missing asset: a reusable definition of value that new suppliers can contest.

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 outcome, permitted inputs and difficult exceptions.
  • Acceptance tests, cost measures, support and security requirements.
  • Review authority, change-control process and publication limits.

Decisions and sequence

  • State which information suppliers can see and reserve some tests from tuning.
  • Ask submissions to link evaluated versions with purchasable operating conditions.
  • Update the standard when the customer’s work changes and preserve the reason/history.

The first useful deliverable

A standing requirement with a versioned evaluation method, submission rules and authorized review process.

Failure modes to catch

A static statement of work alone does not make unlike services comparable. Avoid changing criteria silently to favor an incumbent.

How this follows the paper

Read The Independent Institution, sections 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