Engineering Bid Document Generator

Problem

Writing technical bid documents is often slowed down by two issues: tender requirements are scattered across clauses, scoring items, starred requirements, and disqualification rules; manually reusing templates can also miss the mapping between chapters and scoring criteria. Engineering Bid Document Generator targets technical bid documents. It accepts a Word/PDF tender file, generates a reviewable parse summary, then plans chapters around technical evaluation items and outputs a DOCX.

Workflow and Core Capabilities

• Parse gate: After parsing, it presents a summary of scoring items, starred clauses, disqualification red lines, and qualification requirements. If parsing is empty or fails, the process stops instead of forcing a template.
• Technical bid filtering: The workflow filters out commercial, pricing, formal review, and qualification items, so the output focuses on the technical bid without commercial pricing sections.
• Generation and self-check: The generation step reports output path, estimated page count, failed stages, scoring response rate, review risk score, risk detection rate, duplicate rate, and usability score, helping you adjust page target or enrich the enterprise knowledge base.
• Enterprise knowledge base: Company qualifications, personnel, project records, and equipment can be provided through data/user_knowledge_base.json; sample data should be replaced before delivery.

Boundaries and Cautions

The skill does not replace compliance review. Final documents must be checked by a human before submission. Qualifications, project records, personnel, and equipment must come from real knowledge base data; fabricating them is not acceptable. In LLM cloud mode, outbound data is masked automatically, and API keys should not be included in documents. If parsing fails, the file may need OCR or cleanup before rerunning.