Skip to main content
All insights

Product thinking

What building SENVault taught us about complex information

Why organising documents is only one part of the problem, and how product design can help people see what matters next.

24 July 2026 · 5 min read

Complexity is not just volume

When someone is managing EHCP drafts, school reports, therapy assessments, DLA evidence, correspondence, and appointment notes, the obvious problem is the number of documents. But volume is only part of it.

The harder problem is that every document belongs to a wider story. Information arrives at different times, uses different language, and matters differently depending on whether the next task is an annual review, application, meeting, or tribunal.

Organisation has to support a decision

A digital filing cabinet can make documents easier to find, but it does not automatically make the situation easier to understand. Useful product design has to connect stored information with the action a person is preparing to take.

That is why SENVault combines evidence organisation with timelines, surfaced key points, summaries, and case packs. Each feature helps turn a collection of records into something that can support a real conversation or process.

  • Start with the next decision, not the database structure.
  • Make chronology and relationships visible.
  • Use automation to reduce repeated reading, not remove human judgement.
  • Keep the original evidence accessible alongside any summary.

Calm is a functional requirement

People often use information-heavy products when they are already under pressure. Clear hierarchy, predictable actions, supportive language, and visible progress are therefore not cosmetic preferences. They affect whether the product is usable at the moment it is needed.

The lesson applies well beyond SEND. When the context is complicated, the product should carry more of the organisational burden instead of asking the user to become an expert in the software.