Do not project a current contractor suspension back onto every award date
Current eligibility, eligibility at award and an allegation’s disposition need separate evidence and review owners.
A current register does not describe every past state
Joining contracts to the latest eligibility list can make a present suspension appear to apply to every historical award. Using only historical records can miss a new review obligation. Truthound can check a ledger that keeps those dates and states separate. It does not determine whether a firm committed fraud, establish contract legality or interpret the legal effects of a programme suspension.
Review initiation is not an adjudication
GSA and SBA announced a review of federal contracts involving 689 suspended 8(a) programme firms on 21 October 2026. The release discusses potential fraud and an aggregate contract ceiling. Suspension is not an established fraud finding; a ceiling is neither payment nor proven loss. The evidence needed for an individual contract decision must be examined separately from those announcement-level quantities.
Retain the time to which a state applies
A proposed ledger separates firm identity, eligibility period, award date, current review state and evidence reference. A persistent identity needs confirmation even if a company name changes. Procurement and legal owners define period boundaries. If the start of an eligibility state is unknown, retain a clarification state rather than backfilling the present value across earlier dates merely to complete a historical join.
Apply a date check within its proper role
Truthound Core Python SDK 3.3.4 (open-source SDK, Polars backend) documents DateOrderValidator for specified date-column relationships and InSetValidator for an approved vocabulary. The operator first defines compatible meanings and null handling. These checks do not interpret eligibility law, establish the contract’s underlying facts or decide the nature of an alleged amount. Their result identifies whether the configured record conditions need correction before qualified review can proceed.
Two exceptions can require different actions
Not every old contract of a currently suspended firm has the same conclusion. Evidence of eligibility at the award date is still needed. Conversely, present valid eligibility does not remove every possible question about an earlier transaction. Record why each item is held and assign it to somebody able to answer that question. A common current-status label should not conceal those different obligations.
Start from the contract already maintained
Pandera 0.35.0 (MIT open-source Python DataFrame validation library; pandas, Polars and other supported backends) custom checks can express the same temporal and review-state rules. Retain a process that already maintains evidence and exceptions, comparing Truthound through whether the owner can recheck the result. Neither interface turns an agency allegation into a legal conclusion. Capability documentation is not an audit finding, demonstrated recovery outcome or proof that an institution should reach a particular conclusion about an individual contractor. The documented custom-check example uses a pandas Series; do not assume its predicate transfers unchanged to another backend.
Require an evidence trail before closing review
Begin with one contract for one firm and read the grounds for its eligibility period and present state. Do not guess where date or identity correspondence remains unclear. A completed review record should identify who examined which evidence. That distinction lets recurring contract review operate as accountable fact-checking, rather than an automatic join to whichever status happens to be most recent.
Conditions
Separate eligibility at award from current suspension and its review evidence.
Alternatives
A maintained Pandera 0.35.0 contract can retain the same temporal and review-state rules.
Limitations
Suspension is not a fraud finding, and a contract ceiling is not payment or loss.
Evidence
- Event checked
- Subject checked
- Modified
