PAS 2035 has turned domestic retrofit from a string of isolated measures into a defined, auditable workflow. The paperwork, evidence capture and sign-offs it requires are too complex to manage with email threads and shared drives. That is why retrofit software – not a single app but a set of tools and platforms – is becoming the backbone of compliant delivery, from assessment to lodgement and post-occupancy evaluation. Used well, it reduces rework, speeds up TrustMark submissions, and gives coordinators and installers a shared source of truth that holds up under audit.
TL;DR
/>
– Retrofit software structures PAS 2035 roles, stage gates and evidence so teams can pass audit without drowning in files.
– The value is in standardised templates, photo trails, change control and TrustMark lodgement, not flashy dashboards.
– Adoption lives or dies on site usability: offline capture, clear hold points and subcontractor-friendly checklists.
– Treat configuration like a project deliverable, with explicit data ownership, role permissions and integration to scheduling and cost control.
What retrofit software actually does under PAS 2035
/> At its core, retrofit software turns PAS 2035 into a workflow with permissions. The Retrofit Assessor completes surveys and occupancy assessments using structured forms; the Coordinator assigns a risk pathway and produces a Medium-Term Improvement Plan; the Designer submits measure designs and details; the Installer logs install evidence against measure-specific templates; and the Evaluator captures post-works outcomes. Each role sees the tasks and documents relevant to them, and the platform links the stages so the audit trail is continuous.
Good platforms standardise the documentation that audits hinge on. That includes moisture risk approaches, ventilation strategies, Improvement Option Evaluations, design sign-offs, product data sheets and installer competence records. Evidence capture is time-stamped and geo-tagged; photos and videos are tied to measures and locations, not just dumped into folders. Stage gates – pre-works, mid-install, completion and commissioning – become hold points that block lodgement until required evidence is present and approved.
For busy programmes, batch and archetype management matters. Software can group similar properties so survey questions, U-value assumptions and detail drawings are reused, but still allow property-level exceptions. Version control, mark-ups and change logs reduce the risk of the wrong drawing making it to site. Where heat pumps or solar get added, the better systems maintain the PAS 2035 thread while linking to the PAS 2030 install evidence for those technologies.
TrustMark lodgement is the final hurdle in many schemes, and software can simplify it. Coordinators push a verified bundle rather than chasing files across inboxes. Some tools integrate with scheduling, cost control and document signing, which helps QSs value works and managers forecast labour. None of this removes site reality – access, weather and unexpected conditions still bite – but it means when a property slips, the impact is visible at programme level and the evidence remains coherent.
Delivering PAS 2035 workflows on live housing stock
/>
A UK scenario: occupied maisonettes under programme pressure
A local authority commissions a programme to improve 1960s low-rise maisonettes on a tight funding window. A Retrofit Coordinator is juggling risk path B and C properties, a term contractor, and several PAS 2030 installers. The first survey run turns up damp in ground-floor flats, lofts jammed with belongings, and a few unknown service routes. The site manager is trying to hold a staggered access plan while keeping residents on side and the QS wants evidence aligned to valuations. A week of rain collapses the external works sequence. Senior management wants weekly dashboards, TrustMark lodgements on pace, and no audit surprises.
With configured software, the team clusters the blocks by archetype and loads survey templates tuned for the stock. Assessors complete offline surveys and occupancy assessments, auto-tagged to each dwelling, and flag risk factors that push certain homes to a higher pathway. The Designer’s detail for internal wall insulation goes in as a controlled document with accepted junction details; the ventilation strategy is linked so installers can’t complete insulation without a matched ventilation task. The resident liaison team issues appointment windows and consent forms through the platform, capturing acknowledgment and recording any specific vulnerabilities or access constraints.
On site, installers capture pre-works condition, mid-install photos of fixings, vapour control layers and service penetrations, and completion with airtightness points and sealant continuity. When a service route is discovered in a party wall, the team raises a variation inside the platform, which routes to the Designer and Coordinator for a quick decision; the cost implication goes to the QS. Commissioning sheets for extract fans and system balancing live in the same record. When the week of rain shuffles access, the schedule is updated centrally and the app pushes new dates; evidence capture does not fragment across messaging apps. At the programme level, the Coordinator can see which homes are ready to lodge, which are blocked by missing ventilation sign-off, and which have resident constraints that need managerial intervention.
Pitfalls and fixes when digitising compliance
/> No platform turns a non-compliant design into a compliant one, and software does not absolve dutyholders of judgement. The trap is thinking a ticked box equals a compliant outcome; it doesn’t. Tuning the system to your stock is essential: the default template may not reflect solid wall nuances, mixed tenure constraints or heritage limitations. Get the first archetype right, then replicate.
Data privacy is non-negotiable. Occupancy data, photos inside homes and vulnerability notes need lawful basis, secure storage and role-based access. Build granular permissions so subcontractors only see what they must, and keep a clear line of who the data controller is. Finally, organise training around site realities. If the app doesn’t work offline, or the photo process slows installation, crews will revert to WhatsApp and everything falls apart at audit.
# Common mistakes
/>
– Treating PAS 2035 as only a paperwork exercise. The software must link design intent to site tasks and hold points, not just store PDFs.
– Leaving configuration to the go-live week. Risk logic, templates and permissions should be set and tested on a pilot property before scaling.
– Ignoring ventilation evidence. Insulation and airtightness photos without ventilation commissioning is a common audit fail.
– Not capturing variations in-system. Decisions made on the phone, with no recorded rationale, undermine the audit trail and QS control.
# Site-ready checklist for PAS 2035 software setup
/>
– Configure risk pathway logic, measure templates and MTIP outputs to match the stock and funding rules.
– Set granular permissions for Assessors, Coordinators, Designers, Installers, QS and client so people only see and edit what they must.
– Map stage gates to programme hold points and link them to valuations, so missing evidence holds payments until resolved.
– Load archetype libraries (junction details, U-value assumptions, ventilation strategies) and tag them to dwelling types.
– Enable offline mobile capture, define photo angles and naming, and run a dry run with an installation crew.
– Integrate scheduling and resident communications where possible to reduce double-bookings and missed access.
– Establish change control workflows that route variations to design, coordination and commercial review before site action.
What to watch next for PAS 2035 tech in the UK
/> The next strides are likely to be tighter links between retrofit platforms, asset management systems and funding administration, so the same data set serves assessment, delivery and grant evidence. Expect more baked-in moisture and ventilation risk tools, and optional sensor integrations for evaluation without turning homes into science projects. Interoperability will matter as landlords consolidate multiple systems and look for trusted APIs rather than all-in-one promises. As the regulatory landscape evolves and scrutiny rises under wider building safety expectations, the demand for traceable product data and clearer competence records will only go one way.
Bottom line: software won’t design or install for you, but it will make PAS 2035 deliverable at scale with fewer disputes and steadier cash flow. Invest time in configuration, insist on site-friendly capture, and let the audit trail run itself instead of running you.
FAQ
/>
Is software mandatory to comply with PAS 2035?
There is no legal requirement to use a specific platform, but at programme scale it is close to essential. Coordinators need structured evidence, role-based approvals and reliable lodgement, which are hard to sustain with spreadsheets and email. Auditors tend to expect clearly linked records rather than scattered files.
# Who owns the data captured during retrofit projects?
/> Typically the client or landlord acts as data controller, with consultants, contractors and the software provider as processors. This should be spelled out in contracts and data processing agreements, including retention periods and deletion on project close. Collect only what is necessary, get resident consent where required, and control access tightly.
# Can one platform cover assessment, design, installation and evaluation end to end?
/> Some tools cover most of the lifecycle, but many teams use a blend. The key is that information flows cleanly between systems, with exports and APIs that avoid rekeying. Choose a single source of truth for the audit trail and make other systems feed it, not compete with it.
# Our installers don’t all use digital tools. How do we bring them into the workflow?
/> Pick software with a simple mobile interface, offline capture and clear checklists tied to measures. Provide short, hands-on training that focuses on photo angles, stage gates and commissioning evidence, and appoint a site lead to validate uploads daily. Where necessary, print measure packs and use a supervisor to capture evidence alongside crews.
# How should variations and scope changes be handled to protect compliance and cost control?
/> Run all changes through an in-platform request that captures the reason, updated detail and approvals from the Designer and Coordinator. Link each change to the MTIP and the valuation so the commercial position is explicit. Avoid doing works on verbal agreements; incomplete or informal variation records are prime causes of audit failure and payment disputes.
