Ingest
Save the request, contract, schedules, forms, briefings and addenda. Hash or version the files and record the official portal deadline.
Human-controlled automation
Let the machine organise. Let named people decide.
An LLM can read packs, build matrices, find gaps and draft from approved evidence. It does not choose the legal tenderer, invent proof, approve price, accept risk, sign declarations or lodge the bid.
The bid pipeline.
Keep the source pack immutable. Give every extracted claim a page, clause or official URL. Make uncertainty visible.
Extract
Pull out mandatory conditions, weighted criteria, deliverables, dates, pricing structure, declarations, licences, insurance and contract risks.
Trigger
Run value, buyer, work type, workforce, location, security, Indigenous participation and prequalification rules against the live pack.
Assign
Give every requirement an owner, evidence source, status and deadline. Mark hard fail, clarification needed or response opportunity.
Decide
Run bid/no-bid with the prime, specialists and commercial lead. Stop if mandatory capacity cannot be proven.
Draft
Write only from the approved evidence library. Separate confirmed facts, partner commitments, assumptions and proposed methods.
Review
Technical, legal, financial, safety, cultural, privacy and partner reviewers approve their own claims and departures.
Lodge
An authorised human checks the portal fields, filenames, declarations, time zone and final upload. Save the receipt and final lodged set.
Machine lane
Good automation work
- File inventory, text extraction and clause indexing.
- Requirements matrix and addendum comparison.
- Official-source checks and policy trigger suggestions.
- Evidence matching, gap lists and deadline reminders.
- Draft structure, word-count control and consistency checks.
- Filename, cross-reference and completeness checks.
Human lane
Authority stays here
- Legal tenderer, partner model and authorised signatory.
- Licences, professional opinions and engineering acceptance.
- Price, cashflow, insurance, tax and contract risk.
- Cultural authority, community claims and permissions.
- Conflicts, declarations and use of confidential material.
- Final approval, portal lodgement and contract acceptance.
The minimum data model.
Each opportunity should be readable by a person and a machine.
| Object | Required fields | Control |
|---|---|---|
| Opportunity | Buyer, portal ID, title, scope, value, close date, close time, time zone, briefing, contact, addenda. | Official portal is the source of truth. |
| Requirement | Clause, type, mandatory/weighted, response format, owner, due date, status. | Every row links back to source text. |
| Evidence | Claim, file, owner, approval, expiry, permitted use, confidentiality, source. | No evidence enters a draft without an owner. |
| Partner | Legal entity, ABN, role, workshare, price, licences, insurance, declarations, approval. | Partner approves its own material. |
| Decision | Bid/no-bid, reason, approvers, conditions, unresolved risks, timestamp. | LLM recommends; authorised people decide. |
| Lodgement | Final files, hashes or version IDs, signatory, portal user, submitted time, receipt. | Retain the exact lodged set. |
Start with the templates already in this repo.
Agent brief, requirements matrix, contractor profile and state/federal rules data.