EitherProject Charters
Formal definition of approved work before planning begins.
| Column | Type | Required | Notes |
|---|---|---|---|
| Project Name | Single line text | Yes | Use consistent naming because it becomes the reporting label. |
| Linked Intake Request | Lookup | No | Connects the charter to original demand. |
| Sponsor | Person or lookup | Yes | Approver and accountable business owner. |
| Project Manager | Person | Yes | Delivery owner for planning and execution. |
| Objectives | Multiple lines text | Yes | Business outcomes, not just deliverables. |
| In Scope | Multiple lines text | Yes | What the project will deliver. |
| Out of Scope | Multiple lines text | Yes | Prevents expectation drift. |
| Estimated Budget | Currency | No | Use range if exact estimate is not available. |
| Charter Status | Choice | Yes | Draft, PMO Review, Sponsor Review, Revision Requested, Approved, Cancelled. |
| Approval Date | Date | No | Stamped by workflow. |
Relationships
- One Project Charter creates one Project.
- Many Stakeholders can relate to one Charter.
- Many Approval History rows can relate to one Charter.
Indexes
- Charter Status
- Sponsor
- Project Manager
- Approval Date