In plain English
Pinning standard terms for contract review means writing your playbook once (caps, payment, data, IP, exit) and treating every deviation as a flagged decision. Humans and AI can then cite the clause that wandered. Without a pin, review is vibes. With one, "nonstandard" has an auditable source of truth.
Not legal advice. A pinned playbook is an ops standard, not a substitute for counsel on material or unusual risk.
By version90 staff Published How this was made
What does "pinning" standard terms mean?
Pinning is making one written standard the reference for review: positions you usually accept, language you usually counter, issues you always escalate. The pin is the yardstick. The contract is the thing you measure. Anything that does not match is a deviation, not a surprise.
This is the same instinct as pinning a Startup MSA redline checklist, except the standard is in the system humans and models actually use. An MSA has dozens of places to "be reasonable." Reasonable is not a standard. "Cap = 12 months fees paid, mutual, carve-outs limited to X" is a standard.
version90 calls this pinned standards: your playbook sits with the deal so review can flag where the draft departed. Most teams keep the playbook in a founder's head instead.
Why do AI and humans fail without a pin?
Models are fluent in "typical SaaS MSA." They are not fluent in your insurance, runway, or last board conversation about non-solicit. Humans have the same bug at 11pm: they remember last quarter's deal and call it policy.
Without a pin, "liability looks fine" means "I have seen a cap before," two reviewers mark opposite outcomes on the same Net 60, and AI summarizes tone instead of measuring deviations. With a pin, a finding can say: your standard is X; this draft does Y; cite clause. That is the bar you should already demand from AI contract review with citations. Citations without a playbook still help you find clauses. Citations plus a playbook tell you whether to care.
What belongs in a startup pin?
Pin the handful of positions that repeat. Do not pin a 90-page playbook you will never update.
| Area | Example pin (illustrative, not advice) | Deviation to flag |
|---|---|---|
| Liability | Mutual cap ≈ 12 months fees; consequential damages excluded | Uncapped; one-sided; carve-out laundry list |
| Payment | Default Net 30; Net 60 only as a named order-form exception | Silent Net 60 in the MSA body |
| Term / exit | Auto-renew OK if notice ≥ 60 days | 30-day notice + board cycle |
| IP | Preexisting stays put; deliverables ownership explicit | "Vendor owns all improvements" |
| Data | DPA required if personal data; breach notice numbered | "Comply with law" as the whole privacy section |
| Confidentiality | Mutual; residuals narrow or none on outbound pitches | One-way + broad residuals |
| Indemnity | Mutual on IP/data risks each side controls | "Any and all claims related to the Agreement" |
Write each pin as position + fallback + escalate (prefer mutual 12-month fees cap; escalate uncapped or one-sided). Deep dives live elsewhere (liability cap for startups); the pin is the short form. Make implicit pins explicit: How to review an MSA without a lawyer.
How do you pin standards so review actually uses them?
A pin that nobody opens is a blog post.
- One canonical playbook file: same discipline as contract version control. Not
playbook_v2_REAL. - Clause-shaped entries: searchable names: liability cap, payment, auto-renew, DPA, residuals.
- Attach the pin to the deal, the standard travels with the
.docx, not in a side Slack. - Require deviation reports: every material mismatch is accept / counter / escalate, with an owner.
- Cite both directions, the finding cites the contract and the pin.
- Re-pin after you learn, if you accepted Net 45 six times, update the pin.
The counterparty should receive tracked changes, not your internal playbook.
How should AI use a pinned standard?
Treat the model as a deviation detector, not an approver.
Good: "Pinned standard: payment Net 30 from invoice date. Draft order form § 4: Net 60 from acceptance. Flag: 30 extra days plus a trigger you do not control."
Bad: "Payment terms appear customary for enterprise."
No pin match → say not found, do not invent a "usual MSA." Every flag cites the draft clause and the pin entry. Humans verify material flags before comments go outbound. AI does not approve signature; it queues decisions. That is how pinning stays honest when the model is having a confident day.
What belongs on a pinning checklist?
- Written positions for liability, payment, term/exit, IP, data, confidentiality, indemnity
- Each position has fallback + escalate, not only a dream clause
- Playbook has an owner and a date
- Pin is attached to the review workspace, not buried in Drive
- First-pass review (human or AI) reports deviations with citations
- Accept / counter / escalate recorded against the version
- Counterparty still gets a normal Word redline
- After exceptions repeat, the pin is updated on purpose
Pinning is not auto-signature, and it is not a way to skip counsel on uncapped or regulated risk. It is a yardstick. Yardsticks do not sign.
About this page
Who. Written by version90 staff at Latent Ape LLC, the company that builds version90, working with AI tools. We build contract software and run our own contracts through it; we are not a law firm, and nothing here is legal advice.
How. Each piece starts from the review workflow version90 is built around. AI drafts and structures the text; staff edit, fact-check, and rewrite it before it is published, and we update the date shown above whenever the substance changes.
Why. The library exists to give founders and ops teams a shared standard for reviewing contracts without a legal department. If you spot an error, email [email protected] and we will fix the page.