DWG PN-102 / CONTRACT REDLINING

Redline every contract against your own playbook.

Pantheon classifies each incoming contract, redlines it against your vetted positions, routes it to the responsible owner, and returns a tracked document, declining cleanly on the types you have not covered.

Become a design partner See how it works
SHEET 02 / THE PROBLEM

First-pass review does not scale by hiring.

When every contract gets a manual first pass, your best lawyers spend their day on low-risk boilerplate.

EXISTING CONDITION

Today, without Pantheon

  • Every contract waits for a manual first pass
  • Positions drift between reviewers
  • Senior time spent on low-risk boilerplate
  • No record of why a change was made
PROPOSED WORKS

With Pantheon redlining

  • Playbook positions applied consistently
  • A tracked document back in minutes
  • People review the exceptions, not the boilerplate
  • Every change linked to a vetted position
SHEET 03 / METHOD OF WORKS

What runs on every incoming contract.

Four steps, every contract. The playbook-coverage gate is the hold point: a type you have not covered is never guessed at.

PANTHEON · CONTRACT REDLINING DWG NO. PN-102 SCALE: NONE REV 03
01 Contract received

Lands in the shared inbox or the repository.

trigger: mailbox · sharepoint
02 Classify the type

Pantheon classifies the contract and checks it is a type you cover.

types: nda · msa · dpa
03 Gate: playbook coverage

An uncovered type is declined cleanly and handed to a lawyer.

Hold point gate_key: playbook-coverage
04 Redline and route

Redlined against your playbook, routed to the owner as a tracked file.

docx: tracked changes

NOTE: NO PLAYBOOK, NO REDLINE. UNCOVERED TYPES GO TO A LAWYER.

APPROVED
GENERAL COUNSEL
ProjectPANTHEON · CONTRACT REDLINING
Drawn byLAWYER
Checked byCOMPLIANCE
Approved byGENERAL COUNSEL
Date2026-07-11
Rev03
Sheet3 OF 8
WORKS WHERE YOUR TEAM ALREADY WORKS
Outlook Microsoft Teams Slack SharePoint Word Jira DocuSign Ironclad CourtListener
SHEET 04 / DETAILS

Your playbook does the redlining.

The output reflects your standards, not a generic model's opinion.

DETAIL A / TRACKED OUTPUT

A tracked document back in minutes

Pantheon does the first pass and routes a tracked-changes document to the owner: attributed, auditable, ready to send or to review.

  • Playbook positions applied consistently
  • Every change linked to a vetted position
  • The owner reviews the exceptions, not the boilerplate
Redline vs playbook audited
CL 8.2 / LIMITATION OF LIABILITY

Supplier's aggregate liability shall be unlimited capped at the fees paid in the preceding twelve months.

// linked: position liability-cap · playbook v3
CL 4.1 / CONFIDENTIALITY TERM

Obligations survive in perpetuity for five (5) years after termination.

// linked: position conf-term · playbook v3
// every change linked to a vetted position
playbook=v3DWG NO. PN-102
DETAIL B / COVERAGE GATE

Declines cleanly on types you have not covered

Pantheon handles the types you configure: NDAs, MSAs, DPAs and more. Anything outside your playbook is never guessed at; the run holds and the contract is handed to a lawyer.

  • Coverage checked before any redline is drawn
  • Uncovered types held for a person, not pushed through
  • The hand-off is recorded like every other step
Playbook coverage hold point
NDAplaybook v3 · vetted positions covered
MSAplaybook v2 · vetted positions covered
DPAplaybook v1 · vetted positions covered
Anything elseno playbook on file to a lawyer
// declined cleanly · handed to a lawyer
gate_key: playbook-coverageDWG NO. PN-102
SHEET 05 / THE OUTCOME

Review that keeps its standards.

vetted playbooks live at launch

of changes linked to a position

to a first-pass redline, not days

uncovered contracts pushed through

SHEET 06 / RELATED SHEETS

More workflows your team can run.

PN-101 Intake

Legal Front Door

One entry point that classifies each request, holds sensitive ones for review, and dockets an SLA.

Open sheet → PN-103 Approvals

Approval and signature routing

Send for review or signature, in series or parallel, from the inbox.

Open sheet → PN-104 Reporting

Obligations and digests

Extract key dates into Jira and send weekly compliance digests.

Open sheet →
SHEET 07 / RFI REGISTER

What your team will want to know.

RFI-01What contract types can it handle?
The types you configure: NDAs, MSAs, DPAs and more. Pantheon declines cleanly on anything outside your playbook rather than guessing.
RFI-02Whose positions does it use?
Yours. Redlines are driven by your vetted playbook, so the output reflects your standards, not a generic model's opinion.
RFI-03Does a lawyer still review the result?
Yes, by design. Pantheon does the first pass and routes a tracked document to the owner, who reviews the exceptions rather than the boilerplate.
RFI-04What does the output look like?
A tracked-changes document, attributed and auditable, ready to send or to review, with every change tied to a playbook position.
SHEET 08 / ISSUE FOR APPROVAL

Give every contract a consistent first pass.

Join a small cohort of legal teams shaping Pantheon before general availability.

Become a design partner

TRACKED CHANGES · LINKED TO POSITIONS · EVERY RUN RECORDED