Five Questions Every Housing Development Team Should Ask About Their Appraisal Software

The tool you use to model scheme viability sits at the centre of every development decision your organisation makes. If it was designed for the way teams worked ten or fifteen years ago, it may be quietly creating risks you haven't accounted for.

Development viability has rarely been a higher-stakes function. Persistent build cost inflation, the closing window on the 2021–26 Affordable Homes Programme, evolving rent settlement debates, and the long tail of building safety costs are all sharpening focus on which schemes really stack up. At the same time, development and finance teams are being asked to do more with the same headcount — often from a mix of office, home, and site locations.

Sitting underneath all of that, and rarely talked about, is the actual software your team uses to model viability. It's the layer between a scheme proposal and a board paper. And if it hasn't kept pace with how your team now works, the gap shows up at the worst possible moments: in an audit, in a procurement process, when a key team member leaves, or when a new colleague tries to pick up someone else's appraisal a year later.

Here are five questions worth asking about your current setup.

1. Can your team work from anywhere — and on whatever device they have?

Hybrid working is now the default in housing finance and development teams. New starters arrive with Macs. Consultants and partners log in from laptops you don't control. Senior staff want to glance at a scheme summary on a tablet between meetings.

Tools that are tied to a specific version of Excel on a specific operating system, or that warn users against opening a file in a browser-based spreadsheet because doing so might corrupt the data, make all of this harder than it needs to be. They also create real friction with IT teams trying to standardise on cloud-first, browser-accessible software that reduces the security surface area.

A modern viability tool should run in a browser. No installation, no macro warnings to renegotiate every time a new starter joins, no "you can only open this on the Windows machine in the office."

ProVal is cloud-hosted and accessible from any modern browser. Whether your team is in the office, working from home, or sitting with a local authority partner across the table, the tool, and the appraisal, is the same.

2. Where does the canonical version of an appraisal actually live?

If the answer is "on someone's hard drive" or "in the development folder on the shared drive," there's a version-control problem waiting to happen. File-based workflows rely on people remembering to save copies, follow naming conventions, and not overwrite the master template. They rely on the right version being emailed to the right person at the right time.

When something goes wrong; a board paper drawn from a stale appraisal, two team members editing different copies, a key file lost when someone leaves... The cost is rarely just the cost of redoing the work. It can be the cost of redoing the decision.

ProVal stores every appraisal centrally. There is one version of each scheme, with access governed by user permissions rather than by who happens to have the file open. When a new person joins the team, they don't need to be talked through which folder, which template, and which file labelled "v3 FINAL revised" is the one to actually trust.

3. What does your audit trail actually show?

Audit and assurance functions are increasingly interested in how viability numbers are produced, not just what they are. Two specific areas are worth examining.

Who can override what. Some tools allow privileged users to suppress audit warnings or override cell-level checks. That capability is sometimes necessary, but if an override quietly continues to mask further errors until someone manually resets it, you have a control weakness an auditor will find before you do.

Who changed what, and when. A board paper that says "scheme NPV is £2.4m" is more defensible if you can show the assumptions, the inputs, and who set them. Spreadsheet-based tools rarely capture any of this. Cloud-hosted, multi-user tools, by design, can.

ProVal produces auditable, viability-compliant results and centralises the assumptions, defaults, and overrides driving each appraisal. That matters for internal audit, for regulator conversations, and increasingly for board members who want to understand the workings rather than just the headline.

4. Does your appraisal tool talk to the rest of your development pipeline?

A scheme doesn't end at appraisal. The same inputs: units, costs, timings, funding mix — flow through to project management, into actuals tracking, into sales reporting on shared ownership and Section 106 disposals, and back into benchmarking when you compare what you delivered against what you planned. Every rekeying step is an opportunity to introduce an error and a drag on the team.

This is where an integrated suite earns its keep. ProVal sits alongside Sequel for project monitoring, Landval for land valuation, and Keynect AI for shared ownership and sales CRM. Data moves between them. The team that prepared the viability case doesn't have to re-explain the scheme to the team running the build, and the team monitoring delivery can compare actuals against the appraisal that approved the scheme in the first place.

For organisations trying to grow their development pipelines without growing headcount proportionally, a position many housing associations are now in, that joined-up workflow is where the real efficiency gains come from.

5. What happens when something goes wrong at 4pm on a Friday?

The honest test of business software isn't how it looks in a demo. It's what happens when a board paper is due Monday and something isn't behaving.

A few things are worth checking on your current setup:

• Is there a documented service level agreement, with response times you can hold a supplier to?
• Is support delivered through a proper ticketing system that survives staff changes, or via a named individual's mobile number?
• Is there a structured training programme, ideally externally accredited, that new joiners can be put through?
• Is there a user community where you can compare notes with peers facing the same regulatory and technical questions?
• Has the company behind the software been around long enough, and is it stable enough, to still be there in five years?

These are unglamorous questions, and they don't show up in feature comparisons. They show up the first time you need them.

ProVal is backed by SDS, a team that has worked with the UK social housing development sector for more than thirty years. Support is delivered against published response times. Training is provided by TAP-accredited trainers. Customers meet annually at regional user groups to share experience. The software is available through the G-Cloud framework and operated under documented security, GDPR, and secure-development processes that hold up to enterprise procurement scrutiny.

The takeaway

None of these questions are about whether your current tool can calculate NPV. Most can. They're about whether the tool matches how your team actually works in 2026, and whether it's ready for the scrutiny, the scale, and the complexity the sector is moving towards.

If your answers to any of these questions made you wince, it may be time for a conversation.