The LPM Project Charter is the foundational document for any Legal Operations initiative. It defines the scope, objectives, stakeholders, timeline, and success criteria before work begins. No Legal Ops project should proceed past the planning phase without an approved charter.
## The Charter Template
### 1. Project Overview
<table header-row="true">
<tr>
<td>Field</td>
<td>Description</td>
</tr>
<tr>
<td>**Project Name**</td>
<td>\[Descriptive name, e.g., “CLM Implementation — Phase 1”\]</td>
</tr>
<tr>
<td>**Project Sponsor**</td>
<td>\[Name and title of the executive sponsor, typically GC or CLO\]</td>
</tr>
<tr>
<td>**Project Lead**</td>
<td>\[Name and title of the Legal Ops lead responsible for delivery\]</td>
</tr>
<tr>
<td>**Date Initiated**</td>
<td>\[DD/MM/YYYY\]</td>
</tr>
<tr>
<td>**Target Completion**</td>
<td>\[DD/MM/YYYY\]</td>
</tr>
<tr>
<td>**Version**</td>
<td>\[Charter version number\]</td>
</tr>
</table>
### 2. Problem Statement
*In 2-3 sentences, describe the specific business problem this project addresses. Use quantified data where possible.*
**Template:** “The \[department/function\] currently \[describe current state with data\]. This results in \[quantified impact: cost, time, risk\]. This project will \[describe the change\] to achieve \[quantified target outcome\].”
**Example:** “The legal department currently processes 1,200 contracts per year through a manual, email-based workflow with an average cycle time of 34 business days. This results in approximately \$1.8M in delayed revenue recognition annually. This project will implement a CLM platform with digital playbooks to reduce average cycle time to 18 business days.”
### 3. Objectives and Success Criteria
<table header-row="true">
<tr>
<td>Objective</td>
<td>Success Metric</td>
<td>Target</td>
<td>Measurement Method</td>
</tr>
<tr>
<td>\[Objective 1\]</td>
<td>\[Specific, measurable metric\]</td>
<td>\[Quantified target\]</td>
<td>\[How it will be measured\]</td>
</tr>
<tr>
<td>\[Objective 2\]</td>
<td>\[Specific, measurable metric\]</td>
<td>\[Quantified target\]</td>
<td>\[How it will be measured\]</td>
</tr>
<tr>
<td>\[Objective 3\]</td>
<td>\[Specific, measurable metric\]</td>
<td>\[Quantified target\]</td>
<td>\[How it will be measured\]</td>
</tr>
</table>
### 4. Scope
**In Scope:**
- \[Specific deliverable or work stream 1\]
- \[Specific deliverable or work stream 2\]
- \[Specific deliverable or work stream 3\]
**Out of Scope:**
- \[Explicitly excluded item 1 — with rationale\]
- \[Explicitly excluded item 2 — with rationale\]
**Scope Change Process:** Any change to the defined scope requires written approval from the Project Sponsor. Scope changes will be assessed for impact on timeline, budget, and resource requirements before approval.
### 5. Stakeholders
<table header-row="true">
<tr>
<td>Stakeholder</td>
<td>Role</td>
<td>Responsibility</td>
<td>Time Commitment</td>
</tr>
<tr>
<td>\[Name\]</td>
<td>Project Sponsor</td>
<td>Strategic direction, budget approval, escalation resolution</td>
<td>2 hrs/month</td>
</tr>
<tr>
<td>\[Name\]</td>
<td>Project Lead</td>
<td>Day-to-day management, delivery accountability</td>
<td>\[X\] hrs/week</td>
</tr>
<tr>
<td>\[Name\]</td>
<td>Business SME</td>
<td>Requirements input, UAT, adoption champion</td>
<td>\[X\] hrs/week</td>
</tr>
<tr>
<td>\[Name\]</td>
<td>IT/Technology</td>
<td>Integration, security review, infrastructure</td>
<td>\[X\] hrs/week</td>
</tr>
<tr>
<td>\[Name\]</td>
<td>Vendor PM</td>
<td>Platform configuration, training, support</td>
<td>Per SOW</td>
</tr>
</table>
### 6. Timeline and Milestones
<table header-row="true">
<tr>
<td>Phase</td>
<td>Milestone</td>
<td>Target Date</td>
<td>Dependencies</td>
</tr>
<tr>
<td>**Discovery**</td>
<td>Requirements document approved</td>
<td>\[Date\]</td>
<td>Stakeholder interviews complete</td>
</tr>
<tr>
<td>**Design**</td>
<td>Process maps and system design approved</td>
<td>\[Date\]</td>
<td>Requirements approval</td>
</tr>
<tr>
<td>**Build**</td>
<td>System configured and integration tested</td>
<td>\[Date\]</td>
<td>Design approval, IT resources available</td>
</tr>
<tr>
<td>**Test**</td>
<td>UAT complete, issues resolved</td>
<td>\[Date\]</td>
<td>Build complete</td>
</tr>
<tr>
<td>**Launch**</td>
<td>Go-live with pilot group</td>
<td>\[Date\]</td>
<td>UAT sign-off</td>
</tr>
<tr>
<td>**Stabilise**</td>
<td>Full rollout, training complete</td>
<td>\[Date\]</td>
<td>Pilot success confirmed</td>
</tr>
</table>
### 7. Budget
<table header-row="true">
<tr>
<td>Category</td>
<td>Estimated Cost</td>
<td>Approval Status</td>
</tr>
<tr>
<td>Technology licensing (Year 1)</td>
<td>\$\[Amount\]</td>
<td>\[Approved/Pending\]</td>
</tr>
<tr>
<td>Implementation services</td>
<td>\$\[Amount\]</td>
<td>\[Approved/Pending\]</td>
</tr>
<tr>
<td>Internal resource allocation</td>
<td>\$\[Amount / FTE equivalent\]</td>
<td>\[Approved/Pending\]</td>
</tr>
<tr>
<td>Training and change management</td>
<td>\$\[Amount\]</td>
<td>\[Approved/Pending\]</td>
</tr>
<tr>
<td>Contingency (10-15%)</td>
<td>$`\[Amount]                  | \[Approved/Pending] |
| **Total**                      | **`$\[Amount\]\*\*</td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
</tr>
</table>
```plain text
          |
```
### 8. Risks and Mitigations
<table header-row="true">
<tr>
<td>Risk</td>
<td>Probability</td>
<td>Impact</td>
<td>Mitigation</td>
</tr>
<tr>
<td>\[Risk 1, e.g., “Low user adoption”\]</td>
<td>\[H/M/L\]</td>
<td>\[H/M/L\]</td>
<td>\[Specific mitigation, e.g., “Dedicated change management workstream with WIIFM communications”\]</td>
</tr>
<tr>
<td>\[Risk 2, e.g., “Data quality insufficient”\]</td>
<td>\[H/M/L\]</td>
<td>\[H/M/L\]</td>
<td>\[Specific mitigation\]</td>
</tr>
<tr>
<td>\[Risk 3, e.g., “Vendor delivery delay”\]</td>
<td>\[H/M/L\]</td>
<td>\[H/M/L\]</td>
<td>\[Specific mitigation\]</td>
</tr>
</table>
### 9. Governance
**Reporting cadence:** \[Weekly/Fortnightly\] status reports to Project Sponsor; \[Monthly\] steering committee updates.
**Escalation path:** Project Lead → Project Sponsor → \[Executive Committee / Board subcommittee, if applicable\].
**Decision authority:** Day-to-day decisions: Project Lead. Budget changes \>\$\[threshold\]: Project Sponsor. Scope changes: Project Sponsor with steering committee notification.
### 10. Approval
<table header-row="true">
<tr>
<td>Role</td>
<td>Name</td>
<td>Signature</td>
<td>Date</td>
</tr>
<tr>
<td>Project Sponsor</td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</table>
```plain text
      |      |           |      |
```
```plain text
|
```
\| Project Lead \|<br>\|<br>\|<br>\|<br>\| IT Approver \|<br>\|<br>\|<br>\|<br>\| Finance Approver \|<br>\|<br>\|<br>\|
The charter serves as insurance for your project. It prevents scope drift, maintains stakeholder alignment, and establishes clear success criteria from the start. The 2-3 hours invested in completing the charter saves weeks of rework and misalignment downstream.