Project Management Artifacts

PM Work Samples

How I govern programs at Tier-1 scale: charters, RAID logs, dependency maps, timelines, ownership models, and the reports executives actually read.

Representative artifacts. Details are anonymized and adapted to protect private business information.

School Operations Rebuild and Digital Workflow Implementation

A private education organization needed to rebuild its internal operating structure after years of informal processes, inconsistent documentation, manual tracking, unclear ownership, and gaps in staff alignment. The project focused on clarifying the operating model, documenting repeatable workflows, digitizing key administrative processes, improving reporting accuracy, and preparing the team for stronger long term execution.

Role Project Manager and Strategic Operations Consultant Type Operations transformation and SOP implementation Methodology Hybrid Duration 16 weeks Budget Est. $35K Tools Notion, Trello, Google Workspace, RACI, RAID

Project Charter

A practical charter for aligning scope, outcomes, ownership, and delivery rhythm before implementation begins.

Project overview

The organization needed a clearer operating structure to support staff alignment, parent facing consistency, administrative accuracy, and long term growth. The work included process discovery, SOP documentation, workflow redesign, staff enablement, and early stage digital system implementation.

Business case

Manual processes, undocumented workflows, inconsistent handoffs, and unclear ownership were creating avoidable errors, staff confusion, and weak reporting visibility. A structured operations rebuild would reduce dependency on memory, improve accountability, create repeatable standards, and support a stronger parent and staff experience.

Objective

Rebuild the school's internal operating structure by documenting core workflows, clarifying role ownership, improving administrative tracking, training staff on new standards, and preparing the organization for measurable digital workflow improvements.

In scope

Current state workflow review
Stakeholder interviews with leadership and staff
SOP development for daily operations
Staff reorientation and training
Performance tracking templates
Administrative workflow redesign
Digital system recommendations
Website and digital presence coordination
Handoff documentation

Out of scope

Full HR restructuring
Long term software subscription ownership
Payroll system implementation
Academic curriculum redesign
Ongoing school management after handoff

Success criteria

Leadership signs off on the revised operating structure
Core SOPs are documented and ready for staff use
Staff training attendance reaches at least 90%
Staff understand new workflows, expectations, and ownership paths
Administrative tracking becomes easier to review and maintain
Leadership has a clear handoff plan for continued implementation
Early digital workflow improvements are identified and prioritized

Key stakeholders

CEO / School Owner: Executive sponsor and final decision maker
School Administrator: Daily operations lead and process owner
Teaching Staff: Primary users of classroom and daily workflow standards
Project Manager: Delivery lead, documentation owner, training coordinator
Web / Design Contractor: Digital asset and website support
Parent facing Admin Support: Intake, communication, and records support

Constraints

School operations had to continue during implementation
Staff availability was limited around teaching schedules
Documentation had to be practical, not overly complex
Leadership needed visible progress without overwhelming the team
Budget had to stay lean and focused on high impact improvements

Assumptions

Leadership would remain available for key decisions
Staff would participate in training and feedback sessions
Existing processes could be improved without disrupting daily delivery
Digital improvements would be phased rather than launched all at once
Some manual workflows would remain temporarily during transition

High level milestones

Week 1: Scope alignment and stakeholder interviews
Weeks 2 to 3: Current state process review
Weeks 4 to 6: SOP drafting and workflow redesign
Weeks 7 to 8: Staff training materials and leadership review
Weeks 9 to 11: Training delivery and feedback collection
Weeks 12 to 14: Workflow refinement and digital system planning
Week 15: Handoff documentation
Week 16: Final leadership review and closeout

RAID Log

Risks, assumptions, issues, and dependencies tracked across the project lifecycle.

Reviewed weekly during project check ins. Items were escalated when they blocked timeline, ownership, training adoption, or leadership decisions.

R-001Monitoring

Staff adoption may drop if new SOPs feel too complex.

Category: People / Adoption Owner: Project Manager
Mitigation: Keep SOPs practical, use plain language training, collect feedback after each session, and revise documents based on staff use.

R-002Open

Leadership decisions may delay workflow approval.

Category: Governance Owner: CEO / Sponsor
Mitigation: Create a decision log, batch approvals into weekly review points, and separate must approve now from can refine later.

R-003Mitigating

Manual records may contain inconsistencies before digitization.

Category: Data / Records Owner: Administrator
Mitigation: Conduct a sample records review, identify common gaps, and create a clean up checklist before migration or digitization.

R-004Monitoring

Staff schedules may limit training attendance.

Category: Schedule Owner: School Administrator
Mitigation: Offer short training blocks, provide written recap materials, and capture attendance for follow up.

R-005Open

Scope may expand into unrelated school improvement requests.

Category: Scope Owner: Project Manager
Mitigation: Maintain a scope tracker, separate future improvements from current deliverables, and review new requests against the project objective.

A-001Validated

Leadership will provide timely feedback on SOP drafts.

Owner: CEO / Sponsor
Validation: Weekly review time has been agreed.

A-002Validated

Staff can attend at least one live training session.

Owner: School Administrator
Validation: Training windows mapped around teaching schedules.

A-003Validated

Current workflows can be improved without pausing operations.

Owner: Project Manager
Validation: Implementation will be phased around daily operations.

A-004Pending

Web and digital asset updates can run alongside internal work.

Owner: Web / Design Contractor
Validation: Contractor timeline still needs final confirmation.

A-005Validated

Existing Google Workspace tools are sufficient for early tracking.

Owner: Project Manager
Validation: No new paid software required for phase one.

I-001Open

Staff roles and responsibilities are not consistently documented.

Category: Ownership Owner: Project Manager
Next action: Draft role responsibility matrix and review with leadership.

I-002Mitigating

Parent inquiry and intake handoffs vary by who receives the request.

Category: Process Owner: Administrator
Next action: Standardize inquiry capture, response expectations, and handoff steps.

I-003Monitoring

Training materials are being created while SOPs are still being revised.

Category: Documentation Owner: Project Manager
Next action: Use version control and mark drafts clearly until leadership approval.

I-004Open

Attendance tracking is inconsistent across staff routines.

Category: Reporting Owner: School Administrator
Next action: Create a simple attendance and follow up tracker.

I-005Mitigating

Some staff are unclear on how changes affect their daily work.

Category: Adoption Owner: Project Manager
Next action: Add role specific examples to the training session.

D-001Open

CEO approval is needed before SOPs are finalized.

Owner: CEO / Sponsor Due: Week 6

D-002In Progress

Staff interview feedback is needed before workflow redesign completes.

Owner: Teaching Staff Due: Week 3

D-003Pending

Web contractor input is needed for digital presence updates.

Owner: Web / Design Contractor Due: Week 8

D-004In Progress

Records review must finish before digital tracking is finalized.

Owner: Administrator Due: Week 10

D-005Open

Training attendance must be captured before adoption is reported.

Owner: Project Manager Due: Week 12

Risk Register

A structured view of risk severity, likelihood, impact, mitigation, owner, and status.

Model: 5x5, Severity = Impact x Likelihood Critical: 20+ High: 15 to 19 Medium: 10 to 14 Low: below 10

ID	Risk	Category	Imp	Lik	Severity	Mitigation	Owner	Status
R-001	Staff adoption drops because new workflows feel too complicated.	People / Adoption	5	3	15 High	Keep SOPs short, practical, and role specific. Run live walkthroughs and collect feedback before finalizing.	Project Manager	Monitoring
R-002	Leadership approval delays SOP rollout.	Governance	4	4	16 High	Use a weekly decision log with clear approve, revise, or defer options.	CEO / Sponsor	Open
R-003	Existing records are too inconsistent for clean reporting.	Data / Records	4	3	12 Medium	Review a sample of records, identify missing fields, and create a clean up checklist before digitization.	Administrator	Mitigating
R-004	Staff training attendance falls below target.	Schedule	3	3	9 Low	Offer multiple short sessions, provide written recap materials, and track attendance.	School Administrator	Monitoring
R-005	Scope expands into broader school redesign beyond the agreed project.	Scope	4	4	16 High	Maintain a scope tracker and park future ideas in a phase two backlog.	Project Manager	Open
R-006	Digital tools are introduced faster than the team can absorb.	Change Management	4	3	12 Medium	Phase digital changes and only introduce tools tied to an immediate workflow need.	Project Manager	Monitoring
R-007	External contractor timeline delays website or digital asset updates.	Vendor	3	3	9 Low	Confirm contractor deliverables early and separate internal SOP work from external dependencies.	Web / Design Contractor	Open

Implementation Timeline: 16 Week Roadmap

A phased delivery plan showing discovery, design, training, launch, and handoff.

Phase

1. Discovery and alignment

2. Process mapping and requirements

3. SOP and workflow design

4. Leadership review and refinement

5. Staff training and adoption

6. Digital workflow planning

7. Handoff and closeout

Discovery Process mapping SOP design Leadership review Training Digital planning Handoff Milestone

Weeks 1 to 4

Sponsor alignment and objective confirmation
Stakeholder interview plan
Staff interviews and pain point review
Ownership gap and process mapping

Weeks 5 to 12

SOP templates and daily operations drafting
Intake and records workflow design
Leadership review and sign off
Training delivery and feedback

Weeks 13 to 16

Digital tracking recommendations
Web and automation coordination
Final SOP package and handoff docs
Lessons learned and closeout review

Executive Status Report: Week 10

A weekly status report for leadership review during implementation. Reporting period: Week 10 of 16, Staff Training and Adoption phase.

Overall

Amber

Schedule

On Track

Scope

At Risk

Quality

On Track

Adoption

Monitoring

Budget

On Track

Summary

The project remains on schedule, with the first staff training session completed and SOP revisions moving forward. Scope needs active management because new improvement requests are being raised during training discussions. These items are being captured in a phase two backlog so the core implementation can stay focused.

Accomplishments this week

Completed first live staff reorientation session
Captured training attendance and feedback
Reviewed daily operations SOP with staff
Identified three workflow steps needing clearer ownership
Updated intake and follow up workflow draft
Logged new phase two improvement requests
Confirmed leadership review for revised SOP package

Planned next week

Finalize revised SOP drafts for leadership review
Complete second staff training session
Review role responsibility matrix with administrator
Confirm web contractor timeline for digital asset updates
Draft handoff checklist for ongoing implementation
Prepare digital tracking recommendations

Risks and issues needing attention

Scope creep: Staff raised broader improvement ideas during training. Keep the current project focused and move future ideas to phase two.
Ownership gap: Parent inquiry follow up still needs one clear owner. Decision needed from leadership.
Adoption: Some staff need more role specific examples before full adoption.

Decisions needed

Confirm who owns parent inquiry follow up after initial intake.
Approve revised SOP format before final documentation.
Decide whether digital tracking is implemented now or treated as phase two.
Confirm whether web updates come before or after internal workflow closeout.

Progress indicators

Overall completion62%

SOP package75%

Leadership decisions closed5 of 8

Staff training sessions1 of 2

Open risks 4 Open issues 3 Phase two backlog 6

RACI: Ownership Map

A simple ownership model to make decisions, handoffs, and accountability visible.

Activity	PM	CEO / Sponsor	Administrator	Teaching Staff	Web Contractor
Define scope and success criteria	R	A	C	I
Conduct stakeholder interviews	A	C	I	C
Map current workflows	A	I	C	C
Draft SOPs	A	I	C	C
Approve SOPs	C	A	C	I
Deliver staff training	R	C	A	I
Track attendance and adoption	A	I	R	C
Coordinate website / digital assets	C	A	I		R
Prepare handoff documentation	A	C	C	I
Close project and log lessons	R	A	C	I

R Responsible A Accountable C Consulted I Informed

Clear ownership is the difference between work being discussed and work actually moving.

Workflow Snapshot: Parent Inquiry to Enrollment Follow Up

A workflow showing how a loose process becomes trackable and repeatable.

Inquiry received

Trigger: Parent submits inquiry via website, phone, email, referral, or walk in.

Owner: Admin Support

Output: Inquiry captured in the intake tracker.

Inquiry logged

Trigger: New inquiry is received.

Owner: Admin Support

Output: Name, contact, child age, program interest, source, and date logged.

Initial response sent

Trigger: Inquiry logged.

Owner: Admin Support

Output: Parent receives response with next step or tour info.

SLA: within 1 business day

Tour or follow up scheduled

Trigger: Parent expresses interest.

Owner: School Administrator

Output: Tour date, follow up owner, and notes recorded.

Leadership review

Trigger: Parent needs pricing, availability, or special consideration.

Owner: Administrator, consulted CEO

Output: Decision or guidance recorded.

Follow up completed

Trigger: Tour completed or parent has not responded.

Owner: Admin Support

Output: Follow up message sent and status updated.

SLA: within 2 business days

Enrollment decision logged

Trigger: Parent accepts, declines, or goes inactive.

Owner: School Administrator

Output: Final status recorded in tracker.

Handoff or closeout

Trigger: Enrollment confirmed or inquiry closed.

Owner: Administrator

Output: Student file started or inquiry closed with reason.

Required fieldsOwner assignedFollow up dateCurrent statusNext action

This kind of workflow reduces missed handoffs, because every inquiry has a status, an owner, and a next action.

Want to see how the same instincts show up off the clock?

The artifacts show how I structure delivery. The passion projects show that the same systems thinking follows me into every business, launch, workflow, and operating problem I touch.

See the passion projects