The quality gate

5 min readLast updated: Sep 23, 2026

The quality gate is an automated check that must pass before Propivix prepares submission files. It looks for gaps such as unanswered mandatory requirements, unchecked claims and an RFP that was not fully read.

It sits in the Pre-Submission Quality Gate panel of the editor's Review & export dialog. Select Re-check to run it. It also runs when you choose Prepare submission files and select Check & download for final review, but not for an Internal review draft; see Exporting Your Proposal.

What the gate checks

The panel shows an overall score out of 100, a Pass or Needs Attention badge, and four figures:

  • Compliance: how well this proposal's responses cover the RFP's requirements, with mandatory ones counting double. Only a Compliant response with text scores fully.
  • Clarity: sentence length, very long sentences, lists and paragraphs.
  • Evidence: how often the text gives proof, such as figures, dollar amounts, projects and references.
  • Claim integrity: 100 when no section has unverified claims or an out-of-date claim review, minus 40 for each section that does.

The overall score weights compliance 40%, evidence 25%, clarity 20% and claim integrity 15%, over every section on the proposal. It is a set of automated text signals, not an evaluator's score, and it does not predict whether you win.

Why the gate blocks

The gate passes only when all of these are true:

  • The overall score is 75 or more, and compliance is 70 or more.
  • No mandatory requirement is missing. A mandatory requirement counts as missing when its response has no text, is marked Not Compliant, TBD or Needs Input, has no status, or is only Partial.
  • No section has unverified claims from its claim review.
  • No section's claim review is stale. A review goes stale when someone edits the section after it was reviewed and saves it with the section's own Save button. See AI Proposal Generation.
  • The RFP has at least one extracted requirement.
  • The RFP's analysis read the whole document. The analysis reads the first 100,000 characters; when the text is longer, the gate does not pass. See Truncated analysis.

The panel lists up to three missing requirements and four unverified claims, each linked to its place in the editor.

The server checks again when the file is requested and refuses a failing export with: "This proposal does not pass the submission checks yet. Download an internal review draft, or resolve the findings and try again."

Proposals without an RFP

A proposal not linked to an RFP has nothing to comply with. The gate scores clarity, evidence and claim integrity only, rescaled to 100, and says: "This proposal is not linked to an RFP, so compliance coverage was not checked." The Compliance figure in the panel does not count toward the score. The gate passes at 75 or more when no section has unverified claims or a stale claim review.

Fixing a blocked gate

The panel shows the first of these messages that applies. Each one, and what to do:

  • "N section(s) contain unverified or fabricated corporate claims (e.g. "…"). Remove or substantiate them against your asset library before submission - evaluators treat fabricated past performance as a disqualifier." Open each section listed under "Claims needing evidence". If a claim is true, add its proof to your asset library. Then regenerate the section with AI Generate so a new claim review runs. Saving a hand edit with the section's own Save button marks the review stale, which also blocks.
  • "Claims in this section have not been checked since it was last edited. Regenerate or review it before preparing submission files." Regenerate the section. The review runs only on English text of 100 to 24,000 characters, and only when time allows; otherwise the section stays unreviewed.
  • "The analysis read the first 100,000 characters of 164,000; 64,000 characters at the end were not analyzed. Documents added later, such as amendments, are appended at the end and may be missing from the extracted requirements and dates. Review them by hand." The proposal cannot pass while the RFP's analysis is truncated. Download an Internal review draft, and check the unread part of the RFP by hand.
  • "No requirements have been extracted for this RFP, so compliance cannot be assessed. Extract and map requirements before relying on this score." Re-analyze the RFP; see Re-analyzing an RFP.
  • "Resolve unanswered or non-compliant requirements before submission." and "Mandatory requirements are missing. Address all mandatory items to avoid disqualification risk." Open the Requirements tab in the editor's review panel, write each response and set its Compliance status.
  • "Improve readability by shortening long sentences and structuring content into clear paragraphs/lists."
  • "Add stronger proof points: quantified results, project references, and supporting evidence." Add specific results and references your assets support.
  • "N weaknesses cluster in …" Three or more gaps share one risk area, such as cost; address them together.

When you select Check & download for final review, the dialog names the first blocker it finds. Resolve that blocker, or download an internal review draft while you continue working.

After fixing, select Re-check.

Was this article helpful?

Still have questions?

Our support team is happy to help.

Contact Support
A clearer path to your next win

Ready to Apply This in Your Workflow?

Book a demo and we will walk you through setup with your team.