← All resources

A project charter is the document that authorizes a project and gives the project manager the authority to spend the agency's time and money on it. It is the first deliverable of the Initiating phase — sign it before planning work begins, not after.

Keep it short. A charter is one to three pages. If a section runs longer than a paragraph or two, that detail belongs in the project plan, not here.

Replace every italic prompt with your project's information, then delete the prompt. A fully worked example follows the blank template.

Blank Template
Project Charter

1 Project identification

Project namePlain-language name. "ESO ePCR Transition," not "Project Phoenix."
Agency / department
Charter date
Charter version
Prepared by

2 Sponsor & project manager

RoleNameAuthority
Project sponsorFunds the project and owns the business decision. Usually a chief or director.
Project managerRuns the project day to day. State the spending and decision authority granted — e.g., "may approve changes under $5,000 and adjust the internal schedule within the approved go-live date."
Medical directorName if the project touches clinical care, protocols, or documentation.

3 Purpose & business case

Two or three sentences. What problem does this project solve, and what happens if the agency does nothing? Tie it to something concrete — a compliance deadline, an expiring contract, a quality gap, a grant requirement.

4 Objectives

Three to five objectives, each one measurable. "Reduce chart completion time" is a wish; "reduce median chart completion time from 14 to 8 minutes by go-live + 90 days" is an objective.

5 Scope

In scope

What this project will deliver.

Out of scope

What it explicitly will not, so no one assumes otherwise.

6 Key deliverables

The tangible things the project produces.

7 Success criteria

How the agency will know the project succeeded, measured at a stated point in time. These should trace directly back to Section 4.

8 High-level milestones

MilestoneTarget date
Project kickoff
e.g., Requirements approved
e.g., Vendor contract signed
e.g., Test environment validated
Go-live
Project close

9 Budget & resources

ItemEstimate
Vendor / software cost
Internal staff time (backfill, overtime)
Training & travel
Contingency
Total

Name the funding source — operating budget, grant, or capital. If grant-funded, note the grant period and any reporting obligations.

10 Key stakeholders

Stakeholder / groupInterest in the project
Field crews
Dispatch
QA / quality
Billing
State EMS office

11 Assumptions

What you are taking as true. If an assumption proves false, the plan changes.

12 Constraints

Fixed limits the project must work within — a hard compliance date, a frozen budget, a staffing cap, a required vendor.

13 High-level risks

RiskPotential impactInitial response

This is a first pass, not a risk register. The full register is built during planning.

14 Approval

By signing, the sponsor authorizes the project and the project manager's authority as described above.

RoleNameSignatureDate
Project sponsor
Project manager
Medical director (if applicable)

Worked Example
POCUS implementation

The same charter, filled in for a Point-of-Care Ultrasound (POCUS) implementation — the same project used in the Strada EMS RACI Matrix template, so the two tools line up.

1 Project identification

Project nameField POCUS Implementation
Agency / departmentRiverbend County EMS — Clinical Services
Charter dateMarch 3, 2026
Charter version1.0
Prepared byClinical Project Lead

2 Sponsor & project manager

RoleNameAuthority
Project sponsorDeputy Chief of Clinical ServicesOwns the budget and the go / no-go decision.
Project managerClinical Project LeadMay approve changes under $5,000 and adjust the internal schedule within the approved go-live date. Changes to scope, budget, or go-live date require sponsor approval.
Medical directorAgency Medical DirectorOwns the POCUS clinical protocol, scope of practice, and credentialing standard.

3 Purpose & business case

Riverbend County EMS has no prehospital ultrasound capability. Neighboring systems use POCUS to improve triage of trauma and undifferentiated hypotension, and the agency's medical director has approved a limited POCUS scope of practice. Without a structured implementation, equipment risks being purchased and underused, and uncredentialed use creates clinical and liability exposure.

4 Objectives

  1. Credential 100% of full-time paramedics in the approved POCUS scope by go-live + 120 days.
  2. Document a POCUS exam on at least 60% of eligible patient encounters within two quarters of go-live.
  3. Keep QA image-review turnaround under 7 days, beginning at go-live.

5 Scope

In scope

Device selection and purchase; protocol and documentation build in the ePCR; initial and recurring crew training; a QA image-review workflow; medical-director credentialing.

Out of scope

Ultrasound use by EMT-level providers; integration of images into the hospital PACS; billing for POCUS exams.

6 Key deliverables

  • Approved POCUS clinical protocol and credentialing standard
  • Purchased and deployed ultrasound devices
  • ePCR documentation fields and report template
  • Crew training curriculum and completion records
  • QA image-review workflow

7 Success criteria

  • All Section 4 objectives met and reported to the steering committee at go-live + 120 days.
  • No uncredentialed POCUS use recorded in the QA review.

8 High-level milestones

MilestoneTarget date
Project kickoffMarch 2026
Protocol & credentialing standard approvedApril 2026
Devices selected and orderedMay 2026
ePCR documentation build completeJune 2026
Crew training completeAugust 2026
Go-liveSeptember 2026
Project closeJanuary 2027

9 Budget & resources

ItemEstimate
Ultrasound devices (4 units)$48,000
Crew training (instructor + backfill)$22,000
ePCR configuration$4,000
Contingency (10%)$7,400
Total$81,400

Funded from the FY26 capital budget. Not grant-funded.

10 Key stakeholders

Stakeholder / groupInterest in the project
Field crewsTrained and credentialed; the primary users
Medical directorOwns the clinical protocol and credentialing
QA / qualityRuns the image-review workflow
Receiving hospitalsAffected by the handoff of prehospital findings
FinanceOwns the capital expenditure

11 Assumptions

  • The approved scope of practice will not expand during the project.
  • The devices selected are compatible with the agency's current ePCR.
  • Training can be delivered during scheduled in-service time without added overtime.

12 Constraints

  • Total cost may not exceed the $81,400 FY26 capital allocation.
  • Go-live must fall within the fiscal year ending June 2027.
  • Training cannot pull more than two crews out of service at once.

13 High-level risks

RiskPotential impactInitial response
Slow crew credentialingGo-live slips; devices sit unusedBuild recurring training dates into the schedule from kickoff
ePCR cannot support image documentationRework; QA workflow gapConfirm with the ePCR vendor before devices are ordered
Inconsistent image qualityClinical risk; QA backlogMedical-director-led QA review from the first credentialed shift

14 Approval

RoleNameSignatureDate
Project sponsorDeputy Chief of Clinical Services
Project managerClinical Project Lead
Medical directorAgency Medical Director

Strada EMS Consulting — EMS-native consulting for technology transitions, clinical quality, and project management. This template is free to use and adapt. For a charter built around your agency's project, start a conversation.

Beyond the Template

A template gets you started. A plan gets you to go-live.

If you'd rather have the charter — and the project behind it — built around your agency's vendor, timeline, and org chart, that's a conversation worth having.