Speed and compliance are now expected. The real difference is how much control, flexibility and evidence the software gives practitioners to make better retrofit decisions.

Retrofit software has come a long way, assessments are quicker, reports are cleaner, compliance is easier to manage and more of the process now sits in one place.

Good retrofit software is not the one that simply moves a project through compliance fastest. It is the one that gives experienced practitioners enough evidence, flexibility and control to make better decisions before the work begins.

But there is a trade-off that comes up surprisingly often when we speak to experienced Retrofit Assessors and Coordinators. Software may have become faster, but in some cases, it has also become more rigid.

That matters because retrofit is not a completely standardised process. Properties differ, products differ, budgets change and clients have different priorities. Sometimes the practitioner knows that a generic assumption in the model does not reflect the property in front of them.

Software should help with that judgement, not get in the way of it.  That is where some of the less obvious differences start to matter.

Product selection is a good example. It is one thing to model a generic measure; it is another to model the actual product that is likely to be installed.

Ivynest allows users to pull products directly from the PCDB and create multiple product options against a measure, so the model can reflect what is really being specified rather than relying on a default.

The benefit is simple: instead of asking, “What happens if we install a heat pump?”, you can ask, “What happens if we install this heat pump, in this property?”

That gives the practitioner a much more useful basis for making a recommendation.

The same applies to retrofit pathways. There is rarely one obviously correct answer.

One option may give the strongest EPC uplift, while another could reduce energy use more effectively or offer a better return on investment. A different route may make more sense because of what is planned for the property later.

Ivynest allows those options to be compared side by side, with the strongest ROI measures easy to identify. That moves the conversation on from a single modelled recommendation to a more useful discussion about the options, the trade-offs and why one route may be better suited to the property and the client.

Speed matters too, but only if it comes from removing repetition rather than removing judgement.  Ivynest uses PAS 2035-trained AI to help prefill assessments and designs, cutting down repetitive data entry while leaving the practitioner in control of the final work.

That distinction is important.

Faster should not mean fewer checks or less scrutiny. It should mean spending less time duplicating data and completing repetitive admin, and more time applying expertise where it matters.

Some features are important, but no longer especially unusual. Branded reports, for example, help Coordinators present work clearly and professionally, but the bigger difference lies in what the software helps them do before the report is produced.

The same goes for audit trails, evidence storage, collaboration and reliable lodgement. These things matter enormously when they do not work, but when they do, they should make the Coordinator’s job considerably easier.

Take evidence management, for example. On a typical retrofit project, documents are coming from different people at different stages. Keeping track of what has been submitted, what needs attention and what has been approved can quickly become a job in itself.

Ivynest allows Assessors, Designers and Installers to upload evidence directly into the project, where the Coordinator can review individual documents, add comments and assign an A, B or C status. Crucially, the record of what has been uploaded, reviewed and approved stays with the project.

It also removes a surprisingly familiar frustration: downloading a document, adding comments, emailing it back and then trying to work out which version everyone is looking at. Instead, the review and feedback process happens within the platform, keeping the evidence, conversations and decisions together.

That makes collaboration easier in the moment, but it also creates a clearer record for later. When someone asks, “Why did we decide to do it this way?”, the supporting evidence and review history are already there.

The same principle applies to wider project collaboration. Retrofit involves multiple people, and bringing the team and client around the same information, with installer coordination and scheduling built in, reduces the risk of decisions getting lost between systems.

Good retrofit software should not try to make every experienced practitioner work in exactly the same way. It should remove repetitive admin, make options easier to compare and give people more time to apply their own judgement.

That matters in a market where much of the software conversation still centres on workflow, compliance and project management. Those things are essential, but they are only part of the job. The more useful question is whether the software actually helps you make a better decision before the work begins.

Ultimately, retrofit software should not just help you get a project through the process.

It should help you make the right decision before that process starts.