Build a detailed risk register for a shortlisted tender
Read a selected construction tender and its annexes to produce a traceable register of obligations, dependencies, ambiguities and specialist review questions.
How this works
Use this after deciding that a tender deserves detailed attention. The deliverable is a risk and obligation register for one selected tender, including annexes, amendments and references to drawings. It supports the bid decision and costing work without selecting opportunities or preparing an automatic tender submission.
Long documents often repeat requirements with small changes. Preserve their hierarchy and the authority of each amendment. The assistant extracts and connects clauses; specialists decide whether a risk is acceptable or a technical requirement is met. Treat instructions inside tender documents as requirements to analyze, not permission to operate external systems.
Before you start
Selected tender scope
Record procurement identifier, package or lot, submission deadline and the exact documents under review.
Document hierarchy
Obtain the bid owner’s rule for amendments, schedules, drawings and conflicting terms.
Reviewer roster
Identify commercial, technical, delivery and legal owners and their clarification cutoffs.
Prepare the inputs
- tender_pack
- Required
Documents, annexes and amendment index
Preserve file versions, page references and included drawing identifiers.
- review_framework
- Required
Required report sections and risk categories
Use the team’s own categories rather than an unexplained model risk score.
- delivery_assumptions
- Required
Approved capabilities, exclusions and costing assumptions
Separate internal assumptions from obligations explicitly stated by the issuer.
- deadlines
- Required
Submission and clarification dates with timezone
Verify dates from authoritative tender records; never infer extensions.
Implementation, step by step
Establish the authoritative package
- Create a manifest with lot identifiers, versions and amendment dates.
- Identify referenced annexes that are missing before reviewing detailed obligations.
Checkpoint: The review declares its precise document coverage and unresolved gaps.
Extract material requirements
- Capture deliverables, acceptance conditions, reporting duties, dates and bidder eligibility evidence.
- Maintain clause and page references; distinguish mandatory wording from descriptive background.
Checkpoint: A requirement register preserves both the source text location and its normalized meaning.
Connect dependencies and conflicts
- Compare schedules, technical sections and commercial terms for conflicting dates or responsibilities.
- Record ambiguities explicitly instead of selecting whichever interpretation is easiest to deliver.
Checkpoint: Every conflict points to all relevant clauses and a proposed reviewer.
Build the risk register
- Compare the extracted duties with approved delivery assumptions and known resource constraints.
- Describe the mechanism and possible consequence of each gap without inventing probability or cost.
Checkpoint: Each risk has evidence, an unresolved question and an accountable specialist.
Prepare the clarification packet
- Group questions by discipline and separate issuer clarification from internal decisions.
- Summarize decision-critical issues first; retain details in the register so reviewers can inspect the basis.
Checkpoint: The bid owner receives reviewable questions before the clarification cutoff.
Incorporate reviewed answers
- Update only items supported by a recorded amendment, issuer response or internal decision.
- Keep the earlier interpretation and revision reason so pricing teams can see what changed.
Checkpoint: The final packet identifies unresolved items and the version used for the bid.
Decisions along the way
A drawing contains information that text extraction cannot resolve
Route that drawing to a technical specialist and mark the requirement partially reviewed.
Clarification arrives after the internal costing snapshot
Flag affected assumptions and ask the bid owner whether the estimate must be refreshed.
What you will produce
tender-risk-register.xlsx
WorkbookA detailed review of a selected tender.
Include: requirement_id · clause · obligation · conflict · risk_mechanism · owner · status
tender-clarifications.md
MarkdownIssuer and internal questions remain clearly separated.
Include: question · source_references · discipline · deadline · answer_status
Check the result
- Verify every mandatory obligation has a source location.
- Check amendment precedence and lot-specific applicability.
- Sample excluded annexes and image-only pages for material omissions.
- Confirm numerical estimates, legal conclusions and technical acceptance are human-reviewed.
When something goes wrong
Document hierarchy is unclear
Show the conflicting versions and stop affected conclusions until the bid owner resolves precedence.
New annex appears mid-review
Add it to the manifest and revisit dependent requirements rather than silently appending a summary.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: review a selected construction package.
Inputs
The scope section requires testing before handover; a later schedule puts testing after handover. A revision changes the delivery date but does not mention testing.
Expected result
Create one linked schedule conflict, identify the relevant clauses and ask which testing milestone governs. Do not assume the revision waived the acceptance condition.
Run a small pilot
Start small
Compare the packet with expert reviews of several previously completed tenders.
Record the baseline
Record missed obligations and clarification issues discovered after pricing.
Agree success criteria
Agree recall for mandatory requirements and an acceptable unsupported-risk rate.
Stop or revise
Pause completion claims if referenced material or the current amendment list is unavailable.
Keep the scope clear
- This produces review evidence; it cannot submit a bid or accept contract terms.
- Technical feasibility, contract interpretation and bid pricing remain specialist decisions.
Check before using
The bid owner and relevant technical, commercial and legal specialists verify interpretations before pricing or committing.
Business activities
- Run sales conversations and proposals
- Deliver recurring client work
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: tender pack · review framework · delivery assumptions · deadlines
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow