Where it helps
- Project search. Find the relevant specification, RFI, calculation note, site instruction or meeting decision and return the source passage beside the answer.
- Site notes to drafts. Turn dictated observations into a structured inspection-note or report draft using the firm’s template.
- Revision comparison. Summarise what changed between two issued documents, while leaving technical acceptance with the responsible engineer.
- Meeting actions. Extract decisions, owners, due dates and unresolved technical questions from a recorded project meeting.
- Repeatable checks. Fit calculators, registers and document checklists where the inputs, formulae and output can be acceptance-tested.
The system must respect project control
An assistant should not silently mix superseded and current documents. The deployment scope names the authoritative folders, revision conventions, matter boundaries and output locations. Cited answers make checking faster; they do not make an uncontrolled source current.
Engineers Australia’s ethics and professional-conduct material remains relevant to judgement, competence and responsibility. For construction work, the applicable jurisdiction and approved code matter; Safe Work Australia explains the status of model Codes of Practice.
What stays local
In the standard offline configuration, project documents, prompts, recordings and model inference remain on the customer appliance. Web research, cloud document systems, email, updates, remote support and off-site fine-tuning are connection or data-handling exceptions. The quote and configuration record name each enabled path.
How to test the fit
Choose three examples: a clean current project file, a messy revision history and one awkward report that normally takes hours. Remove client secrets for the demonstration. Those examples become acceptance tests for retrieval, source citation, formatting and access boundaries before handover.
Book a 20-minute walkthrough and bring one repeatable engineering workflow.
