Home/Documents/Legal Notice

Supported document type

Detect tampered and deepfake Legal Notice

A legal notice is a demand rather than an order, and that is what makes a fake one profitable: it costs nothing to send and it can frighten a recipient into paying or conceding. Forged notices arrive on a law firm's letterhead the sender has no right to use, over an advocate registration number belonging to someone else or to nobody. Genuine notices get altered too, usually to inflate the claim or move the deadline. TamperCheck compares the letterhead, the reference block, and the body against each other.

API slug: legal_notice

Last updated:

What a genuine legal notice contains

A legal notice is sent on firm letterhead carrying the firm name, office address, contact details, and the practising advocate's name with their roll or bar registration number. Below that sit the firm's own reference number, the date of the notice, the addressee's name and address, and a subject line naming the matter. The body recites the facts relied on, states the claim particulars and the amount demanded, cites the provision under which the notice is issued, sets a period to comply, and closes with the advocate's signature and the firm's stamp. Postal or courier proof is often attached.

The notice date is the field everything else counts from. A compliance period runs forward from it, so moving the date moves the deadline and the point at which the sender claims a right to escalate. The dispatch receipt carries its own date that has to sit alongside it. The claim amount normally appears twice, once in the narrative and once in the demand paragraph, and the two are written in different forms - figures in one, words in the other. The registration number ties the notice to a person who is answerable for it.

How legal notice forgeries are made

  • Letterhead reproduction

    A firm's letterhead is rebuilt from a published PDF or a scanned original and used to send demands the firm knows nothing about. Rebuilt letterheads lose the fine detail of the original logo and sit at a different scale or baseline offset from the body text than the firm's real template does.

  • Borrowed or invented registration numbers

    The advocate's roll number is fabricated, or taken from a practitioner with no connection to the matter. It is the single most checkable field on the document and the one senders assume no recipient will look up, which is why a number that fails the bar council's own format is a common finding.

  • Claim amount inflation

    A genuine notice is intercepted or reused with the demanded sum raised. The narrative figure and the demand paragraph are meant to agree, and an editor working quickly changes one, leaving a notice that claims two different amounts for the same debt.

  • Notice date manipulation

    The date is moved backwards so a compliance window appears to have already expired, or forwards to revive a notice that lapsed. Either way the printed date then conflicts with the postal proof, the file timestamps, and any correspondence already exchanged about the same matter.

  • Fabricated dispatch proof

    A postal receipt or courier tracking slip is manufactured to show the notice was served on a date it was not. The invented slip usually reproduces a barcode that does not encode the number printed beneath it, and its print quality differs from anything a counter terminal produces.

  • Notices drafted wholesale by a model

    A complete notice can now be produced without a lawyer, correct in tone and structure and free of the errors that used to expose a fake. What it lacks is a firm behind it, so the checkable fields fail first and the text itself shows the uniform rendering of something that was never printed and scanned.

What TamperCheck checks on a legal notice

TamperCheck runs 200+ forensic checks across three layers and returns a risk score from 0 to 100 with plain-English findings tied to specific regions of the document. These three carry the most weight on this document class.

  • Stamp authenticity and placement

    Stamps are assessed for whether the ink was impressed onto the page or printed as part of it, and for whether the impression was placed digitally after the fact.

  • Letterhead, logo, and issuer plausibility

    Issuer branding is checked for resolution and compression consistency against the body text it sits on. A logo lifted from a website carries the signature of its source, not of the document.

  • Date and validity consistency

    Issue, expiry, and period dates are checked against one another and against the file's own creation metadata, which catches backdating and validity extension.

  • And many more checks

    The three above are the layers that carry the most weight on a legal notice. Every upload runs the full suite of 200+ checks regardless of document class, spanning file structure and metadata, pixel-level forensics, font and text rendering, optical and print characteristics, provenance signals, AI-generation signatures, and many more checks.

Who verifies a legal notice, and why

Legal departments and businesses responding to formal demands. In each case the document is being used to unlock money, access, or a legal status, which is exactly what makes it worth forging.

How to verify a legal notice in 4 steps

  1. Check the fields against each other

    Read claim particulars, advocate registration number, and notice date together rather than one at a time. Forgers typically change one value and leave the rest of the document describing the original.

  2. Inspect the file metadata

    Open the document properties and look at the producer, creation date, and modification date. A document produced by a consumer PDF editor, or created long after the date printed on its face, is worth a closer look.

  3. Ask for a second document

    Request a corroborating document from the same issuer or an adjacent period. Forgery effort concentrates on one file, so inconsistencies surface as soon as there are two to compare.

  4. Run a forensic check

    Manual review catches obvious edits but not field-level pixel manipulation or synthetic generation. TamperCheck runs 200+ forensic checks on a legal notice and returns a risk score from 0 to 100 within seconds, at $0.50 per document.

Frequently asked questions

How do I verify a legal notice is genuine?

Contact the firm on the letterhead using details you look up yourself rather than the ones printed on the notice, and ask whether they issued it under that reference number. Check the advocate's registration number against the bar or roll register. Then read the notice for internal conflicts: two different claim amounts, or a compliance date that does not count forward from the notice date.

Can a legal notice be faked?

Yes, easily, because nothing about a legal notice is registered or centrally issued. It is a letter on a letterhead, and both can be reproduced. The cost of sending one is nearly zero and the pressure it creates is real, which is why fabricated demand notices are a common precursor to settlement fraud and to phishing that asks for payment to an unfamiliar account.

What are the signs of a fake advocate letter?

The reliable signs are a registration number that fails the register's format or belongs to another practitioner, a payment account that does not match the firm's published details, a compliance period inconsistent with the notice date, and a letterhead logo that is slightly the wrong scale or resolution against the body text. Urgency and an unusual payment route reinforce all of those.

Should I pay a legal notice I was not expecting?

No. Verify the sender with the firm directly before any payment, since a demand notice creates no obligation until it is shown to be genuine and correct. Fabricated notices rely on the recipient treating the deadline as binding. A forensic check of the file returns findings tied to the letterhead, the reference block, and the signature, at $0.50 per document.

TamperCheck analyses legal notice uploads with a hybrid forensic and AI pipeline tuned for this document class. Upload endpoints accept PDF and common image formats; class is inferred automatically. See the API & MCP documentation for authentication, async jobs, and webhooks.

Related document types

All supported document types