The document fields that cause the most disputes

When customers come to us for audit trail records, it is usually because a dispute has arisen. Over time a pattern emerged: a small number of field-level mistakes account for a disproportionate share of them, and all are avoidable at preparation time.

Ambiguous date formats

The single most common one. A contract with 03/04/2026 written into a free-text box means March 4th to an American and April 3rd to almost everyone else. In a contract with a payment deadline, that is a month of argument.

Use a date field type rather than a text box. It presents a picker and stores an unambiguous value regardless of how it displays. Where a date must be typed, label the format explicitly next to the field.

Auto-filled dates that are not the signing date

A "date signed" field should be system-populated at the moment of signature, not typed. Typed dates get entered wrong, get copied from a draft, or get filled in optimistically before signing actually happens.

A date-signed field that disagrees with the audit trail timestamp is exactly the kind of inconsistency that undermines confidence in an otherwise solid document.

Unlabelled initial boxes

Initials in a margin, with no indication of what they acknowledge, are weak evidence. If the point of an initial is to confirm a specific clause was read, the field needs a label tying it to that clause.

Optional fields that were meant to be required

A field left optional by accident produces documents completed without information you needed. It is invisible at send time and obvious three months later when you need the counterparty’s registered address and the box is empty.

Review required flags before saving any template. It takes a minute and prevents a category of problem entirely.

Amounts in a single free-text field

Contracts have written figures alongside numerals for a reason — the redundancy catches transcription errors and makes tampering harder. Digitising the process is not a reason to abandon it.

For material amounts, use two fields: a numeric field and a text field for the written form. Where possible, derive the written form automatically so they cannot disagree.

Fields assigned to the wrong signer

A field assigned to the wrong party produces a document where someone filled in information they had no authority over. In a two-party agreement it is usually caught. In a five-party agreement it very often is not.

Use the per-signer colour view before sending. Thirty seconds of looking at which colour sits where catches nearly all of these.

Signatures in the wrong place on the page

A signature field that overlaps the clause text underneath it makes the underlying words hard to read in the final document. On a disputed contract, a term partially obscured by a signature image is an argument waiting to happen.

Check the completed output, not just the preparation view. Fields that look correctly positioned while empty can overlap once a long signature or a wide typed name is rendered into them.

Free-text where a dropdown belongs

Any field with a known set of valid answers should be a dropdown. Payment terms typed freely produce "30 days", "net 30", "thirty days", "Net-30", and "30" across five contracts, none of which agree well enough to report on and some of which are genuinely ambiguous.

Dropdowns also remove the possibility of a value nobody intended to offer. A free-text payment terms box will eventually contain "90 days", agreed by someone who did not know that was not on the table.

Attachments nobody checks

Attachment fields — proof of insurance, a certificate, an ID document — get uploaded and then frequently never reviewed. The field being satisfied is not the same as the attachment being correct.

If an attachment matters, assign someone to check it as an explicit approval step. Otherwise you have documented that a file was uploaded and nothing about whether it was the right one, unexpired, or legible.

The one-minute check

1. 1Every date is a date field, not text
2. 2Date-signed fields are system-populated
3. 3Every initial box states what it acknowledges
4. 4Required flags are set on everything you genuinely need
5. 5Material amounts appear in both numerals and words
6. 6The colour view shows each field on the right signer

Six checks, about a minute, on a document you may rely on for years. It is the best-value minute in the whole process.

Fix it in the template, not the document

When you find one of these, the instinct is to correct the document in front of you and move on. That guarantees you will find the same problem again next month.

Fix the template. If the document was not built from a template, that is the actual finding — a document type you send regularly enough to have problems with, and no template governing it. Ten minutes building one closes the whole category rather than one instance of it.