Technology, injections & supplies

CGM lag and trusting symptoms

Sensors read a few minutes behind your actual glucose. Why the feeling of a low outranks the number on screen.

Written by Updated 15 May 2026 6 min read
The 60-second answer

Your sensor is always reading a few minutes behind your actual blood glucose, so when things are moving fast, the number on screen is the past, not the now. If you feel low, treat the feeling. Don’t wait for the sensor to agree.

  • A CGM (continuous glucose monitor, the sensor on your arm) reads the fluid between your cells, not your blood, so it lags roughly 5 to 15 minutes behind.
  • When glucose is dropping quickly, the sensor number is higher than your blood actually is, which is exactly when a hypo (glucose too low, under 4 mmol/L) can catch you out.
  • If you feel shaky, sweaty or confused, do a finger-prick check if you can, and treat a low without waiting for the graph to catch up.
  • The trend arrow (which way glucose is heading) tells you more in a fast-moving moment than the single number does.
The mechanism

Why the number is always a little behind

Your CGM doesn’t sit in a blood vessel. The little filament under your skin reads glucose in the interstitial fluid, which is the fluid around your cells. Glucose gets there from the blood, and that takes time.

When your blood glucose is steady, the two track each other closely and the lag barely matters. But when glucose is changing fast, up after a meal or down during exercise, the interstitial fluid hasn’t caught up yet. So the screen shows where you were several minutes ago, not where you are.

This is why a sensor reading of 5.5 with a sharp downward arrow is not the same situation as 5.5 sitting flat. In the first case, your blood may already be under 4.

What to do with it

When the sensor and your body disagree, trust your body

You were probably told at some point that CGM means you don’t need to finger-prick as much. Mostly true. But there’s one situation where it flips: when what you feel doesn’t match what the screen says.

If you feel low but the sensor says you’re fine, believe the feeling and check with a finger-prick. If you can’t check right then, treat as a low anyway. The cost of eating some fast sugar you didn’t strictly need is small. The cost of ignoring a real hypo because a lagging number said 6 is not.

This isn’t the sensor being faulty. It’s the sensor doing exactly what it does, showing you a slightly delayed picture. Your job is to know when that delay matters.

Reading it better

The arrow is doing the work the number can’t

The single number tells you where you were. The trend arrow tells you where you’re going, and in a moving moment that’s the more useful piece of information.

A flat arrow means glucose is roughly stable, so the number is close to real. A steep arrow, up or down, means the number is already out of date by the time you read it, and the real value is further along in the direction the arrow points. Before you drive, before exercise, or before bed, the arrow changes what a “fine” number actually means.

What varies

What changes how big the lag feels

The lag isn’t a fixed number of minutes for everyone. It’s largest when glucose is changing quickly, which is why it bites during and after exercise, after a fast-acting meal, or when a hypo is coming on. Different sensors handle it differently, and a brand-new sensor in its first day can read further off than a settled one. Lying on a sensor overnight (a “compression low”) can also show a drop that isn’t real.

how fast glucose is movingexercisethe sensor brandthe first day of a new sensorpressure on the sensor while you sleephow well hydrated you are
Real-life examples

When the gap matters

Examples, not instructions or doses.

A fast drop after the gym

Your sensor says 6.2 with a steep down arrow. You feel a bit off. Your blood may already be under 4, because the drop is faster than the sensor can keep up with. This is a treat-now moment, not a wait-and-see one.

The morning after a new sensor

You put a sensor on last night and this morning it reads 3.8, but you feel completely normal. A finger-prick says 6.1. First-day sensors and overnight pressure can both read low. Checking with blood settles it.

Feeling low, screen says fine

You’re shaky and sweating, the classic signs, but the graph shows a flat 5.8. Believe your body. Check if you can, and treat the low. The number is the past.

Steady all afternoon

You’ve been sitting at a flat 7 for two hours with no arrow. Here the sensor and your blood are close, and a finger-prick would mostly just confirm what you already know.

What to notice

Worth paying attention to

If you feel low, treat it, even when the sensor disagrees. Feeling comes first.
A steep arrow means the number is already out of date. Read the direction, not just the digit.
For driving, current DVLA rules do let you use your CGM or flash sensor to check, but you must confirm with a finger-prick if it reads 4.0 mmol/L or below, if you feel low, or if the reading does not match how you feel. You need to be above 5 mmol/L to drive, having checked no more than two hours before you set off, and again every couple of hours on a long experience.
A sudden low overnight that you did not feel and that recovers on its own may be a compression low from lying on the sensor.
If your sensor and finger-pricks keep disagreeing by a lot when glucose is steady, the sensor may be off and worth replacing or reporting.
What to ask your team

Questions that make an appointment useful

"When should I still finger-prick even though I have a CGM?"
"What are the DVLA rules for checking glucose before I drive with a sensor?"
"How should I read the trend arrows on my specific sensor before exercise or bed?"
"My sensor and my meter disagree by a lot even when I am steady. Is that expected, or should I report it?"
"How low should I let a downward arrow go before I act, rather than waiting for the number?"
Sources