Why This Register Exists Separately
The Contract Modification Log records what was executed — every P-number is a signed SF-30. That is the correct scope for that register, but it means a refusal can never appear in it: a request the Contracting Officer denies never becomes a modification at all. It stays an unexecuted request, and if the only register is the mod log, it leaves no trace.
This register holds the requests themselves — Requests for Equitable Adjustment (REA) under FAR 52.243-1 and Value Engineering Change Proposals (VECP) under FAR 52.248-1 — and records what the Government decided on each. Two were granted and became modifications; two were not. ⚠ This is a genuinely different instrument from an internal change control board. On a commercial program a sponsor decides against you. Here there is a counterparty with contractual authority, refusal runs in both directions, and a denial you accept is a cost you absorb rather than a scope item you drop.
Request Detail
Full Determinations
On 14 July 2026 the Contracting Officer directed acceleration of the identity-integration increment by three weeks to align with an agency communications event. The direction was issued as a unilateral change order; under FAR 52.243-1 the contractor performed as directed and submitted a Request for Equitable Adjustment afterwards. That sequence matters and is often misunderstood: the contractor does not get to decline a directed change and negotiate first. It performs, then claims.
What was claimed. $412,000 and 21 calendar days of schedule relief. The cost comprised overtime premium across 14 developers and 3 testers, a surge license uplift for the test environment, and two weeks of contracted UX capacity brought forward at short notice.
What the Contracting Officer determined. The full 21 days were granted without argument — the Government did not dispute that its own direction caused the schedule impact. Of the cost, $144,000 was granted and $268,000 denied. The denial rested on a single finding: the overtime premium was proposed at a blended rate that did not segregate hours which would have been worked under the baseline from hours genuinely additional to it. The determination did not say the cost was not incurred. It said the contractor had not demonstrated which part of it was attributable to the change.
Why it was accepted rather than claimed. Under the Contract Disputes Act the contractor could have certified the denied amount as a claim. It did not. The estimated cost of preparing and prosecuting a claim was $60,000–$90,000 against $268,000 in dispute, with no assurance of recovery on an evidentiary weakness that was the contractor's own. The deciding factor was recorded honestly in the file: the timekeeping was not good enough to win. The corrective action was a change to how directed work is booked — a separate charge code is now opened the day any change order is received, before work starts.
⚠ This is the entry a reviewer should read first. It is the one where the program lost money and the reason was its own recordkeeping, not the Government's decision.
The Authority to Operate for the production environment was scheduled for issue on 22 June 2026. It issued on 26 July 2026, 34 days late, for reasons wholly within the Government's control — a security control assessor was reassigned and no replacement was named for four weeks.
What was claimed. $196,000 and 34 calendar days. The cost was standby time for the integration team, which could neither deploy to production nor be redeployed to other work without breaking the sequencing of the increment behind it.
Why it was granted without reduction. Three things made this claim clean where REA-001 was not. The delay had a dated documentary trail the Government itself had generated. The affected labour was booked to a discrete charge code from the first day of standby. And the contractor had notified the Contracting Officer in writing on day 3 that a delay was accruing and costs were being incurred, rather than presenting a total at the end.
Executed as modification P00009.
⚠ Read REA-001 and REA-002 together. Same contract, same year, same Contracting Officer, opposite outcomes. The difference was not the merits and not the relationship. It was whether the contractor could show which hours belonged to the change.
Submitted under the Value Engineering clause, FAR 52.248-1. The proposal was to replace the commercially licensed eligibility rules engine with an open-source equivalent, eliminating approximately $340,000 per year in license cost for the remaining life of the system. Under the clause the contractor would have shared 50% of the saving in the year of implementation.
Why the Government rejected it. Two reasons, both sound. The replacement carried no FedRAMP authorization, so adopting it would have reopened an ATO that had just been obtained at the cost of a 34-day delay (see REA-002). And sustainment would transfer at the end of the task order to an agency team with no experience of the component — the saving was real, but it would have been paid for out of an operations budget the contractor does not carry.
Why it is recorded here even though it went nowhere. A register that shows only accepted proposals cannot distinguish a contractor who never offered savings from one whose savings were declined. ⚠ The VE clause is the one place in a task order where a contractor argues against its own revenue — accepting this proposal would have reduced the value of the contract to the firm proposing it. Recording the rejection is what makes the acceptance of VECP-002 credible.
CDRL A004 (Section 508 Conformance Report) and CDRL A006 (Accessibility Test Evidence Package) overlapped substantially: the same test results were formatted twice, reviewed twice, and commented on twice, on different cycles. The proposal merged them into a single deliverable on the A004 schedule.
Accepted, saving an estimated $62,000 of duplicated preparation and review effort, shared 50/50, and executed as an administrative modification. ⚠ The Government's acceptance turned on a point the proposal made explicitly: the merge removes a review cycle, not a piece of evidence. The agency receives the same artifacts, on the same standard, once. A VECP that reduces what the Government actually gets is a descope wearing a value-engineering label, and would rightly have been refused.
How to Read This Register
- A denial is not the end of the matter. Under the Contract Disputes Act the contractor may convert a denied REA into a certified claim. REA-001 was accepted as determined rather than claimed — the $268,000 was absorbed, because the cost of a claim exceeded the amount in dispute and the working relationship with the Contracting Officer was worth more than the recovery.
- A VECP is the contractor arguing against its own revenue. Accepting VECP-002 reduced the value of the task order. That is the point of the clause, and it is why a rejected VECP is worth recording: it shows value offered and declined, not value never proposed.
- Granted requests appear in both registers. REA-002 and VECP-002 became modifications and carry P-numbers; the request is recorded here, the executed instrument there.