Proposal fraud: which fields get edited and how it is caught
A contractor proposal is a written offer to do defined work for a stated price, usually for a named project, and owners, lenders and procurement teams rely on it to support a budget or a draw schedule. Forgeries change the price, the scope or the acceptance, because those are the fields a decision rests on. Checking one means testing the arithmetic, the dates and the signature block against each other.
Last updated:
Where the edits land
Figure
scope item prices and total
Overwritten in place; derived totals stop reconciling.
Date
proposal and acceptance dates
Cheapest to change, easiest to leave out of sequence.
Seal or signature
client signature block
Lifted from a genuine document and composited on.
Person or party
contractor name and contact details
Borrows a real issuer's credibility for someone else.
Where forgers attack a proposal
Total and line-item edits
Prices are raised or the contract sum is rewritten so the proposal supports a larger budget or draw. The lines then fail to add up to the stated total, or a per-run price multiplied by the run count no longer matches its line amount. Arithmetic on a typed proposal is unforgiving, and one stale figure exposes the edit.
Single-figure patching
One price, quantity or total is replaced in a different font, weight or alignment from its neighbours, or sits on a patched background. Loose, hand-typed layouts make this tempting, but the edited figure still carries its own rendering and sharpening.
Acceptance block transplant
A signature is lifted from another document and placed in the client acceptance block. Its ink, resolution and compression differ from the typed body, which is different from the ordinary case of a signature page that was scanned separately and then attached.
Date manipulation
A signing date earlier than the proposal date, or an acceptance that falls outside the stated validity period, shows a date was changed to make an old offer look live. The proposal date normally precedes the signing date, so the order of the dates is a check in itself.
Letterhead and cover-up edits
The proposer's name, licence or contact details disagree between the letterhead and the body, or an overlaid image hides original text where no stamp, logo or signature belongs. Both leave a boundary that does not match the page beneath it.
The forensic checks that matter most for a proposal
Arithmetic reconciliation
Stated totals are recomputed from their components, and running or cumulative figures are checked for continuity across periods. A single edited value breaks the chain even when the page still looks right.
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.
Signature forgery analysis
Signature regions are assessed for ink consistency and for how the stroke sits on the page, which distinguishes a genuine pen stroke from a pasted image of one.
And many more checks
The three above are the layers that carry the most weight on a proposal. Every upload runs the full suite of 300+ 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.
Visible warning signs in a proposal
Scope item prices and total that do not sit with the figures around it
Work through every number the page lets you recompute. The scope item prices and total are the value a forger most wants to change, and the one a careless edit leaves out of step with the totals and running figures derived from it.
Proposal and acceptance dates that break the chronology
Lay the proposal and acceptance dates against every other date on the document and against when the file says it was created. Backdated and extended dates tend to land in an order no real issuing system would have produced.
Bank details that differ from earlier documents
Compare the payee account against the last genuine document from the same sender. A changed account number is the single most expensive edit on this class.
A logo and layout that look perfect
A flawless layout proves nothing, because the template is the easy part. Look at the fields that carry money and identity instead.
Totals, tax and line items that disagree
Recompute line totals, tax and the grand total. Edits to one figure often leave a dependent figure untouched.
How to check a proposal step by step
1. Add the lines to the total
Sum the scope items and compare the result with the stated total or contract sum. Where prices are given per run, multiply by the run count and compare with the line amount.
2. Put the dates in order
Check that the proposal date comes first, that any acceptance falls inside the validity period, and that the signing date does not precede the proposal.
3. Compare the acceptance block with the body
Look at whether the signature and date block share the resolution and compression of the typed text, and whether the proposer's name and contact details agree between letterhead and body.
4. Run a forensic check on the file
The arithmetic and dates tell the logical story, and the file tells the edit history. TamperCheck runs 300+ forensic checks including arithmetic validation and patch detection, returning a risk score from 0 to 100 with findings tied to regions of the image.
Anatomy of a genuine proposal
A genuine proposal opens with the proposer's name, address, phone and email on a letterhead, followed by a proposal date and the project name and address. The scope of work lists items or trades, often with a price on each line or a single lump sum, and notes which plans or drawings the price relied on.
The conditions carry the weight. Exclusions, assumptions, a validity period and change-order wording for work that differs from the plans sit above a total or contract sum, payment terms and a client acceptance block with a signature and date. The layout is often hand-typed, with uneven spacing, mixed fonts and prices written as lead-ins such as a dollar amount followed by a quantity, and the countersigned copy is frequently scanned after the proposal was issued.
Where reviews of a proposal go wrong
Duplicates are hard to spot at scale
The same document with one altered field passes as a new one unless submissions are compared with each other.
Urgency discourages checking
Payment documents arrive with a due date and a deadline. A rushed reviewer approves what looks familiar.
The template is the easy part
A sender's layout is trivial to copy. What a forger changes is the account number, and it sits in an unremarkable corner of a proposal.
Questions people ask about a proposal
How can I tell if a contractor proposal is fake?
Start with the numbers. A genuine proposal's line items add up to its total, its dates run in order, and its letterhead and body agree on who the proposer is. A figure in a different font, a signature block with different image quality from the body, or an overlay hiding original text are the usual signs of an edit.
Why is the signing date later than the proposal date?
That is the normal order. A proposal is issued first and countersigned by the client afterwards, so a signing date that follows the proposal date is expected. The suspicious case is the opposite, a signing date earlier than the proposal or an acceptance outside the validity period.
Can a scanned proposal with a signed page still be genuine?
Yes. Proposals are often printed, signed and scanned, so the signature page can have a different resolution from the typed body without anything being wrong. What matters is whether a specific figure or block shows its own edit traces, not whether pages differ in scan quality.
Does an authentic proposal prove the work was done?
No. A proposal is an offer. An authentic one says nothing about whether the work was carried out or paid for, so a lender or owner still needs the contract, invoices and payment records to support a draw.
Where does a forensic review of a proposal start?
On a proposal, the review prioritises the scope and exclusion wording, the acceptance signature and date, and the validity period. Pixel, font and metadata checks then run across the rest of a proposal.
What inconsistency most often exposes a forged copy of a proposal?
Compare the itemised prices with the stated total. A forger who changes one rarely updates the other, and on a proposal that gap is among the first things measured.
How do I catch altered payment details on a proposal?
Confirm any change out of band using contact details you already hold, and compare scope item prices and total against earlier documents from the same sender. A forensic check on the file shows whether the region around proposal and acceptance dates was edited.
What should accounts payable do when a proposal looks right but feels wrong?
Pause payment and confirm through a known contact. Then check the file: metadata, fonts and compression around scope item prices and total usually say whether a proposal was produced by one system or assembled from parts.
Can I automate checks on a proposal in my own workflow?
Yes. Upload a proposal through the REST API, receive a JSON verdict, and use async jobs and webhooks for high volume. The docs cover authentication, webhooks and MCP.
Check a document
Upload a PDF or a photo of proposal. TamperCheck returns a risk score from 0 to 100 and marks the region that was edited, usually within seconds.
For developers, the API class is proposal. See the API and MCP documentation.