Key takeaways
- A digital hold point earns its place only when it can stop the next trade, the concrete booking or the next inspection until the work behind it has been released.
- Every release should be tied to one named person logged in under their own account, because a shared login records a device rather than the person who looked at the work.
- Time stamps must come from the system at the moment of release, and any later correction should be added as a visible new entry rather than a silent edit.
- Test the gate on a practice job with an item deliberately left open, and confirm that the next step really is blocked before any trade relies on it.
- Keep the released records, the locked history and the access list together, because a dispute over an inspection can arrive years after the work was covered.
A hold point is only useful if it stops the next step until someone has inspected the work and taken responsibility for it. On paper, that usually means a checklist signed at the end of the day, or a name written on a sheet that has been sitting in the ute since the last pour. A digital hold-point checklist can do the same job far better, but only if it is built as a gate rather than as a form. The difference is whether the system can refuse to let the concrete be booked, the frame be covered or the next inspection be arranged while an item is still open.
This article is about building that gate: how to set it up, who should be able to release it, what the record must show and where the setup usually goes wrong. It does not try to say which hold points a particular job needs. That list belongs to the job specification and the designer, and this article takes it as given. The concern here is the mechanics, because a well-chosen hold point that can be signed off at any time by anyone is a weak control, and a builder who relies on it will eventually be asked to explain why it did not stop anything.
What a hold point gate has to do
A gate has three jobs. It stops the next trade from proceeding until the work behind it has been checked, it records who checked the work and when, and it keeps that record in a form that cannot be quietly rewritten later. A checklist that only does the third of those is a diary. A checklist that does all three is a control, and it is the control that matters when a pour is disputed or a defect surfaces after the walls are lined.
Safe Work Australia’s guidance on digital technologies and artificial intelligence makes a point that applies well beyond the software itself. Any system that changes how work is recorded, checked or approved needs its own controls, including who can change it, what it keeps and how it is switched off. A hold point gate is one of those systems, so its controls belong in the job plan alongside the inspection, not in a settings screen that only the office ever sees.
The commercial reason is simple. A pour that goes ahead without a released hold point is the kind of error that is discovered after the concrete has set, when the cost is a breakout, a reinstatement and a programme delay, and the first question from the client or the certifier is who was responsible for checking the reinforcement. If the answer is a sheet nobody can find, or a checklist that was filled in afterwards, the builder carries the argument. The gate exists to make that question answerable on the day, not six months later.
Who can release the gate, and why logins must be individual
Every gate should name one person who has authority to release it, usually the supervisor or the person who inspected the work. Releasing a gate for work you did not see is the quickest way to turn a control into a liability, because the record then says a person vouched for something they never looked at. The system should make that person’s identity part of the release itself, not a line that someone typed into a box.
That is why shared logins defeat the purpose. If the foreman, the apprentice and the concreter all use the same tablet login, the record says the gate was released by the account, and nobody can tell from it who actually looked at the steel. Set each person up with their own login, even on a small crew, and require the login to be used for the release. The cost is a few minutes of setup. The benefit is a record that answers the question of who was responsible, which is the only question a dispute will really ask.
Time stamps and the record nobody can quietly edit
The time stamp is the feature that gives the record its weight, and it is the feature most often broken in practice. The stamp should come from the device or the system at the moment of release, not from a field the person fills in. A release that is entered at the end of the day, with the time typed as the start of the morning, is worse than no record, because it looks like evidence and is not.
The record must also be locked once a gate is released. A correction should be added as a new entry that says what changed, who made the change and when, so the original release stays visible. Any system that lets a supervisor go back and alter an old release without leaving a trace has given the builder a document that can be rewritten, which is no protection at all. Ask the software supplier how edits are recorded before the system goes live, not after the first dispute.
The shortcut that undoes it. Releasing a gate from memory after the work is covered, and letting the record show a later time, turns the checklist into evidence that the inspection did not happen when it was supposed to. A late release should be recorded as late, with the reason, because an honest late entry is worth far more than a tidy one that cannot be trusted.
Setting up the gate, step by step
Set-up is where most of the value is won or lost. The sequence below assumes the job’s hold points are already known and the system has been chosen. The aim is to make the gate work on a live site before the first real pour depends on it, not to discover on the day that a release can be saved without a photo or that the concrete booking is not linked to anything.
Setting up the gate
- 1Write the gate downName the hold point, the work it covers and the trade that must release it before the next step can start.
- 2Assign one releasing personName the person with authority to release the gate, and make sure they use their own login.
- 3Link the gate to the next stepTie the release to the concrete booking, the next inspection or the next trade so that step cannot be arranged while the gate is open.
- 4Set the evidence requiredDecide the photographs, measurements and notes that must be attached before a release can be saved.
- 5Test on a practice jobRun the gate with one item deliberately left open and confirm the next step is blocked.
- 6Brief the tradesShow each trade how the gate works and what a rejected release means for their programme.
Testing is the step that gets skipped most often. Run the gate through a practice job with one item deliberately left open, and check that the next step is actually blocked. If the system will still let the concrete be booked while the reinforcement gate is open, the control is not working, and the fault should be fixed before any trade is asked to rely on it. Keep a written note of the test, because it is the first thing you will want if the system is ever questioned.
The evidence to attach to each release
A release should carry more than a tick. Decide in advance what evidence each gate needs: a photograph of the reinforcement with the cover visible, a measurement of the fall, a photo of the cable run before it is covered, or a note of the pressure reading on a test. The gate should not be able to close without that evidence, because a photo added later is much weaker than one taken in the moment with the time recorded alongside it.
Keep the evidence requirements short. A gate that asks for a long list of photographs will be completed with the same three photographs every time, and the people using it will learn to tick past the requirement. Ask for the one or two items that actually prove the work was checked, and make them specific enough that a stranger could look at the record and understand what was seen. A named person, a time, a photograph of the thing that matters and a short note of any concern is usually enough.
Some gates need a reading rather than a tick. A measurement taken with a digital tool can be logged straight against the gate, which removes the copying step where most transcription errors creep in. The article on digital measuring tools that log results covers how those readings are captured at the point of work. The same rule applies to them: the device should stamp the reading, not the person who copies it onto a sheet afterwards.
Working when the signal drops
Many sites have patchy coverage, and a gate that only works with a live connection will fail on the day it is most needed. Choose a system that saves the release on the device and syncs it later, and check that the time of the release is kept separately from the time of the sync. A release that was made on the slab at a particular hour should show that hour, even if the upload did not happen until the crew got back to the office.
Keep a paper fallback for the days when the device fails or the battery is flat, and write down what the fallback is in the job plan before it is needed. When the record is reconciled, the paper entry should be transferred with its original time and a note that it was entered later. The point is not to avoid paper altogether. It is to make sure that a gap in the digital record is visible and explained, rather than covered over.
Paper or digital: what actually changes
A paper sheet and a digital gate can hold the same list of checks. What differs is what the record can prove and what the system can stop. The comparison below is the practical difference for a builder deciding whether the switch is worth the effort.
Paper sign-off and a digital gate
| Paper sign-off sheet | Digital gate |
|---|---|
| Signed after the work, often from memory | Released in the field, with the time recorded when it happens |
| Anyone holding the sheet can write a name | Each release is tied to one person and their own login |
| Dates depend on whoever fills in the sheet | Time stamps come from the system at the moment of release |
| Easy to lose, damage or misplace | Stored with the job and backed up |
| Does not stop the next trade being booked | Can block the next step until the gate is released |
Paper is not wrong for every site. A small job with a single trade and a supervisor standing over every task may not need more than a well-kept sheet, and a digital gate that is set up badly is worse than a sheet that is used honestly. The question is not which format looks modern. It is which format can show, on the day a dispute arrives, that the right person checked the right work before the next step went ahead.
The gate is also easier to audit. When a builder can show a sequence of released gates, each with its own login, time and evidence, and can show that the concrete booking was blocked until the reinforcement gate was released, the record speaks for itself. A stack of paper sheets, however carefully kept, usually needs someone to explain them, and by then the person who filled them in may no longer be on the job.
Getting the crew to use the gate without working around it
A gate is only as good as the habit of using it. The most common workaround is the release done in a batch at the end of the day, which turns each gate into a tidy list rather than a moment of inspection. Tell the crew plainly that a release is made standing next to the work, and that a release made from the ute at lunch is not a release. The supervisor should check the release log each morning, and any gate released in a batch should be followed up before the next trade is booked against it.
Brief each trade on what a rejected release means for their programme, and make sure they understand that a rejection is a normal part of the process rather than a complaint about their work. A rejected gate that is fixed the same morning costs a short delay. A gate that is worked around can cost a breakout. Crews who understand that difference tend to take the gate seriously without being told twice, and the supervisor’s time goes on the work rather than on chasing signatures.
A worked example: a builder in the Hunter
A builder in the Hunter was running three homes on one estate with a single slab crew and a separate framing crew. The slab gate had been set up on a shared tablet, with the foreman releasing the reinforcement check for whoever was on site that morning. The pour went ahead, and months later the owner’s engineer asked whether the reinforcement had been inspected before the truck arrived. The record showed a release, but it was made from the shared login, and the timestamp showed the release had been saved after the concrete was already in the pump.
The builder could not show who had looked at the steel or when, and the record did not help the argument. The rebuild was not complicated. Each foreman got their own login, the concrete booking was linked to the reinforcement gate so it could not be confirmed while that gate was open, and a photograph of the cover was made compulsory before release. On the next pour, the gate blocked the booking because the photograph was missing. The foreman rang the designer, the cage was adjusted at one corner and the release went through with the photograph attached.
What to keep for a dispute that arrives years later
Keep the released gates, the locked history of any corrections, the photographs and the list of who had access to the system at the time. Keep the setup note, because it shows how the gate was designed and tested, and keep a copy of the job specification that the gate was built from. If the system is replaced, export the records in a readable form before the old subscription lapses, because a builder who cannot open their own history will find that their evidence is only as good as their vendor’s continued existence.
These records are also the working evidence for a builder’s own professional development. The PointCPD guide to how NSW builder CPD works explains how supervision and site practice are assessed.
The article on QR codes for site materials and inspections covers a related way of tying a check to a physical item. A gate is only one part of a site system, and it should be designed alongside the rest of it.
Questions builders ask
Does a digital hold point replace the inspection?
No. The gate records that an inspection happened and who released it, but the inspection still has to be carried out by someone competent to do it. A digital record of a poor inspection is still a poor inspection, only now it is easier to prove.
Can a released digital checklist be changed afterwards?
It should not be changed silently. A released gate should lock, and any correction should be added as a new entry showing what changed, who made the change and when. A system that allows quiet edits gives the builder no reliable evidence at all.
What happens if there is no phone signal on site?
Choose a system that saves the release on the device and syncs it later, and make sure the time of the release is kept separate from the time of the sync. Keep a paper fallback for when the device fails, and reconcile the two entries straight afterwards with a note explaining the gap.
Who should be allowed to release a hold point?
The person who inspected the work, or the supervisor responsible for it, and nobody else. Releasing a gate for work that was not seen is the fastest way to turn a control into a liability.
Should subcontractors have their own logins to the gate?
Yes, where the subcontractor is the one completing the work and is responsible for releasing their own gate. Each person should use their own login, so the record shows the individual who took the action rather than the company or a shared device.
Is a digital gate worth the effort for a small builder with one crew?
It can be more useful for a small builder. The owner is often the only person who knows the job well, and a gate that records each sign-off protects the business when the builder is off site or the work is disputed long after it was covered.
Sources
- Digital technologies and AI · Safe Work Australia
- Continuing professional development for builders and swimming pool builders · NSW Government
- General building work licensing · NSW Government
Published 22 October 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.
