Ops Knowledge Garden

First 90 Days as an EMS Supervisor

Living noteLast tended 5 min read

First 90 Days as an EMS Supervisor

You just got promoted. Yesterday you were responsible for your own work. Now you may be responsible for a crew, a shift, documentation metrics, fleet safety, and conversations nobody trained you for.

This is what I would focus on first.

The First Thing to Understand

Your clinical skill still matters. It just is not the whole job anymore.

As a field provider, I could often solve the problem in front of me myself. As a supervisor, I had to help other people make good decisions when I was not in the room. That was a much larger identity change than the promotion made it sound.

The question I wish I had asked earlier was: what will this crew be able to handle without me?

Days 1–30: Listen First

I would resist the urge to arrive with a list of changes. The title gives you a new view of the operation, but it does not mean you understand it yet.

Go where your crew works. Watch. Ask questions. Learn what frustrates them, what has been broken for a while, and what works better than leadership realizes. The dates here are a useful rhythm, not a law. Some operations will require action before Day 30.

Specific things to do in the first 30 days:

  • Ride along. At least a handful of shifts. Not to supervise — to observe. What does a normal shift actually look like for your crew?
  • One-on-ones with everyone. Not formal reviews. “I want to understand your experience, what’s working, what isn’t.” Listen more than you talk.
  • Learn the numbers. What are your chute times, your addenda rate, your incident history? You can’t know if things are getting better if you don’t know where they are. See Operational Metrics.
  • Find out what the last supervisor did well and what they didn’t. You don’t need to ask directly. It’ll come out in the one-on-ones.

Days 31–60: Build Credibility

By the second month, you should have heard enough to act on something real. The title may give you authority. People still need evidence that you listened.

This is the phase where you start acting on what you learned — slowly and visibly. Fix one thing that’s been annoying the crew for a while and that you can actually fix. Not the biggest systemic problem. Something concrete, small, and immediately visible.

Fixing one concrete problem is a good way to show that the first month was not a listening performance.

This is also when I would begin making expectations visible: calmly, specifically, and without a dramatic memo announcing a new era. What you consistently notice and address will teach people more than a speech about standards.

Days 61–90: Start Building Systems

By now you may have enough context to choose one or two underlying problems. If you do not, keep learning rather than forcing the calendar.

Choose them from what you observed and what the records suggest. Define the problem, establish a baseline, try something proportionate, and decide how you will know whether it helped. A new policy may be part of the response, but publishing one is not the same as changing the operation.

For fleet safety, see Fleet Safety. For documentation, look at where your addenda are clustering. For crew development, build a simple FTO feedback cadence if you don’t have one.

Document what you’re doing and why. Not for credit — for continuity. If you leave, your replacement shouldn’t have to start from scratch.

The Things That Will Trip You Up

Friendship vs. leadership. Some of the people you’re now supervising may have been your peers or friends. The relationship does not need to become cold, but pretending nothing changed creates confusion. You can be warm and still hold standards.

Trying to have all the answers. You will not. And you should not pretend to. “I don’t know, let me find out” is a legitimate response, especially in the first 90 days. What erodes credibility is not the absence of an immediate answer; it is pretending to know and being wrong. Later, you may face the opposite problem: knowing so many answers that the team begins routing every decision through you.

Neglecting your own crew’s development. You’ll be busy with logistics, paperwork, and fires. The first thing that gets dropped is usually the proactive development work — the debriefs, the FTO check-ins, the one-on-ones. Build them into your routine before you get busy, not after.

The fires will always argue that they are more urgent than the system. That is why preventive work has to become part of the operating rhythm before the crisis decides the rhythm for you.

Waiting to have hard conversations. See Hard Conversations. In my experience, delay usually reduced the options available to everyone.

What Success Looks Like at Day 90

By Day 90, I would want to know the crew well enough to stop guessing about their work, understand the baseline numbers without pretending they explain themselves, and have followed through on at least one problem people trusted me with.

You may still feel uncomfortable. I did. A calendar does not finish the transition; it only gives you somewhere to begin.

At Day 90, the Supervisor Self-Evaluation gives you a structured way to look at what you actually built.

Graph View

Backlinks