The IOB Guide for T1D — Part 2

Different Models For Calculating Insulin On Board

Part 1 explained how rapid-acting insulin behaves biologically. Part 2 turns to how diabetes devices attempt to model that insulin mathematically. These are not the same thing — and understanding the difference is what makes the trade-offs legible.

Your body and your device are using different systems

Your body runs on pharmacodynamics. Your diabetes device uses mathematics and decay algorithms. Physiological insulin action is variable, dose-dependent, and influenced by dozens of biological factors. Device IOB models are simplified. They have to be.

The key point

Once the selected AIT/DIA time window ends, the displayed IOB becomes 0.0 — regardless of whether physiological insulin activity is still present.

What devices are actually calculating

Devices define IOB using three inputs: the Active Insulin Time (AIT/DIA) setting, a mathematical decay curve, and the total insulin delivered within the time window. None of these inputs know about your body weight, your current insulin sensitivity, or whether the insulin you gave was for food or for a correction. That matters enormously — and it is at the root of almost every frustrating IOB experience.

How physiological insulin exposure from a 0.2 U/kg bolus is massively under-represented when AIT is set to 2, 4, or 6 hours

Carbohydrate absorption: the other moving variable

Devices are trying to match variable insulin with variable glucose appearance. Carbohydrate absorption is not a fixed curve. Simple carbohydrates and high glycaemic foods can lead to rapid glucose appearance, while meals containing fibre, fat, or protein often slow digestion and produce a more gradual rise. Some meals, particularly those high in fat, can delay glucose appearance for several hours. Gastric emptying speed, gut hormones, individual digestive physiology, and conditions such as gastroparesis all further influence the picture.

Glucose appearance from carbohydrate over time: rapid to slow absorption patterns and the factors that influence them

In other words, we are trying to match variable insulin with variable glucose appearance using a simplified model. Is it any wonder managing Type 1 diabetes can sometimes feel like a proper graft?

The meal insulin vs correction insulin problem

Most systems do not distinguish between insulin given for carbohydrate and insulin given for correction. They are lumped together as IOB. This is problematic because meal insulin is often still covering carbohydrate that has not yet finished digesting. Only the correction insulin is targeting excess glucose in circulation. Physiologically, these behave differently. Mathematically, most devices treat them the same.

High IOB blocks a correction

You take 14 units total: 10 units for food and 4 units for correction. Your AIT/DIA is set to 4 hours and the bolus calculator treats everything as one pool of IOB. Two hours later, when glucose is still entering circulation because your meal has not been fully digested, your glucose is 13.9 mmol/L (250 mg/dL) and rising. You expect a correction. The device says no.

How total IOB blocks a correction when meal insulin and correction insulin are pooled together

It sees approximately 4 units of total IOB and blocks insulin — even though only approximately 1 unit may be true correction insulin, and the rest is still covering food that has not been absorbed yet. When carbohydrate has been underestimated, which happens 30 to 50% of the time, the algorithm assumes it is preventing stacking by treating all bolus insulin as one pool.

The calculator does not know why insulin was given. It only knows how much was delivered and how much remains within the model. Most of the insulin still circulating is actually meal insulin working against carbohydrate absorption — not free correction insulin, which is the one that matters in this situation.

So what happens in real life? You override. You ghost-carb. You inject by pen. Glucose comes down. You avoid hours of hyperglycaemia. Later, someone says, “Just trust the technology.”

You think: Foxtrot Oscar.

But this is not about trust. It is about modelling. The algorithm sees total risk. Humans think dynamically: food versus correction versus activity. These are the two jobs in conflict.

Why shortening AIT works for tighter glucose management

Consider someone who consistently runs high at 2 to 3 hours post-meal due to carbohydrate underestimation. With AIT set at 5 hours, the system may show substantial IOB and suppress a correction, because it assumes insulin is still active. But if much of that insulin is still dealing with unabsorbed carbohydrate, a correction may in fact be physiologically appropriate. So they shorten AIT to 2 hours, which reduces displayed IOB sooner and allows more aggressive corrections.

How a 2-hour AIT allows the full correction dose that a 4-hour AIT blocks — and the hidden physiological cost

On paper, that looks logical. But physiologically, there is still correction insulin working in the background — about 2 units. The result: you may overshoot by roughly 2 units.

Now imagine there is no food involved, just a very high glucose — say 20 mmol/L (360 mg/dL) — and you are correcting every two hours. Because the algorithm treats bolus insulin as effectively gone at 2 hours, it keeps offering full corrections each time. But in reality, some insulin from the previous dose is still active. This is where insulin stacking risk rises quickly.

Not user error — model architecture

A short AIT compresses the model’s memory of insulin action. Each new correction is calculated as if the previous one has finished, even when physiology has not caught up yet. When the screen shows 0.0 IOB, many people reasonably assume they are bolus insulin-free. That assumption can create a false sense of security — particularly before exercise, which supercharges insulin, or when giving repeated corrections every two hours.

The predictable results are: unexpected exercise hypoglycaemia, late crashes after stacked corrections, and loss of trust in the bolus calculator. This is not about good or bad settings. It is about what you are optimising for.

Not all IOB models are identical

There are three main approaches to how devices handle IOB in correction calculations.

Model 1: No IOB deduction from corrections

Some systems display IOB but do not use it to reduce correction recommendations. The full calculated correction is always offered. This approach gives maximum correction freedom but carries the highest insulin stacking risk. The displayed IOB, often calculated using a 4 to 6 hour duration, still provides useful information about total circulating insulin for exercise planning — but this information is advisory only, not used by the calculator.

Model 2: Correction-only IOB

Only insulin given explicitly as a correction dose blocks further corrections. Meal boluses are excluded from the correction calculation. This improves correction logic and may reduce stacking from aggressive correction calculations. However, it risks over-correction early after meals, can underestimate true circulating insulin, and may increase hypoglycaemia risk with high-glycaemic meals or when pre-bolusing is inconsistent. It solves one problem but creates others.

Some bolus calculators that exclude meal insulin from correction logic still display both meal and correction insulin on the screen. This transparency helps mitigate the risk. It is essential to check how your system presents this information.

Model 3: Total IOB (meal plus correction pooled)

All insulin — both meal and correction — counts against further corrections. This provides the most stacking protection and the most realistic representation of total circulating insulin for exercise risk. The trade-off is that it can block needed corrections when carbohydrates are underestimated, and may produce persistent hyperglycaemia if corrections are restricted for too long.

The core trade-off: short AIT gives correction freedom, long AIT gives physiological accuracy — but both cannot be fully optimised simultaneously
How different IOB models change the correction offered from the same physiological situation: no IOB = 4 units, correction IOB only = 2 units, meal + correction pooled = 0 units

The trade-off nobody explains

You can optimise AIT for correction performance (shorter AIT, 2 to 3 hours) or for physiological accuracy (longer AIT, 4 to 6 hours). But you cannot perfectly optimise for both at the same time if meal and correction insulin are grouped together. This is the structural limitation of current IOB models. It is not user error. It is a model architecture decision.

Shorter AIT (2–3 hours)

  • More aggressive corrections
  • Lower IOB deducted sooner
  • Greater correction freedom
  • Lower visibility of circulating insulin
  • Higher exercise hypoglycaemia risk

Longer AIT (4–6 hours)

  • More stacking protection
  • More IOB deducted for longer
  • Corrections more restricted
  • Better visibility of circulating insulin
  • Better exercise hypoglycaemia risk awareness

Linear vs curvilinear decay models

Most commercial systems use one of two mathematical decay shapes. Linear degradation means insulin declines evenly over time. Curvilinear degradation means insulin falls more steeply early on, with a longer tail — which more closely mirrors actual pharmacodynamics.

In the curvilinear model, insulin action is front-loaded. The greatest glucose-lowering effect occurs in the first two hours after dosing. After this early peak phase, the rate of effect progressively slows. However, the chosen AIT/DIA duration matters more than the exact curve shape.

Practical implication

Getting the duration broadly right is the major issue. Whether the curve is linear or slightly curved is minor in comparison.

Linear vs curvilinear decay: the duration chosen matters more than the exact shape of the curve

Advanced models: offset, peak, and meal-rise settings

Some systems move beyond a simple one decay curve model by introducing the idea of the expected glucose rise after eating. Three settings allow personalisation:

  • Meal-rise expectation — an estimate of the peak glucose typical after meals for that individual (1.7 to 5.6 mmol/L or 30 to 100 mg/dL).
  • Offset time — at what point does glucose start to decrease from the peak meal-rise (45 to 120 minutes).
  • Acting time — an estimate of how long the insulin lasts (3 to 8 hours), creating the drop-off from the end of the offset time.
The offset + meal-rise + acting time model: how expected glucose behaviour after eating changes correction logic

With this model, corrections during the expected glucose rise phase are restricted, but once the glucose trajectory is expected to start falling, corrections become available again. This means the system avoids blocking corrections when they are genuinely needed — which is a meaningful improvement over pooled IOB models for post-meal management.

AID and hybrid closed-loop systems: an extra layer of complexity

Automated Insulin Delivery systems add a second layer: a user-facing bolus calculator and an internal control algorithm. These layers may not use the same insulin accounting. In practice, displayed IOB may not reflect total insulin exposure generated by automation.

Most systems distinguish between user-entered correction boluses and algorithm-driven micro-corrections, and may apply different decay assumptions to each. When insulin delivery falls below the expected level, this may display as negative IOB — indicating that circulating insulin exposure is lower than anticipated, which can help refine understanding of hypoglycaemia risk.

The key implication: what is displayed on screen may not fully represent what the algorithm is accounting for in the background. Despite these structural differences, the central tension remains. Insulin modelling must balance protection against over-correction while reflecting the front-loaded physiological action of rapid-acting insulin.

The detailed summary table

This table brings together the main IOB modelling approaches used in pumps, bolus calculators, and AID systems, and shows how different configuration choices influence day-to-day behaviour. A simplified version appears at the start of Part 3.

Model typeModeAggressivenessTypical settingsDaily behaviourAdvantagesRisksExercise and hypo trade-off
Linear / Curvilinear decayNo IOB deductionAggressiveAIT 2.0–2.5 hFull correction offered for every glucose above target.Full correction, no deductions.High insulin stacking risk. Multiple correction-induced hypos common.Undercorrection common if carbohydrate underestimated.
MediumAIT 3.0–3.5 hFull correction offered for every glucose above target.Full correction, no deductions.High insulin stacking risk.Insulin shown active longer, but exercise hypo risk underestimated.
ProtectiveAIT 4.5–6.0 hFull correction offered for every glucose above target.Full correction, no deductions.High insulin stacking risk.Insulin tail more visible, exercise hypo risk well estimated.
Linear / Curvilinear decayCorrection-only IOBAggressiveAIT 2.0–2.5 hCorrections in 1–3 hour post-meal window only minimally reduced.Rapid glucose corrections.High insulin stacking risk.Very poor insulin tail recognition. Exercise hypo risk massively underestimated.
MediumAIT 3.5–4.5 hCorrections reduced appropriately if recent correction insulin present.Balanced protection against stacking.Minor risk of correction stacking.Insulin active longer but exercise hypo risk underestimated.
ProtectiveAIT 5.0–6.0 hCorrections very conservatively reduced.Strong protection against correction stacking.Insulin beyond 3 hours under-represented.Insulin tail more visible, exercise risk well estimated.
Linear / Curvilinear decayMeal + correction pooled IOBAggressiveAIT 2.0–2.5 hCorrections reduced during 2–4 hour post-meal window.Some stacking protection.Meal insulin tail truncated. Early corrections may still stack.Very poor insulin tail recognition. Exercise hypo risk massively underestimated.
MediumAIT 3.5–4.5 hCorrections heavily reduced during 2–4 hour post-meal window.Strong stacking prevention.Insulin beyond 3 hours under-represented.Insulin shown active longer but exercise risk underestimated.
ProtectiveAIT 5.0–6.0 hPersistent hyperglycaemia if meal underestimated.Maximum stacking protection.Corrections frequently blocked for 4–6 hours.Insulin tail more visible and exercise risk better estimated.
Expected glucose after-meal behaviourCorrection IOB deducted outside expected glucose behaviourAggressiveAIT 3 h, Offset <60 min, Meal rise 1.7Insulin beyond 3 hours under-represented.Faster post-meal correction.Higher stacking risk if glucose rise prolonged.If displayed: exercise risk massively underestimated.
MediumAIT 4 h, Offset 60–120 min, Meal rise 3.0Corrections restricted during meal rise phase.Better post-meal trajectory governance.IOB remains hidden from user.If displayed: exercise risk underestimated.
ProtectiveAIT 6 h, Offset 120 min, Meal rise 6.0Corrections limited for longer.Minimises premature over-correction.Hyperglycaemia may persist.If displayed: exercise risk well estimated.
AID: User and algorithm separate IOBAggressiveAIT 2.0–2.5 hRapid user corrections and algorithm adjustments.Faster correction of highs.Higher hypo risk.Exercise hypo risk massively underestimated.
MediumAIT 3.0–4.0 hBalanced user and automated adjustments.Moderate corrections of highs.Earlier corrections allowed.Exercise risk still underestimated.
ProtectiveUser AIT 4.5–6.0 hPersistent hyperglycaemia possible.Reduced stacking risk.Hyperglycaemia if carbohydrates underestimated.Insulin tail visible and exercise risk well estimated.

Common workarounds — and the risks they carry

  • Shortening AIT to unlock corrections when the system feels too protective. This allows more aggressive corrections but can increase correction stacking and give a false sense of security when being active in the 2 to 4 hours after a bolus.
  • Repeated small corrections in the first 1 to 3 hours after eating. A common pathway to correction hypos — otherwise known as rage bolusing.
  • Ghost carbohydrates, pen injections, or manipulated correction factors. These may restore the ability to correct highs, but they undermine the accuracy of IOB tracking and can introduce unintended risks, particularly delayed insulin stacking and hypoglycaemia.
  • Using a behaviour-based app for exercise planning without a visible IOB number. If insulin exposure is hidden, the user may underestimate risk and over-trust a screen that looks safe.

The practical goal is not to eliminate trade-offs. It is to recognise which trade-off you are choosing, and then manage the predictable risks deliberately rather than reactively.

Part 3 examines how commercial AID and HCL systems model IOB in practice, breaking down the underlying logic, assumptions, and practical implications for users. For a comprehensive review of net IOB, read the excellent netIOB article from Professor Michael Riddell.

Continue the guide

Back to The IOB Guide for T1D

Verified by MonsterInsights