Key takeaways
- A QR code is a pointer to a record and proves nothing on its own, so the person checking the link has to read the certificate against the item.
- Label the items that carry a performance or compliance claim and the inspection points that cannot be repeated once the building is closed in.
- Generate every code from a register and test the full chain before the crew moves on, so that labels cannot point to the wrong document by accident.
- Keep the superseded versions withdrawn from the system and keep personal details out of the code, because anyone can scan a label.
- Keep an archive copy and a printed index of the codes in the job file, because a digital record that exists only behind a code is easy to lose.
Most builders now carry a phone on every job, and most of the paperwork that matters still lives in a folder in the ute, a filing cabinet in the office or a certificate taped inside a cupboard door. A QR code is a small way to close that gap. Stick a label on a pallet, a bundle of timber, a wall board or an inspection point, and anyone with a phone can scan it and go straight to the document that describes the item or the inspection.
The idea is simple, and that simplicity is the trap. A QR code does not hold a certificate or prove anything about a product. It is a pointer. It sends the reader to whatever record sits at the other end of the link, and if that record is out of date, mislabelled or missing, the code is not a control at all. It is a confident-looking way of showing the wrong document. The value of the system depends on the discipline behind the label, not on the technology printed on it.
This article covers linking physical items and inspections on a residential building site to their records. It covers labelling, the control of the records behind the codes, offline access and what should never be put into a code. It does not cover tracking tools or equipment across the fleet, which is a different job, and it does not replace the approvals, inspections and certificates the building work requires.
What a QR code does on a building site
On a site, a QR code does one of three jobs. It identifies an item, such as a particular bundle of structural timber or a particular box of fixings, so that the batch can be traced later. It links a physical item to the document that certifies it, such as a product certificate, a test result or a manufacturer’s installation sheet. Or it links an inspection point to the record of the inspection, so that a hold point signed off on the day can be seen by anyone who looks at the wall afterwards. Each of these is useful, and each needs a different kind of control.
The certificate side is where the real value sits. When a builder can show, at handover or in a later dispute, that a particular product in a particular wall had a particular certificate on the day it was installed, the builder has evidence. When the same builder has only a box with a sticker and a memory of what was in it, the evidence is weaker. A QR code is one way of making the link between the product and its paper unbroken, provided the paper is the right paper.
Which items are worth labelling and which are not
Not everything on a building site needs a code. A label on every nail box and every off-cut adds noise, costs time and teaches the crew to ignore the labels. The useful question is whether the item carries a performance or compliance claim that someone may need to check later. A bundle of structural timber, a batch of waterproofing membrane, a particular wall system, a set of windows with a required rating, and a footing inspection all carry claims. The labels belong on those.
Inspection points are the second group. A hold point where the reinforcement is checked before the pour, or where the frame is checked before the lining goes on, is a moment that cannot be repeated once the building is closed in. The record of that inspection is the evidence that the inspection happened, who did it and what was seen. A code on the physical point, linking to a dated record, is far more useful than a sheet filed in the office at the end of the week.
The third group is the one builders most often miss. Items that are hidden by finishes, such as a wall cavity, a subfloor or a membrane under tiles, need their records to be discoverable from the outside of the finished building. A label placed where it will be seen before the lining goes on, with the record it points to, is the only way the evidence will be found in a decade’s time.
Labelling discipline: where the code goes and how it survives
The label is the physical part of the system, and it fails in predictable ways. It peels off in the rain, it is painted over, it is stuck to a surface that is about to be covered, or it is printed so small that a phone cannot read it at arm’s length in poor light. A good label is printed on a material that survives the site, placed where a person will see it before the work covers it, and tested with a phone before the crew moves on.
Consistency matters as much as durability. Every label should carry the same information in the same order: the project name or code, the item or inspection reference, and a short human-readable text beside the code, so that a person without a phone can still identify the item. Use the same format on every job so that the crew, the certifier and the next trade recognise it at a glance. The code itself should be generated from a register, not typed by hand, so that two labels cannot point to the same record by accident.
Setting up a label that will still mean something later
- 1Choose what needs a labelLabel items that carry a performance or compliance claim, and every inspection point that cannot be repeated.
- 2Print on durable materialUse a label that survives the weather, handling and the trades, and place it where it will be seen before the work is covered.
- 3Generate codes from a registerCreate each code from the register so that two labels cannot point to the same record by accident.
- 4Test the whole chainScan the label, open the record and check the version and date before the crew moves on.
- 5Name the owner of the recordDecide who may replace a certificate, and keep the decision in writing.
Test the chain once before relying on it. Scan a label on the bench, follow the link, and check that the record opened is the correct version and carries the right date. A label that scans correctly on the day of printing can still point to a document that was replaced last week. The test catches that, and it also catches labels that point to a login page, a folder that requires a password, or a file that opens only on the office computer.
Labels will also be damaged, and the replacement process needs as much thought as the first print. A label that has been torn, painted over or scratched should not be re-stuck from memory. Reprint it from the register, check the new label against the record again, and remove the old one from the item where it can be done without disturbing the work. Note the replacement in the register so that a later scan of the old code, if one survives in a photograph, can be traced to the current record.
Controlling the record behind the code
The code is only as good as the record it points to. The record needs an owner, a version and a date, and it needs to be the document the project actually relies on. A product certificate that has been superseded by a newer issue must be replaced in the system, not left in place beside it. Where a code points to a folder rather than a single document, the folder must be arranged so the current version is obvious, and the older versions must be kept but clearly marked as superseded.
Control of the link is the other half. A code that points to a file in a personal cloud account, a shared link that can be edited by anyone with the address, or a document on a laptop that gets replaced, is not a record. It is a risk. Use a document store that the business controls, that keeps version history, and that the people who need the records can reach. Decide who is allowed to replace a certificate, and keep the decision in writing.
Do not let the code point to the wrong version. The mistake that costs the most is a label that scans cleanly and opens a superseded certificate, because it looks like proof. The product may then be installed against the wrong rating, and the error surfaces at the final inspection, or years later in a defect claim, when the only paper says the product was compliant. The label has made the error harder to see, not easier.
Offline access and the site office problem
Many building sites have patchy mobile reception, particularly on new estates, in cuttings and in basements. A code that opens a document only when the phone has signal is of limited use at the point where the item is being checked. The better approach is to make the current version of the key records available offline on the device, or to print a controlled copy and keep it in the site file with the code printed beside it, so that the record is present even when the network is not.
Offline copies create their own problem. A printed certificate in the site file is a superseded document the moment a newer issue arrives, unless someone is responsible for replacing it. Build the replacement into the process. When a record is updated, the old copy is withdrawn from the site file and the new one is placed alongside the code. Keep a short note of when the change was made.
Privacy and what must not go into a code
A QR code can carry text, and the text can be read by anyone who scans the label. That makes the label a publication. Do not encode personal information about a worker, a client or a neighbour in the code, and do not put a licence number, a bank detail or a password into the link. Keep the code as a reference to a record held in a controlled system, and let the system decide who can see the detail. A code on a wall in a finished house may be scanned by a future owner, a tradesperson or a stranger, and the label should reveal nothing it should not.
Keep the content of the record separate from the label. A label that says which product is in the wall is useful. A label that names the installer, gives their home address and their phone number is not, and it invites misuse.
Worked example: a bundle of timber and the wrong certificate
A builder in western Sydney was framing a double-storey home on a sloping block, with a bundle of engineered timber joists delivered on a single truck. The builder labelled each bundle with a code that linked to the product certificate for that grade and supplier, and the labels went on as the bundles were unloaded. The system was set up carefully, and the crew was pleased with how quickly the certificate could be found.
Partway through the frame, a second delivery arrived from the same supplier, but a different grade was supplied for the upper floor. The crew printed the labels from the register, but the register still pointed to the certificate for the first grade, because the record for the second delivery had been entered under the old product name. The codes scanned cleanly, the certificate opened, and the crew saw what looked like confirmation. Nobody read the grade on the certificate against the grade on the bundle.
The error was caught by the framing inspection, when the certifier asked for the grade of the joists on the upper floor and the builder scanned the code to produce it. The certificate showed the wrong grade, and the bundle showed a different one. The timber was replaced before the lining went on, at a cost the builder did not budget for. The lesson the builder took was that a scan proves only that the link works, not that the link is right. The check is reading the grade on the paper against the grade on the item, every time.
Keeping paper as the backup and the audit trail
The digital system should not be the only record. A product certificate, a test result or an inspection sign-off that exists only behind a code is one phone upgrade or one account lockout away from disappearing. Keep an archive copy of every key record in a second location that the business controls, and keep a printed index of the codes in the job file. The index is cheap, and it is the first thing a certifier or a lawyer will ask for if the online system is unavailable. The same logic applies to attendance records, and our article on digital timesheets for site attendance covers that side of the job.
Safe Work Australia’s guidance on digital technologies and AI recognises that new tools bring their own risks, including the risk of relying on them without checking their output. The same principle applies to a records system. Introduce the codes deliberately, train the crew on what a valid scan looks like, and check the chain on a sample of items each week. Where the records bear on the performance of a product, such as a system under a CodeMark certificate, the certificate and the conditions attached to it must be the document the code opens. Where the site sits in a flood hazard area or the wall construction relies on managing condensation, the records of the materials and layers must match the approved design. A code that points to the right document makes that easy to show. A code that points to the wrong one makes it impossible to prove.
From the delivery to the handover file
- DeliveryThe item arrives with its certificate, and the certificate is entered against the batch.
- LabellingThe code is printed from the register and placed where it will be seen.
- CheckingThe grade or rating on the paper is read against the item before the work is covered.
- InspectionThe inspection is recorded against the point it concerns, while the work is still open.
- HandoverThe index of codes and the archive copies go into the job file with the other records.
- Later yearsAnyone who scans the label in future finds the current, correct record, or a clear note that it has been superseded.
The purpose of the system is to make the true record easy to find, at the moment it is needed and years afterwards. A builder who treats the code as the evidence has built a tidy way of being wrong. A builder who treats it as a pointer to controlled, current, checked paper has built a useful tool.
The measurement side of the same story is covered in our article on digital measuring tools that log results, which shows how a logged reading can be tied to the job that produced it.
The record-keeping expectations that sit behind the licence are set out in PointCPD’s guide to how NSW builder CPD works.
Questions builders ask
Is a QR code on a product label enough to prove it is certified?
No. A code points to a record, and only the record proves anything. The person checking the link must read the certificate and confirm that it matches the product, the grade and the current issue. A scan that works is not the same as a certificate that is right.
What should I label on a residential building site?
Label items that carry a performance or compliance claim, such as structural timber, waterproofing products and systems with a required rating. Label inspection points that cannot be repeated once the building is closed in. Leave out consumables and small items that add noise without adding evidence.
What happens if the site has no mobile signal?
Keep the current version of the key records available on the device for offline use, or keep a controlled printed copy in the site file with the code printed beside it. Replace the printed copy whenever the record is updated, and note the change.
Can I put a licence number or contact details in the code?
Keep personal and sensitive information out of the code. A code should be a reference to a record held in a controlled system, and that system should decide who can see the detail. Anyone can scan a label, including people who have no business with the job.
How do I stop a label pointing to an old certificate?
Generate codes from a register that records the current version of each document, and withdraw superseded versions from the system when a new one arrives. Check the chain on a sample of items each week. Assign one person to replace certificates, so the responsibility is clear.
Should I keep paper records as well as the digital system?
Yes. Keep an archive copy of every key record in a second location the business controls, and keep a printed index of the codes in the job file. The index is the first thing a certifier or a lawyer is likely to ask for if the online system is unavailable.
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 20 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.
