8.2 Project Management, Work Plans, and Timelines

Moving from plan to organized work

A health education plan is useful only if the team can implement it. Project management is the structure for doing the work: it translates goals and SMART objectives (Specific, Measurable, Achievable, Relevant, Time-bound) into activities, timelines, roles, budgets, materials, partner commitments, and monitoring steps. On the CHES exam, project management often appears as the practical next step after planning (Area II) and before evaluation (Area IV).

Anatomy of a work plan

A work plan (sometimes called an action plan) shows what will be done, who is responsible, when, with what resources, and how completion is documented. A strong work plan ties each activity to a SMART objective and an evaluation indicator. It also lists dependencies, such as completing facilitator training before classes begin.

Tasks must be specific enough to manage. "Conduct outreach" is too broad; better tasks are drafting a contact list, calling partner sites, scheduling information tables, preparing materials, confirming interpreters, and recording referrals. Breaking work into tasks reveals staffing, time, and resource needs.

Timelines, Gantt charts, and milestones

Timelines need realism. If recruitment materials require translation, review, printing, and partner approval, a one-week deadline is risky. School-based sessions depend on the academic calendar, so testing weeks and holidays matter. Tools such as a Gantt chart display tasks across a calendar with bars, dependencies, and milestones (key checkpoints, like "first cohort enrolled"). A CHES should check constraints early rather than discovering them after implementation starts.

The constraint triangle and risk

Project managers balance the constraint triangle of scope, time, and cost, with quality at the center. Change one and the others shift. If funding is reduced, the team may cut the number of sessions, secure in-kind space, or adjust staffing, while preserving the program's core purpose and ethical commitments. Cutting evaluation, accessibility, or safety usually creates bigger problems later.

Risk management anticipates what could interfere with implementation. A simple risk register names each risk, its likelihood, impact, prevention step, and backup plan:

• Staff turnover, low enrollment, transportation barriers, weather, technology failure, partner delays, or supply shortages.
• Example: if a webinar platform fails, the backup is a dial-in number plus a recorded session sent afterward.

Monitoring versus final evaluation

Monitoring (also called process evaluation) happens during implementation, not at the end. It asks whether activities are occurring as planned, whether participation is adequate, whether materials are available, and whether barriers are emerging. Attendance logs, fidelity checklists, budget burn reports, and partner check-ins are monitoring tools. This is distinct from final outcome evaluation, which judges whether objectives were met. If a program is behind schedule, the exam-correct first step is to use monitoring data to identify the cause, then adjust the work plan with the team, not to wait for the final report.

Documentation and communication

Documentation supports continuity: if a staff member leaves, written procedures and an updated work plan let the next person continue, and it supports grant reporting and accountability. It should be accurate but not so burdensome that staff cannot maintain it. Regular check-ins should focus on decisions, barriers, next steps, and deadlines; meetings without action notes waste time. A CHES may use a shared tracker, brief status report, or dashboard.

In exam scenarios, choose the response that makes work clearer and more controllable. If implementation lags, diagnose the cause first. If roles overlap, clarify responsibilities. If an activity no longer supports an objective, reconsider it. Avoid options that hide problems, abandon evaluation, or push ahead without rebalancing constraints.

Logic models, work plans, and the planning chain

Project management does not stand alone; it sits inside the planning chain a CHES learns across the eight areas. A logic model maps inputs, activities, outputs, and short-, intermediate-, and long-term outcomes, showing the theory of how resources produce change. The work plan operationalizes the activities and outputs columns of that logic model. When an exam stem asks whether an activity belongs in the program, trace it back: if the activity does not lead to a planned output and outcome, it is scope creep and should be questioned.

This is also how a CHES defends a budget line, because every resource should connect to an activity that connects to an objective.

Defining roles with a responsibility matrix

Larger projects benefit from a responsibility assignment matrix, sometimes called a RACI chart, which labels each task by who is Responsible (does the work), Accountable (owns the outcome and signs off), Consulted (gives input), and Informed (kept in the loop). Confusion on the exam often comes from two people both believing they were Accountable, or no one being clearly Responsible. The correct managerial fix is to clarify the matrix rather than to redo the work or assign blame after the fact.

Critical path, slack, and sequencing

Not all delays matter equally. The critical path is the longest chain of dependent tasks that determines the earliest possible finish date; a delay on a critical-path task pushes the whole program back, while a task with slack (float) can slip without affecting the end date. Practically, this means a CHES prioritizes attention on the tasks that gate everything else. If curriculum translation must finish before printing, which must finish before recruitment materials reach partners, that chain is the critical path and deserves the earliest start and closest monitoring.

Scope creep and change control

Scope creep is the gradual, unmanaged expansion of work beyond what was planned and resourced, often from well-meaning requests to add sessions, audiences, or topics. Unchecked, it consumes time and budget and threatens quality. Good project management uses a simple change-control habit: when a change is requested, evaluate its effect on scope, time, cost, and quality, decide deliberately, and document the decision. Saying yes to everything is not service; it is a management failure that the exam will frame as the wrong answer.

The disciplined response is to weigh the request against objectives and constraints and, when needed, secure approval before committing resources.