When you prepare submission files, Propivix first runs an automated quality gate over the proposal. If the gate does not pass, the file is not produced. This article explains the refusal and how to move forward. The full list of checks is in The quality gate.
What you see
In the editor's Review & export dialog, you chose Prepare submission files and selected Check & download for final review. Instead of a download, the dialog showed one of these messages:
- "Resolve the fabricated or unverified corporate claims listed above before preparing submission files. You can still download a draft for internal review."
- "No requirements have been extracted for this RFP, so compliance cannot be checked. Extract requirements first, or download a draft for internal review."
- "Resolve the linked review issues before preparing submission files. You can still download a draft for internal review."
The server also checks the gate when the file is requested. If it does not pass there, you see: "This proposal does not pass the submission checks yet. Download an internal review draft, or resolve the findings and try again."
Two other messages stop a prepared export for reasons outside the gate: "The RFP calls for separate pricing. Assign sections and download the technical and pricing files separately." and "Some sections have no saved content. Review them before preparing submission files." See Exporting Your Proposal.
Keep working with a draft
A refused submission export does not stop you from sharing or reviewing the proposal.
- In the Review & export dialog, choose Internal review draft under Export purpose.
- Select Download draft.
A draft contains whatever is saved, including unfinished work, and runs no checks. Use it for team reviews while you fix the findings.
Find what is blocking
The Pre-Submission Quality Gate panel in the same dialog lists the findings. It shows a score, a Pass or Needs Attention badge, and up to three missing requirements and four unverified claims, each linked to its place in the editor. Select Re-check after each fix to see where you stand.
The most common causes, and where each fix is explained:
- Unverified claims in a section: a section's claim review found statements your library does not support. See Fixing a blocked gate.
- A section was edited after its claim review: saving an edit with the section's own Save button marks the review out of date, which also blocks. See AI Proposal Generation.
- Mandatory requirements without a complete answer: a mandatory requirement counts as missing when its response is empty, only partial, or not marked compliant. See Why the gate blocks.
- No requirements on the RFP: there is nothing to check compliance against. See Re-analyzing an RFP.
- The RFP's analysis was cut short: the gate cannot pass while part of the RFP was never read. See An RFP analysis was cut short.
- A low overall score: the gate also needs an overall score of 75 and a compliance score of 70. See What the gate checks.
What the gate does not mean
A passing gate does not mean the proposal is compliant with the solicitation, or that it will win. It is a set of automated checks on your saved text. A blocked gate does not mean the proposal is bad either; it means one of those checks found something to resolve or confirm. You remain responsible for the final solicitation's forms, portal rules and instructions.