Keep Method Statements and Risk Assessments

Our method statements are reused from job to job without anyone reading them. Build me a method statement library. Keep one document per task type with the hazards identified, the control measures, the equipment required, the qualifications needed, the version and the review date. When it is used on a specific site, record any site-specific hazards or variations against that job rather than editing the master. Make the document easy to read on a phone on site. Record which crew members were briefed on it, when, and capture their acknowledgement. Add an AI agent that drafts a first version for a new task type covering the usual hazards and controls for that kind of work, always for a competent person to review and complete rather than to use as written, and that flags documents overdue for review or being used on sites whose conditions differ from what the document assumes. Automate three things: a review reminder before each document expires, a prompt to brief the crew when a job is scheduled, and a scheduled monthly report of documents in use that are past review. Two logins: a site lead who briefs crews and records variations, and a compliance owner who writes and approves documents.