Contract Signature Authority Checklist
Four documents and three sheets that check a signer's authority against your delegation matrix, not just their title, and catch counterparts nobody circulated.
Free download · No account needed
Execution Checklist
[Agreement] · [Party A] and [Party B]
Four defects a signed-looking signature block does not rule out.
| Check | Cleared on | Status |
|---|---|---|
| Every named entity matches its formation record | [date] | [ ] |
| Every signer's authority checked against the delegation matrix, not the title | [date] | [ ] |
| Every required signature page identified and circulated | [date] | [ ] |
| Every date-triggered clause resolved to one governing date | [date] | [ ] |
What closes a row
A name checked against a real formation document. An authority basis on file, not assumed from title. A page accounted for, not just requested. A date resolved in writing, not left to whichever reading is convenient later.
Every bracket fills from your own agreement. Nothing here ships with a defect already in it.
Every checklist for signing authority gives the same advice: keep a delegation of authority matrix by title and dollar threshold, and check each signer against it. That advice is right, and it is where the checklists stop. Delaware's default rule gives an officer only the authority the bylaws or a board resolution grant, under 8 Del. C. Section 142(a), so a title is a starting point, not a limit. None compute what happens once the matrix catches a defect, or once the Effective Date and the execution date pull one deadline in two directions.
Ridgeline Analytics, Inc. signs a three-year, 2,400,000 services agreement with Corvell Foods Group, LLC through its Vice President of Sales. Ridgeline's own delegation matrix, adopted by board resolution, caps a Vice President at 1,000,000 in total contract value, so this signature sits 1,400,000 outside it. The fix is a dated Authority Confirmation Request naming the exact gap, not a re-signed document. The same agreement assigns one schedule to Ridgeline Analytics UK Ltd, a separate legal entity that never signed anything, so that schedule currently binds nobody to perform it at all.
Section 1.1 sets the Effective Date thirteen days before the actual signatures, to match the customer's fiscal month, and the forty-five day milestone in Section 4.1 never says which date it runs from. Read one way, the milestone was due 18 March and a service credit is already accruing. Read the other, it is not due until 31 March. Settling a firm's positions before signature and structuring a master agreement against its order forms both happen earlier than this. What a signed contract obligates you to do next goes into the standing obligation register.
What's in the pack
Signatory Register
One row per signer, with the legal entity name matched to its formation record, the authority basis, and the contract value threshold it has to clear.
Execution Checklist
The four checks in order: entity names, signer authority, every required counterpart, and which date each clause actually runs from.
Signature Block Set
Correct legal entity names for every party, including a co-obligor or subsidiary a schedule assigns work to but the caption never named.
Authority Confirmation Request
The dated request naming the exact gap between a signer's title and the delegation matrix, addressed to whoever can actually rule on it.
Execution Status Tracker
Entity name, authority, counterpart, and effective date tracked separately per signature page, so 'pending signature' stops meaning four different things.
Counterpart and Effective Date Note
Every date-triggered clause resolved to one governing date, with both readings priced in dollars when a clause attaches money to lateness.
Post-signature Distribution List
Who receives the executed set and why, with the method and receipt confirmation tracked instead of assumed.
How to use it
- 1
Open in River, or take it blank
Send River the final negotiated document, the signing entities' formation records, and your delegation of authority matrix. Or take the Word documents and CSV sheets from the template library.
- 2
Build the Signatory Register first
Every legal entity name checked against a formation record, and every signer's authority checked against the matrix at this contract's value, not assumed from title.
- 3
Count what the document actually needs
Every required signature page, including a rider, joinder, or guaranty a schedule creates, tracked separately until it is signed and returned.
- 4
Resolve every date-triggered clause
The defined Effective Date and the execution date checked against each clause that measures time, with both readings priced when a clause attaches money to lateness.
Frequently asked questions
Is this free?
The download costs nothing and needs no account. Edit with AI opens a free River account and installs the same pack as a private space, with the agent ready to read your document and your delegation matrix. Both buttons point at one pack.
What format are the downloaded files?
Word documents for the four written pieces, the Execution Checklist, Signature Block Set, Authority Confirmation Request, and Counterpart and Effective Date Note, plus CSV for the three sheets. They open directly in Word, Pages, Google Docs, Excel, Numbers and Sheets, with nothing to convert.
We already have a signing authority matrix. What does this add?
A matrix is a reference document. This checks a specific contract against it, computes the dollar gap when a signer is outside it, and drafts the confirmation request naming exactly what has to be answered before the signature is treated as binding.
What happens if a signature turns out to be outside authority?
The contract is not automatically void. It is voidable, and a company can ratify it later by a properly authorised act, expressly or by knowingly accepting its benefits. The Authority Confirmation Request dates that decision instead of leaving it assumed.
Does an electronic signature change any of this?
No. The ESIGN Act says a signature cannot be denied legal effect solely because it is electronic, but it says nothing about whether the signer had authority or which entity was actually named. Those two checks run the same way regardless of how the page was signed.
How is this different from reviewing the contract before signing?
Timing. Applying settled positions to an inbound contract happens before anyone signs. This runs at the point of signature, on the document as finally negotiated, and what it creates once it is cleanly executed feeds the standing obligation register.