The ACASS Due Date That Nobody Wrote Down
Contractor performance evaluations under the federal ACASS and CCASS systems are time-sensitive obligations. A Contracting Officer Representative who misses the evaluation window—either the due date for initiating the evaluation or the deadline for finalizing it—creates a compliance gap that becomes a problem at the next audit cycle, the next contract award review, or the next contractor protest. The ACASS/CCASS Due Date field in this template is there specifically because these deadlines are not self-managing.
The ACASS/CCASS Status field tracks the evaluation through six stages: Registered, Initiated, Drafted, Rated, Final, None. Each stage represents a distinct action in the evaluation workflow. A contract that has been Initiated but sits at that status for six weeks has stalled. In the Memento database, that stall is visible on a filter of contracts with ACASS Status = Initiated—a list that should be short and cycling, not growing.
Actual Versus Scheduled Performance: The Gap That Predicts Problems
Actual Performance and Scheduled Performance are two numeric fields representing percentage completion—what the contractor has achieved against what the schedule called for at the current project status date. The gap between them is the early warning signal for a contract that is drifting toward a completion date it won't hit.
A contract at 40% actual performance against 55% scheduled performance has a 15-point variance. At a $2.4M contract total, that variance represents a significant schedule lag that, if unaddressed, compounds as the project approaches completion date. Documenting both figures at regular status reviews creates a trend record. A gap that was 5 points at the last status review and is now 15 points is not the same situation as a gap that has been stable at 15 points for two consecutive reviews.
The Completion Date field anchors the performance comparison to a contractual deadline. When a contract shows both significant schedule variance and an approaching Completion Date, the Comments field carries the narrative: the contractor's corrective action plan, the government's position on schedule recovery, and any Contract Line Item Number adjustments that have been processed to extend the period of performance.
Status Lifecycle and the Contract Vehicle Link
Contract Status—Pre-Award, Awarded, Completed, Closed—tracks the contract through its full lifecycle. Pre-Award contracts are in the pipeline. Awarded contracts are active. Completed contracts have met their performance objectives. Closed contracts have been through the final administrative closeout, including ACASS evaluation, deobligation of remaining funds, and file disposition.
The distinction between Completed and Closed is procedurally important. A construction contract where all work is physically finished and the contractor has demobilized is Completed. The same contract after the contracting officer has processed all modifications, confirmed the final invoice payment, completed the past performance evaluation, and transmitted the file to the records repository is Closed. Filtering by Status = Completed surfaces the contracts that are administratively pending and need closeout action—a list that should not be long or aging.
Contract Vehicle links to a separate library entry, allowing the contract management system to reference the vehicle-level data—MATOC, IDIQ, BPA, or standalone—without duplicating it in every contract record. This matters when multiple contracts are awarded under the same vehicle and vehicle-level performance or ceiling limitations need to be tracked across all awards.
Project Manager and Contact Specialist fields create the accountability assignment. A PM with six active contracts shows up as such when the database is filtered by PM name. When a PM departs or rotates, the reassignment is visible across all affected contracts simultaneously.