Lesson reader
Domain III, Functions of Management
Plan, Staff, Organize, and Control Operations
Connect every plan to the mission
Planning converts a mission into choices about results, resources, timing, and responsibility. A strategic plan establishes a multi-year direction and the few priorities that deserve sustained investment. Long-term plans translate that direction into capacity, workforce, technology, and capital needs. Short-term plans commit near-term resources. An operational plan names the work, owner, schedule, budget, standard, and measure used to deliver a service. A policy sets a durable rule or decision boundary, while a procedure explains the approved steps. An emergency or continuity plan protects essential functions under disrupted conditions. These layers must agree. If the organization promises bedside meal ordering but the operating budget, staffing model, network resilience, and downtime procedure cannot support it, the strategy is only an aspiration. Start with the required outcome, state assumptions and constraints, identify dependencies, and assign an accountable owner. Use a deadline and one or more measures that reveal whether execution is on course. Review plans when demand, regulation, risk, or resources change rather than waiting for the annual planning cycle.
| Plan type | Primary question | Typical evidence | Common trap |
|---|---|---|---|
| Strategic | Where must the service be in several years? | Mission, environmental scan, demand, capability, risk | Listing projects without choosing priorities |
| Operational | Who will deliver what, when, and with which resources? | Workload, workflow, budget, standards, schedule | Setting activity targets unrelated to outcomes |
| Policy and procedure | What rule applies, and how is it carried out? | Law, accreditation, risk, approved workflow | Confusing a rule with step-by-step instructions |
| Emergency and continuity | How will essential functions continue during disruption? | Hazards, dependencies, alternate resources, exercises | Writing a plan that staff have never practiced |
- Plan type
- Strategic
- Primary question
- Where must the service be in several years?
- Typical evidence
- Mission, environmental scan, demand, capability, risk
- Common trap
- Listing projects without choosing priorities
- Plan type
- Operational
- Primary question
- Who will deliver what, when, and with which resources?
- Typical evidence
- Workload, workflow, budget, standards, schedule
- Common trap
- Setting activity targets unrelated to outcomes
- Plan type
- Policy and procedure
- Primary question
- What rule applies, and how is it carried out?
- Typical evidence
- Law, accreditation, risk, approved workflow
- Common trap
- Confusing a rule with step-by-step instructions
- Plan type
- Emergency and continuity
- Primary question
- How will essential functions continue during disruption?
- Typical evidence
- Hazards, dependencies, alternate resources, exercises
- Common trap
- Writing a plan that staff have never practiced
| Management lens | Primary contribution | Useful application | Limitation if used alone |
|---|---|---|---|
| Scientific management | Standard work, measurement, specialization, and efficiency | Study motion, time, layout, and repeatable production steps | Can underweight judgment, variation, and social needs |
| Administrative management | Planning, organizing, directing, coordinating, and controlling | Clarify authority, roles, plans, and management functions | Formal design does not guarantee engagement or adaptation |
| Human relations | Social context, participation, recognition, and group behavior | Design communication, supervision, teamwork, and motivation | Morale cannot replace standards, resources, or sound process |
| Systems | Interdependent inputs, processes, outputs, feedback, and environment | Trace how a local change affects patients, staff, suppliers, cost, and quality | A broad map still requires a specific decision and owner |
| Contingency | The effective approach depends on task, people, risk, technology, and environment | Fit structure and leadership to the actual situation | It depends is not an excuse to omit evidence or standards |
- Management lens
- Scientific management
- Primary contribution
- Standard work, measurement, specialization, and efficiency
- Useful application
- Study motion, time, layout, and repeatable production steps
- Limitation if used alone
- Can underweight judgment, variation, and social needs
- Management lens
- Administrative management
- Primary contribution
- Planning, organizing, directing, coordinating, and controlling
- Useful application
- Clarify authority, roles, plans, and management functions
- Limitation if used alone
- Formal design does not guarantee engagement or adaptation
- Management lens
- Human relations
- Primary contribution
- Social context, participation, recognition, and group behavior
- Useful application
- Design communication, supervision, teamwork, and motivation
- Limitation if used alone
- Morale cannot replace standards, resources, or sound process
- Management lens
- Systems
- Primary contribution
- Interdependent inputs, processes, outputs, feedback, and environment
- Useful application
- Trace how a local change affects patients, staff, suppliers, cost, and quality
- Limitation if used alone
- A broad map still requires a specific decision and owner
- Management lens
- Contingency
- Primary contribution
- The effective approach depends on task, people, risk, technology, and environment
- Useful application
- Fit structure and leadership to the actual situation
- Limitation if used alone
- It depends is not an excuse to omit evidence or standards
Convert demand into coverage
Staffing begins with demand, not the current roster. Define service units such as meals, assessments, follow-ups, production batches, or open-counter hours. Forecast volume by day and time, stratify work when acuity or complexity changes the standard time, and include required coordination, documentation, setup, cleanup, and handoff work. Workload hours equal units multiplied by standard minutes per unit, divided by 60. A full-time equivalent is an hours-based measure, not a person. For a stated period, FTE equals total qualifying hours divided by the employer's full-time hours for that period. The denominator must be stated because 40 hours per week and 2,080 hours per year are conventions, not universal laws. Productive capacity is smaller than paid capacity when leave, training, meetings, and other nonproductive time are included. Required paid FTE equals required productive hours divided by productive hours available from one paid FTE. A coverage model must then be translated into people, shifts, competencies, breaks, relief, and overlap. Never round a calculated need downward when doing so creates an uncovered safety-critical interval.
Worked example
Calculate clinical staffing and build a weekly schedule
Convert units to direct workload
The weekly forecast is 42 initial assessments at 35 minutes, 70 follow-ups at 20 minutes, and 8 interdisciplinary rounds at 45 minutes. Direct workload is 1,470 plus 1,400 plus 360, or 3,230 minutes. Divide by 60 to obtain 53.83 hours.
Account for productive capacity
The standard minutes above include encounter documentation. After accounting for other measured time such as required meetings, training, and leave, the department's productive fraction is 78 percent. One 40-hour paid FTE supplies 31.2 productive hours. Required paid FTE is 53.83 divided by 31.2, or 1.73 FTE.
Translate FTE into people
The manager has one 1.0 FTE RDN and two 0.4 FTE RDNs, for 1.8 authorized FTE and three people. The total is adequate on paper, but the manager must place qualified coverage at demand peaks and preserve handoffs, leave, and backup rather than spreading every person evenly.
Test the schedule
Map appointments and rounds by day, reserve documentation time, verify meal-break and overtime rules, and stress-test one absence. If Monday demand requires 18 productive hours but only 12 are scheduled, moving hours from Thursday is a scheduling correction even though weekly FTE is sufficient.
Build a lawful and resilient schedule
A staffing plan states the capacity required; a schedule assigns named employees to specific times and duties. Build the schedule around service windows, workload peaks, required credentials, supervision, opening and closing work, handoffs, and emergency backup. Then test it against wage and hour rules, state and local scheduling or break requirements, approved leave, accommodation, the collective bargaining agreement, and organizational policy. Under the federal Fair Labor Standards Act, covered nonexempt employees generally earn overtime after 40 hours worked in a fixed 168-hour workweek. Federal law does not create a general lunch or coffee-break requirement, but short breaks that an employer provides are generally compensable, and state law may be more protective. Do not average two workweeks to hide overtime. Publish schedules with enough lead time for the applicable rule and use a transparent method for rotations, weekends, holidays, and requests. Fairness does not mean identical shifts. It means job-related rules applied consistently, a usable request process, and review of recurring burdens. Monitor overtime, missed breaks, vacancies, call-outs, agency use, and fatigue as staffing signals rather than treating each as an isolated event.
| Measure | Formula | Interpretation |
|---|---|---|
| Workload hours | Units x standard minutes / 60 | Time required for forecasted work |
| Coverage FTE | Required coverage hours / standard full-time hours | Hours equivalent before relief and placement |
| Paid FTE need | Required productive hours / productive hours per paid FTE | Capacity after measured nonproductive time |
| Labor productivity | Output units / labor hours | Efficiency only when output and hours are defined consistently |
| Schedule coverage | Qualified staffed intervals / required intervals x 100 | Whether hours are placed where service requires them |
- Measure
- Workload hours
- Formula
- Units x standard minutes / 60
- Interpretation
- Time required for forecasted work
- Measure
- Coverage FTE
- Formula
- Required coverage hours / standard full-time hours
- Interpretation
- Hours equivalent before relief and placement
- Measure
- Paid FTE need
- Formula
- Required productive hours / productive hours per paid FTE
- Interpretation
- Capacity after measured nonproductive time
- Measure
- Labor productivity
- Formula
- Output units / labor hours
- Interpretation
- Efficiency only when output and hours are defined consistently
- Measure
- Schedule coverage
- Formula
- Qualified staffed intervals / required intervals x 100
- Interpretation
- Whether hours are placed where service requires them
Organize, delegate, and coordinate
Structure should make the work and authority visible. A functional structure groups similar expertise and supports standardization, but can create handoff barriers. A service-line or product structure improves end-to-end ownership, but may duplicate specialists. A matrix shares authority across functions and programs, which can improve coordination while creating conflicting priorities unless decision rights are explicit. Use the simplest structure that handles the actual dependencies. For each recurring process, name who performs the work, who owns the result, who must be consulted, and who must be informed. Delegation transfers authority to perform a defined task, not the manager's accountability for selecting a capable person, giving resources and limits, monitoring risk, and following up. State the expected result, deadline, quality standard, allowed decisions, prohibited actions, reporting points, and escalation triggers. Confirm understanding through a read-back or work demonstration when risk is high. Coordination then connects delegated tasks through shared schedules, huddles, handoffs, dashboards, and exception routes. Overcontrol delays work and suppresses judgment. Undercontrol creates hidden variation. Match the frequency of supervision to consequence, novelty, competence, and reliability.
Control performance without chasing noise
Management control is a learning cycle: define the standard, measure actual performance, calculate and interpret variance, investigate cause, act at the correct level, and remeasure. Pair productivity with quality, safety, experience, and cost. Trays per labor hour can rise because workflow improved, because documentation was skipped, or because fewer complex trays were produced. First verify definitions, denominators, case mix, timing, and data completeness. Then distinguish common process variation from a meaningful shift, and distinguish a system constraint from individual conduct. Corrective actions should match the cause. A knowledge gap may need training and demonstration. A confusing label may need redesign. Chronic understaffing may require capacity or demand changes. Deliberate disregard after clear training may require performance management under policy and contract. Set an owner and due date, protect immediate safety, and measure whether the action corrected the process without causing a balancing harm elsewhere. A favorable result should also be standardized and monitored for sustainment. Control fails when managers punish the nearest person before understanding the work system.
Reference list