Skip to main content
Contract review is the request Legal teams most want structure around and most often end up doing over Slack DMs. The fix is a five-field form and a triage rule, not a workflow engine.
Prerequisites: a private Legal workspace with a channel, and the Day one track finished.

​
What good looks like

1

Ask five questions, and make four of them required

Attach the document to the ticket rather than linking to a drive folder. The attachment is what makes the ticket self-contained six months later.
Learn more about forms and attachments
2

Let the standard cases skip the lawyer

An NDA on your own template, under your value threshold, with no changes requested, does not need a lawyer’s attention. Write that rule down and let the desk act on it.A workflow on Form Submitted with a condition on contract type and whose paper can set the priority low, apply a “standard terms” tag, and post to the triage channel with a note saying why it was classified that way. Someone still looks, but they look at a pile of five instead of a pile of forty.
Learn more about workflow triggers and actions
3

Triage on risk and deadline, not arrival order

Three views run the desk:
  • Due this week, not resolved, sorted by deadline. The working list.
  • Their paper, not resolved. These take three times as long, so they need earlier attention.
  • High value, above your threshold. Nothing here should be a surprise to the person who owns the relationship.
Learn more about views
4

Make the review itself a checklist

A task template per contract type turns a review from “someone is working on it” into visible progress the requester can see without asking.For an MSA on the counterparty’s paper:
  1. Confirm scope and term against the order form
  2. Check liability cap and indemnities against the playbook
  3. Check data processing terms, and route to Privacy if personal data is involved
  4. Send redlines to the counterparty
  5. Record the negotiated position for reuse
  6. Route for signature
Step 5 is the one teams skip and the one that pays off. A recorded position becomes knowledge, which means the same question does not need a lawyer next quarter.
Learn more in task templates
5

Approve the deviations, not the contracts

Do not put an approval on every contract. Put it on the exceptions your playbook names: liability above the cap, non-standard indemnity, unusual term length, anything above your value threshold.Use one approval template with skip conditions on the fields, so a standard NDA passes straight through and a deviation collects the sign-off it needs.
Learn more in approval flows
6

Send for signature from the ticket

Signature is the step that most often falls out of the process, because it moves to a different tool and the ticket goes quiet.There is no native e-signature integration, but a Foundry action can send an envelope and record the result on the ticket. The DocuSign OAuth walkthrough covers the connection setup.Build this last. A signature action on a desk with no intake automates the wrong end of the problem.

​
Where teams get this wrong

Every request then implicitly means “urgent”, and the desk cannot be prioritized.
It is the largest single predictor of effort and it costs one dropdown.
If a standard NDA takes a lawyer’s afternoon, the desk will not survive its second busy quarter.
Six months later nobody can reconstruct which version was signed.
Tempting, because it is the fun part, and it changes nothing about the backlog.

​
Next

Policy and compliance questions

The other half of Legal’s volume.

Approval flows

Skip conditions and rounds in detail.
Last modified on September 17, 2026