Five people, one folder, and a missing passport
A family of five instructs you. The main applicant has one set of documents, the spouse another, and each of the three children has their own birth certificate, passport and school letter. Everything is saved in one matter folder, named by whoever uploaded it. "Passport 2.pdf" could be the spouse or the eldest child.
The caseworker keeps a note of who has sent what. When they ask for the missing items, they ask for "the children's documents" and get two of the three. The fee calculation is done on paper. At submission, someone notices the youngest child's passport expired last month.
Case systems think in matters, families think in people
Most case management systems are organised by matter, and a family application is recorded either as one matter with free-text notes about the dependants, or as several matters that are not formally linked. Neither shows you the family as a set of people with their own documents, dates and steps.
So the structure lives in the caseworker's head. It works while that caseworker is on the file, and falls apart the moment someone else picks it up. It also makes firm-wide questions impossible to answer, like how many dependants you currently have in progress, or which children's passports expire within the next few months.
Children's documents are a particular trap. Passports for children often have shorter validity, birth certificates may need translations, and school or consent letters come from third parties. Each has its own timetable, and none of it is visible if the child is only a name in the notes.
Where family files go wrong
| Issue | Effect |
|---|---|
| Documents not tagged to a person | Time spent working out whose passport is whose |
| Dependants' dates not tracked | An expired document found at the last minute |
| Fees worked out on paper | Mistakes in what the client is told to pay |
| Separate unlinked records | A dependant's step missed because it sat on a different matter |
| Knowledge held by one person | Handover to a colleague is slow and risky |
How we build a linked family view
- Every person on the application gets their own record, linked to the family, with name, relationship to the main applicant, date of birth and passport details.
- Document checklists are generated per person, so the client sees what is needed from each family member separately, and uploads are tagged to the right person automatically.
- Key dates are tracked per person, including passport expiry, and anything expiring within a window your firm sets is flagged on the family view.
- Fees and charges are listed per person using the figures your firm maintains, so the quote and the payment instructions match the household.
- Post-submission steps and decisions are recorded per person, because family members do not always move in step.
- The family view sits in your case management system if it supports linked records, or alongside it with links back to the matter.
The build organises information. Decisions about who applies, on what basis and when, are made by your advisers.
One screen for the whole household
Caseworkers see each family member's progress at a glance. Clients know exactly which child still owes a document. Expiring passports are spotted early. A colleague picking up the file sees the structure without a handover call, and partners can finally answer questions about dependants across the firm.
Clients notice the difference too. Parents juggling documents for several children appreciate a list that tells them exactly which child still owes what, instead of a general reminder that something is missing.
Is this how your family files look?
- Family members' documents share one folder with vague file names
- Dependants are recorded only in notes
- You have found an expired dependant passport late in a file
- Fees for families are calculated by hand
- Only the caseworker understands the structure of the file