- 01Notifiable jobs, flagged at creation
- Every project record carries an explicit F10 flag marking the job notifiable to the HSE, set when the project is opened and visible on the project detail page, the client portal and the staff mobile app, next to a second flag recording whether you hold the principal contractor position. Every notifiable job on the system can be listed at once rather than recalled. Sending the notification itself remains the client's duty. (Regulation 6)
- 02The construction phase plan, held and issued
- The project holds a dedicated area for the construction phase plan. Each plan is stored with its title, the original filename, the uploading user and the date and time, and it publishes to the client portal and the client app on upload, as a live file rather than an emailed copy, so a revision is an upload instead of a reprint and a delivery run. Drawing up the plan is the principal contractor's work. (Regulation 12)
- 03RAMS a named operative actually accepted
- RAMS are held per job, each with its documents and its own approval status, so the office reviews and approves before they reach site. The app checks that RAMS exist for the job before work proceeds, lists the current documents and lets the operative read them on the phone. When an operative reviews and accepts them the platform records who, which job, when, and captures a signature, tied to the document that was current that day. Most systems can show a document existed. Very few can show who accepted which version of it.
- 04Briefings signed one person at a time
- A toolbox talk is scheduled against a project and a named presenter, drawn from a library of prepared templates, delivered on site, concluded, then signed by each attendee individually on the phone screen, every signature stored with the exact time it was given. Attendance is recorded per person rather than as a head count, with a free text field so agency labour, subcontractors' operatives and visitors sit on the same register as employed staff. The app will not take a signature against a talk still marked as scheduled, so a register cannot be signed in advance.
- 05Permits raised before the work, not after it
- Hot work, work at height, task specific ladder and steps, lone working, limitation of access, and the four part safe isolation permit with its switching schedule. Each is raised on the phone on site and stamped with the time it was created and the user who created it, so a permit written up after the event shows that it was. The office can add, rename and reorder the questions without a code change or an app release, and every permit stores the questions and answers as they stood on the day, so a historic permit keeps the wording that was actually asked. The five site permit types are exposed read only to the client portal and the client app.
- 06Expiry watched, and one thing enforced
- The training matrix, the e-learning matrix and the staff certificate registers each hold a per person expiry date, banded onto one dashboard page with a thirty day window, which is where the competence evidence behind an appointment decision comes from. Subcontractors go further. A nightly job reads the certificate and insurance registers and removes any firm whose cover has lapsed from approved status, with the reason stamped on the record, which withdraws that firm from the subcontract order form, the small works order form and the labour planner. On one live deployment that automatic stamp sits on 62 of 164 subcontractor records. (Regulation 8)
What stays with you
Unibuild records, evidences and prompts. It holds and organises the information that goes into the health and safety file, with near miss and accident reports, sign-off records and site photographs retained against the project and their provenance intact. Risk assessment, competence decisions, professional judgement and statutory notification stay with the duty holder, which is where the regulations put them.