🖨 Print

Citations come from the PTS state law library, checked against each state’s official statute text as of the date shown. Laws can change after that date; confirm with counsel before formal action.

Contract Risk Review ratings. Each area is rated STRONG (protective, specific, enforceable), ADEQUATE (present but improvable), WEAK (present but vague, hedged, or below standard), or MISSING (absent entirely). The compliance score weights these (4/3/2/1) as a percentage of a perfect score across assessed areas.

Proposal Scorecard verdicts. Responsive — a specific commitment meets the RFP requirement; Partial — addressed but vague or below the standard ("industry standards" and "best efforts" without specifics are Partial at best); Non-Responsive — contradicts or clearly falls short; Silent — not addressed. Silence is never treated as compliance. Responsiveness weights mandatory ×2, scored ×1, informational ×0.5.

Evidence badges. ✓ VERIFIED IN DOCUMENT means the quoted language was mechanically confirmed in the source text. ⚠ CONFIRM AGAINST SOURCE means the finding is paraphrased — check it against the document before formal use.

The boundary. Reports document risk and responsiveness; they never recommend award, rejection, or execution. Those decisions rest with authorized procurement personnel and counsel.

Erosion statuses. Each RFP requirement is traced into the final contract: Preserved — a contract term meets it; Weakened — present but diluted, hedged, or below the requirement; Eliminated — absent or contradicted. Promise statuses. Each proposal commitment is tested for a binding contract term: Kept, Diluted, or Absent — a promise outside the contract is unenforceable.

Score. Lifecycle integrity is computed by fixed formula (Preserved/Kept = 1, Weakened/Diluted = 0.5, Eliminated/Absent = 0; RFP requirements weighted mandatory ×2). Analysis runs deterministically (temperature 0); contract evidence is mechanically checked against the source. Statutory references are drawn from the PTS state law library (checked against official state text); confirm with counsel. This report documents change across the procurement chain only — award and execution decisions rest with authorized personnel and counsel.

Verdicts. Each RFP requirement is scored against the proposal's actual language: Responsive — a specific commitment meets the requirement; Partial — addressed but vague, hedged, or below the stated standard (commitments to "industry standards" or "best efforts" without specifics are Partial at best); Non-Responsive — contradicts or clearly falls short; Silent — not addressed. Silence is never treated as compliance.

Score. The responsiveness percentage is computed by fixed formula, not by AI judgment: requirements are weighted (mandatory ×2, scored ×1, informational ×0.5) and verdicts valued (Responsive = 1, Partial = 0.5, Non-Responsive and Silent = 0). "Mandatory met" counts only fully Responsive verdicts. Analysis runs deterministically (temperature 0) for run-to-run consistency.

Evidence. Every verdict carries the proposal's own language. Excerpts are mechanically checked against the source document; verified excerpts are badged, and paraphrased findings are flagged for human confirmation.

Authority & boundaries. Statutory references are drawn from the PTS state law library (checked against official state text) and should be confirmed with counsel before formal action. This scorecard documents responsiveness only; it does not recommend award or rejection. Award decisions rest with authorized procurement personnel and counsel.

Only completed reviews consume credits. Partial, failed, and blocked runs are shown at no charge. This statement reflects the account ledger as of the generation date and may be used as a receipt of use for purchase-order documentation.