Tender & Submission Documents

Start with the truth about these documents: they are graded on completeness and compliance far more than on eloquence. A tender is typically assessed against a defined set of requirements - eligibility, technical response, methodology, forms, certificates, a priced return - and anything missing or non-conforming can be fatal regardless of how good the rest is. A statutory submission - a building-permit or development-approval application - must contain exactly the drawings, forms, certificates and reports the authority prescribes, in the format it prescribes. Miss one and the clock resets.

That makes the first and most valuable job a checklist, and checklists are something Claude builds fast and completely. Give it the tender notice or the authority's submission requirements and ask it to turn them into a structured checklist: every required document, form and certificate; every conformance rule (format, copies, signatures, order); every deadline and submission-mode instruction. Then ask it to map your current package against that list and flag what is missing or not yet conforming. "Here is the tender's instructions-to-bidders and here is our draft return - list every required item we have not yet provided, and every instruction we may not be meeting."

The crucial move is where the checklist comes from. Claude must build it from the actual notice or the authority's current requirements that you paste in - not from its own memory of what such submissions usually contain. Requirements vary by authority, by scheme, by year, and Claude's training cutoff means its general recollection may be outdated or generic. A checklist built from the real document is a powerful tool; a checklist built from Claude's assumptions is a false comfort. Feed it the source, always.

Used well, this turns the most dangerous part of the job - the silent omission - into a visible, trackable list. You still confirm the checklist against the source yourself, because a missed requirement is on you, not Claude. But you are now working against an organised list assembled in minutes rather than hoping you remembered everything at midnight before submission.

A tender return also has narrative to write: a technical response, a methodology or programme, a quality and safety approach, answers to the client's specific questions, often within word limits. This is real writing under time pressure, and Claude drafts it fast and well from your inputs - your actual approach, your real project experience, your genuine team. It will structure a methodology, answer each question in turn, hit the word count, and keep the tone professional and consistent across a long document.

The discipline is that the substance must be yours and true. Claude can shape and word your methodology; it cannot invent your track record. This is where a real ethical and practical line sits: never let Claude fabricate project references, certifications, personnel, turnover figures or compliance claims to fill a tender. It will happily generate plausible ones if asked loosely, and a bid built on invented facts is not just weak - in many procurements it is fraud, and it is discoverable. Give Claude your true material and let it present it well; that is the whole and honest use.

The same holds for statutory submissions, with the stakes higher still. Claude can draft covering letters, design statements, and the narrative parts of an application, and it can help you understand what a form is asking. It cannot certify anything. Structural certificates, area statements, fire and services compliance, and the professional declarations a submission requires are signed acts by qualified people who carry the liability - you, your structural engineer, your services consultant. Claude does not know your specific authority's current rules, cannot confirm a form is the current version, and cannot make a professional attestation. Draft and organise with it; certify and submit as the professional you are.

So the split is clean: Claude drafts the narrative and organises the package; you supply every fact, make every professional attestation, and never let a fabricated credential or an unverified requirement into a document that is graded on exactly those things.

The defining professional skill in this lesson is knowing where Claude's help stops and where a named human must take over - and building that gate into your process rather than discovering it after submission. There are a few places the gate always sits.

Legal terms and contracts. Tender documents carry contract conditions, warranties, indemnities, liability caps and dispute clauses. Claude can explain and draft these and flag ones that look onerous, which is genuinely useful for understanding a bid's terms. But committing to them, and any bespoke legal wording, is a lawyer's call - the exposure is real and Claude is not your solicitor. Statutory compliance and certificates. Whether a submission actually meets the code, and every certificate it carries, is a professional attestation by a qualified person; Claude can help you assemble and check for completeness, but it cannot tell you the design complies, and it must never be the basis of a compliance claim. Anything the authority or client alone can confirm. The current required forms, formats, fees and rules come from the authority; the specific evaluation criteria from the client. Claude's general knowledge is not a substitute for the source or, where needed, a direct query.

Being honest about this gate is not a weakness in the workflow - it is the workflow. A useful habit is to have Claude itself mark the gate: "go through this package and flag every item that requires a professional sign-off, a legal review, or confirmation from the authority, and who must provide it". It will produce a routing list - draft-and-done items versus must-be-signed items - that makes the hand-offs explicit. You confirm and act on it, but the package now carries its own map of where accountability transfers.

This honesty is also client-facing. When AI has helped assemble a submission, the professional position is unchanged: you are responsible for its contents as if you had typed every word, and the certificates carry the seals they always did. Claude changes how fast the package comes together, not who stands behind it. Module 10 takes up liability, disclosure and confidentiality in full; here, the operating rule is simply that the sign-off gate is real, it is named, and it is never delegated to a plausibility engine.

The loop, built for a deadline. One: source the requirements. Paste the actual tender notice or the authority's current submission rules; do not rely on Claude's memory of what is usually needed. Two: build the checklist. Have Claude turn the source into a structured list of every document, form, certificate, format rule and deadline, and confirm it against the source yourself. Three: draft the narrative. Feed Claude your true material and let it write the technical response, methodology and question answers to the word limits - facts and track record yours, wording its. Four: reconcile the package. Have Claude map your assembled documents against the checklist and flag gaps, non-conformances and inconsistencies across the set. Five: route the gate. Have Claude mark every item needing legal review, professional sign-off or authority confirmation, and get those from the named people. Six: final human read. You read the whole package as the professional submitting it - complete, conforming, true, signed - and send it.

The interiors version is the FF&E and fit-out tender: a package of specifications, schedules, drawings and terms sent to suppliers and contractors. The same rules hold - Claude builds the enquiry checklist and drafts the instructions and evaluation matrix, you verify product facts and lead times, and commercial terms and any warranty or liability wording go through proper review. A tidy-looking enquiry that omits a key spec or misstates a term costs real money at the wrong moment.

The honest close to the module: documentation is where a design becomes an instruction and a commitment, and it is Claude's strongest home - structure, boilerplate, consistency, completeness, checklists, all done fast and tirelessly. Across these four lessons the division of labour never changed. Claude drafts the specification, writes the BOQ description, orders the notes, builds the tender checklist. You prove every standard, count every quantity, confirm every code edition, supply every fact, and stand behind every certificate. It is a drafter, and a superb one; it is never the authority. Keep that line bright and Claude will give you back hours on exactly the work that used to eat your evenings - without ever putting your seal on something you did not check.