Operational service leadership for the people who run field teams
Technical tracks build technician judgment. This pilot builds the managers who run those technicians: the standard they are held to, how they are placed, how jobs are supervised, and how callbacks come down.
Seven lessons, seven artifacts, one 30-day plan — written in your industry's field language.
Who this pilot is for
Owners
You carry the warranty risk and the reputation. You need a written standard your team is actually held to, not a culture statement.
Service managers and supervisors
You place technicians on jobs every morning. You need honest readiness grading, a brief-checkpoint-review rhythm, and callbacks costed in real money.
Senior technicians moving into leadership
You can do the work. This is the shift from fixing the fault yourself to coaching the diagnosis and still leaving site on time.
Not for you if you want general management theory, or a licensing pathway — this is operational service leadership, and it is complementary to local licensing.
How the program works
Industry-specific decision labs
Branching field scenarios with a named seat, a named site, a hard constraint and a technician whose readiness you already know. Every choice carries into the next.
Artifacts you keep
Each lesson ends in a document you fill in for your own team — not a worksheet you throw away.
Supervision and callback standards
Pre-job brief, one decision-point checkpoint, post-job review, a leave-site rule and escalation criteria that move the callback number.
A 30-day team upgrade plan
The capstone assembles everything into a plan another supervisor could execute and review without you in the room.
What leaders leave with
Seven working documents, filled in for your own team as you go.
- 01
Team Competence Standard
Four observable pillars a supervisor can mark pass or fail on a live job.
- 02
Readiness Matrix
Every technician graded per job type, so placement stops being a guess.
- 03
Development Plan
Academy modules assigned against observed weakness, not seniority.
- 04
Supervisor Script
Brief, checkpoint and review, worded so you coach without taking the call over.
- 05
Callback Board
Callbacks costed honestly and tracked against a target you set.
- 06
Service Workflow
Arrival to handover in EcoService OS, with exit conditions at every stage.
- 07
30-Day Upgrade Plan
The capstone deliverable: owners, cadence and measurable outcomes.
Your industry, not a generic case study
You select your industry once at the start of the pilot. From then on every decision lab renders in that field's language — its access reality, its constraints, its cost of a return visit — while the standard being taught and the way you are graded stay identical across industries.
Curriculum
- 01
Setting the Standard
What high-competence service looks like
Define the standard your team is held to, in words a technician can act on: safety judgment, diagnostic reasoning, measurement discipline, documentation quality.
- 02
Building the Team
Hiring, assessing, and placing technicians
Readiness levels instead of job titles: what someone can actually be trusted with, who they should be paired with, and which Academy modules are required before solo work.
- 03
Building the Team
Training systems that stick
Assign Academy modules against observed weakness, read lab performance as data, and build a weekly rhythm that survives a busy month.
- 04
Running the Work
Supervising real jobs without micromanaging
Three touchpoints instead of constant contact: a pre-job brief, one decision-point checkpoint, and a post-job review that coaches the diagnosis rather than taking the call over.
- 05
Running the Work
Reducing callbacks and raising ticket quality
Cost a callback honestly, install a first-visit mindset with a written leave-site rule, and protect the company commercially through documentation.
- 06
Running the Work
Building the service operating system
One standard service flow in EcoService OS — arrival, diagnosis, repair, verification, handover — with an exit condition and a required record at every stage.
Capstone — 30-Day Team Upgrade Plan
Assemble the six artifacts into one executable 30-day plan: competence baseline, Academy assignments, supervisor cadence, callback target, workflow standards.
Unlocks once the six operating lessons are complete.
What you will be able to do
- Write a one-page standard of competence a supervisor can mark on a live job
- Grade every technician by readiness level per job type and place them accordingly
- Assign Academy modules against observed weakness and review lab performance as data
- Run a pre-job brief, a single decision-point checkpoint and a post-job review
- Coach a diagnosis with questions instead of taking the call over
- Cost callbacks honestly and set a leave-site rule and escalation criteria that move the number
- Run one standard service flow in EcoService OS with exit conditions at every stage
- Produce a 30-day team upgrade plan that another supervisor could execute and review
Where this sits in the Academy
Technical tracks build technician judgment. Service Leadership builds the managers who run those teams.
After the labs, you know which exam to book
- After the labs, you know which exam to book. Prep here for EPRA, NABCEP, EPA 608, NATE, CEC, SAQCC Gas and ESSCI, then book with that body when the labs are done.
- EcoPowerHub Academy is the prep and issues its own completion record. The examining body is the issuer of the credential you sit for.
- Work on photovoltaic, battery, and electrical systems involves potentially lethal voltages and must only be performed by qualified persons, in accordance with applicable codes, regulations, and employer safety programs.
- Labs and materials are educational. The technician and their employer remain solely responsible for safe work practices, isolation, PPE, and compliance on actual jobs.
- Exam and licence fees are paid to the examining body. Academy completion is training.