Software supports compliance workflows. People still own the responsibility.

A risk assessment and method statement is a working document about how specific work will be carried out and what is being done about the risks involved. Its value comes from the competence of the people who prepare and review it, and from its relevance to the actual work and site conditions.

Built Still supports the distribution of prepared RAMS documents, the recording of acknowledgement, and the retention of the resulting record. It does not generate RAMS, does not review them, and does not assess whether a document is suitable, sufficient or adequate.

An acknowledgement recorded in the platform confirms that a person was issued with a document and indicated they had received it. It does not establish that the person understood it, was competent to carry out the work, or that the method described is appropriate.

Toolbox talks are short, practical briefings delivered to people about to carry out work. What makes them effective is the relevance of the topic, the competence of the person delivering it, and the attention of the people receiving it.

Built Still records that a talk took place, what topic was covered, who attended and who acknowledged it. It makes no assessment of the content, the delivery or the effectiveness of any talk.

Selecting appropriate topics, delivering them properly, and deciding how frequently they are needed remain matters for the business.

Site inspections vary enormously in purpose, scope and formality. Some are general walk-rounds. Others must be carried out by a specified competent person and recorded in a particular way.

Built Still provides a structure for recording checks. It does not determine what should be checked, how often, or by whom. Checklists must be appropriate to the activity and should be completed by appropriately competent persons where required.

Inspection records support documentation but do not themselves establish that work, equipment or a workplace is legally compliant or safe. A completed checklist is evidence that a check was carried out and what was recorded at the time — nothing more than that.

Recording an incident and responding to an incident are different activities. Built Still supports the first. The second — securing the area, caring for people, investigating, escalating and reporting — is carried out by people, according to the business’s own procedures and legal obligations.

Incident logging supports structured record keeping and follow-up. Separate statutory reporting, investigation and legal requirements may apply, and whether they apply in a given case must be assessed by the business and its advisers.

The platform does not notify regulators, does not submit statutory reports, and does not determine whether an event is reportable.

Photographs associated with a record help a reader understand what the person recording it was looking at. That is genuinely useful, and it is also the limit of what is being claimed.

Built Still associates photographs with the record and item they were captured against, together with the time the entry was made. It makes no claim about geographic location, device verification, tamper resistance, chain of custody or cryptographic proof.

Photo evidence and digital sign-off support the record but should not be described as automatic proof of legal compliance.

Digital sign-off can support acknowledgement and completion records where configured. Legal requirements for signatures, consent, competence and record keeping vary by context, and a signature recorded in software does not automatically satisfy every requirement that might apply.

Where a particular form of signature, witness or approval is required, that requirement is unaffected by the platform. Businesses should take their own advice on whether an electronic acknowledgement is adequate for their purposes.

No claim is made regarding biometric authentication, identity verification or the legal status of any signature captured.

Competence is about the combination of training, knowledge, experience and ability to recognise limits. Software cannot supply any of those, and cannot assess whether a person has them.

Built Still records who did what. It does not verify qualifications, check cards, confirm training currency or determine whether a person is competent for a particular task.

Decisions about who is competent to prepare, review, approve, supervise or carry out work remain entirely with the business.

Site compliance records frequently contain personal information: names, roles, attendance, acknowledgements and sometimes accounts of events involving identifiable individuals. Occasionally they contain information about a person’s health.

Where a business uses a deployed product to hold such records, that business is ordinarily the data controller for the information it collects. Decisions about what is collected, who may see it, how long it is kept and how it is disposed of are decisions for that business.

Information submitted through this website is a separate matter and is covered by our privacy policy.

Privacy policy →

Construction and trade work in the United Kingdom is subject to an extensive framework of legal and regulatory requirements. Which of those apply to a given business, project, activity or role depends on the specific circumstances.

Nothing on this website is legal advice, health-and-safety advice or professional advice of any kind, and nothing here should be relied on as a statement of what the law requires in a particular case.

Built Still holds no approval, certification or accreditation from any regulator or scheme, and makes no claim that using the platform will satisfy any legal duty, pass any audit or meet any scheme requirement.

A business using Built Still remains responsible for the accuracy and completeness of the information it records, for configuring the product to suit its own processes, and for making sure the people using it understand what is expected of them.

The platform reflects what is entered into it. Where records are incomplete, inaccurate or not made at all, the resulting record will reflect that.

Site managers, supervisors and duty holders remain responsible for real-world safety on site, regardless of what is recorded in any system.