An RFP analysis was cut short

3 min readLast updated: Sep 23, 2026

Propivix's AI analysis reads an RFP's document text up to a fixed length. When an RFP is longer than that, the analysis still runs, but only on the first part, and Propivix tells you so. This article explains the warning and what it changes.

What the warning says

The warning appears on the RFP page after you select Analyze with AI or Re-analyze, or after you add documents on the Documents tab. It reads like this, with your RFP's own numbers:

"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."

You can close the warning. The footer of the Compliance matrix tab keeps the same fact on screen, for example "extraction covered 61% of the document text". That percentage is the share of the RFP's text the analysis read. It says nothing about how many requirements were found or how well your proposal answers them.

Why it happens

The analysis reads the first 100,000 characters of the RFP's combined document text. A long solicitation with its attachments can pass that limit.

Documents you add after the first upload, such as amendments or answers to questions, are placed after the original text. On a long RFP they are the first thing to fall past the limit. So the most recent changes to the solicitation are often the part that was not read.

Anything past the limit is invisible to the analysis. Requirements, dates and page limits that appear only there are not in the compliance matrix, the fact strip or the go/no-go analysis. Running the analysis again reads the same first 100,000 characters, so it does not make the warning go away.

What it means for your proposal

A proposal on an RFP with a cut-short analysis cannot pass the quality gate. The gate shows the same warning among its findings, and it does not pass while the analysis is truncated.

As a result, in the editor's Review & export dialog:

  • Prepare submission files is refused, because it requires the quality gate to pass.
  • Internal review draft still works. It downloads whatever is saved, with no checks.

See Exporting Your Proposal for the two export purposes.

What to do

  1. Find the part of the RFP that was not read. It is the end of the combined text, so start with the last documents you added and the final sections of the original.
  2. Read that part yourself and list any requirements, deadlines, forms or page limits it contains.
  3. Check your proposal answers each of them. The compliance matrix will not list them for you.
  4. Export an Internal review draft whenever you need a file for review or for your own final assembly.
  5. If you need help preparing submission files for this RFP, contact support. Include the RFP page address.

Re-analyzing an RFP describes the same limit from the RFP page's side.

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.