Merge Tool 5’s drafted tender package and Tool 6’s compliance register into one submission-ready Final Tender, plus a Reasoning + References Pack for your agency’s own legal team — pure consolidation, nothing drafted new.
1 Import Upstream Context
Paste Tool 5’s Build Output and Tool 6’s Compliance Gate Summary into their own boxes below. Both are saved to this browser automatically as you type, so nothing is lost between sessions. If Step 2 finds a conflict later, resolve it by editing the text directly here — Tool 7 has no separate editing surface of its own.
2 Consistency & Conflict Check
Compares the two pasted sources for disagreement or overlap — e.g. a material Tool 6 flags as Not on Register, or an item named in Tool 6’s register that Tool 5’s text never mentions. This is a best-effort scan of what was pasted in Step 1, not a guarantee. Tool 7 never picks a side silently — every conflict below is resolved by editing Step 1’s text directly.
3 Section Mapping & Merge Plan
How the Final Tender document’s structure will be assembled — which source each section comes from — so you can review before anything is generated.
Budget & Pricing
Budget and pricing figures are external to Tool 7 (T7-OQ6, resolved 13 Aug 2026). This tool reserves the fields below for your agency’s own figures — it never sources, calculates, or drafts a value itself.
Supporting Documents Checklist
Plans, geology/geotechnical reports, contour maps, and soil profiles travel as separate files, never drafted by Tender Writer under any circumstance — the same rule Tool 5 already applies to drawings and geotechnical data. This checklist only tracks whether each has been supplied; it never generates content for one.
4 Generate Final Tender Document
Direct in-tool build of the consolidated, submission-ready Tender document from Steps 1–3. No external-AI step — this is mechanical assembly and formatting of content Tools 5 and 6 already produced, never new drafted content.
Complete Steps 1–3 above, then click “Build Final Tender.”
5 Generate Reasoning + References Prompt
Copy Prompt → External AI → Paste Back. Builds a structured prompt asking an AI to draft the Reasoning + References narrative — one tender section at a time — explaining why each section was drafted as it was, for your agency’s own legal team to review.
Routing reminder (Section 3, Principle 7 & 9): if the pasted Tool 5/6 text above carries any real budget, pricing, or other pre-release-sensitive figure, run this prompt in a local-only AI — e.g. Qwen via LM Studio — and paste it in as text, never upload it as a file. Otherwise any external AI (Claude, ChatGPT, Gemini) is fine.
6 Legal Pack Assembly & Output
Assembles the Reasoning + References Pack for your agency’s own legal team (T7-OQ3): the mechanically-generated VERIFY roll-up and Supporting Documents Checklist first, then the pasted-back reasoning, one tender section at a time.
Drafted this session, not yet independently verified. This pack is AI-drafted content until a human reviews it — never present it as a verified legal opinion. CDD’s process requires a mandatory human hand-QA pass on this pack before it goes to legal (T7-OQ4, resolved) — Tool 7 does not enforce a technical release gate itself.
Complete Step 5 above, then click “Build Legal Pack.”
