Site Supervision Assistant

Problem Context

Building supervision work involves many repetitive, format-sensitive tasks: witness logs, supervision notices, meeting minutes, safety inspection records, document reviews, and site issue triage. These items often depend on templates, code references, meeting notes, and approved project plans, which makes manual drafting prone to missing fields, stale dates, weak citations, or inconsistent hazard classification.

Core Workflows

Site Supervision Assistant routes requests by keywords into practical workflows:

• Document generation: for inputs such as witnessing, concrete pouring, notice, or minutes, it collects required fields, locates templates under assets/, and fills .docx files using python-docx rules. Meeting minutes can include progress deviation analysis based on critical path references.
• Document review: for schemes, drawings, or contracts, it confirms scope and depth, checks completeness, compliance, and data correctness, then outputs A/B/C level comments with cited standards.
• Safety inspection: it structures checks around protective equipment, openings, scaffolding, formwork support, temporary electricity, lifting equipment, excavations, working at height, and fire safety, helping decide whether the issue needs verbal correction, a notice, or a stop-work order path.
• Consulting and renovation supervision: it can reference standard indexes for quality, safety, or schedule questions, and also support renovation quote risk review, stage acceptance, water-tightness tests, and contract addendum drafting.

Boundaries

The skill depends on local resources such as templates, project summaries, and references/规范条文索引.md. When templates or references are missing, the user must decide whether to generate from scratch. It is useful for drafting supervision documents, review checklists, and issue triage, but it should not replace a licensed supervision engineer’s judgment or automatically issue stop-work orders, payment certificates, or final settlement decisions.