Review AI analysis against the source files

After this lesson you should be able to run Analyze solicitation on a saved company draft, open each cited file, and decide whether a quantity, deadline, missing-attachment flag, or conflict is actually in the source wording. You should treat Not found as a missing extract, not as permission to guess. You should also know that a declined, incomplete, empty, or timed-out analysis leaves your files and any previously saved result unchanged.

The on-screen notice states that the analysis is AI-generated from your company files, that a bidder must review it against the source documents before relying on it, and that it is not a bid, eligibility decision, or legal opinion.

Analysis runs only after files are stored on the draft. The button is Analyze solicitation the first time and Re-analyze documents after a result is saved. It reads PDF pages, including scans where the model supports them, Word paragraphs and tables from .docx, and Excel sheets from .xlsx, including displayed values and formulas. Macros are not executed. Word extracts do not invent page numbers. Older .doc and .xls files, and PNG or JPEG images, are stored and listed as skipped or not analyzed.

The result is saved on the draft and remains after refresh until the source files change or you save a new analysis. It shows what the agency wants; products and services with quantity, unit of measure, pack size, ordering period, specifications, and delivery; contract and ordering duration; deadlines with source wording, time of day, and time zone; eligibility; evaluation criteria; required documents; amendment acknowledgments; bid and proposal submission instructions; post-award invoicing and payment instructions; referenced attachments missing from this upload; per-file analysis status; unreadables; and conflicts across documents. Each cited line names a file and a page or locator, or Not found.

If a quantity looks converted from a pack or case count, a review flag tells you to keep the source quantity and unit. If unit of measure, pack size, time of day, AM/PM, or time zone is not in the source wording, the extract shows Not found or a flag and does not assume a zone. If saved analysis is outdated because files changed, the previous result stays on screen until a new analysis is saved. AsherGate has no control to edit a saved extract. If a line is wrong, keep the original document’s wording in your own notes, or upload the missing file and choose Re-analyze documents.

If the model declines the files, the product shows that AI analysis was declined, and that your files and any previously saved analysis are unchanged. You can still download and review the documents manually. If the run is incomplete, empty, filtered, or times out, AsherGate also leaves the stored files and the last saved analysis in place. Do not treat a failed run as a cleared draft.

AsherGate does not verify that the extract matches the PDFs. You do. Open the cited file, find the line, and keep or reject the extract in your own notes. There is no field to rewrite the saved analysis. If two files disagree, use the Conflicts across documents list as a starting pointer, then decide from the amendment or the controlling clause. Nothing in this step submits a bid.

Using the Larkspire story below, the RFQ PDF says responses are due 18 November 2026 at 4:00 p.m. Eastern Time. The first extract shows 2:00 p.m. and flags a missing time zone. Quantity shows 48 with no unit, while Attachment 1 says 48 each. Attch 2 is listed as missing. Conflicts notes the time mismatch after the bidder looks closer.

Open the RFQ PDF and keep 4:00 p.m. Eastern Time from the source wording in your own notes. Open Attachment 1 and keep 48 each. Upload Attch 2 Price Sheet.xlsx, choose Re-analyze documents, and confirm Attch 2 is no longer missing. Treat the first extract as unusable until those checks. Do not edit a saved extract. Do not submit a bid.