Tender Intelligence QA

Tender Intelligence QA is a dedicated quality review that runs across your entire tender response. It analyses your answers for issues that are hard to spot manually — weak coverage, tonal inconsistencies, scoring criteria missed, and gaps in evidence — and surfaces them as actionable findings.

When to use it

• After bulk generation — to quickly identify which questions need the most attention.
• During refinement — to check whether your edits have addressed the issues from a previous audit.
• Before submission — as a final quality gate to catch anything you may have missed.
• Run QA at least once before export; ideally run it twice (once after generation, once after your editing pass).

How to launch QA

• Open the project page for the tender response.
• From the Status tab in the right-hand sidebar, click Run New Audit, or look for a Tender Intelligence QA button in the top actions area.
• The audit runs as a background job. A progress indicator will show. For large responses this may take a couple of minutes.
• You will receive a notification when the audit is complete.

Reading the report

• Open the full report using Open full report. This shows a question-by-question breakdown with findings.
• Each finding includes a category (tone, coverage, scoring, evidence) and a description of the issue.
• Severity indicators help you prioritise: address high-severity findings first.
• An overall score or confidence indicator gives you a summary read on the response's readiness.

Acting on findings

• Where findings link directly to a question, click through to open that question and make changes.
• For tone findings, ask the AI Assistant to rewrite the section to match your writing style guidelines.
• For coverage gaps, check whether the Content Vault has relevant material — if not, add it and regenerate.
• For scoring criteria missed, look at the question text carefully and ensure your answer addresses every point the buyer is looking for.

Re-running QA

• After making edits to several questions, run a fresh audit to see whether the issues have been resolved.
• Each audit run is independent — previous reports are stored so you can compare before and after.
• A clean second audit (with no high-severity findings) is a good signal that the response is ready for export.