What building SENVault taught us about complex information
Organising documents is the easy half of the problem. The harder half is helping someone see what matters before a meeting that counts.
Filed under Product thinking / a guidance note, kept current rather than dated
01The pile is only half the problem
SENVault exists because SEND casework produces paper faster than any family can file it: EHCP drafts, school reports, therapy assessments, DLA forms, letters, appointment notes. The obvious problem is the size of the pile.
The harder problem is that each document belongs to a wider story. Things arrive out of order, use different language for the same need, and matter differently depending on whether the next step is an annual review, an application or a tribunal.
02Organisation has to serve a decision
A tidy filing system makes documents easier to find. It does not make a situation easier to understand. The useful product question is what decision the person is preparing for, and what they need in front of them to make it.
That is why SENVault pairs evidence organisation with timelines, key events, summaries and case packs. Each one turns stored records into something you can take into a meeting.
- Start from the next decision, not the database schema.
- Make dates and relationships visible, because chronology is often the argument.
- Use automation to cut repeated reading, never to replace judgement.
- Keep the original evidence one click from any summary of it.
03Calm is a requirement, not a style
People open tools like this at stressful moments, often late at night before a deadline. Clear hierarchy, predictable actions and progress you can see decide whether the product works at the exact moment it is needed.
That lesson carries well beyond SEND. When the subject matter is heavy, the software should carry more of the load, not hand the user another system to learn.
Working on something this note describes? Tell us about it.