AI for In-House Counsel

# CONTRACT TRIAGE PROCESS BUILDER PROMPT ## ROLE You are an experienced in-house legal operations consultant and process designer. Your task is to design a complete, self-serve triage process that lets a client or business team handle low-value, low-risk matters themselves, while routing anything above an agreed risk threshold to a lawyer. Be specific and operational. Every output should be something that could be published to an intranet or handed to a business team this week — not a description of what a good process would look like in general. --- ## INPUT **Contract or matter type:** [INSERT TYPE — e.g. NDAs, vendor agreements, low-value purchase orders] **Current volume:** [INSERT — e.g. 40 requests per month] **Who currently handles it:** [INSERT — e.g. in-house counsel, paralegal] **Known risk factors:** [INSERT — e.g. liability cap, data processing terms, indemnities, termination rights, governing law] **Business team who would run this themselves:** [INSERT — e.g. procurement, sales operations, HR] --- ## OUTPUT FORMAT ### 1. Risk Threshold Definition Define the specific, objective criteria that separate "self-serve" matters from "escalate to counsel" matters. Express each as a yes/no or numeric test, for example: * Contract value below £[X] * No deviation from the approved clause set * Term under [Y] months * Counterparty is not on the restricted/high-risk list List every threshold needed to fully resolve this matter type without ambiguity. ### 2. Decision Tree Lay out the full triage logic as a step-by-step decision tree, starting from intake and ending in one of two outcomes: **Approved for Self-Serve** or **Escalate to Counsel**. Include every branch and edge case implied by the risk factors above. Present this as a numbered sequence of questions a non-lawyer could follow without help. ### 3. Self-Serve Intranet Page Copy Draft the actual page copy for an intranet page that walks a non-lawyer through the decision tree. Include: * A plain-language explanation of what they can and cannot approve themselves * The intake form fields needed to capture everything the triage logic requires * What happens automatically when a matter is escalated, and what the business team should expect next ### 4. Escalation Triggers & Audit Trail List the specific triggers that force escalation regardless of the decision tree's outcome (for example: counterparty objects to standard terms, unusual governing law, a relevant regulatory change). Define what record should be kept of every self-serve decision, so the process can be audited later. ### 5. Review Cadence Recommend how often the risk thresholds should be reviewed, who should own that review, and what data — volume, escalation rate, error rate — should trigger an earlier review than scheduled. ### 6. Rollout Plan Provide a practical two-to-three-week rollout plan: who to brief first, how to pilot with a small volume before full rollout, and how to measure whether the process is actually working once live. --- ## ADDITIONAL INSTRUCTION Be specific and operational, not theoretical. Write the decision tree and the intranet page copy so they are ready to use immediately, with no further editing required to make them sound human and clear to a non-lawyer. Finally, take the self-serve page from Section 3 and output it again as a complete, ready-to-upload HTML page — full markup with inline CSS, no external dependencies — so it can be published directly to a website or intranet without any further development work.