What to bring to the conversation

1) Three patterns you can name without heat

It’s tempting to walk in with “the system is bad,” especially when you’re tired of patching the same gaps. In an admin conversation, that phrasing usually turns the meeting into defense mode. People start explaining why things are the way they are instead of looking at what’s actually breaking down.

Naming patterns keeps it grounded in how the school runs.

Bring three, not ten. Ten starts to sound like a pile-on and invites the response, “This is too much to tackle.” Three is enough to be credible and specific, and it leaves room for the conversation to stay constructive.

Choose the three that are most consistent for you:

• “We spend time tracking down basic permissions that should be quick to confirm.”
• “The same context lives in multiple places, so we retype and re-explain.”
• “When I’m out, decisions slow down because the right information isn’t easy to retrieve.”
• “We lean on email threads to reconstruct what’s already documented.”

A calm way to summarize it:

2) One ordinary story that makes the gap visible

A lot of nurses reach for the worst story they have because it feels persuasive. In schools, that often backfires. Extreme stories invite people to argue about the exception instead of fixing the daily weak spot.

A familiar story works better because most admin can picture it immediately.

Example:

“A student shows up to PE with an inhaler. Staff aren’t sure whether self-carry is approved. Someone checks a folder. Someone emails me. Someone asks the division head. The student waits while adults try to confirm something that should take under a minute.”

That’s exactly how these situations unfold. The setup makes normal days harder than they need to be, and it puts students in the middle of adult uncertainty.

If you can, pick a story that shows one of these themes:

• a basic permission that should be easy to confirm
• a handoff problem when you’re out or covering elsewhere
• a decision that got reconstructed from email later

One story is enough.

3) A rough price tag in school terms

Admin don’t need perfect measurement. They do need to understand what this costs in a normal week, because “small” problems become real when they repeat.

Keep it to two or three cost frames:

• time spent on retrieval and retyping
• extra interruptions to deans/teachers/coaches
• back-and-forth with parents that could be prevented
• fragile coverage when you’re out

Examples that stay grounded:

• “This is about 10 minutes a day in retrieval and retyping. It adds up.”
• “It pulls deans and teachers into health questions they can’t answer.”
• “It creates extra back-and-forth with families that could be avoided.”
• “Coverage is harder when I’m out because there isn’t a clean handoff.”

A line that keeps the tone neutral:

4) A clear picture of what “working” would look like

This is where the conversation stops being personal and starts being operational.

Without a shared definition of “working,” admin will default to, “We haven’t had any big incidents,” which can be true while the system is still fragile.

Try this phrasing:

A short list that’s clear and school-relevant:

• one place to find the current truth for plans, permissions, and key health information
• fast retrieval during the day, especially when things are moving
• clean handoffs when a nurse is out or covering another area
• a clear boundary between clinical notes and operational messages
• access that matches roles, so people see what they need and nothing more
• confidence that the record supports decisions without rebuilding the story from email

This list does two useful things. It keeps you out of a tool debate, and it gives admin a way to say yes to a reasonable next step.

5) One small ask that doesn’t trigger defenses

If you ask for a new tool in the first conversation, you’ll hit budget and timing immediately. Even admin who agree with you will start thinking about procurement instead of the problem you’re trying to describe.

A request for a short review is easier for people to accept, and it leads to better decisions.

A clean ask sounds like this:

That keeps the conversation adult and contained. It also gives you a way to move forward without demanding a decision on the spot.

Who should be in the room (at first)

The first conversation goes better when it stays small.

A good starting group:

• you
• one division head or dean
• counselor lead, if mental health workflow touches your documentation and communication

Athletics and operations can come next if the conversation continues. The goal of meeting one is alignment, not consensus across the whole school.

Pushback you’re likely to hear, and what to say back

Having calm responses ready changes the tone of the meeting. It makes you sound steady, not frustrated.

“We haven’t had any major issues.”
“I’m glad. I’m not pointing to one incident. I’m talking about consistency under pressure, especially when someone is out or the day is moving fast.”

“This is probably training.”
“It might be part training. That’s why I’m not asking for a purchase. I’d like us to separate process, training, and tools and then decide what actually needs attention.”

“We can’t change systems mid-year.”
“I’m not asking to change mid-year. I’m asking us to define what needs to be true next year, and to tighten what we can now.”

“This sounds like preference.”
“If it were preference, it would mostly affect me. This shows up in consistency, handoffs, and how quickly we can make safe decisions.”

None of those responses are combative. They’re designed to keep the conversation in the lane you want.

Bring a one-page leave-behind

Admin can’t hold the details the way nurses do, especially in January. A one-page leave-behind makes it easier for them to carry this forward after the meeting ends.

If you only have time for one thing, bring this.

Health continuity review: what I’m seeing and what “working” looks like

• Patterns (3 bullets)
• One example (3–4 sentences)
• Cost (2–3 bullets)
• What “working” looks like (5–6 bullets)
• Next step (one sentence):
  “Schedule 30 minutes to align on outcomes and identify whether this is process, training, or tools.”

That’s enough to keep the problem clear without turning it into homework for anyone.

A steady opener you can use

If you want a script that doesn’t come off dramatic, this one is reliable:

“I want to flag a pattern I’m seeing in our health workflow. We can make it work day-to-day, but it gets fragile when the pace picks up, especially when I’m not available. I’d like to align on what ‘working’ should look like and do a short review to see whether the gap is process, training, or tools.”

It names the issue, avoids blame, and gives admin a path.

Quick prep list

Before you meet with admin, have:

• three patterns you can name calmly
• one ordinary story
• two rough cost frames
• an outcomes list for what “working” should look like
• a 30-minute review ask
• a one-page leave-behind

That’s enough to raise the issue early, without sounding like you’re sounding an alarm.