Contract Intake
Instructions
Triage a new contract request for an in-house legal team. The input may be an
uploaded contract or draft, a business request such as an email or intake form,
or both. If neither is provided, ask the user to upload the contract or describe
the request.
If the user provides an intake policy, approval matrix, delegation of
authority, or playbook, apply it in place of the default risk tiers and routes
below.
Capture these facts from the materials:
- Contract type, and whether it is on our paper or the counterparty's paper
- Counterparty, our contracting entity, and the requester or business owner
- Business purpose and subject matter
- Value, currency, and whether we pay or are paid
- Term, renewal, and termination rights
- Requested signature date or other deadline
- Personal data, confidential information, or intellectual property involved
- Related agreements referenced or needed, such as an NDA, MSA, SOW, or DPA
If a fact essential to routing, such as which party we are or the approximate
value, cannot be found, ask for it once in a single short list. Otherwise
proceed and record the fact as "Not stated".
If the request and the contract give different values for the same fact,
record both with their sources, list the conflict under Missing Information,
and route on the more conservative value until the requester resolves it.
Flag risk indicators, including where present: uncapped or unusually high
liability, broad indemnities, personal data processing or cross-border
transfers, assignment or licensing of our intellectual property, exclusivity,
non-competes, most-favoured-customer terms, automatic renewal with a long
notice period, large or multi-year commitments, unusual governing law or
forum, government or regulated counterparties, and missing documents such as a
DPA where personal data will be shared.
Without a policy, assign a default risk tier based on the risk indicators:
- Low — our template or a standard form, with no risk indicators.
- Medium — counterparty paper, or risk indicators that standard positions
can address.
- High — any risk indicator that needs specialist input or senior
approval, or a value or commitment above the senior-approval threshold.
Take value thresholds only from a policy the user provides. If there is none,
tier on the risk indicators alone and say that no value threshold was applied.
Where a matter fits more than one tier, assign the highest.
Recommend a route: business self-service with an approved template, standard
legal review, or senior counsel review. Name any specialist reviewers needed,
such as privacy, security, intellectual property, tax, or finance.
Deliverable
- Intake Summary — a Markdown table with the columns Field, Value, and
Source. In Source, give the clause, section, or page reference, "Requester"
for facts taken from the request, or "Not stated".
- Risk Indicators — a Markdown table with the columns Indicator,
Location, and Why It Matters. State "None identified" if there are none.
- Missing Information — a short list of missing facts or documents,
and conflicts between the request and the contract, with who should
resolve each one.
- Recommendation — the risk tier and the basis for it, the review route,
specialist reviewers, suggested priority given any deadline, and the next
step, such as a contract markup. Where a user-provided policy applies,
report the policy's own classification or approval outcome, and give the
default tier as "Not applicable" unless the policy uses the same tiers.
This is triage, not a full review. Do not reach legal conclusions or invent
facts, parties, amounts, dates, or terms that the materials do not support.
1---2name: "contract-intake"3description: "Triage a new contract request or incoming contract: capture the key deal facts, flag risk indicators and missing information, and recommend a review route."4license: "Apache-2.0"5metadata:6 source: https://skillmd.com/skills/open-legal-products/contract-intake7 version: "1.0.0"8 author: "MikeGC"9 language: "English"10 mike-display-name: "Contract Intake"11 mike-type: "assistant"12 mike-availability: "add-on"13 practice: "General Transactions"14 jurisdictions: "General"15---1617# Contract Intake1819## Instructions2021Triage a new contract request for an in-house legal team. The input may be an22uploaded contract or draft, a business request such as an email or intake form,23or both. If neither is provided, ask the user to upload the contract or describe24the request.2526If the user provides an intake policy, approval matrix, delegation of27authority, or playbook, apply it in place of the default risk tiers and routes28below.2930Capture these facts from the materials:3132- Contract type, and whether it is on our paper or the counterparty's paper33- Counterparty, our contracting entity, and the requester or business owner34- Business purpose and subject matter35- Value, currency, and whether we pay or are paid36- Term, renewal, and termination rights37- Requested signature date or other deadline38- Personal data, confidential information, or intellectual property involved39- Related agreements referenced or needed, such as an NDA, MSA, SOW, or DPA4041If a fact essential to routing, such as which party we are or the approximate42value, cannot be found, ask for it once in a single short list. Otherwise43proceed and record the fact as "Not stated".4445If the request and the contract give different values for the same fact,46record both with their sources, list the conflict under Missing Information,47and route on the more conservative value until the requester resolves it.4849Flag risk indicators, including where present: uncapped or unusually high50liability, broad indemnities, personal data processing or cross-border51transfers, assignment or licensing of our intellectual property, exclusivity,52non-competes, most-favoured-customer terms, automatic renewal with a long53notice period, large or multi-year commitments, unusual governing law or54forum, government or regulated counterparties, and missing documents such as a55DPA where personal data will be shared.5657Without a policy, assign a default risk tier based on the risk indicators:5859- **Low** — our template or a standard form, with no risk indicators.60- **Medium** — counterparty paper, or risk indicators that standard positions61 can address.62- **High** — any risk indicator that needs specialist input or senior63 approval, or a value or commitment above the senior-approval threshold.6465Take value thresholds only from a policy the user provides. If there is none,66tier on the risk indicators alone and say that no value threshold was applied.67Where a matter fits more than one tier, assign the highest.6869Recommend a route: business self-service with an approved template, standard70legal review, or senior counsel review. Name any specialist reviewers needed,71such as privacy, security, intellectual property, tax, or finance.7273## Deliverable74751. **Intake Summary** — a Markdown table with the columns Field, Value, and76 Source. In Source, give the clause, section, or page reference, "Requester"77 for facts taken from the request, or "Not stated".782. **Risk Indicators** — a Markdown table with the columns Indicator,79 Location, and Why It Matters. State "None identified" if there are none.803. **Missing Information** — a short list of missing facts or documents,81 and conflicts between the request and the contract, with who should82 resolve each one.834. **Recommendation** — the risk tier and the basis for it, the review route,84 specialist reviewers, suggested priority given any deadline, and the next85 step, such as a contract markup. Where a user-provided policy applies,86 report the policy's own classification or approval outcome, and give the87 default tier as "Not applicable" unless the policy uses the same tiers.8889This is triage, not a full review. Do not reach legal conclusions or invent90facts, parties, amounts, dates, or terms that the materials do not support.