How the problem develops
A client gives the service address to sales, enters it in a web form and is asked again before the first appointment. Each system has its own version. The apparent missing-data problem is really a failure to reuse confirmed information.
What to check first
- Map each repeated field to its current source and who can update it.
- Check whether staff cannot find the value, cannot trust it or cannot access it. These require different fixes.
A better process
- Choose a source of truth for each routine field and record when it was confirmed.
- Carry approved values into the next step with a correction option.
- Ask only for missing or changed details, rather than resending a blank intake form.
What a system can do
Populate the handover record from confirmed sources and request targeted confirmation where the value may have changed.
Where people stay in control
Do not expose information across clients or use a similar name as proof of identity. Sensitive-data handling needs separate review.
Benefits and tradeoffs
The useful outcome
Clients have fewer repetitive questions and staff can see where a value came from.
The tradeoff
Reusing stale data can spread an old error. Define which fields expire and when a person must confirm them.
Test before going live
Test a changed service address, two similar client names and a missing access permission. No guessed or cross-client value should be inserted.