Looping Systems at School: How They Work, How They Fail, and Why Staff Need to Know

A looping system can be the single most useful piece of technology your child brings to school. It can also be the least understood thing in the building, and an unmanaged loop stops protecting anyone.

Here is the honest reality of looping systems at school. The algorithm is doing math every few minutes, all day, and it is only as good as the information it is given and the adults who are paying attention. When it works, it is remarkable. When it fails quietly for two hours, that is where preventable emergencies live.

First, the words

Families use a few terms for the same idea. You will hear looping system, automated insulin delivery (AID), hybrid closed loop, or simply the loop. They all describe a system where a continuous glucose monitor and an insulin pump talk to each other through an algorithm that adjusts insulin automatically.

The word hybrid matters. These systems are not fully automatic. They automate background insulin and can deliver correction doses on their own, but meals still require someone to announce or bolus the carbohydrates. So the system is doing part of the work and a person is doing the rest. That split is exactly where school-day problems come from.

How a looping system works

Three parts, working together:

• The sensor measures glucose under the skin every few minutes and sends a number to the system.
• The algorithm predicts where glucose is heading and decides what insulin is needed. On many systems the algorithm runs inside the pump. On others it runs on a pod or on the student's phone.
• The pump delivers that insulin as small automatic adjustments, and pauses delivery when the algorithm predicts a low.

The system is reacting to a prediction, not to a single number. That is why it can suspend insulin before a low happens, and why it can quietly deliver extra insulin when it thinks a high is coming. Many systems also have modes the family switches on: a sleep mode with tighter targets, an activity or temp target mode, and a manual mode.

What the system cannot do is sense what it cannot see. If the sensor reading is off, if the phone is out of range, or if nobody tells the system that the student just ate, the algorithm is making careful decisions based on the wrong picture. When a child is in a classroom with a substitute teacher, a phone locked in the office, and a sensor that came off during PE, the system is not looping. It is guessing, or worse, doing nothing at all.

What a working loop gives a student at school

The upside is real and worth naming, because it is why families fight to keep these systems in their children's hands.

• Fewer and shallower lows, including during and after activity, when the system predicts a fall and eases off insulin.
• Less time in high ranges, which affects mood, focus and how a student feels in class.
• Fewer interruptions to learning. A system that pauses insulin on its own means fewer trips out of class, fewer snacks in the middle of a lesson, and less attention drawn to the student.
• Data the nurse can actually see, so patterns become visible instead of anecdotal.
• Less reliance on a single adult's memory, which matters on the days that adult is at lunch, in another building, or out sick.

That is the promise. Now the part families learn the hard way.

How looping systems fail

Failures cluster in five places. Nearly every difficult school day traces back to one of them.

1. The sensor fails. Sensors expire mid-school-day, get knocked off in PE, or read inaccurately. A compression low from lying or pressing on the sensor during floor time can look like a dramatic crash when the student is fine. The first day of a new sensor is often the least accurate.

2. The connection fails. These systems run on Bluetooth and short range. Bluetooth between the sensor and the pump or phone drops. The phone goes into a locker or a backpack and the system loses its link. The phone battery dies at 11am. A phone that is treated as a distraction and taken away for the day is a loop that has been switched off without anyone deciding to switch it off.

3. The pump or site fails. Insulin delivery problems are the ones that turn serious fastest: a kinked cannula, an occluded line, an empty reservoir, a pod that got knocked loose during a scrimmage, insulin that sat too long in a hot car or hot gym bag. The device reports high glucose and the student is not receiving insulin at all.

4. The algorithm drops out of auto mode. Systems routinely exit automated mode or enter a limited state. Sometimes that happens for a good reason, and sometimes a student or an unfamiliar adult dismisses the message and keeps going. A system that quietly spends the afternoon in manual mode is no longer looping. Nobody notices, because nothing sounds an alarm about an alarm.

5. The humans around the system fail it. Carbs eaten but never announced. A snack given for a low while the system is still in activity mode. Alarms silenced during a test. A phone put in the student's backpack so it is not "out during class." An adult who does not know what the alert on the screen means, and dismisses it because it keeps beeping. This is the most common and the most fixable category.

The risk of ignoring alarms and errors

An alarm on a looping system is not an annoyance. It is a component telling you it can no longer do its job.

• Ignored delivery alarms escalate into DKA. When insulin delivery stops, high glucose is not the only outcome. Insulin delivery failure in a student on a pump is a medical situation measured in hours, which is why a stubborn high on a looping system should prompt a check for a delivery problem and a ketone check as directed by the DMMP. It is not a wait-and-see high.
• Ignored sensor problems cause wrong decisions. If the system is dosing based on an inaccurate reading, it can under-deliver or over-deliver insulin. Over-correction on bad data becomes a low an hour later. An adult who knows only the number on the screen, and not that the number may be wrong, cannot catch it.
• Dismissed alerts become invisible alerts. Once alarms are repeatedly silenced, the day runs on stale data. The system is still making decisions, nobody is watching them, and no one can say later what actually happened. That is also how a documented pattern gets lost, which is often the difference between an incident being understood and an incident being repeated.
• A "quiet" system can be a broken system. Silence is not the same as working. The most dangerous state is a loop that has stopped communicating, a phone in a locker, and staff who think everything is fine because nothing is beeping.

How looping fits into the school day

The plan is not to think about the loop constantly. It is to build the loop into the day at the moments that matter.

• Arrival. Confirm the system is in the mode the family expects for a school day, the sensor is current, the reservoir has insulin, and the phone is charged and with the student. This takes a minute and prevents most 1pm surprises.
• Meals and snacks. Be explicit about who announces carbohydrates and where: does the student do it, or does the nurse, and at what point in the lunch line. An unannounced snack is a system working on incomplete information.
• Recess and PE. Activity should be planned for before it starts, not treated after symptoms appear. That usually means switching to an activity or temp target ahead of time, ensuring fast-acting carbohydrate is within reach, and knowing that a sensor on an arm or abdomen may need a different plan for contact sports.
• Tests and quiet periods. Decide in advance how alerts are handled so the student is not choosing between managing their diabetes and disrupting an exam, and so no one silences the system to keep the room quiet.
• Device issues. The moment something comes off, dies, runs out, or stops communicating, the plan should say who is called and how quickly.
• Dismissal and after-school activities. Who confirms the system is running, that the phone left with the student, and how the parent is informed of anything that happened with the technology during the day.
• Phone as medical equipment. A looping system's phone is not a distraction and should not be collected, locked in a pouch, or powered down. It needs to stay on, charged, and near the body, including during testing and assemblies.

Why school staff knowledge is not optional

You can have a perfect loop and still have a bad day, because the algorithm makes decisions in the background and the people around it make decisions in the foreground.

Staff who understand the system can do three things that change outcomes:

• Recognize the states that matter. The difference between an informational beep and a delivery alarm, and what it means when the system says insulin delivery is suspended, or that auto mode has turned off.
• Troubleshoot the ordinary failures. Check that the sensor is still attached, that the phone and pump are near each other and charged, that the reservoir is not empty, and verify with a fingerstick when the reading does not match how the student looks or feels.
• Escalate on the right ladder. Nurse, then parent, then provider, and 911 for a severe low or symptoms concerning for DKA. That sequence belongs in the plan, written out, so no one has to invent it under pressure.

Two boundaries worth stating plainly. Staff should never change pump settings, algorithm targets, or dosing to fix a problem. Settings belong to the family and care provider. And school staff should never be the last line of defense for a device problem. The system fails, the student is not getting insulin, and the response should already be written down.

What the school care plan should say about the loop

A care plan that does not describe the student's actual system leaves the school team to infer it. Most strong plans cover:

• The specific system in use, and which parts live on the body versus on a phone.
• The normal school-day mode, and who is allowed to change it, if anyone.
• Which alerts must never be silenced, and what each one means in plain language.
• Where backup supplies live: spare sensor, extra pod or pump supplies, backup insulin and a syringe or pen per the DMMP, ketone strips, fast-acting carbohydrate.
• The student's self-management level: does your child insert their own sensor, announce their own carbs, or need hands-on help?
• What to do when the sensor fails or becomes unreliable, and what fallback monitoring schedule applies.
• Fingerstick expectations, including when to verify rather than trust the reading.
• The escalation ladder with names and numbers.
• Who documents device issues, and where, so patterns become visible.
• A review date, because device setups change and the plan should change with them.

Looping technology is excellent at the part of diabetes care that never stops. It cannot replace the adults around it knowing what a failure looks like. That knowledge is a training issue, a plan issue, and ultimately a safety issue, and it is one of the most straightforward gaps a school can close.

This article is a planning aid and not medical or legal advice. Always follow the student's DMMP, physician orders, and your school or district policy. In an emergency, treat first and call 911.

In hope for a cure, until then keeping the good fight.

Jacqueline