Check the contract before it goes out for signature

Drop the finalized agreement and list who signs. Your browser finds the blanks, the leftover notes, the missing exhibits and the entity names that do not match the signature blocks, and proposes the signing order - free, before you sign in, and nothing is uploaded. Then a paid run writes the signing packet: the pre-signature checklist, what to fix, the signing table, each signer's fields and the envelope message. Nothing is sent. Not legal advice.

Each example has a saved model run, so you can see the whole page for free.

Agreement (what you call it)

Your company's legal name

Signing order

Sending on

The agreement, as it will be signed

Include the opening paragraph, the signature blocks and every exhibit. A .docx is unzipped in your browser, and its tracked changes and comments are counted.

Drop a .docx, .txt or .md, or a pack .json saved from this page, or

Signers (one per line: name, email, title, party)

Party is a name from the agreement, or us / them.

Internal approvers (approve before anyone signs; name, email) Copy when complete (name, email)

This is the final version both sides agreed - no open points Counsel has reviewed this final version

Prescan (free, in your browser, no AI)

Pre-signature checklist, as the browser reads it

Item	Browser's read	Flags

Flags

Parties and signature blocks

Ref	Opening paragraph	Signature block	Signers

Proposed signing order

Step	Ref	Name	Email	Role	Action

Free: no account, no run.

Anything to ask (optional)

Paste the agreement to price the run.

Not legal advice. Written by AI from the contract and the browser's checks - confirm before sending.

issues to fix

signing steps

prescan flags answered

disagreements

Pre-signature checklist

Item	Status	Note	Refs

Fix before sending

Ref	Severity	Issue	Fix

Signing configuration

Order	Ref	Name	Email	Role	Action

CC when complete

Fields to place

Envelope message

Next steps

Prescan flags, answered

Reconciliation with what you entered

The status could not be looser than the flags left standing, every high or medium flag needed an issue line, every flag an answer, every signer and approver exactly once with the email you typed, the order had to follow your routing choice, and no email address or party name could appear that is not in your list or the contract.

Raw model reply

The reply did not parse as the structured result, so it is shown as it arrived.

Your recent checks

What this does, and what it does not

The most common signing error is a wrong legal entity name. The prescan reads the parties from the opening paragraph and compares each one, letter for letter, with the name over its signature block and with the company name you typed. It finds unfilled blanks ([●], TBD, ____ outside the signature lines, bracketed alternatives), leftover notes to draft, and - in a .docx - tracked changes and comments. It lists every exhibit and schedule the text refers to and checks that each is attached after the signature section and has something under its heading.

The signing order puts internal approvers first, then either the counterparty before your side (so you countersign last and hold the fully signed copy), your side first, or everyone at once. Witness, notary and initials lines are flagged so you can set them up - whether a witness or notary step can be done electronically is a question for counsel.

Nothing is sent: you load the recipients CSV and the envelope message into your own e-signature tool. It knows nothing you did not paste. Derived from the agent skill @anthropics/signature-request (anthropics/knowledge-work-plugins, Apache-2.0). The example companies and people are fictional.