Savills, one of the UK’s leading estate agents, needed to overhaul the way valuation reports were created, both in terms of efficiency and presentation.

Valuers were drowning in repetition: typing the same details thousands of times, battling Word formatting to make reports look vaguely on-brand, and juggling multiple external tools just to meet basic due diligence requirements. It was draining their time, energy, and focus.

What they needed was a system that could take care of the repetitive admin, ensure reports were consistently formatted and looked great, and ultimately free valuers up to do what they do best: conduct meaningful valuations and build stronger relationships with clients.

Deliverables

Services

My role

Listening to Valuers

We began by talking to valuers, hearing how they worked each day, the shortcuts they relied on and the frustrations they lived with. Every valuer did things their own way, but the challenges were the same: repetitive tasks, clunky tools and reports that never quite looked right.

Mapping the journey revealed exactly where the process stumbled and where we could make a difference. These insights set the stage for a system that worked with valuers, not against them, freeing them to focus on meaningful valuations and client relationships.

Project image

Untangling Complexity

With the interviews complete, we could see the patterns across valuers and departments. Beneath the differences lay a core workflow, from creating a new job to delivering the final report. This gave us a foundation for the first user flows and sitemap of features, focusing on the stages before any work on the report itself.

Savills’ internal processes were complex, shaped by rigorous auditing requirements. But every feature also had to be flexible enough to serve users across different teams. UX thinking guided the design, ensuring the system could meet varied needs without forcing the development team to rebuild the same feature again and again.

Project image

Design in Action

Once the MVP features were prioritised around the core workflow, we focused on the steps valuers took before starting a report: logging new opportunities, validating addresses, performing conflict checks, and sending fee quotes.

The interface needed to be clear and reliable rather than flashy, with robust error handling, validation, and state management at its core. We built a design system upfront, defining components like forms, tabs, cards, headers, and footers, which allowed us to rapidly create interfaces ready for testing. Savills didn’t respond well to traditional wireframes, so we developed branded “wires” early, enabling fast iteration and efficient validation of design decisions.

Project image
Device 1

Create Opportunity

The first feature we tackled was Create Opportunity, essential for capturing potential jobs in the system. Valuers entered key details through a structured form, with data automatically logged in both Dynamics 365 and VWS. That information then fed directly into the report’s Glossary, which was automatically populated throughout the report.

Because the form was long and expected to grow, we introduced anchors and dynamic validation to guide users smoothly through each section and catch errors in real time.

Device 1

Conflict Check

The second step in the Create Opportunity flow was Conflict Check. Valuers needed to ensure there were no known conflicts before proceeding. Information from the Create Opportunity form fed directly into this step and integrated with the internal Conflict Check System (CCS).

If a conflict was found, valuers could classify it as no conflict, manageable, or unmanageable. Unmanageable conflicts stopped the work from progressing, but the information was stored for future reference, keeping the process safe and transparent.

Device 2

Fee Quote

Once a valuer could proceed, the next step was issuing a fee quote. They entered key details, including whether it was a desktop valuation, base fees, liability caps and the basis for the valuation, and the system generated the quote automatically.

Quotes required sign off from Group Legal. If changes were needed, the quote was versioned, allowing the valuer to edit and resend. Once approved, it could be sent directly to the client from VWS, with an email generated automatically and issued for signature via DocuSign. Once signed, the system created the job, enabling the valuer to begin the report.

Turning Insight Into Design: After streamlining core workflows and job setup, phase two focused on the heart of a valuer’s work: making valuation reports faster, easier and error free.

Device 1

Report Builder

Two key insights guided this phase. First, formatting reports in Word was slow and frustrating, causing delays across the company. Second, reports were highly repetitive, with valuers spending significant time rekeying the same information, increasing the risk of error.

The Report Builder feature was designed to strike a balance between control and flexibility. It integrated with third-party systems to gather accurate property information, reduced rekeying and automatically formatted reports so valuers could focus on the work itself, not presentation.

We analysed dozens of reports from multiple departments to identify patterns and differences, ensuring the components were flexible enough to support both personal style and departmental requirements. This was particularly challenging as reports needed to render in HTML for PDF download, and the client had very specific requirements for how information should be displayed.

Device 1

Report Builder Continued

The Report Builder was a major feature that evolved over approximately 60 sprints and continues to develop today. For the MVP, valuers created reports using simple rich text editors, with the ability to format text, insert images, and use tables. While not a long-term solution, it allowed work to continue while the full Report Builder was developed.

We built a component-based system, offering several advantages: no need to worry about formatting, with previews rendered in the browser via HTML; components could connect to the Dynamic Glossary to automatically populate the correct fields; and valuers could personalise reports using designed components without risking off-brand results.

This was the most challenging part of the system to design. Each of the eight departments created reports slightly differently, requiring components to be flexible while still adhering to best practice, legal requirements, and brand guidelines. Large features such as Statutory Enquiries, Dynamic Glossary, and Income Analytics also had to integrate seamlessly, avoiding copy-pasting and ensuring smooth workflows.

A complex system, designed and refined over four years, now smooth, fast, and built to scale. Here’s a showcase of some more features:

Device 1

Statutory Enquiries

This feature pulls title boundary information from third-party systems and lets users adjust it if needed by editing the red lines on the map. Once satisfied, they move to the next tab to retrieve planning history, flood risk, EPC, and Council Tax data. When everything is correct, a single click sends the data straight into the report, automatically formatted into tables.

Device 1

INCANS Data

This feature connects with the third-party INCANS system, letting users retrieve accurate tenant information for properties in the Commercial division. The data is presented in infographics and tables, and, like Statutory Enquiries, a single click pushes it into the correct sections of the report, automatically formatted for use.

Device 1

Report Inputs

The Dynamic Glossary stores all the information valuers would normally have to rekey repeatedly throughout a report. Any edit made here updates across the entire report automatically. Much of the data is pulled from other areas of the system, further reducing the need for manual entry.

Each input is linked to specific sections of the final report, down to individual fields within components, ensuring accuracy and consistency every time.

Device 1

Library

Everything a valuer uploads during report creation is automatically stored in the library for audit purposes and to ensure nothing is lost. Some files are placed in the correct folders automatically, while others can be filed manually by the valuer. A card sort helped determine the best way to name and structure the library, mirroring an existing internal process.

Device 1

File Checklist

To ensure compliance and reduce risk, Savills requires an audit checklist for every job. At the end of each report, valuers complete the checklist and submit it to a Director-level RICS chartered valuer for approval before sending the report to the client.

With the platform live and 500 active users onboard, we ran research and testing to refine the experience. Monthly surveys tracked usage, highlighting features that needed attention or were redundant.

Usability testing ensured the system aligned with existing processes and encouraged adoption. The MVP remained central, with UX guiding and validating each new iteration.

Next up

Sky: Positioning a product to target Gen Z

View Sky