Tender Document Smart Reader

Problem

Tender documents are long, clause-heavy, and easy to misread. A bidder may miss disqualification red lines, scoring weights, or bid-control signals before deciding whether to participate.

How It Works

The skill structures the tender workflow around three capabilities:
- Smart interpretation: accepts .pdf, .doc, or .docx tender files and extracts project information, eligibility items, disqualification red lines, scoring criteria, key requirements, commercial terms, pricing requirements, and procurement background, plus bid-control signals and participation advice.
- Bid document drafting: after interpretation, it selects a package, generates an outline, fills standard sections, and outputs a .docx bid document with table of contents, chapters, and pending-field bookmarks.
- Compliance review: against the interpreted tender, it checks one or more bid documents, classifies risks, cites tender clauses, locates evidence, suggests edits, and detects duplication across files.

The outputs are chained: interpretation can lead to drafting, drafting can lead to compliance review, and review can lead to re-checking after fixes. For partial inputs or generic questions, it can answer common bidding concerns first and then ask for a full file path or upload.

Boundaries

Tender files and bid files have size limits. Draft generation can take time, and uncertain information may be left as pending fields. Compliance findings such as to-review items or partial results are not the same as a clean pass. Report export, platform balance, and credit rules should be confirmed before running production work.