TL;DR

/> – Expect more transparency and performance evidence in public tenders, and prepare bid libraries accordingly.
– Refresh policies on conflicts, exclusions and supply chain payment, as these areas are likely to face closer scrutiny.
– Build data readiness: performance KPIs, past contract references, and prompt-payment records may be requested more systematically.
– Train bid and project teams on new terminology, notices and timelines to avoid disqualification on technicalities.

What the shift signals for contractors and their supply chains

/> The new procurement regime points to authorities seeking demonstrable value over the life of a contract, not just the lowest initial price. That means bidders should anticipate questions that go deeper into methodology, risk transfer, net-zero delivery plans, social impact and how performance will be measured on site. While each authority will phrase it differently, the overall picture is a procurement landscape where claims need to be evidenced, data-backed and auditable. Main contractors will also need clearer line-of-sight into their supply chains, as authorities increasingly ask how payment terms, safety standards and ethical policies cascade down.

In practical terms, contractors should expect more formalised declarations around conflicts of interest and exclusion grounds, with less tolerance for incomplete or inconsistent responses. Records management becomes a competitive issue: the ability to produce clean, attributable performance data and references can shorten evaluations and reduce clarifications. Commercial teams may also encounter more frequent publication of procurement and contract notices, including updates during delivery, which places a premium on contract administration discipline. All of this nudges the market towards earlier market engagement, sharper bid/no-bid decisions, and fewer speculative pursuits.

# Caveats

/> The detail of how each contracting authority applies the regime will vary, and secondary guidance is still being interpreted across the market. Timings, thresholds and the extent of reporting expected from suppliers may evolve as systems bed in. Scotland operates under a separate framework, so cross-border operators will need to segment approach and messaging. None of this should be taken as legal advice; the safest route is to monitor live procurements and respond to clarifications early.

Immediate actions many are taking to stay bid-ready

/> Commercial directors are prioritising a refresh of bid libraries to align with the anticipated assessment focus: clearer method statements, quantifiable outcomes and risk registers that tie back to deliverable controls on site. Businesses are consolidating proof-points—client testimonials, practical completion certificates, defect data, and programme recovery examples—so they can be dropped into responses without a last-minute scramble. Policies on prompt payment are being tightened and evidenced, with clearer subcontract terms and better reporting mechanisms in case authorities ask for proof of practice. Teams are also reviewing onboarding and exclusion checks to ensure declarations are accurate and consistent across all submissions.

Digital readiness is emerging as a practical bottleneck. With more notices, templates and potential data publications in play, contractors are testing portal access, document control and scrutiny trails well before deadlines. Training is moving beyond bid writers: project managers and quantity surveyors are being briefed on the likelihood of more performance monitoring, change notifications and auditable records during delivery. Consultants and JV partners are being asked to evidence their own compliance postures, as misalignment can damage a prime bid.

# A likely site-level scenario

/> A medium-sized UK civils contractor targets a local authority highways package expected to run under the new regime. The selection stage asks for recent performance evidence tied to measurable outcomes, alongside details of how subcontractor payment will be monitored. During the tender, the authority publishes an additional notice clarifying how it will review risk allowances and value-for-money proposals, prompting the bidder to refine its method statement and programme logic. The contractor’s bid team leans on pre-prepared performance dashboards and audited references to answer clarifications quickly. On award, the authority sets out expectations for periodic reporting that align with the commitments made at tender, requiring the site team to align cost, programme and quality data capture from day one.

# What to watch next

/> The immediate markers will be how consistently authorities apply new evaluation language and what evidence they accept as sufficient.
Attention will turn to whether data and reporting expectations increase administrative load for SMEs or are proportionate and staged.
Market watchers will look for signs that payment scrutiny improves cash flow down the tiers without slowing awards.
Contractors will track whether early market engagement becomes more meaningful and shapes procurement design in practice.

The market signal is clear: transparency and demonstrable performance are moving from nice-to-have to non-negotiable in public work. The open question is whether the regime will reward those investing in robust data and delivery systems quickly enough to justify the change costs.

FAQ

/> What is changing under the new procurement regime?
The regime is widely framed as a reset of how the public sector buys, with more emphasis on transparency, demonstrable value and contract performance. Contractors should anticipate clearer publication of procurement information and closer scrutiny of how promises made at tender translate into delivery.

# Who is affected in the UK?

/> Any contractor, consultant or supplier pursuing public sector work in England, Wales and Northern Ireland should prepare for the shift, with Scotland operating its own approach. Framework operators and major programmes are likely to move first, but smaller competitions will follow as authorities update processes.

# When will contractors start to feel the impact?

/> Industry commentary suggests changes will phase in across 2024 and beyond as authorities adopt new templates and portals. Some procurements will still run under existing rules during transition, so bidders should read documents carefully to confirm which regime applies.

# What practical steps should bid teams take now?

/> Refresh bid libraries to provide hard evidence of outcomes, not just claims, and align method statements with value-focused criteria. Tighten declarations, conflicts checks and supply chain payment policies so they withstand increased scrutiny.

# Will tender evaluations prioritise price less than before?

/> The direction of travel is towards broader value considerations over a contract’s life, with price remaining important but not the sole determinant. Bidders who can evidence risk management, delivery capacity and measurable social or environmental outcomes are likely to be better positioned.

The post Procurement Act 2024: what contractors must do now appeared first on Goldcast Academy Magazine | All the latest news from the UK building industry.

TL;DR

/> – Put the appointing party’s information requirements front and centre and insist on a configured CDE with WIP/Shared/Published/Archive states, metadata, audit and approvals aligned to ISO 19650.
– Append an Information Protocol to contracts, name an Information Manager with duties and authority, and fix data ownership, access and archiving up front.
– Specify naming conventions, classification, status/suitability codes and submission workflows that match the UK National Annex and your review gates.
– Budget time for mobilisation: templates, metadata, training and pilot submissions before Gate 1 to avoid non-compliant drops wrecking the programme.
– Measure value with hard metrics: review turnaround, non-compliant submissions, completeness at each data drop and handover readiness for asset information.

Specifying an ISO 19650-compliant CDE in UK public tenders

/> The most robust public sector specifications start with Exchange Information Requirements that are practical and unambiguous. Set out the purpose of information (planning, coordination, cost, handover), the level of information need by workstage, naming conventions, classification, required states and approval routes. Provide a pre-populated Master Information Delivery Plan template with roles and delivery dates, and define how task teams maintain Task Information Delivery Plans against it.

Choose a CDE that can be configured to the 19650 lifecycle: Work in Progress restricted to authoring teams; Shared for coordination; Published for contractual information; and a secure Archive. Require container-level metadata fields that match your EIR (project, asset/system, originator, classification, revision, suitability and status). Lock in transmittal features, immutable audit logs, configurable review workflows, and granular permissions. Many platforms can do this if correctly set up; the tender should ask for a configuration plan, not a brand.

Public clients often attach an Information Protocol. Ensure it dovetails with your main contract, sets responsibilities (appointing party, lead appointed party, task teams), confirms rights to use and distribute information, and addresses defects, disputes and termination in the digital realm. Include a security-minded approach suitable for the asset type, including role-based access, watermarking and guidance on redacting sensitive layers where necessary.

Don’t skimp on interoperability. Ask for support for open formats used by UK public bodies during coordination and handover, plus import/export pathways to asset systems. Spell out expected exchanges (models, drawings, schedules, RFIs, site photos, nonconformance records) and map them to the states and approvals. If you’re buying licences, probe how the supplier will onboard the supply chain, provide project templates, and support offline capture for field teams.

# Common mistakes

/> – Assuming “ISO 19650 compliant” is a badge any platform can wear without configuration. The compliance lives in the setup and behaviours, not the logo.
– Letting the CDE be a read-only vault. If subcontractors can’t contribute, information will leak into email and file shares.
– Skipping naming conventions and metadata. Without them, searches, filters and automated approvals don’t work when it matters.
– Treating the Information Manager as an admin. The role needs authority to enforce states, stop non-compliant uploads and escalate.

Interfaces, responsibilities and risk in a live programme

/> The CDE’s success turns on how roles and systems meet under workload. Appoint an Information Manager early with time during mobilisation to stand up the environment, agree templates, test submissions and brief teams. Map interfaces between design tools, commercial systems, site management apps and the CDE: where does an RFI originate, who applies metadata, and when does it become contractual? The goal is one source of truth with controlled gateways from email, mobile apps and federated models.

Scenario: A phased refurbishment of a live NHS outpatients department in the Midlands is running under an NEC option with a tight 18-week programme for each zone. The client’s project manager wants weekly packages of coordinated drawings and fire stopping details through the CDE to sign off night works. The main contractor’s design manager is juggling late revisions to MEP runs to avoid shutdowns, while the clerk of works insists on seeing “Published” documents only. An MEP subcontractor uses a separate site app to capture as-built photos; the digital coordinator must push those into the CDE against the right rooms and systems. An electrical containment clash triggers a hurried redesign; the Information Manager freezes the previous Shared model and routes the revision through the approval workflow so only the updated drawings hit the Published state by Friday. Monday’s QA walk picks up that a supervisor printed an out-of-date drawing; the CDE watermarking and QR codes help the team trace and replace it before night shift.

Managing risk means closing the gaps that let unauthorised or non-compliant information steer the works. Use role-based permissions so only designated reviewers can move items between states. Make the RFIs and technical queries visible in the CDE, or at least synchronised, so design and commercial decisions are auditable. Agree how contract change control maps to information states; for example, no instruction becomes live until the related details reach Published. For sensitive information (secure rooms, IT layouts), apply separate workspaces or masked layers with restricted access and a redaction policy.

Measuring value from the CDE on a public job

/> Value on a public scheme is evidenced by certainty, traceability and a clean handover. Set KPIs at tender and track them: average review cycle times by discipline, proportion of submissions accepted first time, and the number of non-compliant items rejected at each gate. For coordination, measure model federation frequency, issue close-out times and how many open issues exist at design freeze. For delivery, use field links: how many nonconformances are tied to a specific drawing revision, and how quickly they’re closed once corrected information is Published.

Handover is the public sector’s acid test. Define the asset data structure early, align it with your EIR, and confirm how models, manuals, certificates and product data will be delivered and validated. Insist on container metadata that supports asset registers and room-level tracking. Run a pre-handover data audit to catch omissions while teams are still on site. After completion, provide an archived, immutable snapshot of the CDE with agreed access terms for facilities teams.

Checklist for tender and kick-off
– State the EIR clearly, including naming rules, classification and required metadata fields.
– Demand a CDE configuration plan with screenshots of states, workflows and permissions mapped to your approvals.
– Require an Information Protocol and nominate an Information Manager with a mobilisation period and training plan.
– Map system interfaces: where RFIs, site photos and transmittals originate and how they land in the CDE.
– Define handover deliverables with test uploads in month one to de-risk the last 4 weeks.
– Set KPIs for review times, non-compliance rates and data drop completeness, and agree how they will be reported.
– Establish a security-minded access model for sensitive zones and information types.

Public frameworks are gradually tightening expectations around information management maturity, not just platform choice. Expect more emphasis on asset-ready data and demonstrable audit trails. The bottom line: specify the behaviours you need, resource the roles that enforce them, and measure the outputs that prove certainty under programme pressure.

FAQ

/> Is “ISO 19650-compliant” about the software or the process?
It’s mainly about process and configuration. A capable CDE must be set up to reflect ISO 19650 states, naming, metadata and approvals, and the project team needs to use it consistently. Most problems come from weak EIRs and poor onboarding, not from the choice of platform.

# Who should act as Information Manager on a public sector scheme?

/> It varies by procurement route. Some clients appoint one directly; others expect the lead appointed party (often the main contractor) to provide the role. What matters is clear duties, authority to enforce compliance, and time during mobilisation to configure the CDE and train contributors.

# How do you handle subcontractors who won’t use the CDE?

/> Provide simple gateways: email-to-CDE inboxes, upload portals and site-app connectors that assign metadata automatically. Pair this with toolbox talks and quick guides that show how to find the current “Published” information. The main contractor’s digital coordinator should monitor compliance and step in where information starts slipping into side channels.

# Who owns the data and how long should it be available after completion?

/> Ownership and access should be fixed in the Information Protocol and contracts. Public clients typically require an archive and continued access for operations, with retention periods aligned to asset life or statutory duties. Clarify formats, storage location and handover of administrator rights before practical completion to avoid disputes.

# How is sensitive information controlled in the CDE?

/> Use role-based permissions, segregated workspaces and watermarked outputs for controlled circulation. For highly sensitive layouts, split models or use redacted views so only authorised users see full detail. Make sure the security approach is documented in the EIR and reinforced in training, including what can and cannot be printed or emailed.

The post ISO 19650-compliant CDEs for public sector tenders appeared first on Goldcast Academy Magazine | All the latest news from the UK building industry.

TL;DR

/> – Telehandlers aren’t cranes: treat suspended loads as lifting operations with a plan, supervision and a signaller.
– CPCS A17e and NPORS suspended-loads endorsements prove you can control radius, communication and travel with a hanging load.
– Focus on pre-use checks of hook/attachment, accessory certification, weather, routes, and exclusion zones.
– Keep the load low, steady and aligned; avoid sudden inputs; stop if conditions or instructions aren’t clear.

Expectations vs reality: A17e and the NPORS suspended-loads endorsement

/> Both schemes recognise that slung loads bring extra risk beyond pallet work. CPCS A17e is an additional endorsement that sits on the telehandler category to confirm suspended-load competence. NPORS typically records this as an additional endorsement or course outcome for telehandlers. Sites differ, but many now ask specifically for proof of suspended-load competence when telehandlers are used with hooks, jibs or lifting eyes.

On live jobs, nobody expects an operator to “wing it”. A competent person plans the lift, a supervisor or appointed person briefs it, and a signaller controls the movement. The operator must understand the lift plan, know the machine’s capacity chart for the attachment in use, and work strictly within the stated radius and configuration. Telehandlers are easily pulled forward by a swinging load; wind, travel speed, ground conditions and boom angle all matter more than they do on forks.

Reality bites with paperwork and hardware. Lifting accessories (chains, slings, shackles, swivels, hooks) need to be fit for purpose and within date. The telehandler’s attachment (hook, jib or quick-hitch hook) must be suitable and secure. Load charts must match the attachment actually fitted; do not rely on memory or a generic decal. Communication must be unambiguous: standard hand signals backed up by radios where agreed. Exclusion zones are non-negotiable; members of the public and non-essential trades should be physically kept out.

How to prepare for suspended-load assessments and real work

/> Preparation is twofold: refresh your lifting knowledge and make the basics second nature. Revisit radius, working load limits, centre of gravity, sling angles and why “keep it low” is more than a slogan. If your machine offers attachment selection on a load indicator, practise selecting the correct configuration so the in-cab chart aligns with reality. If it’s a simpler model with only static charts, get comfortable reading those charts and relating them to boom stages and extension marks.

Practise calm control. Small joystick inputs, gentle acceleration and smooth braking reduce swing. Use tag lines when the plan permits and the environment allows. Build the habit of pausing to let a load settle before slewing the chassis or adjusting boom angle. In-house drills in a training yard help, but ask for time handling awkward shapes (mesh, roof trusses, rebar bundles) because those are the ones that show up the gaps.

Sort your documentation and kit. Expect to be asked about accessory condition, certification in date, attachment type and the basics of the lift plan. Walk the route on foot: ground-bearing, cambers, manholes, soft spots and parked vehicles become problems once the load is on the hook. Agree signals with the signaller before moving a millimetre, including stop/hold and what happens if comms fail. Check the weather; gusty conditions and long, light loads are a bad mix.

How to perform on the day: proving safe suspended-load control

/> Most assessments follow a predictable flow: pre-use checks, understanding of the task and plan, set-up, controlled pick, steady travel, accurate placement, and shutdown. Verbalising your thinking helps show competence without guessing at “test answers”. Point out attachment security, the correct chart, accessory checks, exclusion zones, communication, and how you’ll manage swing. On the move, keep the load low to the ground to shorten the pendulum, travel at walking pace, and avoid abrupt steering or braking. If you lose sight or lose comms, stop and ask for the signaller to regain control. Never exceed the planned radius; boom in rather than inching the chassis if you’re close to the limit.

# A housing plot scenario: windy roof trusses under time pressure

/> A mixed-weather afternoon on a tight estate site, with delivery lorries blocking half the access road and scaffold lifts at different heights. The telehandler is fitted with a manufacturer’s hook, and the task is to lift a long roof truss from the delivery trailer to the scaffold. Wind gusts are coming down the street, funnelled between plots. The signaller has agreed hand signals and radio backup, and an exclusion zone is taped off. As the operator takes the strain, the truss wants to weathervane. A tag line handler keeps distance and controls rotation under the signaller’s instruction. The operator holds the boom steady, allows the swing to dampen, then travels in a straight line at walking pace, stopping twice to settle the load before edging in to the drop-off. Once the truss is placed, the slings are released with the load secure, and the route is cleared before the telehandler withdraws.

# Suspended-load essentials checklist

/> – Confirm the attachment type matches the in-cab capacity information and is correctly locked.
– Inspect chains/slings/shackles, check identification and in-date certification.
– Walk and agree the travel route, gradients and exclusion zones; remove avoidable obstructions.
– Agree communication: primary signals, radio protocol, and what happens on loss of comms.
– Take the strain slowly, check balance, and pause to let swing settle before moving.
– Keep the load low, boom-in wherever possible, and travel at walking pace.
– Stop work if wind, visibility, ground or instructions change beyond what the plan allows.

# Common mistakes

/> – Treating a hook like forks. Suspended loads behave dynamically; the same speeds and turns that are fine on pallets can cause uncontrolled swing.
– Ignoring the attachment-specific chart. Capacity can reduce significantly with a hook or jib; using a forks chart is guesswork.
– Poor comms discipline. Mixed hand signals, dead radios, or “just follow me” instructions lead to confusion and unsafe movement.
– No exclusion zone. Allowing trades or the public to walk under or near the load is a predictable route to a serious incident.

Staying competent after the card

/> Competence drifts when real work gets busy and shortcuts creep in. Build refreshers into your calendar rather than waiting for a near miss. Rotate through awkward loads in safe practice areas so you don’t only ever lift neat bundles. Keep accessory control tight: quarantine damaged slings, record inspections, and make it easy for operators to reject non-compliant gear without grief.

Toolbox talks should cover wind limits in practical terms, how to manage swing, and what a “stop” looks like in your environment. Supervisors should check that lift plans are briefed in plain English, not filed in a folder. If a telehandler is being used for repeated suspended lifts, ask whether a crane or roto with stabilisers is the safer choice. The machine can do it doesn’t mean the system is right.

Bottom line: suspended loads on telehandlers demand crane-thinking with telehandler feel. Get the plan, attachment, comms and pace right, and you’ll keep people, plant and programme on track.

FAQ

# Do I need CPCS A17e or an NPORS endorsement to lift on a hook?

/> Most UK sites now expect a telehandler operator to hold specific proof of suspended-load competence rather than only a standard forks ticket. CPCS shows this as the A17e endorsement; NPORS records a similar suspended-loads outcome on the telehandler category. Always check the principal contractor’s requirements before turning up.

# What do assessors typically look for on suspended-load tests?

/> Assessors want to see controlled, deliberate operation with good communication and planning. Expect to demonstrate thorough pre-use checks, correct identification of attachment and charts, safe pick-up, low-and-slow travel, and accurate placement within an exclusion zone. Explaining your decisions and stopping when unsure usually counts in your favour.

# How far can I travel with a suspended load on a telehandler?

/> There’s no one-size-fits-all distance; it depends on the plan, the load, the ground and the site controls. Good practice is to keep routes short, straight and segregated, keeping the load low and stable, and stopping if swing builds. If you’re doing repeated long-distance moves, challenge whether the method is suitable.

# What paperwork should be in place for suspended-load lifts?

/> Expect a basic lift plan and briefing, evidence that lifting accessories and the attachment are suitable and in date, and a clear method for communication and exclusion. Many sites also record pre-use checks and dynamic risk assessments. Keep it practical and accessible so the operator and signaller can actually use it.

# How often should I refresh my suspended-load skills?

/> Initial training proves capability at a point in time; skills fade without practice. Many operators benefit from periodic refreshers or on-site verifications, especially if they rarely handle slung loads or if site methods have changed. Toolbox talks and short supervised practice sessions can keep standards up between formal courses.

The post Telehandler suspended loads: CPCS A17e and NPORS explained appeared first on Goldcast Academy Magazine | All the latest news from the UK building industry.

TL;DR

/> – Draw the load path and drop zone on the lifting plan, then mark it on the ground with barriers that take effort to defeat.
– Put a named controller on the zone; if they walk off, the lift stops.
– Keep pedestrians, trades and vehicles out with one-way routes, spotters and clear waiting areas.
– Brief at the start, re-brief on change, and record each lift as a short entry in the diary or permit.
– Wind, line of sight and adjacent work can collapse your zone—pause, recalc and reset rather than wing it.

The danger space: swing radius, load path and the real drop zone

/> Exclusion zones are built around where the load will travel, where it might land if released, and where the crane or telehandler could slew or jack-knife. The primary zone is the load path and the immediate drop area; nobody not essential to the lift should be inside it. A secondary zone considers what happens if the load drifts in wind, catches on a protrusion, or components fall during slinging/unslinging. Good practice is to give the lifting team unbroken space to manoeuvre, with set entry points controlled by a signaller. The size of the zone is driven by load size, radius, plant type, and nearby edges or overhead obstructions, not by what barrier you have in the container. Where the public or live buildings are nearby, the secondary zone needs stronger measures—solid hoarding, occupied building controls, or timed isolations.

How it plays out on a live build

/> A mid-rise housing block in a busy town centre is lifting bathroom pods with a tower crane. The pods land onto a level four deck where two fit-out crews are also trying to work. The foreman sets out cones and tape, but deliveries push past to get to a laydown. A visiting MEP supervisor walks under the load to “just grab a quick measure.” Wind picks up and the pod starts to weathercock, pushing tag line handlers towards an open slab edge protection. The lift pauses. A new zone is marked with Heras and crowd barriers, the route is cleared by the banksman, and the site gate agrees a 30-minute hold on deliveries until the pods are placed and unslung.

Controls that turn lines on a plan into a real barrier

/> Start with the lifting plan that defines the route, set-downs and communications. Translate that into ground truth: place barriers where the drawing says, not where they’re convenient. Use barriers that change behaviour—crowd barriers or Heras panels, not just tape—backed by signage that says who may enter. Have a named signaller controlling entry and a plant marshal managing interfaces with traffic. At set-down points, create a quiet area for unslinging with stable footing, good lighting and zero trip hazards.

Keep interfaces tidy. If other trades must pass nearby, create a signed diversion and a physical “stop line” well before the danger space. On high lifts or long booms, radios with agreed phrases matter more than shouting; add a back-up hand signal plan if radios fail. Where the risk increases (wind, blind lifts), add tag lines and keep the team size tight—only those needed to land and secure.

Pre-lift zone checklist
– Mark the load path and drop zone on the deck with paint and set barriers to match.
– Establish one controlled entry point, managed by the signaller, with “No admittance” signage.
– Confirm housekeeping: no trip hazards, no loose materials, and slab edges protected.
– Agree a delivery and pedestrian hold with the gate and adjacent supervisors during each lift.
– Test comms: radios working, call-and-response confirmed, alternative signals agreed.
– Confirm weather limits and what triggers a pause; have a plan for lowering or making safe.
– Record the setup in the permit or lift diary, including who is controlling the zone.

Where zones unravel on UK sites

/> Letting pedestrians “nip through” the tape
Shortcuts quickly become the norm. Once one person is waved through, others will follow and your barrier becomes decoration.

# Barriers that move with a boot

/> Tape or single cones won’t stop a distracted subcontractor. Lightweight kit gets nudged, and your clear line is gone.

# No named controller

/> If everyone is in charge, nobody is. Without a specific person owning the line, the zone steadily fills with “helpers”.

# Changing the load without resetting the zone

/> A larger panel or a lift to a different bay needs a bigger or differently shaped zone. Reusing the old layout invites near misses.

Policing the zone through the shift

/> Exclusion zones last only as long as someone is visibly enforcing them. Put a single accountable person on the boundary: the appointed person or crane supervisor sets the standard; the signaller or plant marshal holds the line. Use simple, verbal prompts—“Stop there, we’re mid-lift”—backed by relocation of barriers when work phases change. Keep distractions down: the signaller shouldn’t also be juggling deliveries, radios for other trades, or inductions. If a change creeps in—wind increases, a new set-down, or poor sight lines—pause the lift and re-brief. Record each lift session with a short note: what changed, who was present, any holds or resets; this creates continuity across shifts and defends decisions.

Where public interfaces exist, add layers: a second marshal at the outer boundary, timing lifts to quieter periods, and temporary closures signed at street level. On small sites, plant like telehandlers can feel informal; hold the same standard as a tower crane—suspended is suspended.

# What to tighten this week on the lifting plan

/> – Map the next five lifts on deck with chalk and paint so the team can see the real path before barriers go in.
– Mark the primary zone with crowd barriers and the secondary zone with cones, and brief what each means.
– Brief adjacent trades at start-of-shift and before any late lift; agree where they will wait and who calls them back in.
– Station the signaller at the single entry point, and swap them out if they are pulled onto other tasks.
– Log wind checks and any pauses in the lift diary; escalate early if the zone repeatedly collapses under programme pressure.

The discipline is simple and visible: if people can walk under a suspended load, the job stops. Expect more scrutiny on how zones adapt to change, not just how they look at 8am.

FAQ

/> How big should a lifting exclusion zone be?
Size it to the load path, the set-down area, and any credible drift or swing, not to a default number. Consider the plant’s radius, blind spots, slab edges and nearby activities. If in doubt, make it larger and then trim with barriers once you prove the space is controlled.

# Do we need a permit for every lift?

/> Use a permit or lift diary for planned operations and anything non-routine. The aim is to capture the method, comms, people, and the zone setup, plus any hold points. For repetitive lifts, one permit can cover a series, provided the conditions and zone stay the same and you record changes.

# What if deliveries turn up during a critical lift?

/> Hold them at the gate and use a pre-agreed waiting area away from the zone. Coordinate with the logistics lead so the gate knows when a lift window is live. It’s better to slip a delivery than to compromise a live exclusion zone.

# How do we manage exclusion zones near the public?

/> Layer controls: robust barriers or hoarding, a secondary buffer, and a marshal at the outer edge. Time the lift to quiet periods where possible and communicate with neighbours ahead of high-risk moves. If you can’t maintain clear margins, postpone or re-engineer the lift.

# Is PPE enough inside an exclusion zone?

/> PPE is the last line of defence and does not make it acceptable to stand under a suspended load. The priority is to keep non-essential people out, maintain stable footing, and use reliable comms and tag lines. Use PPE appropriate to the task, but don’t rely on it to compensate for a weak zone.

The post Setting Up and Policing Lifting Exclusion Zones appeared first on Goldcast Academy Magazine | All the latest news from the UK building industry.

TL;DR

/> – First safety case-related certificates for higher-risk buildings suggest the regulator’s expectations are now being applied in live assessments.
– Owners should tighten evidence of risk control, competence, maintenance and resident engagement, not just narratives.
– Gaps in golden thread data and legacy fire safety works are likely to slow approvals and push remedial programmes.
– Supply chains will see greater demand for traceable products, competent installers and verifiable inspections.
– Watch for how conditions, timelines and enforcement evolve as more buildings are assessed.

What the early certificates signal for HRB owners and dutyholders

/> For owners and managers of higher‑risk residential blocks, the practical implication is a pivot from assembling a safety case report to proving its effectiveness. Industry conversations suggest the regulator is testing three things in particular: whether major hazards are properly identified for the specific building; whether controls are reliable, maintained and competent; and whether information is live, retrievable and used to manage risk day to day. Paper frameworks without clear evidence of inspection, testing and rectification are unlikely to satisfy that test. Resident engagement also appears to carry more weight than some expected, with a focus on whether residents understand arrangements and can report concerns.

Expect procurement and project delivery to shift. Clients will ask for traceability of products and installations that map into the golden thread, with auditable sign‑off suitable for future regulatory scrutiny. Competence claims will need to be evidenced for those designing, installing and maintaining life‑safety systems, not only at project completion but across the operational life of the building. Interim measures may be tolerated where proportionate, but the direction is towards sustainable, engineered controls that are monitored and recorded.

Consider a typical scenario. A landlord of a 15–20 storey block is asked to submit its safety case report and supporting evidence. In pulling records, the team discovers incomplete documentation for fire‑stopping in risers and historic smoke control performance tests. Resident drop‑ins reveal inconsistent understanding of evacuation messaging, with language barriers flagged. The owner commissions targeted surveys, upgrades signage and agrees a planned programme to verify compartmentation, documenting the rationale and timelines. When the regulator reviews the submission, the focus turns to whether proposed fixes are proportionate, resourced and tracked, rather than the narrative alone.

Operational implications, programme risk and what comes next

/> From an operational standpoint, these first decisions will likely harden client expectations on programmes, budgets and competencies. Building managers may push for earlier invasive surveys to confirm compartmentation, more frequent end‑to‑end testing of fire alarm, smoke control and power supplies, and clear evidence trails for corrective actions. Where supply chains are thin, programme risk will rise: a limited pool of specialists for complex systems can become a bottleneck, and owners may need to stagger works to maintain safety. Insurers and lenders are watching too; while there is no automatic link, visible regulatory assurance may influence cover terms or due diligence questions.

Handover and ongoing management are converging. New build teams will be under pressure to deliver a digital golden thread that downstream operators can actually use, not just archive. For existing stock, many owners are reassessing their internal competence frameworks and escalation routes, ensuring that known risks cannot sit unresolved without clear justification and timescales. The emerging lesson is that the safety case is not a one‑off document; it is an operating system for the building that must stand up to external challenge.

# What to watch next

/> – How quickly the regulator scales up assessments and whether timelines or sequencing for further buildings are signalled.
– The extent to which certificates include conditions that drive specific remedial actions and monitoring.
– Any published insights or case studies from the regulator clarifying what evidence proved persuasive.
– Whether visible regulatory assurance affects insurance appetite, resident confidence and market transactions.

# Caveats

/> Only a small number of decisions appear to be in the public domain, and each building’s characteristics will drive different outcomes. Terminology and documentation requirements may evolve as the regime beds in and more cases are assessed. Owners should avoid assuming that what worked for one block will pass for another with different age, systems and resident profile, and should seek competent advice tailored to their stock.

The groundwork is being laid for a more disciplined, evidence‑led approach to managing higher‑risk buildings. The open question is whether owners and their supply chains can scale competence, data quality and remedial capacity fast enough to keep pace with regulatory expectations.

FAQ

/> What is meant by a safety case and a certificate in this context?
A safety case is a structured argument, supported by evidence, that the building’s major fire and structural risks are identified and controlled as far as is reasonably practicable. Under the current regime, owners of higher‑risk buildings are required to prepare a safety case report and, when assessed, may receive regulatory certification linked to that assessment. The precise title and form of the certificate can vary, but the principle is formal assurance following scrutiny.

# Who is responsible for preparing and maintaining the safety case for an HRB?

/> The duty typically sits with the accountable person, and where more than one exists, the principal accountable person leads coordination. In practice, owners often engage competent consultants and contractors to assemble evidence, but legal responsibility remains with the dutyholder. Day‑to‑day management teams must be able to demonstrate how the safety case drives operational decisions.

# What kind of evidence is the regulator likely to look for?

/> Expect to provide building‑specific risk assessments, maintenance and testing records for life‑safety systems, product and installation traceability, and clear records of remedial actions taken. Evidence of resident engagement, communication strategies and how concerns are handled also features. The emphasis is on verifiable data rather than general policies.

# Does receiving a certificate change what residents or building users will notice?

/> Residents may see more visible communications, clearer signage and potentially works programmes to improve systems or compartmentation. In some cases, owners might adjust management strategies or testing regimes, which could affect access, alarms or scheduling. The goal is to improve control of risk while maintaining practical living conditions.

# What happens if gaps are found during assessment?

/> Where gaps are identified, owners can expect requests for further information, conditions attached to assurance, or instructions to undertake specific remedial actions. Outcomes will depend on the nature and severity of the issues and the credibility of the plan to address them. Proactive, well‑evidenced programmes are more likely to be viewed constructively than reactive or unresourced proposals.

The post BSR issues first Safety Case Certificates: lessons for HRB owners appeared first on Goldcast Academy Magazine | All the latest news from the UK building industry.

TL;DR

/> – NUAR gives an authoritative, combined picture of underground utilities but does not replace HSG47 practices, PAS 128 utility surveys, or trial holes.
– Treat NUAR as a planning tool: use it early for design coordination, traffic management staging, and utility deconfliction, then validate on site.
– Get access sorted before mobilisation, define who can use the data, and align NUAR outputs with your CDE, method statements, and permit-to-dig packs.
– Expect variable coverage and data quality during rollout; manage residual risk with vacuum excavation, CAT & Genny, and change control when reality differs.

NUAR in plain English: what it is and what it isn’t

/> NUAR is a government-backed digital service that brings together underground asset data from multiple owners—water, gas, power, and telecoms—into a consistent map for authorised users. It aims to reduce utility strikes and speed up planning by letting teams see what is likely under the ground before they cut, core, or trench. In practice, it complements (not replaces) established workflows: HSG47 safe digging, PAS 128 utility detection surveys, and permits to dig still stand. NUAR helps you decide where to scan, where to trial hole, and how to phase works; it does not make buried infrastructure “certain”.

Expect the rollout to be phased by region and asset owner onboarding. Coverage and data richness will vary until more utilities are connected and records are normalised. Access is controlled—organisations need to register users and follow usage rules set by the service and data providers. Treated properly, NUAR becomes a front-end planning layer that cuts guesswork and supports coordination across designers, planners, and site teams.

How NUAR fits real UK site workflows

/> Picture a junction upgrade under a Section 278 agreement in a busy town centre. The principal contractor has a five-week night-time traffic management window and faces a tight diversion milestone linked to the school term. The general foreman wants to get a drainage run in on week one; the temporary works coordinator is nervous about unknown services under the footway. The utility survey subcontractor is booked for GPR and EML, but only has two night shifts before core plant arrives. Using NUAR at tender stage, the planner identifies a likely 11kV and two comms ducts in the conflict zone and revises the method to start with vacuum excavation and trial holes. The commercial lead flags potential diversion cost exposure and starts C2/C3 enquiries early. The result: a resequenced programme that keeps the TM window viable and removes a strike-shaped hole in the risk register.

Operationally, bring NUAR in as early as possible. During tender and ECI, the design manager and planner should overlay NUAR with proposed alignments and street works constraints, then engage utility owners sooner where diversions are likely. At pre-start, the SHEQ lead can embed NUAR outputs into the design risk register, site induction, and RAMS—defining where “no mechanical excavation” zones apply, where vacuum excavation is mandated, and where GPR needs to be repeated due to changing ground or phasing. Before the first cut, the site engineer folds NUAR extracts into the permit-to-dig pack with clear date/time stamps and a route for escalation when what’s found doesn’t align.

On site, NUAR is a reference, not a green light. Supervisors treat it like any plan-of-record: useful for positioning and sequencing, but always verified by CAT & Genny, marked-out scans, and controlled trial holes. If the ground differs from the NUAR picture, stop, inform the engineer, and trigger change control to update method statements, redesign details, or book utility attendance. Post-excavation, the team should capture as-built locations and feed lessons back to design and the client.

# Site-ready checklist for NUAR-enabled digs

/> – Secure organisational access to NUAR before mobilisation; nominate a data steward to manage users and permissions.
– Export NUAR extracts with clear scales, legends, and timestamps, and file them in the CDE alongside utility survey outputs.
– Map NUAR “zones of concern” onto RAMS: define vacuum excavation areas, scanning extents, and no-go corridors.
– Coordinate early with utility owners where conflicts are likely; align NUAR outputs with C2/C3/C4 communications.
– Brief foremen and plant operators on what NUAR shows and, critically, what it might miss; link to HSG47 steps.
– Schedule GPR/EML and trial holes to validate high-risk areas before major plant arrives or TM windows open.
– Set a rapid escalation path for mismatches: who to call, who authorises hold points, and how drawings and permits are updated.

Pitfalls and fixes with NUAR data

/> The biggest trap is over-trust. NUAR isn’t a perfect map; it’s a better starting point. Records may be incomplete, offsets imprecise, and service connections patchy, especially in older streets. The fix is cultural as much as technical: write NUAR into your process as an input to risk-based verification, not an alternative to it.

The second pitfall is access lag. Teams often leave registration until the week of mobilisation, then scramble. Treat NUAR access like any other critical system—get it in the pre-start checklist and ensure supervisors can actually open the viewer on their devices. Third, data sprawl can bite. Screenshots and shapefiles drift out of context, lost in email chains. Anchor NUAR outputs in your CDE with disciplined naming, versioning, and linkage to permits to dig.

Finally, procurement misalignment. If your utility survey provider, street works consultant, and principal designer aren’t set up to consume NUAR data, you’ll lose most of the value. Write NUAR usage into scopes and information requirements, including expected deliverables and update protocols.

# Common mistakes

/> – Treating NUAR as if it were PAS 128. It’s not a detection survey and cannot prove absence.
– Printing a single NUAR plot and building a week’s work around it. Data can change and scale matters; refresh and annotate by area.
– Failing to brief plant operators. If only the engineer has seen the map, the risk stays in the trench.
– Ignoring change control when the ground disagrees. Discoveries must trigger a method, drawing, and permit update, not a shrug.

What to watch next in the UK rollout

/> Expect coverage to deepen as more utility owners onboard and data is cleaned, which will make NUAR increasingly useful beyond dense urban cores. Clients and highway authorities are already signalling stronger expectations around demonstrating how underground risks are managed; showing NUAR-informed decisions in RAMS and permits is likely to become normal practice.

The bottom line: treat NUAR as an early-warning system that sharpens planning, but keep HSG47, PAS 128 and competent supervision front and centre. The contractors who get ahead now—access sorted, scopes aligned, crews trained—will save time, money, and stress as the service matures.

FAQ

# Is NUAR mandatory for contractors to use on UK projects?

/> There is no blanket mandate across all projects, and expectations vary by client and highway authority. However, as NUAR rolls out, more public clients and permit authorities are asking to see evidence that underground risks have been considered, and NUAR is a credible way to demonstrate that. Using it proactively helps you meet general duties around planning and risk management without claiming it replaces other standards.

# How should NUAR sit alongside PAS 128 and HSG47?

/> Treat NUAR as an input to planning, not a substitute for detection or safe digging. Use it to identify high‑risk corridors, then specify PAS 128 surveys in those zones and embed HSG47 steps into RAMS and permits to dig. If survey or excavation findings differ from NUAR, adjust the plan promptly and document the change.

# Can NUAR data be shared with subcontractors and suppliers?

/> Access is controlled and subject to terms; pass data only to those who need it for the work and keep it within agreed systems. A practical approach is to export area-specific plots with legends and timestamps into the CDE, then reference them in RAMS and permits rather than circulating raw datasets widely. Make sure your subcontract orders state how NUAR outputs will be used and updated.

# Will NUAR replace the C2/C3/C4 diversion process?

/> No. NUAR can inform where diversions might be needed and help you ask better questions earlier, but formal enquiries and cost estimates still run through utility owners’ established processes. Use NUAR to focus those enquiries on real conflicts and to sequence them to suit programme pressure and traffic management windows.

# How do we evidence NUAR use in QA and handover?

/> Include dated NUAR extracts in the permit-to-dig pack, note how they informed risk controls, and capture any deviations found during works. Keep a simple audit trail: pre-construction NUAR snapshots, validation survey results, trial hole logs, and redlined plots showing as‑found positions. At handover, summarise what changed and feed improved records back to the client where contractually allowed.

The post NUAR rollout: what UK contractors need to know appeared first on Goldcast Academy Magazine | All the latest news from the UK building industry.

TL;DR

/> – Don’t lift off forks; use an approved lifting hook/attachment with current certification and tagged lifting gear.
– Have a simple lift plan, a designated signaller, and a segregated route including set-down positions.
– Check charts, wind and ground; boom angle and travel speed matter more with a swinging load.
– Keep taglines on and people out; if comms fail or the route isn’t clear, stop and reset.
– Expect sites to ask for the suspended-loads endorsement or other proof you’re up to it.

Competence for suspended telehandler lifts, in plain English

/> Operating a telehandler with suspended loads is a step up from pallet work. Sites look for proof you’ve been trained for suspended lifts and that your recent experience matches the task. That usually means a card or endorsement covering suspended loads, plus familiarisation on the specific machine and attachment. Supervisors may also ask about recent refresher or on-site verifications, especially if you’ve been mostly on forks and not done a suspended lift in months.

You’re expected to understand the difference between telehandler pick-and-carry and crane lifting. A telehandler’s stability is sensitive to boom extension, boom angle and dynamic movement when a load can swing. Charts and load indicators help, but they don’t replace judgement about ground conditions, gradients and wind. Using a certified hook or jib, correct shackles and slings with visible tags is fundamental; “from the forks” is not acceptable.

Communication and coordination are part of competence. A named signaller/banksman, agreed signals or radios, and an exclusion zone are standard. A short, written lift plan that covers who does what, the path, holds, set-down spots and wind triggers is normal practice on controlled sites.

On live sites: the routine that keeps suspended lifts boring

/> Before the first pick, walk the route with the signaller. Mark pinch points, low headroom, blind turns, overhead services and areas where people tend to stray. Confirm the set-down area is stable and level enough to land without last-second booms in and out. Check the hook/attachment is pinned and locked, the lifting gear is in date, and the load is correctly slung with the centre of gravity understood.

The signaller controls the space. They keep people out, manage the pace, and call stops when wind or visibility changes. The operator drives as if the brakes are made of glass: smooth acceleration, steady steering, never chasing a swinging load. Taglines on longer or awkward pieces reduce the pendulum effect and help the signaller correct rotation without stepping under the load.

If the site wants you to travel with a suspended load, agree a crawling speed and boom position that keeps the load low but clear, without risking ground strike. Avoid side slopes and sudden steering inputs. Don’t let anyone rush you into booming out to “just reach that last metre” without checking capacity at that angle and radius. Be ready to stand down if the plan on paper doesn’t survive first contact with the real site.

# Scenario: cladding frames, tight plot, shifting wind

/> A 14 m telehandler is tasked with moving three cladding frames from a delivery wagon to a fifth-floor edge protection zone on a city-centre office build. It’s mid-afternoon, wind has picked up and the laydown is tight with a cabin and temporary fencing pinching the route. The frames are on a certified lifting beam, with two taglines ready. The operator and signaller walk the route, noting a blind corner by the hoist and a slight crossfall toward a drainage trench. On the first lift, the signaller halts at the corner as a labour gang drifts into the exclusion. Radios crackle; they’re cleared and the lift resumes at a crawl. A gust starts the frame swinging; the operator holds position, the signaller dampens with taglines, and they agree to land the first frame on a nearer, level pad rather than chase the original set-down in worsening wind. The supervisor updates the plan to split the lift into two moves.

Pitfalls and fixes you can control

/> Telehandlers are unforgiving when the boom is long and the load is moving. A small steering input can become a big swing. Most incidents stem from rushing, poor comms, or using the wrong kit. Fixing those is less about paperwork and more about slowing down, choosing the right attachment and keeping the signaller in charge of space and pace.

Suspended lifts go best when they’re dull. Repeatable signals, a route that’s been walked, steady machine movements and taglines that do the rotation work instead of the boom. The moment things feel “heroic” is the moment to pause.

# Common mistakes

/> – Lifting from the forks or an unapproved hook: a shortcut that risks dropped loads and a quick stop by the supervisor.
– No agreed signaller or signals: two people shouting different instructions leaves the operator guessing under load.
– Overreaching to “just make it”: load charts don’t bend; boom-out under pressure is a common tip-over trigger.
– Ignoring wind and ground: gusts and soft spots combine with a swinging load to turn stable into marginal fast.

# Fixes that stand up to supervisor scrutiny

/> – Pre-lift huddle: operator, signaller and supervisor agree the load, gear, route, holds and stop points.
– Attachment and gear check: approved hook/jib fitted correctly; slings/shackles tagged and suitable; no nicks, twists or bent pins.
– Route and segregation: cones/barriers set, pinch points cleared, spotters only where necessary and never under the load.
– Comms confirmed: radios tested or hand signals agreed; only one signaller talks to the operator.
– Machine settings: stabilisers (if fitted) deployed as specified; boom angle and extension managed to keep capacity in hand.
– Movement plan: crawl speed, smooth controls, taglines in use; stop if swing builds, dampen, and reset.
– Weather and ground: check wind and rain; avoid side slopes; reassess if conditions change.

The direction of travel on UK sites is tighter control of suspended loads on telehandlers, closer to mini-crane standards. Expect more supervisors to ask for visible endorsement, a short lift plan and evidence of the right attachment, not forks with a chain.

FAQ

# Do I need a specific endorsement to use a telehandler for suspended loads?

/> Most UK sites expect operators handling suspended loads to hold the relevant suspended-loads endorsement or have documented training covering it. Your plant card should show the category and any endorsements. If you’ve only worked with pallet forks, arrange additional training or familiarisation before taking suspended lifts.

# What do assessors typically look for during a suspended-loads assessment?

/> Assessors want to see safe setup, correct attachment and gear selection, proper pre-use checks and a clear understanding of the machine’s capacity at different boom positions. They watch your coordination with a signaller, your route choice and your control of swing. Smooth, deliberate movements and stopping the job when something isn’t right are strong indicators of competence.

# Can I travel with a suspended load on a telehandler?

/> Travel is sometimes permitted if the plan, ground conditions and load type allow, but it needs tight control. Keep the load low but clear, move at a crawl, and avoid side slopes and sharp steering. If the route is congested or wind is building, split the move into stages or reconsider lifting options.

# What paperwork will a site usually want for suspended telehandler lifts?

/> Expect to be asked for a simple lift plan, evidence the attachment and lifting gear are in date, and proof of operator and signaller competence. Toolbox briefings or point-of-work risk assessments are often used to capture route, comms and weather limits. Keep the plan practical and match it to what you’ll actually do on the deck.

# How often should I refresh or be re-checked for suspended-load competence?

/> There isn’t a one-size timetable, but many sites look for recent experience, periodic refresher training and on-site verifications, especially after long gaps. If you’ve not done suspended lifts for a while, ask for a refresher or mentoring session. Familiarisation on unfamiliar models or attachments is also expected before you start.

The post Telehandler Suspended Loads: What UK Sites Expect appeared first on Goldcast Academy Magazine | All the latest news from the UK building industry.

TL;DR

/> – Treat every excavation as if live services are present until proven otherwise with competent scans and trial holes.
– A permit-to-dig must fix scope, method, markings, hold points, supervision and stop-work triggers.
– Revalidate permits after delays, weather, plant changes or any change in markings or ground conditions.
– Use insulated hand tools or vacuum excavation near suspected services and document as-built findings.

A staged permit-to-dig approach that actually works

# Plan the dig from the desk, not the trench

/> Start with a defined excavation scope linked to programme and boundaries. Gather utility records from statutory undertakers and the client, including any private services for site compounds, lighting, EV points and previous tenants. Agree no-dig zones and proximity limits as good practice where high-risk assets are suspected. Build the method with temporary works needs, plant types, access routes and spoil locations to keep plant and people separated. Allocate a named permit issuer and supervisor; set competence expectations for scanning and excavation. Identify isolation opportunities early; if they’re not possible, plan the work around live status with increased controls.

# Scan, survey and mark with discipline

/> Use calibrated cable avoidance tools and, where the risk profile warrants it, bring in ground-penetrating radar to build confidence in congested areas. Scanning must be done by a competent person who understands limitations, signal interpretation and the traps around depth indications. Mark services on the ground with clear, colour-coded lines, arrows and text; capture time-stamped photos tied to a sketch on the permit. Refresh markings regularly and after rain, trafficking or delays. Remember private and temporary services are rarely on utility plans—walk the route from source to likely destination and include these on the mark-up. Define the permitted excavation footprint on the ground so operators can see exactly where they are allowed to dig.

# Control interfaces and isolate where possible

/> If an isolation is achievable and proportionate, coordinate it with the asset owner and lock it into the programme. Where work must proceed around live assets, adopt a safe digging methodology: set exclusion zones, control plant slew, position the banksman where they can see both bucket and markings, and manage plant–pedestrian interfaces. Pick plant and attachments to suit the method—avoid percussive tools near suspected services and limit bucket width where precision is needed. Manage environmental interfaces too: planned dewatering points, bunded fuel zones away from services, and clear drainage routes to avoid flooding trenches and washing off markings. Protect open excavations with shoring or battering and maintain access with edge protection; buried-services control often slips when teams are busy chasing temporary works or traffic management changes at the same time.

# Authorise the dig and brief the team

/> A permit-to-dig is not a formality—it is a job-specific permission that ties together location, depth, method, equipment, supervision and emergency arrangements. It must include drawings, ground markings photos, list of known services, isolation status, proximity limits, hold points (e.g. after trial holes) and stop-work triggers. Fix the permit duration; if work pauses, the site changes, markings degrade or plant swaps, the permit lapses and requires revalidation. Deliver a toolbox talk on the exact dig area and method; deal with language barriers and ensure the operator and banksman can point to no-dig zones. Display the permit at the workface and keep copies with the supervisor and machine operator.

# Dig like there is a cable everywhere

/> Start with trial holes to expose services where the scan suggests risk or where records are poor. Use insulated hand tools or vacuum excavation around suspect locations; progress with care and continuously relate what you find to the mark-up. Never assume one exposed service is the only one—keep scanning and observing as you go. If anything unexpected appears—ducts, marker tape, a different cable direction—stop, make the area safe, and rebrief. Maintain tidy edges, safe egress and spoil placement away from markings; poor housekeeping hides clues and increases the chance of a strike. Record actual positions with photos and sketches so the permit and as-builts reflect reality.

# Monitor, record and close out properly

/> Supervision should include periodic hold-point checks and a final review before deeper cuts. If the job runs into another shift or subcontractor changeover, handover the live permit pack and walk the workface. Close the permit only when the dig is complete, services are protected, and as-built information is captured and shared. If there’s a near miss, pause, document, and share lessons with the wider site—most service strikes have had at least two missed opportunities to stop.

A civils near-miss that reset the approach

/> On a road-widening scheme, a subcontractor planned to excavate a short trench to tie in a new gully. Utility plans were reviewed and a scan completed the day before, with markings placed in chalk due to rain. The morning brought heavy traffic management changes and a late plant swap to a larger excavator. Chalk marks had largely vanished, and the operator took guidance from memory and a week-old sketch. Within minutes the bucket scraped an orange duct not shown on the plans, feeding the temporary compound. Work stopped, the area was made safe, and a vacuum excavator exposed the run properly. The strike was avoided by luck; the lesson learned was simple: no visible markings and plant change equals no dig. The team switched to paint and pin flags, revalidated permits after traffic management changes, and introduced vacuum excavation for all tie-ins near the compound.

Supervisor’s pocket checklist before breaking ground

/> – Walk the marked area and verify every line corresponds with the latest records and scan notes.
– Confirm the permit-to-dig is in date, specific to the exact footprint and signed by issuer and supervisor.
– Check the CAT/Genny calibration status and operator competence; agree scan hold points during the dig.
– Verify isolation status or live-working controls; brief emergency actions and stop-work triggers.
– Inspect that hand tools are insulated and the correct plant/attachments are on site as per the method.
– Make sure markings are visible, weatherproof and refreshed; add physical indicators like flags or pegs if needed.
– Agree banksman position, exclusion zones, spoil placement and communication signals.

Where buried-services control often falls down

# Assuming records are accurate

/> Utility plans are often incomplete, out of date or missing private services. Treat them as a starting point, not the answer.

# Letting markings fade

/> Rain, dust and traffic quickly erase ground marks. If you can’t clearly see them at the workface, you don’t have permission to dig.

# Relying on one person’s memory

/> The competent scanner might not be on the machine when the trench goes in. The permit, drawings and photos must allow any competent person to understand the risks.

# Pushing on after finding the first service

/> Finding one asset can create false confidence. Keep looking—cables and pipes commonly share corridors and cross at shallow angles.

Tightening buried services control this week

/> – Map every live excavation and verify each has an in-date, location-specific permit pinned at the workface.
– Run a 15‑minute re-brief with operators and banksmen using the near-miss scenario above to reset expectations.
– Tag all CATs with calibration dates and record which named, competent persons are authorised to use them.
– Introduce a simple rule: any weather event, delay over a day, traffic management change or plant swap triggers permit revalidation.
– Trial vacuum excavation for first-pass trial holes in one high-risk area and capture the time and damage avoided.

Bottom line on permits-to-dig for buried services

/> Permits only work when they control behaviour at the workface, not just paperwork at the office. Tight scope, visible markings, disciplined scanning and a supervisor who is willing to stop the job will keep buckets clear of cables and pipes.

FAQ

# How often should we rescan during an excavation?

/> Rescan at defined hold points and whenever the dig extends beyond the originally permitted footprint. It’s also good practice to rescan after breaks, shift changes or when new obstructions or unexpected ducts appear. Treat scanning as a continuous verification, not a one-off tick.

# When is ground‑penetrating radar worth bringing in?

/> GPR helps in congested corridors, complex junctions and where records are poor or conflicting. It’s also useful on concrete or paved areas where standard avoidance tools struggle. Use competent providers and integrate results into the permit drawings and briefings.

# Can hand digging alone keep us safe near a marked cable?

/> Hand digging with insulated tools reduces risk but doesn’t eliminate it. Combine careful hand excavation with fresh scanning, trial holes and clear stop-work triggers if the ground doesn’t look as expected. Avoid percussive tools near suspect services.

# Who should sign a permit-to-dig?

/> A competent permit issuer who understands services risks should authorise, and the responsible supervisor should accept it before work starts. The operator and banksman must be briefed and able to explain the permit controls. If roles change mid‑shift, re‑brief and re‑sign.

# What if we suspect private services that aren’t on the plans?

/> Walk the likely routes from sources such as cabins, EV chargers or temporary lighting to the workface, and scan those corridors deliberately. Mark findings clearly and treat them as live until proven otherwise with exposure. If in doubt, escalate, bring in additional survey, or adjust the method to avoid.

The post Preventing Buried Services Strikes with Permit-to-Dig appeared first on Goldcast Academy Magazine | All the latest news from the UK building industry.

TL;DR

/> – Public projects are moving to hard 30‑day payment terms that flow down from the client to every tier of the supply chain.
– Main contractors will need watertight processes for “valid invoice” checks, dispute notices, and payment approvals to avoid breaching contracts.
– SMEs could see improved cashflow, but only if paperwork is clean and any disputes are handled quickly and in writing.
– Bid teams should expect closer scrutiny of payment performance and contract clauses that compel prompt, pass‑through payment.

What it means for UK construction supply chains

/> The practical intent is to lock prompt payment into the commercial mechanics of public sector works. Public bodies are already under expectation to pay primes within 30 days; the change now cements corresponding obligations down to subcontractors, consultants and materials suppliers engaged on the same project. In procurement and contract terms, that typically translates into mandatory flow‑down clauses, evidence requirements on payment performance, and potential tender consequences for poor payers.

For tier‑one contractors, the immediate impact is procedural. Expect closer alignment between valuation cycles, payment notices, and invoicing windows, with less tolerance for informal approvals. Finance teams may lean more on digital invoice workflows, standardised dispute notifications, and clearer definitions of when the 30‑day clock starts. Some clients may look again at project bank accounts or other ring‑fenced arrangements to de‑risk late payment, particularly on multi‑tier packages. For consultants and housebuilders working on publicly funded schemes or frameworks, the same logic applies: pay within 30 days unless there is a properly recorded dispute, and ensure downstream appointments mirror upstream obligations.

Commercially, the market signal is two‑way. Contractors with strong payment records could gain a competitive edge at tender, while those with sluggish processes risk contractual non‑compliance and reputational drag. Supply chain finance and early‑payment programmes may be reframed as optional accelerators rather than workarounds for extended terms, especially if the underlying contract now requires 30‑day payment as standard.

# Caveats

/> How far and how quickly enforcement will bite remains to be seen. Much hangs on definitions such as “valid” or “undisputed” invoices, and whether disputes are used legitimately or tactically to pause the clock. Legacy contracts may not change overnight and private‑only schemes are not directly affected unless parties opt in. Market practice will likely consolidate over the coming months as contract forms and PPNs are updated and test cases emerge.

On‑the‑ground impact: a typical project scenario

/> Consider a council‑funded refurbishment with a tier‑one main contractor and a multi‑trade subcontractor base. Historically, some packages were paid in 45–60 days after valuation; under the strengthened regime the main contractor updates all sub‑orders to specify 30‑day payment from receipt of a valid, undisputed invoice, and aligns payment runs accordingly. A mechanical subcontractor submits its invoice two days after valuation sign‑off; the QS flags a measurement query within the notice period, splits out the disputed line, and the undisputed balance is paid within 30 days. A small electrical supplier, accustomed to slower cycles, tightens its own processes to issue compliant invoices on the same day as delivery confirmation. Cashflow evens out across the job, but the contractor’s commercial team carries a heavier admin load to keep the paperwork watertight.

# What to watch next

/> – How standard forms and public sector frameworks update clauses to mandate 30‑day flow‑down and define disputes.
– Whether tender evaluations place greater weight on verified payment performance data from previous projects.
– The extent to which project bank accounts or similar tools re‑emerge on complex, multi‑tier public works.
– How insolvency risk and retention practices interact with stricter payment timelines during market stress.

The industry appears to be moving toward faster, more accountable payment on publicly funded projects, with process discipline as the price of certainty. The open question is whether enforcement and culture change will be strong enough to turn policy intent into everyday site reality.

FAQ

/> What does “binding down the supply chain” actually mean?
It refers to contract terms that require each tier to pay the next tier within the same 30‑day window used upstream. In practice, main contractors, subcontractors and consultants on a public project would be expected to mirror the client’s prompt payment obligations in their own orders and appointments. The aim is to stop delay at the top from cascading into longer waits further down.

# Does this apply to private sector projects as well?

/> The change is tied to public procurement and publicly funded work. Purely private jobs are not automatically captured, though some clients may adopt similar terms for consistency or competitive reasons. Market pressure could nudge private projects toward the same standard over time, but it is not a given.

# When will the 30‑day flow‑down start to bite on live contracts?

/> New procurements and new contracts are the most likely to reflect the tightened position immediately. Existing projects may only pick it up if the parties agree a variation or where a framework or call‑off already mandates such terms. Commercial teams should check the wording of current orders before assuming any change.

# How are disputed invoices treated under the 30‑day rule?

/> The focus is on paying undisputed sums within 30 days, while genuinely disputed items follow the contract’s resolution process. To avoid ambiguity, disputes should be raised promptly and in writing, setting out what is in dispute and why. Robust records will matter if performance is later scrutinised.

# What should SMEs and specialist trades do to benefit?

/> Submit clean, compliant invoices aligned to agreed valuations or milestones, and keep evidence of delivery, approvals and notices. Clarify what constitutes a valid invoice on the project and who must sign off, so the payment clock starts without argument. If payment is delayed, use the contract’s escalation routes early and in writing.

The post Procurement Act: 30‑Day Payments Now Binding Down the Supply Chain appeared first on Goldcast Academy Magazine | All the latest news from the UK building industry.

TL;DR

/> – Pick a system that captures design intent at Gateway 2 and traces it through installation, testing and commissioning to Gateway 3, with clear responsibility trails.
– Use a data model that codes locations, systems and safety-critical elements consistently across drawings, models, photos and certificates.
– Operate a formal change workflow that links product substitutions and design updates to approvals, RFIs and site areas.
– Validate completeness weekly with dashboards; do not wait for end-of-job trawls.
– Package outputs in client- and regulator-ready formats alongside O&M and asset data for operations.

The Golden Thread playbook for Gateways 2 and 3

A UK scenario: A 20-storey residential block over a podium car park is heading into superstructure in a regional city centre. The principal designer has fixed the fire strategy and external wall details, but procurement has split the façade across two subcontractors to meet lead times. The principal contractor’s digital engineer is under pressure to ready Gateway 2 evidence while the concrete frame races up and logistics fight tight delivery windows. A late substitution on insulation lands after a supply squeeze; the façade PM needs approvals fast without losing traceability. The MEP team is also squeezing commissioning into a narrowed window after weather delays on the roof plant. With quarter-end approaching, Gateway 3 planning starts early, but the evidence trail is patchy across field apps, email threads and a file server. The job needs one coherent Golden Thread spine, or the regulator submission and client handover will both wobble.

# Stage 1: Define scope and responsibility at Gateway 2

/> Pin down exactly which information proves the design intent for fire and structural safety at Gateway 2, and who owns each part. Agree an information standard with the principal designer, principal contractor and key packages: location codes, system breakdown (e.g. Uniclass), document naming and versioning. Decide mandatory fields for safety-critical elements—product identity, approvals, installer competence, inspection outcomes, photos, exact location—before any works start. Require suppliers to commit to these data points in their contracts and ITPs. Establish how RFIs, TQs and design changes will be captured and linked to affected zones or elements.

# Stage 2: Choose the system architecture that fits your programme

/> Pick a common data environment (CDE) as the source of truth and connect it to the site capture tools that supervisors and specialists will actually use. Your core platform needs role-based permissions, immutable audit trails, reliable revision control and APIs to pull/push data with models and field apps. Mobile capture must work offline, with time-stamped photos and quick QR/label lookups at point of install. Make sure the model viewer can anchor records to spatial context—grid, level, zone, room—so evidence lives where the element lives. Confirm how data is stored and backed up in the UK context, including who owns it after completion.

# Stage 3: Build templates and a data model for safety-critical records

/> Create structured forms for product declarations, approvals, installation records, tests and commissioning logs. Include picklists for products and systems to avoid free-text chaos. Mandate photo requirements (e.g. before-close-up, label, firestopping tag, datum) and enforce minimum evidence counts. Set unique identifiers that follow an element across drawings, model objects and records. Map these to your issues workflow so anything that fails inspection lands in a punch list tied to the right element and location.

# Stage 4: Run change control and product provenance on site

/> Use your software to drive a formal substitution route: request, assessment by designer/fire engineer, approval, then link to the exact zones and quantities affected. Every variation, RFI answer and sketch that shifts safety-critical scope should be tagged to the impacted elements. Require suppliers to upload product evidence (certificates, test reports, manufacturer guidance) against the exact installed item, not a general folder. Where like-for-like is claimed, log the basis and attach comparisons. Keep version freezes clear so supervisors know which drawing or model revision governs each install.

# Stage 5: Validate, close out and package for Gateway 3

/> Run weekly completeness checks: which apartments or risers have full install records, which firestopping entries are missing photos, which commissioning sheets lack signatures. Use dashboards for package managers and the clerk of works to prioritise close-out. Align evidence to Gateway 3 needs without rigidly fixing one export format—expect PDFs for narratives, structured data (CSV/COBie) for asset registers, and native model files for spatial context. Ensure competence logs and sign-offs are tied to dates and areas, not just dumped in a folder. Redact personal data where appropriate before regulator or client submissions.

# Stage 6: Handover-ready data for operations

/> Bundle an asset register that matches the client’s CAFM import needs: unique IDs, locations, model links, warranty dates, PPM schedules and spares. Split evidence into two tracks: safety-case-critical vs general O&M, but keep the links between them. Include an index that a facilities manager can navigate without the project team present. Verify that post-completion updates (snag rectification, late product swaps) can be appended without breaking the audit trail. Agree who maintains the Golden Thread after handover and through early defects.

# Common mistakes

/> – Treating Golden Thread as a document dump: without structured fields and links to locations/elements, you can’t prove what is installed where.
– Leaving software choice to IT alone: site teams then hack around workflows that don’t match inspections, approvals or commission sequencing.
– Ignoring change control in the field: product swaps and RFIs happen; if they’re not tied to zones and quantities, provenance is lost.
– Waiting until practical completion to assemble evidence: that’s when photos are missing, tags are boarded over and supervisors have moved on.

# Golden Thread software checklist for Gateways 2 and 3

/> – Capture design intent and approval history with immutable timestamps, and link them to specific zones/elements in the model and drawings.
– Enable mobile, offline field capture with enforceable templates for install records, tests, and photo evidence anchored by location codes.
– Operate a robust change workflow for product substitutions and design updates, with auditable approval chains and impact mapping.
– Provide transparent dashboards for completeness by area/package, plus automated reminders for missing evidence and overdue sign-offs.
– Support open exports (e.g. IFC, COBie, CSV, PDF bundles) and cross-references so Gateway 3 and O&M packages can be assembled without rework.
– Integrate with your CDE and issue management, preserving a single source of truth and consistent metadata across tools.
– Deliver granular permissions and data ownership clarity, including post-handover access for the client and their operator.

# Bottom line

/> Golden Thread success at Gateways 2 and 3 comes from structured data, tight linkage between design and install, and change control that mirrors how site work really happens. Choose software that enforces those behaviours, and the gateway submissions become a by-product of good delivery rather than a cliff-edge exercise.

FAQ

# What’s the minimum software stack I need to manage the Golden Thread?

/> At a minimum, you need a reliable CDE for documents and models, plus a field capture tool that ties install records to locations and elements. Issue management and approval workflows should sit within or integrate tightly with these tools. If you already use BIM, ensure the model viewer and data schemas align with your field records.

# How do I get subcontractors to use the system properly?

/> Bake requirements into contracts and ITPs with clear templates, deadlines and acceptance criteria for evidence. Provide short, practical training and name a point of contact on site to unblock access and answer queries. Incentivise compliance by linking payment stages to evidence completeness, not just physical progress.

# Who owns the data and who can see it after handover?

/> Agree data ownership and access in appointments and the contract, including how long the platform stays open post-completion. Clients often want a copy of the structured data and evidence bundles that import to their CAFM. If the platform is licensed to the contractor, set up an archive transfer or client tenancy so the Golden Thread continues through operation.

# How should change control work for product substitutions?

/> Use a standardised digital form that captures the reason, proposed product, supporting documentation and the areas affected. Route it for review by the designer and relevant specialists, then auto-link the approval to the specific elements and drawings. Make sure installation cannot be closed out in the system until the approval is in place and evidence matches the approved item.

# How do we measure value from Golden Thread software beyond compliance?

/> Track time saved on close-out, reduction in aborted works from using the wrong revision, and fewer disputes due to clear provenance. Monitor how quickly you can assemble regulator and client packages without offline chasing. Over time, use the data to spot recurring quality issues by trade or detail and push fixes earlier in the programme.

The post Golden Thread software checklist for Gateway 2 and 3 appeared first on Goldcast Academy Magazine | All the latest news from the UK building industry.