Comprehensive Acquisition Readiness Assessment

Record Identity and Evidence Cut

Start with a blank live record or load the illustrative example. All substantive input values are required for analysis; blank is unknown and zero is an asserted fact.

USD formatting is used for monetary results. The source register below records the actual input provenance. Dashboards require manual reconciliation; they do not pull data from other files.

1. Assumptions & Inputs

2. Executive Results

3. Analysis & Decision Signals

4. Category-by-Category Detail

5. Required Controls & Validation

6. Decision Triggers & Management Response

7. Action Register

8. Executive Review & Approval

Input Source and Reconciliation Register

For every numerical input or rating, record its source and accepted version, basis or calculation, preparer, reviewer and verification date. Include population, period, currency and accounting basis where relevant. Blank source cells identify unfinished evidence work.

Reconciliation and Unresolved Stop Conditions

Any edited entry clears the reconciliation marker. Mark it again after review. A manual stop raises the overall signal to red; it does not enforce an actual transaction restriction. Approval and signatures remain in the organization’s controlled decision records.

Operating Procedure and Working Example

Define the organizational assessment perimeter

The assessment lead identifies the buying entity, program scope, expected transaction range and cutoff. Finance, leadership, operating, people and legal owners review their questions independently before reconciling the six-category view. Keep the buyer’s household position separate; it is assessed through 02.17–02.19 and can constrain the program even when organizational scores are favorable.

Score capability with observed evidence

Use 0 for absent or unknown, 1 for initial work, 2 for developing documented capability, 3 for substantially implemented capability with bounded unfinished work, and 4 for implemented, tested and accepted capability. Identify exactly which question and source supports each answer. For a service not needed under the chosen scope, obtain reviewer agreement on a suitable demonstrated control rather than silently removing it from the fixed denominator.

Reconcile the six categories and eleven dimensions

Each five-question category is equally weighted; the total is the average of six category percentages. The eleven dimension tools ask different questions and use a different enterprise weighting, so their totals need not match. Compare underlying capabilities: strategy to 02.05; finance and funding to 02.06–02.07; leadership and governance to 02.08 and 02.10; operations and technology to 02.09 and 02.12; people and culture to 02.13–02.14; legal to 02.15. Explain any conflicting evidence or scope before certification.

Approve remedies rather than a cosmetic score

For every low answer identify the required capability date, work product, cost, funding, responsible owner, reviewer, backup and acceptance test. Use the manual stop control for an unresolved critical condition. A high category average does not cover an unstaffed or legally restricted critical task. Preserve original and reassessed scores with the source change that justifies the difference.

Worked reconciliation

Illustrative case: 29 answers at 4 and one at 0 yield 96.7 percent overall. The absent capability remains visible and the readiness tier is held for review. If it is a critical funding or authority task, activate the stop control and hold the affected spend. A divergence from the functional assessment is resolved by comparing the actual question, evidence, scope and date, not by averaging the two tools together.