Connected working · 3 minute read
Join up client information without losing control
A system-neutral field map and handover exercise for mortgage teams using a CRM, documents and reporting tools.
The useful bit
Decide where each fact is maintained, who can change it and how another system receives a reviewed update.
Who this is for: Owners, administrators and operations leads in mortgage firms with more than one system. Useful before a CRM or integration discussion.
Start with a real task
In this fictional team, Morgan's address appears in a client record, a fact find and an application draft. If Morgan corrects it, three separate edits can drift apart. The team first maps the field and its owner, then agrees how to update each destination. This example describes a controlled process; it does not assume that any named software already synchronises every field.
A routine you can adapt
-
Process owner
Choose the maintained record
List the facts used across a case: contact details, circumstances, document status, next action and outcome. Identify the maintained record for each. Keep client information separate from case-specific assessments and historic evidence. Do not overwrite an earlier document to make history appear consistent.
Keep: A field map with record location, owner and the places that use it.
-
Authorised case user
Check and record a change
When Morgan reports a correction, follow the firm's verification process. Record what changed, when, why and who reviewed it. Flag any assessment or submitted information that may need reconsideration; a corrected field is not automatically an approved revised application.
Keep: The change record, supporting message and any review decision.
-
Owner of the destination process
Update each destination deliberately
For a manual transfer, assign the update and confirm completion. For an integration, test field mapping, permissions, failures, duplicates and which direction changes travel. A successful connection message does not establish that a specific case is correct.
Keep: Transfer result, reconciliation, exceptions and a named person to resolve failures.
-
Adviser, administrator and team lead
Practise the handover
Use a fictional case in a training environment. Ask the administrator to record a correction, the adviser to review its consequences and the team lead to locate the evidence. Swap roles for an absence scenario and name a deputy. Stop if anyone has to guess which value is current.
Keep: A completed exercise, a list of gaps, agreed owners and a date to repeat the check.
Filled example · fictional data
Morgan's information map — fictional training case
| Information | Maintained record / owner | Used by | Update or review rule | Evidence |
|---|---|---|---|---|
| Current contact address | Client record / case owner | Fact find and application preparation | Verify correction; review affected documents and submissions | Dated change and review note |
| Income evidence | Controlled documents / case manager | Adviser assessment | Keep versions; adviser checks consequences of a new document | Document version and assessment link |
| Document review status | Case task / assigned reviewer | Daily queue and oversight report | Received and reviewed stay separate; confirm result | Reviewer, result and date |
| Next client update | Case task / named owner and deputy | Team queue | Agree the date; deputy accepts ownership during absence | Commitment and completed update |
| Management information | Defined report / team lead | Oversight review | Use agreed definitions and access controls; trace exceptions | Sample, definition, decision and follow-up |
The map reduces uncertainty before it reduces typing. Automate only after the team can explain the ownership and exception process. Measure avoidable re-entry separately from necessary checks, and verify the actual supplier capability before assuming a transfer is automatic.
Free tools · no sign-up
Take it into your next review
Start with the completed example, or use the blank version with your firm's own information. CSV files open in Excel and other spreadsheet apps. Store any live case data in your firm's approved location.
One next step
Put it to work
Map one repeated item, such as a corrected address, from source to every destination. Walk through one successful update and one failed transfer, including who notices and fixes the failure.
Check Achos integration scopeThe product walkthrough illustrates the workflow. Your firm remains responsible for its advice, controls and decisions.