How a name discrepancy in a client document can delay completion — and how to catch it first

A mismatch between the name on a client's ID and the name in a deed or contract is enough to halt completion — or, worse, to give grounds for a challenge after the fact. It is also one of the most common errors that only gets spotted on the day itself.

Why it gets caught so late

The issue is rarely carelessness. The more common cause is that name checks happen mentally and partially: the fee earner reads through the file, recalls the client's name, and moves on. An actual side-by-side comparison of the name field on the ID against the name field in the deed only happens when something feels off — and sometimes nothing feels off until the client is sitting across the table.

Four types of discrepancy come up regularly:

• Middle names: the ID reads "James Robert" and the deed reads "James" — or the other way round.
• Maiden name versus married name: the ID was issued under a previous surname, but the deed uses the current one, or the opposite.
• Transcription errors: a letter transposed, an apostrophe added or dropped, or the legal spelling differing from the everyday one.
• Informal names: the document uses a version of the name the client goes by, which doesn't match the name on the ID.

When to look

The right moment for a name consistency check is when the file is first assembled, not when the appointment is already confirmed. There are two reasons for this.

First, the time available to resolve a discrepancy matters. A name error in a deed may require an amendment that takes several days. If it's caught early in the week before completion, there is room to act. If it's caught ten minutes before the client arrives, there isn't.

Second, early detection allows a calm response. There is time to contact the client, request up-to-date ID, and carry out a careful comparison of the fields that matter: full legal name, document number, expiry date, and — where relevant — whether the ID reflects the client's current legal name.

How to structure the check

A systematic name check doesn't take long. The practice is to compare, when the file is first assembled, the name on every piece of client ID against the name as it appears in the document to be signed. Field by field, not from memory.

The check has three steps:

1. Collect ID from all parties before the first draft of the deed is prepared. If the document is drafted first and the ID arrives later, an error can be built in from the start.

2. Compare the full legal name on the ID against the full name in the deed. Not a quick read — a literal comparison, character by character when any variation is present.

3. Record the check in the matter file. A note confirming which ID was used, when the comparison was done, and whether any variation was found. If a discrepancy was found and resolved, the resolution should be on the file too.

What to do when the discrepancy is already there

If the name in the deed has already been drafted and doesn't match the ID, the matter has to be resolved before completion, not at it. The available options depend on the nature of the error and the type of document — but the principle is always the same: neither version of the name can be left unresolved.

The most common response is a deed amendment or re-engrossment. That takes time and, in most cases, input from whoever drafted the document. Which is exactly why catching it early matters.

If the discrepancy is on the client's ID — because the document is out of date or records an earlier name — the problem sits outside the matter file. The question becomes which official document is current and whether it is sufficient for the transaction in question. That is a judgement the practice needs to make well before completion day.

What can be systematised

This kind of check does not have to depend on one person's attention at a critical moment. Comparing names across documents is precisely the type of cross-referencing that can be delegated to a tool — especially on matters with multiple parties, or where the volume of instructions doesn't leave room for detailed manual review on every file.

The point is that the check happens consistently, on every file, and that any difference is recorded before it becomes a problem at the table.

If you'd like support with document review and verification in your practice, VerifyAct has tools built for that.