What to do when a party's details appear differently in two places in the same deed

The transfer deed in front of you names the seller as "Patricia Anne Wheeler" in the parties clause and "Patricia Ann Wheeler" in the execution block. There is no external document creating the conflict — the deed contradicts itself. That needs resolving before anyone signs.

Internal inconsistencies are different from the mismatches you find when cross-referencing a deed against a client's identity document. When a name differs between a passport and a contract, you have two sources and can work out which is likely authoritative. When the conflict sits inside the same document, you have no reference point: the document is arguing with itself.

Why it happens

Most internal inconsistencies trace back to document assembly. A deed starts from a precedent, goes through several rounds of drafting, has clauses copied and pasted, and somewhere in that process a field gets left behind. The client's name was updated in one clause but not another. The title number was corrected in the body but still reads the old value in the schedule. The address was amended in the engrossment but remains unchanged in the notices clause.

Occasionally the cause is a version merge — two fee earners working off separate copies, with an incomplete reconciliation at the end.

In either case, the result is a document that carries two versions of the same fact.

Which fields are most likely to diverge

Not every field appears just once in a standard deed or contract. The ones that travel through multiple clauses are the ones that create this problem:

• Full name of each party: typically in the parties clause, repeated in operative provisions, and again in the execution block.
• ID or registration number: may appear in the parties clause and again in a recital or schedule confirming identity.
• Capacity: "as beneficial owner" or "as trustee" may be stated correctly in one place and dropped or varied in another.
• Property description: the address or title reference may differ between the operative clause and an annexed schedule.
• Date: an execution date can appear in the opening and again at the signature page; if they don't agree, the document has a problem.

How to structure the check

The efficient approach is field-by-field rather than paragraph-by-paragraph. Before you cross-reference the deed against the client's identity documents, work through the deed itself and confirm that each field is identical everywhere it appears.

A minimum extraction list for each party:

1. Full legal name, as it appears on first mention.
2. Identifying number (where applicable — passport number, Companies House number, land registry reference).
3. Capacity (own name, trustee, director, authorised signatory).
4. Address, if stated.

For each one: does this field appear in more than one place? If so, is it exactly the same each time?

A document comparison tool can extract all values for each field across the document and flag which ones don't match — faster than reading the whole deed looking for repetitions.

How to handle a discrepancy once you find one

The first rule is not to assume which version is correct. If a name appears two different ways, neither carries more authority than the other within the document itself. You need to go outside the document to resolve it.

For names and identification numbers, the reference is always the client's identity document. If you have the passport or driving licence to hand, you can determine which version is right. If you don't, the discrepancy becomes a reason to request it before going further.

Once you have identified the correct version, both incorrect instances need to be flagged and corrected before execution. It is not enough for the client to confirm verbally which version is right: the document needs to be internally consistent before it leaves the office.

A specific case: the date

The execution date deserves separate attention because the consequences are different. If the opening clause says "executed on the tenth day of September" and the signature page reads "11 September", the document carries two different execution dates. That is not resolved by reference to identity documents — you need to establish the actual date of execution and correct the document accordingly. In conveyancing, where dates carry legal significance for completion, land registry applications, and SDLT deadlines, an inconsistent date is a material defect, not a drafting irritant.

What to record

When you document the review, "name discrepancy" is not sufficient. Record where each version appears — for example, "name differs between parties clause and execution block" — with the actual value in each location. That gives whoever is correcting the document exactly what they need to find it without re-reading the whole file.

If the discrepancy is not resolved before execution — because the correction is still outstanding, because identity documents have not arrived, or for any other reason — record that too, with the date and the reason. The review log should reflect what was found and what happened next, not just what was clean.