Change Management Logs: A Guide for Mortgage Brokers

Change Management Logs: A Guide for Mortgage Brokers

A change management log is a chronological register of every change made to a record: what was requested, who made it, what changed, when, and who checked it. For a UK mortgage broker, the same discipline applies to the case file. Each document received, checked, queried, replaced or sent to a lender needs a dated entry that a compliance officer, lender or auditor can follow without asking anyone. This guide explains what to log, how a change log differs from an audit trail, and 7 practices that make the record trustworthy.

TL;DR

  • A change log records requested, implemented, verified and closed changes. A document's own version history does not replace it.
  • For each document and review action, record the event, who did it, when, the source and the result.
  • Log enough to reconstruct the case, but no more. Excess logging creates noise and privacy risk.
  • Protect the log from tampering, restrict access and retain it only for the period you need.
  • Automated capture beats manual notes, because gaps appear when entries depend on memory.

Table of Contents

What a change management log is

In project and quality-system practice, a change log is a separate register that records each change from request to closure. QueryChart's guidance on document revision logs describes it as chronological, covering requested, implemented, verified and closed changes, with who acted, what changed and when.

The pages that rank for this topic mostly treat it as a project tool: a table with a change number, description, initiator, date, status and impact. That format works for scope and budget changes. A brokerage needs the same fields applied to client documents rather than project plans.

A typical entry has these fields:

  1. A unique reference for the change.
  2. The date and time it was requested and made.
  3. The person or process that requested it.
  4. The record affected (for example, the March payslip for applicant two).
  5. A description of what changed and why.
  6. The reviewer who checked it.
  7. The status: open, implemented, verified or closed.

Change log, version history and audit trail: how they differ

The three terms overlap, and brokers often use them interchangeably. They answer different questions.

RecordQuestion it answersTypical content
Version historyWhat did this document look like before?Earlier copies of one file, with dates
Change management logWhich changes were requested, made and verified, and who closed them?A register across documents, with status
Audit trailWhat happened to this case, step by step?Every upload, view, check, flag, approval and hand-off, with user and time

QueryChart makes the first distinction explicitly: the change log is distinct from a document's own version history. In a mortgage setting, the audit trail is the broader record, and the change log sits inside it as the part that shows corrections and their sign-off. Our guide to document version control for UK mortgage brokers covers the version side in detail.

What a mortgage document audit trail should record

Auditability is more than a list of timestamps. The Canadian Centre for Cyber Security's guidance on audit and accountability says records must identify the event, its source, the result and the responsible entities. It also warns that the trail itself creates privacy risk and needs managing.

Applied to a broker's case file, that gives a practical minimum for each document and review action:

ItemWhat to capture
EventRequested, uploaded, viewed, checked, flagged, corrected, approved, rejected, sent
SourceHow it arrived: client upload, adviser upload, lender request
ActorNamed adviser, administrator, client or automated check
TimeDate and time from a single synchronised clock
ObjectThe specific document, applicant and period covered
ResultPass, fail, query raised, discrepancy found and its resolution
ReasonWhy a document was replaced or an exception accepted

The OWASP Logging Cheat Sheet uses the same logic: record when, where, who and what, including the action, the object and the result. It suits financial case files well because the aim is to reconstruct the original sequence of events.

7 practices for a trustworthy log

1. Define the purpose before the fields

OWASP advises setting logging requirements around purpose and risk. For a broker, the purposes are usually three: show the regulator an orderly record, answer a lender query quickly, and defend a decision if a case is later questioned. Fields that serve none of these do not belong.

2. Log enough, but not everything

Researchers at Harvard, in Correct Audit Logging: Theory and Practice, treat audit-log quality as a correctness problem. The log must capture sufficient and correct information for the question it will be asked, and avoid collecting more than needed, since excessive logging slows systems and produces very large logs. In a brokerage, this means do not copy full bank statement contents into a note field when a reference to the stored document will do.

3. Capture entries automatically where possible

A log that depends on an adviser remembering to write a note will have gaps. Uploads, views, approvals and automated check results should be written by the system at the moment they occur. Manual entries are for judgement calls, such as why an explanation of a large deposit was accepted.

4. Use one time source and a fixed format

OWASP recommends structured formats and synchronised time. A consistent date format and a single clock make entries comparable across advisers, devices and the client's own uploads.

5. Separate implementation from verification

QueryChart's perspective is that a change log can be trusted only when the implementation is independently checked against the document that actually changed, and the entry is then closed. In practice: the person who replaces a payslip is not the person who marks the correction verified. Our piece on document approval workflow controls sets out how to build that separation into the approval queue.

6. Protect the log itself

OWASP says logs should be protected from tampering and unauthorised access, and retained only for the required period. Restrict who can read entries, prevent anyone editing past entries, and record any administrative change to the log as an event of its own.

7. Record the evidence behind each change

UpGuard's explanation of ISO/IEC 27001 control 8.32 lists the kind of evidence that supports a change: approved change tickets, impact analysis, rollback plans, test results, deployment logs and post-implementation reviews. A brokerage does not need all of these, but the principle transfers. A correction should point to the approval, the reason and the check that followed.

Tracking a case from collection to lender hand-off

The log earns its keep when it follows the case through every stage. These are the points where a broker should expect an entry.

  1. Document list created. Record which documents were requested and why, based on how the client is paid (employed, self-employed, contractor). Our guide to automated document collection explains how lists can build themselves from payment type.
  2. Client upload. Record the time, the applicant and the capture method. If clients photograph documents on a phone, the mobile document capture guide covers quality checks at this stage.
  3. Identity check. Record the result and which checks were run. See identity document verification for UK mortgage brokers.
  4. Authenticity and tampering checks. Record any flag and how it was resolved. The tampering detection guide explains what these checks look for.
  5. Cross-checks. Record discrepancies between documents, such as wage deposits that do not match payslips or commitments on statements that were not declared. Log the question put to the client and the answer received.
  6. Correction. Record the replaced document, the reason, and the verifier. The earlier version stays retrievable.
  7. Approval. Record who approved the file and when.
  8. Lender submission. Record exactly which documents and versions were sent, and any query received afterwards.

The last step matters most in disputes. If a lender raises a query three weeks later, the log should show which version of the payslip they received, not merely that one was sent. For wider process choices, see what to automate and what to keep.

Common gaps that weaken an audit trail

These are the weaknesses we see most often in how case records are kept. They come from our experience of broker workflows rather than from a published study.

  • Email as the system of record. Documents arrive in inboxes, are saved into folders and renamed. Nothing shows who changed what.
  • Overwritten files. A new payslip replaces the old one with the same file name, and the earlier version is lost.
  • Undated or unsigned exceptions. An adviser accepts an explanation verbally, but no entry records the decision or its reason.
  • Shared logins. When several people use one account, the actor field is meaningless.
  • Logs that can be edited. An editable log is a note, not evidence.
  • No link between check and outcome. A flag is raised, but the log never shows how it ended.
  • Excess personal data in the log. Copying sensitive details into free-text fields widens the privacy exposure the trail was meant to reduce.

Our mortgage fraud red flags checklist shows which discrepancies are worth a logged follow-up.

Retention, access and the UK position

For UK brokers, the starting point is the FCA's general record-keeping rule. SYSC 9.1.1 requires a firm to keep orderly records of its business and internal organisation, including all services and transactions, sufficient for the FCA to monitor compliance and to check that obligations to clients were met. That standard is why a scattered inbox is a weak answer.

For regulated mortgage contracts, MCOB 6.4 requires an adequate record of each offer document and its retention for one year from issue, including information sent in a separate accompanying document. Retention periods differ by activity and by firm type, so confirm the periods that apply to your permissions with your compliance support or network.

US rules are sometimes quoted in this area, and they are useful as a benchmark only. Fannie Mae's electronic records requirements say electronic records must be reproducible, securely stored, accessible to entitled persons for the required period, accurate and protected against loss and unauthorised access. Those principles match good UK practice, but they are not UK law, and the US retention periods do not apply to a UK brokerage.

Keep the data in one place, too. Where client documents and their logs sit matters for UK data protection. Casefile keeps data in the UK, and we describe how in how Casefile handles your documents.

Retention, access and the UK position — overview diagram

Our perspective

We build for small and mid-sized UK brokerages, and the pattern is consistent. The audit trail is rarely missing because a firm disagrees with keeping one. It is missing because keeping it by hand costs time that an adviser would rather spend with a client.

Our perspective — overview diagram

Our view is that the log should be a by-product of the work. When a document is requested, uploaded, cross-checked and approved inside one platform, each step writes its own entry, and nobody has to remember anything. Discrepancies such as an undeclared commitment or a wage deposit that does not match a payslip are flagged and logged before the file reaches a lender, which reduces queries rather than just documenting them.

We also hold that privacy belongs in the design. A trail should show who did what without spreading applicant data into every note. That is why we keep processing in the UK, with no manual or offshore handling of documents.

— Darren

How Casefile supports the audit trail

Casefile is a cloud-based platform that automates document collection and review for UK mortgage brokers. It builds document lists from client payment types, cross-checks bank statements, payslips, tax forms, ID and utility bills, flags discrepancies, manages approval queues and keeps a clear audit trail under your own branding, with UK-only data residency. Pricing is not published. You can see how it works on the Casefile site.

FAQ

What is the difference between a change log and an audit log?

A change log records changes to a record and tracks them through request, implementation, verification and closure. An audit log is wider and records events such as access, uploads and approvals, whether or not anything changed. In a mortgage file, you want both, with the change log forming part of the audit trail.

What should a mortgage audit trail include?

For each action, record the event, the source, the person or process responsible, the time, the document and applicant affected, and the result. Add the reason for any correction or accepted exception. Keep sensitive content out of the log and refer to the stored document instead.

How long should a broker keep these records?

It depends on the activity and your regulatory permissions. The FCA requires orderly records under SYSC 9.1.1, and MCOB 6.4 sets a one-year retention for offer document records. Confirm the full set of periods for your firm with your compliance support, and delete data once the required period ends.

Can a spreadsheet work as a change log?

For a very small volume it can record the fields, but it cannot prove they were not edited afterwards, and it relies on people to complete it. Once a firm handles many cases, automated capture with restricted editing is more reliable.

Sources

This article was generated with AI, and whilst it is our expectation that the article is accurate, it should not be taken as advice.