tender compliance copilot

The problem

Tender packs and RFPs are high-stakes, document-dense projects where a single missed mandatory requirement or deadline results in immediate disqualification. Manual extraction of requirements into compliance matrices is slow, prone to oversight, and often lacks a clear audit trail back to source text.

What it does

• Extracts mandatory, scored, and informational requirements from PDF, DOCX, and XLSX files with direct source citations.
• Builds an editable compliance matrix mapping requirements to specific owners and evidence candidates.
• Identifies deadlines and submission instructions for human verification to prevent late entries.
• Facilitates a data-driven bid/no-bid process using weighted scorecards and hard-gate logic.
• Performs pre-submission QA to flag missing files, unresolved statuses, or duplicate documents in the final package.

Frameworks & tools

Python 3.x, pdftotext (Poppler), and standard library modules for ZIP/XML parsing of Office formats.

Why this beats prompting it yourself

General-purpose prompts often hallucinate certifications or lose track of document locators. This skill enforces a local-first, English-first workflow that treats every requirement as a cited object, ensuring you can always trace a claim back to a specific line in the original tender pack.

Use cases

• Generating a compliance matrix for an ITT or RFQ within minutes of receiving the bid pack.
• Matching company evidence folders against tender requirements to identify capability gaps early.
• Running a formal bid/no-bid workshop with structured weighted scoring.
• Automating final folder QA to ensure all mandatory submission attachments are present before upload.

Known limitations

Scanned PDFs require external OCR before processing. The CLI does not execute macros or calculate Excel formulas. All dates are marked as unverified and require human confirmation.