Review generated content in the proposal editor against the buyer's requirements and your evidence, then read the export checks before you produce a final file. A fluent draft, a completed generation or a high estimated score does not replace human review.
Check the inputs
Open the RFP and verify its requirements, scoring criteria and deadline against the source. Review the assets selected for the proposal, especially dates, qualifications and project claims. In Analytics, use Library health to find review-due and expiring evidence that may need attention.
Review the draft
Read each section for requirement coverage, factual support and consistency. Correct unsupported statements and replace generic wording with verified evidence. Open the Requirements tab beside the section to investigate missing or partial coverage, and use the Assets tab to check the evidence the section draws on. A warning should lead you to the requirement and source, not simply to another generation attempt.
Check before export
Open Enhanced Export and read the checks under Pre-Submission Quality Gate and any submission findings. Resolve missing evidence, mandatory gaps and stale approvals before producing a final response. Where an authorized acknowledgment is offered, record it only after reviewing the specific reason. Use a Red Team review, which needs the Trial, Professional or Enterprise tier, to examine the draft against the published scoring grid, then assess its rationale rather than accepting the simulated score as a buyer decision.