The Wet Signature Is Not the Problem: Capturing Its Evidence in UK Digital Workflows

Wet signatures have a curious status in UK business. Electronic signatures are widely accepted, and the Law Commission's 2019 statement gave them a firmer footing, yet many records still arrive on paper because a statute, a counterparty, a professional body, or simple institutional habit demands ink. Deeds, some land registration documents, statutory declarations, certain HR and board papers, and contracts negotiated with cautious overseas parties continue to generate signed paper in 2026. The capture team rarely controls that decision. It inherits the consequence.

Treating signed paper as an afterthought creates two failures. The scan is often poor, and the evidence around it is thinner still. A signature that has been copied at low resolution, separated from its covering letter, and saved into a shared drive proves very little when a dispute arises months later. The answer is not to resist wet signatures. It is to capture them with the same discipline applied to any other controlled business record.

The signature is not the whole record

Legal teams rarely ask only whether a document was signed. They ask who signed it, in what capacity, on what date, in whose presence, and whether the version now being examined is the version that was executed. A deed may require attestation. A statutory declaration may require particular wording and a witness. An employment contract may depend on an offer letter, a job description, and a signed acceptance forming a coherent set. The signature is one element of a record, not a substitute for the record itself.

This distinction matters for capture design. If the scanning process treats each page as an isolated image, the link between the signature page and its supporting documents is lost. If the process treats the signed bundle as a case, with a unique reference and a defined document set, the evidence survives. Capture teams should therefore avoid batch scanning signed material without context. The signed page should enter the workflow with its related documents, its version number, and a clear indication of why the paper version exists.

Capture at the point of signing

Where paper must be used, the strongest capture point is close to the signing itself. A document scanned immediately after execution is less likely to be lost, amended, or separated from its envelope. A document left in an in-tray for a week is a document waiting for an exception.

In practice, this means giving signing locations a simple capture route. A departmental scanner, a mobile scanning application, or a reception desk device can all work, provided the output meets a consistent standard. Scan in colour where the document contains coloured seals, stamp duty evidence, or handwritten amendments. Use a resolution sufficient to read small print and distinguish a signature from a photocopied mark. Capture both sides where the reverse carries terms, witness details, or continuation notes. Record the operator and the device, not to assign blame but to support reconstruction.

A separator sheet with a unique barcode can help. It allows a batch to be split reliably and gives the scanned bundle a reference that can be matched to a workflow case. The separator should not replace metadata, but it can reduce indexing errors when several signed documents are processed together.

Build a signature evidence record

A scanned image on its own is a picture. A signature evidence record is a controlled package. For each wet-signed document, the record should identify the signatory, their role or capacity, the document type, the version signed, the date of signature, the date of capture, the capture device or operator, any witness or attestation details, and the location of the original paper if it is retained.

Where the document is part of a set, the record should link to the other components. Where an exception exists, such as a missing date or an illegible witness address, the record should state the exception code and the action taken. Where the paper original is to be destroyed after scanning, the record should show the authority for that decision and the retention rule applied.

This need not require a bespoke system. A document management platform with mandatory metadata fields, version control, and an audit log can carry the record. The important point is that the evidence lives with the image rather than in an email chain or a local spreadsheet.

Hybrid signing without theatricality

Many UK organisations operate a hybrid ceremony: part digital, part paper. A contract may be negotiated and approved electronically, printed for signature, signed in a meeting, scanned back into the workflow, and then circulated as a PDF. This can work well, but only if the handoffs are controlled.

The printed version should be generated from the approved final text and marked with a version reference. The signing meeting should capture any manuscript amendments on the document itself, with initials and dates. The scan should happen before the document leaves the room or the building. The returned PDF should be checked against the version that was printed. If the scan is unclear, the document should be rescanned rather than enhanced beyond recognition.

A useful discipline is to treat the wet-signed paper as the execution copy and the scan as the working copy, while the document management record explains the relationship between the two. That prevents staff from treating a later digital copy as if it were the signed original.

Exceptions need a route, not a shrug

Signature capture generates exceptions: a signatory forgets to date a page, a witness signs in the wrong box, a company seal is omitted, or a document arrives with a covering note instead of the required form. A policy that sends every exception to legal is not a policy. It is a queue.

Define a small set of exception categories and a proportionate response. Minor omissions might be resolved by a documented clarification email, a re-signature of the affected page, or a noted acceptance by an authorised officer. Material defects should be escalated. The key is that the exception is recorded, the resolution is linked to the document, and the audit trail shows who approved the outcome. Staff should not be left to improvise quietly.

An audit trail legal teams can follow

The evidence trail should be reconstructable without interviewing the staff who happened to be in the office. That means an audit log showing when the document was captured, by whom, from which device, and with what metadata. It means access controls that show who viewed or exported the record. It means version history that distinguishes the executed copy from later working copies. It also means retention rules that prevent signed records from being deleted casually while preserving the organisation's ability to meet its data protection obligations.

Legal teams are usually less interested in the scanner model than in the chain of custody. A clear signature-capture policy gives them that chain in advance, rather than asking them to assemble it after a challenge.

The missing piece in most digitisation plans

Most UK digitisation plans describe scanners, storage, and workflow routing. Fewer describe how wet-signed paper will be recognised, captured, evidenced, and retired. That gap is the missing piece. A practical policy can be short: state which document types require wet signatures, who may capture them, what standard applies, how exceptions are handled, where the evidence record lives, and how long both paper and digital versions are retained.

For UK capture teams in 2026, the objective is not to eliminate ink. It is to make the ink defensible. A wet signature captured promptly, linked to its document set, and supported by a clear evidence record will serve the organisation far better than a perfect digital workflow that quietly loses the paper it depends on.