Steel erection — Level 2
Issued
Illustrative interface — example data
- Operative A Steel fixer Signed 07:46
- Operative B Steel fixer Acknowledged 07:52
- Operative C Banksman Viewed 08:04
- Operative D Plant operator Issued 07:31
Site control board / Live record
Capture the record
while the work
is happening.
Built Still helps construction and trades businesses manage RAMS, toolbox talks, inspection checklists, incident records, photo evidence and digital sign-off through practical mobile-first site workflows.
- RAMS
- Talks
- Inspections
- Incidents
- Evidence
- Sign-off
Site 01 / Today
Illustrative interface — example data
- RAMS Issued
Steel erection — Level 2
2 acknowledgements outstanding
07:31 Rev 03 RMS-0412 - Toolbox talk Complete
Manual handling
8 signed
08:02 Talk TBT-0088 - Inspection Attention
Weekly site check
3 items require attention
- AccessPass
- HousekeepingAttention
- Work areaAttention
10:18 Check INS-1140 - Incident Record open
Near miss — loading area
Follow-up action assigned
13:44 Log INC-0031 - Evidence 4 photos
Attached to inspection
10:21 Photo 04 EVD-0219 - Sign-off Recorded
Daily record closed
16:12 Signed SGN-0077
Sheet 01 / Site activity to site record
Work happens. The record should happen with it.
Every stage below is a point where information usually gets written on paper, remembered, or lost. Built Still is built around keeping that sequence intact.
- 01 Work
Actual task occurs
The activity happens on site, at the point of work, in real conditions.
- 02 Check
Appropriate site check
The relevant check or record for that activity is opened on a mobile device.
- 03 Capture
Information & evidence
Details, notes and photographs are captured while the work is still in front of you.
- 04 Acknowledge
Reviewed by the relevant person
The relevant person reviews or acknowledges what has been issued to them.
- 05 Sign
Digital sign-off where configured
A digital sign-off is recorded where that step is part of the configured workflow.
- 06 Record
Structured record retained
The completed record is retained in a consistent, retrievable structure.
Sheet 02 / One field system
One field system, not six separate habits.
RAMS, talks, checks, incidents, photographs and sign-off usually live in six different places. Built Still is designed so they share one structure, one record and one place to look.
- 01 RAMS Distribute, review, acknowledge and retain method statement records.
- 02 Toolbox Talks Record the talk, the attendance and the acknowledgement in one place.
- 03 Site Inspections Repeatable site checks captured as structured, reviewable records.
- 04 Incident Logging Capture the facts, the immediate action and the follow-up status.
- 05 Photo Evidence & Sign-Off Attach what was seen and record what was acknowledged.
Sheet 03 / RAMS
Get the RAMS to the people doing the work.
A method statement sitting in an office folder is not reaching the operative on Level 2. Built Still is designed to move that document to the people carrying out the task, and to keep a record of who acknowledged it.
RAMS workflow
- 01 Upload / prepare
- 02 Issue
- 03 Review
- 04 Acknowledge
- 05 Sign
- 06 Record
- Toolbox talk
- TBT-0088
- Date
- Example date
- Topic
- Manual handling
- Attendees
- 8 recorded
- Acknowledgement
- 8 of 8
Signature
Status Signed
Conceptual product view
Sheet 04 / Toolbox talks
Deliver it. Record it. Know who acknowledged it.
The talk happens at seven in the morning in the car park. The sign-in sheet ends up in a van. Built Still is designed so the topic, the attendance and the acknowledgement stay attached to the same record.
Toolbox talk workflow
- 01 Select
- 02 Deliver
- 03 Attend
- 04 Acknowledge
- 05 Sign
- 06 Store
Sheet 05 / Site inspections
Turn repeat site checks into structured records.
The same walk-round, done weekly, written differently every time. A repeatable checklist produces records you can actually compare, search and follow up.
Weekly site check
Check INS-1140Illustrative interface — example data
| Item | Status | Comment | Evidence |
|---|---|---|---|
| Access | Pass | — | — |
| Housekeeping | Attention | Material stacked in walkway | 2 photos |
| PPE | Pass | — | — |
| Work area | Issue | Edge protection to be reinstated | 1 photo |
| Equipment | Pass | — | — |
| Documentation | N/A | Not applicable to this visit | — |
- Pass
- Attention
- Issue
- Not applicable
Comments · Evidence · Follow-up · Completion · Sign-off
Sheet 06 / Photo evidence
Attach the evidence to the record.
A photograph on someone's camera roll is not a record. A photograph attached to a specific inspection item, with a note and a time, is one.
Sheet 07 / Incident logging
Record what happened while the detail is still fresh.
Detail fades within the hour. A structured entry captured at the time gives the business something consistent to review, act on and retain.
Incident record
Log INC-0031Example data — not real site information
- Date / time
- Example date · 13:44
- Location
- Loading area, ground level
- Description
- Example description of what was observed at the time.
- People involved
- Recorded against the entry
- Photo
- 1 photograph attached
- Immediate action
- Area cordoned and supervisor notified
- Follow-up
- Action assigned with a review date
Status Follow-up assigned
Sheet 08 / Digital sign-off
Create a clear record of acknowledgement.
Who was issued with it, who opened it, who acknowledged it and who signed. Four states, recorded consistently, rather than a signature sheet nobody can find.
- 01 Issued
- 02 Viewed
- 03 Acknowledged
- 04 Signed
Illustrative interface — example data
| Person | Document | Date | Status | Signature |
|---|---|---|---|---|
| Person A | RAMS — Steel erection | Example date | Signed | |
| Person B | RAMS — Steel erection | Example date | Acknowledged | Not signed |
| Person C | Toolbox talk — Manual handling | Example date | Signed | |
| Person D | Weekly site check | Example date | Viewed | Not signed |
| Person E | Weekly site check | Example date | Issued | Not signed |
Sheet 09 / Site evidence timeline
One day, as a site record.
This is what a structured day looks like when the record is captured as the work happens rather than reconstructed on a Friday afternoon.
Illustrative interface — example data
- 07:31
RAMS issued
Method statement issued to the working party.
Issued - 07:46
RAMS acknowledged
Acknowledgement recorded against the document.
Acknowledged - 08:02
Toolbox talk completed
Topic, attendance and acknowledgement stored together.
Complete - 10:18
Site inspection recorded
Repeat checklist completed; three items flagged.
Attention - 10:21
Photo evidence attached
Photographs associated with the flagged items.
Evidence - 13:44
Action updated
Follow-up action progressed and noted.
Attention - 16:12
Record closed
The day’s record retained in a consistent structure.
Recorded
Sheet 10 / Field use
Built for the point of work.
Site software fails when it is designed for a desk. These are the design principles Built Still is built around — how the interface behaves, not claims about what your device can do.
- 01
Large touch targets
Controls sized for gloved hands and awkward positions, not office mice.
- 02
Concise actions
Short, obvious steps rather than long forms that get abandoned halfway.
- 03
Structured forms
Consistent fields so two people recording the same thing produce comparable records.
- 04
Fast record entry
The quickest route from noticing something to having it written down.
- 05
Photo capture
Photographs taken against the record they belong to, not separately.
- 06
Status clarity
What is outstanding, what needs attention and what is done, stated in words.
- 07
Site-first navigation
Organised around what is happening on site rather than around an admin menu.
- 08
Minimal admin friction
Less to re-key later, because it was captured properly the first time.
Open items
- RAMS ack. 2 open
- Inspection 3 items
- Talk Complete
Add photo
Attach to item 04
Conceptual product view
Sheet 11 / Construction & trades
Designed for construction and trade businesses.
Built Still is designed for construction and trade businesses requiring structured field compliance records.
- 01
General Construction
Principal contractor and subcontractor field records across multiple work packages.
- 02
Electrical
Method statement acknowledgement and structured checks for electrical work packages.
- 03
Plumbing & Mechanical
Mechanical services teams recording checks, evidence and sign-off in the field.
- 04
Roofing
Working-at-height documentation captured against the task rather than after it.
- 05
Scaffolding
Repeat check records, photographic evidence and acknowledgement trails.
- 06
Fit-Out
Fast-moving internal packages where paperwork usually lags behind the work.
- 07
Maintenance
Short-duration visits that still need a consistent, retrievable record.
- 08
Property Services
Distributed operatives working across many addresses and property types.
- 09
Civil Works
Groundworks and infrastructure teams capturing structured checks on site.
- 10
Specialist Trades
Specialist packages needing their own checklists, evidence and acknowledgement.
Sheet 12 / Manager view
See what needs attention without reading through a pile of forms.
The point of structured records is that somebody can look at them. A management view is about surfacing what is outstanding — not about generating charts nobody acts on.
Site 01 / Attention
Illustrative interface — example data
-
Open acknowledgements
2
AttentionRAMS awaiting acknowledgement
-
Inspections
1
AttentionCompleted with items flagged
-
Actions
3
AttentionFollow-ups assigned
-
Incidents
1
OpenRecord open
Recent activity
- 16:12 Daily record closed
- 13:44 Action updated on incident record
- 10:21 Photo evidence attached to inspection item
- 10:18 Weekly site check completed
- 08:02 Toolbox talk recorded with 8 acknowledgements
Sheet 13 / Compliance is a process
Compliance is a process, not a product feature.
Software supports
- Distribution of documents to the people doing the work
- Acknowledgement of what has been issued
- Structured records in a consistent format
- Evidence attached to the record it belongs to
- Workflow consistency between sites and teams
- Visibility of what is outstanding
The record supports the process.
It does not replace the responsibility.
Software does not replace
- Competent persons
- Site supervision
- Risk assessment
- Professional advice
- Legal duties
- Safety judgement
Next step
What does your site team still record on paper?
Tell us how your business currently handles RAMS, toolbox talks, inspections, incidents and site evidence.