Best Temporary Works Management Software for UK Sites: TWS and TWC Focus

Why Is Choosing Temporary Works Software Harder Than Choosing a General Construction App?

A general construction app is judged on drawings, snags, daily reports and communication. Temporary works software is judged on something narrower and less forgiving: whether it can show, for a single prop, trench box or item of falsework, that the right people did the right things in the right order.

That order matters. In outline, an item is identified, a design brief is issued, the design is prepared and checked at the right category, the works are built, inspected and released for loading, maintained and inspected in use, and finally dismantled. HSE operational guidance, written for its inspectors, describes the same shape: a register of temporary works items, a design brief for each, design checks proportionate to the risk, a permit to load once the works have been checked against the design, and a permit to dismantle where the permanent works need to have reached adequate strength first. The CITB's free register template organises the register the same way, in six steps from identifying the scheme to dismantling and removal.

The result is that a tool can be excellent at one part of the process and weak at another. A register-and-permit system may be a poor fit for a supervisor inspecting in a basement with no signal. A fast inspection app may not know what a permit to load is. Most disappointing purchases come from buying for one role and discovering the other cannot work with it.

Note: roles, categories and procedures vary between projects and companies. Always follow the temporary works procedure for your own project and the edition of BS 5975 it specifies.

What Does Each Role Need From the Software?

HSE guidance describes the TWC as the person who ensures the contractor's temporary works procedures are implemented on site, who is normally not the designer but ensures a suitable design is prepared, checked and built as specified, and who should be formally appointed with authority to stop unsatisfactory work. On larger sites one or more TWSs may assist the coordinator. HSE's guidance is written around an older edition of BS 5975 and the current standard is BS 5975-1:2024, so the exact wording of duties can differ between sources and projects.

Even so, the two roles pull a buyer in different directions.

If the person signing the contract is a project manager or commercial lead, a third need appears: price, contract terms, data ownership and an exit route. We cover those in the vendor questions below.

What Should Software Cover Across the Temporary Works Lifecycle?

Use the six steps in the CITB register template as a coverage map. It is a practical way to see which parts of the process a product actually handles. The template is a general industry aid, not a statement of what your own procedure must contain.

Two details from the CITB permit to load template are worth testing in any demo, because they show how time-sensitive these records are. The template states that loading must take place within 24 hours of the issue date and time, and that the supervisor directly responsible for loading must hold the permit before loading begins. A good system should make both of those easy to see and hard to get wrong. Your own procedure may set different rules, so check what yours requires.

What Types of Temporary Works Software Are on the Market?

Products tend to fall into five groups.

1. Dedicated temporary works management systems

Built around the register, appointments, permits and inspections. They are the most direct fit for a TWC and for principal contractors that want one controlled system.

Check: how well the supervisor experience works on a phone, and whether it works offline.

2. Document and quality management platforms with a temporary works module

Broader systems for registers, approvals, QA and document control that include a temporary works offering. They suit larger contractors that already run structured document control.

Check: how much is configuration versus a finished temporary works workflow, and whether site supervisors can use it quickly.

3. Permit-to-work platforms

General permit products for all types of permits. They can be configured for permits to load and dismantle, but are not necessarily built around the temporary works register and design process.

Check: whether the register, design brief and design check category sit inside the tool or remain separate.

4. Inspection and compliance apps

Focused on carrying out inspections, capturing evidence and following up findings. They serve the TWS well and need a plan for how records connect to the TWC's register.

Check: how inspection records are reconciled with the register and permits.

5. Free templates, spreadsheets and paper

The CITB publishes free temporary works register and permit templates, including versions labelled digital. For a small project with few items, a well-kept register and a disciplined paper or PDF process can be enough. It is also the benchmark any paid product has to beat.

Check: whether you can still find records quickly, show timings and follow up findings as items and sites multiply.

How Do the Verifiable Options Compare?

The table below uses only what each vendor's own public page states. We have not tested any product. Where a page was silent, we say "not stated" rather than assuming. Vendor pages are marketing material, and a statement of alignment with a standard is a claim to test, not a certification.

Three points about this table.

It is not a ranking. We cannot tell you which is best, because none of the vendor pages published enough to compare on price, offline performance or workflow depth, and we have not tested any of them. A genuine comparison needs a demo, a trial and some reference calls.

Pricing is largely unpublished. None of the vendor pages we reviewed listed prices apart from calls to book a demo or start a trial. Ask for the full cost for your number of users, projects and storage over a year, including onboarding and any per-project fees.

Standards claims need unpicking. BS 5975 sets out management procedures and design and implementation guidance. A piece of software can support a procedure, but it cannot be compliant with a standard in the way a person or an organisation can follow one. When a vendor says its tool is compliant, aligned or supports BS 5975, ask what specifically it does, against which edition and part, and what the contractor still has to do.

What Is the Best Choice for Your Situation?

These are not mutually exclusive. Many teams will use a register system for the coordinator and an inspection tool for supervisors, provided records can be reconciled and nobody is entering the same data twice.

How Do You Score the Shortlist?

A weighted scorecard stops the loudest demo winning. Agree the weights before you see any product, with both the TWC and the TWS in the room. The two sets below are starting points, each adding to 100. Adjust them to your own procedure.

Coordinator-led purchase (register and permits matter most)

Supervisor-led purchase (inspections matter most)

Score each product from 0 to 5 on each row, multiply by the weight and add up. The number is only as good as the test behind it, so score from a hands-on task, not from the brochure.

How Should a TWC and a TWS Test a Product Together?

Run one shared scenario with both roles taking part.

1. TWC creates an item. Use something your team actually builds, such as trench support or a section of falsework. Record the description, risk class and design check category.
2. TWC records the design brief and approval. Check that dates, approvals and the person responsible are clear.
3. TWS completes a pre-use inspection on a phone. Add photographs and time it.
4. Repeat it offline. Use flight mode, reconnect and check that every record, photograph and timestamp arrived correctly.
5. TWC issues a permit to load. Check who it went to, whether the recipient holds it before loading and whether time limits are visible.
6. TWS records a defect. Assign it to someone new to the system and watch them close it.
7. Run a weekly in-use inspection. See how the next one is prompted and recorded.
8. TWC checks the register. Can they see every item and its evidence without asking anyone?
9. Test dismantling. Check that a permit or completion record can be issued and that the history makes sense.
10. Test the exit. Ask for an export of a full item, including photographs and the audit trail.

If any step needs the vendor to explain it, expect your wider team to hit the same wall.

What Should You Ask Every Vendor?

• Which edition and part of BS 5975 does the product reference, and what exactly does it do to support it?
• What is the full annual cost for our users, projects and storage, including onboarding?
• Does the supervisor experience work fully offline, including photographs and permits received on site?
• Are timestamps recorded when the action was done, or when it uploaded?
• Can we configure design check categories, risk classes and permit wording to match our procedure?
• Who can edit or delete a record, and is there a history of changes?
• Can the coordinator see all items across several projects in one view?
• Can we export all our data, including attachments and audit history, if we leave?
• Where is our data hosted and who owns it?
• Can we speak to a UK contractor who uses it for temporary works specifically?
• What happens to our records if the contract ends?

Temporary Works Software Selection Checklist

• [ ] We have agreed whether this is a coordinator-led or supervisor-led purchase, and both roles are involved.
• [ ] The product covers the steps of our own procedure, not just the ones the vendor highlights.
• [ ] The register records design brief, risk class, design check category and approval status.
• [ ] Permits to load and dismantle are handled in the way our procedure requires.
• [ ] Time limits and "held before loading" rules are visible and hard to bypass.
• [ ] A TWS can complete a full inspection on a phone, including photographs, without a signal.
• [ ] Timestamps reflect when the check was carried out.
• [ ] Defects can be assigned, checked and closed, with a history.
• [ ] The TWC can see status and evidence without chasing.
• [ ] Records show who did what, and when, and changes are tracked.
• [ ] Claims about BS 5975 have been tested with the vendor, not just read.
• [ ] Full annual cost has been confirmed in writing.
• [ ] We can export all data, including attachments and history.
• [ ] A supervisor and a coordinator have run the same scenario end to end.
• [ ] We have compared the result against our current template or spreadsheet process.

How KaelSite Fits TWS and TWC Teams

KaelSite is a mobile-first construction compliance platform for UK teams. Its strength is on the inspection side, which is where supervisors spend their time: offline-first inspections with photo, video, voice and geotag capture, Form Studio for building inspection forms that match your own procedure, an Issue System for recording and following up findings, and Certificates with expiry alerts for tracking the documents behind competence and equipment.

It is not a dedicated temporary works register and permit system, so it is not a like-for-like replacement for the products built around that workflow. The honest test is how it sits alongside your own register and permit process, for example a TWS completing inspections and logging issues in KaelSite while the TWC maintains the register in the system or template they already use. Check the current plans on the KaelSite Plans page, including project and team member limits, before assuming that a coordinator and several supervisors can share one project on the entry plan.

Frequently Asked Questions

What is temporary works management software?

It is software that helps a contractor manage the temporary works process: a register of items, design briefs, design checks, approvals, permits, inspections and records. Some products cover the whole process, while others cover one part, such as inspections or permits.

What is the difference between a TWC and a TWS?

The TWC coordinates the temporary works process on a project and ensures designs are prepared, checked and built as specified. The TWS usually supports the coordinator on site by overseeing the works and making sure checks and inspections are carried out and recorded. Appointment arrangements vary by project.

Do I need software for temporary works?

No law specifies software. The requirement is a controlled process with competent people and records. A well-run register and permit process on paper or in templates can meet that on a small project. Software tends to earn its cost when there are many items, several sites, multiple subcontractors, or a need for quick retrieval and evidence.

Can software issue a permit to load?

Some products support digital permits. Whether a digital permit is acceptable depends on your procedure. Check who signs, who receives it, how time limits are shown and what evidence is kept, and confirm it with your coordinator and designer.

Is any software BS 5975 compliant?

Compliance with BS 5975 depends on procedures and competent people. Software can support a procedure, but treat a claim that a product is compliant with caution and ask what it actually does, against which edition and part.

What changed in BS 5975:2024?

BSI published BS 5975-1:2024 (management procedures for the control of temporary works) and BS 5975-2:2024 (falsework design and implementation), announced by BSI on 25 February 2025 and splitting the previous 2019 edition into two parts. BSI highlights updates on wind force calculation, permissible stress, limit state design for falsework and the extent of control measures for different project sizes. Read the standard itself for what it requires of your project.

Who should choose the software, the TWC or the TWS?

Both. The TWC will care most about the register, approvals and permits, and the TWS about how quickly an inspection can be completed on site. A product that pleases only one will be used inconsistently.

Are the free CITB templates enough?

For a small number of items, possibly. The CITB register and permit templates give you a structure to follow. They do not remind anyone, link evidence or show status across sites, so the question is whether those gaps matter on your projects.

Final Thoughts

The best temporary works management software is the one that both your coordinator and your supervisors will actually use, and that makes the order of events visible: brief, design, check, build, inspect, permit, use, dismantle.

Start by deciding who the purchase is really for. Use the CITB lifecycle as a coverage map, score a shortlist against weights you agreed in advance, and run one realistic scenario with a TWC and a TWS in the same room. Where a vendor's page is silent on offline use, permits or price, treat that as a question, not a yes.

This article is intended as general information for orientation and does not constitute legal or professional advice. Software can support temporary works procedures but does not replace competent people, designs, checks, permits or the responsibilities set out in BS 5975, CDM 2015 and your project's own temporary works procedure. Product descriptions are drawn from vendors' public pages and may have changed.

Sources

• HSE, The management of temporary works in the construction industry (operational guidance for inspectors; refers to BS 5975:2008 and the 2011 amendment): hse.gov.uk
• BSI press release, New standards for temporary works published by BSI (25 February 2025): bsigroup.com
• CITB, temporary works register template, version 02.00: citb.co.uk
• CITB, completed example temporary works register: citb.co.uk
• CITB, temporary works permit to load template: citb.co.uk
• Temporary Works Management Software (Eryri Consulting Limited): temporaryworks.online
• Zutec, Temporary Works Management: zutec.com
• Inndex, Temporary Works: inndex.co.uk
• Sitemate, Permit to Work App and Software: sitemate.com
• Working Load: workingload.com