Source and Scope Boundary
This page is the public derivative of `RM-MKS-10005 — Planner Role`, v1.0, Approved Internal. It owns the planner role: competencies, staffing, organizational placement, onboarding, decision rights, and role-performance governance. The planning method — how a work package is actually built — belongs to Maintenance Planning. The scheduler role and schedule construction belong to Maintenance Scheduling and Planning and Scheduling Governance. This page describes a role model, not craft licensing or statutory qualification rules.
Plain-English Definition
The maintenance planner prepares future work so execution teams receive a clear, safe, technically usable package — with realistic labor, material, tool, access, and information requirements. The role protects the future-work horizon: it converts validated demand into executable preparation and improves reusable job knowledge from field feedback.
The planner is not the daily supervisor, and not the default expediter, scheduler, storeroom clerk, buyer, or emergency coordinator. Small sites may combine roles, but a combined assignment must explicitly protect planning capacity and decision boundaries.
Why the Role Matters
A protected planning role reduces avoidable execution uncertainty, improves reuse of job knowledge, and makes future labor and material demand visible before the week it is needed. The benefit depends on work volume, planner competence, supervisor discipline, and CMMS quality — no universal productivity number is claimed.
The single most common way the role fails is role erosion: the planner is pulled into chasing today's parts and dispatching today's work until no time is left to prepare tomorrow's. Protecting planning capacity is the core governance job.
What the Planner Does — and Does Not
| Does | Does not |
|---|---|
| Prepares future work packages to the required depth | Control today's execution (that is the supervisor) |
| Verifies field conditions and technical requirements | Approve engineering changes or safety permits by role alone |
| Estimates labor, duration, materials, tools, access | Own the storeroom, procurement, or scheduling function |
| Coordinates specialist inputs and unresolved constraints | Chase parts for today's jobs as a default |
| Improves reusable job plans from execution feedback | Get judged by document volume alone |
Core Competencies
| Competency | Expected capability |
|---|---|
| Maintenance technical | Understand equipment, failure, task sequence, and craft constraints |
| Work management | Apply planning boundaries and interfaces |
| Estimating | Build transparent labor/duration assumptions and calibrate them against actuals |
| Materials | Specify correct parts; interpret availability and control status |
| CMMS / data | Use master data, history, job plans, statuses, and feedback correctly |
| Communication | Obtain field knowledge and resolve cross-functional inputs |
| Risk / control awareness | Recognize when qualified safety, engineering, quality, or regulatory authority is required |
The Planning Cycle (the planner's flow)
- Validated, prioritized work leads to Screen scope and planning need.
- Screen scope and planning need leads to Field and technical verification.
- Field and technical verification leads to Develop work package.
- Develop work package leads to Coordinate materials, operations, specialists.
- Coordinate materials, operations, specialists leads to Readiness assessment.
- Readiness assessment leads to Scheduler selects eligible work.
- Scheduler selects eligible work leads to Supervisor controls execution.
- Supervisor controls execution leads to Technician feedback and actuals.
- Technician feedback and actuals leads to Improve reusable job knowledge.
- Improve reusable job knowledge leads to Develop work package.
The planner develops the package but does not own every contributing function — engineering dispositions, safety approvals, and procurement decisions are escalated to their accountable owners, not absorbed by the planner.
Operating Model
Planners may be centralized, area-based, craft-aligned, or hybrid. The model should give the planner access to assets and technicians while keeping consistent standards and coaching. Organizational placement should avoid a structure where immediate production pressure routinely displaces future-work preparation without managerial visibility.
No universal planner-to-craft ratio is prescribed. Staffing follows workload, job complexity, planning depth, work mix, and support-system maturity.
Decision Rights
| Decision | Planner authority boundary |
|---|---|
| Select planning depth | Within approved risk/complexity rules |
| Define job steps and estimates | Responsible, using qualified input |
| Approve an engineering change | Not authorized unless separately delegated and qualified |
| Approve a safety permit or isolation | Not through the planner role alone |
| Mark planning complete | Within the planning method and evidence requirements |
| Declare overall readiness | Participates under the readiness policy; authority follows that policy |
| Select the weekly schedule | The scheduler's process |
| Direct daily work | The supervisor's execution authority |
Roles and Interfaces
| Interface role | Relationship to the planner |
|---|---|
| Supervisor | Supplies field knowledge, reviews feasibility, controls execution |
| Scheduler | Receives eligible work; challenges unclear duration, craft, or constraints |
| Operations | Confirms access, operating context, isolation concept, and windows |
| Technician | Supplies execution knowledge and feedback; retains ownership of craft quality |
| Storeroom / Procurement | Confirms material identity, availability, reservation, substitution, lead time |
| Engineering / Reliability | Supplies technical disposition and reliability requirements |
| Maintenance Manager | Provides staffing, priorities, role protection, and performance governance |
Safety Considerations
The planner identifies foreseeable hazards, prerequisite controls, required qualifications, permit-planning needs, and technical information. The planner does not replace competent-person determinations, field hazard assessment, lockout/tagout authority, permit issuance, or supervisor control. Planners must have stop-and-escalate authority when critical safety information is absent. Jurisdictional licensing, inspection, environmental, quality, and process-safety requirements are determined by qualified organizational functions.
Metrics and KPIs
No universal staffing ratio or target is prescribed. Each metric needs a defined owner, period, inclusion/exclusion rules, and stated limitations.
| Metric | Formula | Interpretation / gaming control |
|---|---|---|
| Protected Planning Time | Hours on defined planning work / planner available hours × 100 | Diagnoses role erosion; do not encourage miscoding time |
| Feedback Disposition Rate | Completed jobs with feedback disposition / completed jobs requiring feedback review × 100 | Measures the learning loop, not whether every suggestion is accepted |
| Package Defect Rate | Planned jobs with a verified package-caused defect / planned jobs reviewed × 100 | Requires causal evidence and consistent sampling |
| Estimate Calibration | Σ actual labor hours / Σ estimated labor hours for comparable completed work | Segment by work type; do not punish honest uncertainty or absorb uncontrolled scope changes unflagged |
| Planner Queue Aging | Σ days work remains in an actionable planning state / actionable planning items | Separate blocked external constraints from planner-controlled delay |
Avoid raw "plans completed" rankings that reward shallow packages.
Common Failure Modes
- The planner becomes the default parts chaser or daily dispatcher (role erosion).
- Desk-only planning misses field conditions.
- One planner owns more work than can be prepared to the required depth.
- The planner is blamed for decisions owned by engineering, operations, or procurement.
- A combined planner/scheduler role has no protected capacity.
- Feedback is collected but never incorporated.
- Performance is measured by quantity only.
Best Practices
- Publish a clear role charter and escalation model.
- Select planners for technical credibility, communication, systems thinking, and willingness to learn.
- Provide regular field time and technician access — planning is not a desk-only job.
- Protect future-work capacity visibly, and measure protected planning time.
- Use peer review for high-risk or novel work.
- Train planners in the CMMS, estimating, materials, drawings, job-plan governance, and applicable controls.
- Review role health separately from process output.
Maturity Model
| Level | Characteristics |
|---|---|
| 1 — Reactive | Planning happens during execution, by supervisors or technicians |
| 2 — Assigned | A planner title exists, but daily expediting dominates |
| 3 — Protected | Charter, competencies, queues, interfaces, and capacity controls are defined |
| 4 — Integrated | Planning, readiness, scheduling, materials, and feedback operate through connected data |
| 5 — Learning | Competency, staffing, package quality, and reusable knowledge improve from evidence |
Practical Examples
Role erosion. A planner spends most mornings locating parts for today's jobs — useful work that displaces future preparation. Management assigns expediting ownership elsewhere, fixes material-status visibility, and measures protected planning time, rather than simply telling the planner to "plan more."
Small facility, combined role. One person plans and schedules. The site sets time blocks, separate CMMS statuses, and a weekly decision point: first complete evidence-based readiness, then build the schedule. The combined role does not permit self-declaring unresolved work as ready.
Novel repair. A planner lacks authority to approve a structural repair detail. They record the constraint, obtain an engineering disposition, then incorporate the controlled drawing into the package — rather than guessing to keep the job moving.
Audit Questions
- Is there a role charter defining planner authority and interfaces?
- Is protected planning capacity defined and measured?
- Are planning queues and aging maintained separately from total backlog?
- Is field verification evidenced where risk or novelty warrants it?
- Are technical, material, and safety decisions routed to their accountable owners?
- Is feedback disposition tracked, not just collected?
- Where roles are combined, are capacity and conflict controls documented?
Related Reliability Method Topics
- Maintenance Planning (the planning method)
- Maintenance Scheduling
- Planning and Scheduling Governance
- Job Plan Management
- Work Execution Excellence
- Backlog Management
References
References trace to the authoritative MKS; no licensed standard text is reproduced and no universal staffing ratio is asserted.
- RM-MKS-10005 — Planner Role
- SMRP Body of Knowledge, Work Management subject area (verify current licensed edition)
- OSHA 29 CFR Part 1910, where applicable — qualified review determines role-specific obligations
Revision History
| Version | Date | Change |
|---|---|---|
| 1.0 | 2026-08-16 | Initial public derivative created from Approved Internal `RM-MKS-10005` v1.0, activating the reserved Knowledge ID KN-5009 under owner direction; supersedes the retired KN-5005 "Planner Development" record. |