Technology, injections & supplies

Trust your CGM (but verify): first-day wobble, compression lows and when to reach for a fingerprick

When can I trust my CGM? First day is wildly off, and I get 'lows' when I lie on it at night.

Written by Updated 18 June 2026 8 min read
A person scans the sensor on their upper arm using a phone.
Photo by Sweet Life on Unsplash
The 60-second answer

A CGM (continuous glucose monitor, the sensor that tracks your glucose day and night) is brilliant, but it is not a blood test, and knowing when to double-check it keeps you safe. It reads the fluid just under your skin, not your blood directly, so it lags a few minutes behind when your glucose is moving fast, the first day of a new sensor is often the least accurate, and lying on it at night can force a false low. The golden rule is simple: when the number and how you feel disagree, do a fingerprick. Never ignore a real low because you assumed it was the sensor.

  • A CGM measures glucose in the fluid under your skin, which trails your actual blood glucose by several minutes, so it lags when you are rising or falling fast.
  • The first day of a new sensor is often the wobbliest, as it settles in, so treat early readings with a bit more caution.
  • Compression lows are false lows caused by lying on the sensor and squashing it, classically overnight, and they recover once you move off it.
  • The trend arrow matters as much as the number: it tells you which way, and how fast, you are heading.
  • When your symptoms and the reading disagree, or before you act on a surprising low, do a fingerprick (a blood test from your finger).
What it is measuring

Why the number lags real life

Your CGM does not test blood. A tiny filament sits in the fluid between your cells, called interstitial fluid, and glucose takes a few minutes to move from your blood into that fluid. When your glucose is steady, that gap barely matters. When it is moving fast, after a meal, during exercise, or while you treat a hypo, the sensor is reporting where you were a few minutes ago, not where you are now. That is why a CGM can still say 4.5 and falling while your fingerprick already reads lower, or why it keeps showing a low for a while after you have treated one and are actually climbing again. It is not broken, it is just always a step behind fast changes. Watching the trend arrow, which shows direction and speed, is how you read around that lag.

Day one

The first-day wobble is normal

Lots of people find a fresh sensor is at its least reliable on the first day, and sometimes through a short warm-up period after you put it on. The site is still settling and the readings can run oddly high or low, or jump around, before they steady up. This is common enough that it is worth expecting rather than panicking over. In the first day especially, lean on fingerpricks when a reading looks off or a treatment decision hangs on it, and if your device lets you calibrate (enter a fingerprick value to correct it), a check when your glucose is steady, not racing up or down, is the time to do it. If a sensor stays wildly wrong well past the first day, that is worth reporting to the manufacturer, as it may simply be a faulty one.

The 3am false alarm

Compression lows: when lying on it lies to you

A compression low is a false low caused by pressure on the sensor, most often from lying on it in your sleep. The weight squeezes the fluid around the filament, the sensor reads a sudden low, and the alarm wakes you convinced you are crashing. The tell is the pattern: it happens when you are lying on that side, the drop is steep and out of nowhere, and it bounces back up once you roll off. Here is the careful bit, though: you cannot assume every night-time low is compression, because sometimes you really are dropping. The safe move is always the same, a quick fingerprick settles it. If it reads fine once you have rolled off, it was compression; if it reads genuinely low, treat it. Wearing the sensor somewhere you do not sleep on can cut these right down.

The golden rule

When to trust your body over the number

The one habit that keeps CGM safe is this: if how you feel and what the sensor says do not match, do a fingerprick and trust that. If you feel low but the sensor says you are fine, check, because the sensor can lag or be wrong, and a real hypo does not wait. If the sensor screams low but you feel completely normal, still check before you pile in sugar, so you do not over-treat a compression low or a bit of lag. Other moments a fingerprick earns its place: the first day of a sensor, any reading that does not fit what you have been doing, and before driving, where the rules expect you to be sure. Trusting the tech and checking it are not opposites. The sensor catches the trends you would miss, and the fingerprick is your tie-breaker when it really matters.

What varies

What affects how accurate your CGM feels

Accuracy is not one fixed thing: the same sensor can feel spot on when you are steady and out by a fair bit when you are rising or falling fast. Placement, pressure, and how your particular body reacts to a new site all play in, and different devices behave differently. This is why a fingerprick check now and then is a normal part of using a CGM well, not a sign that anything is wrong.

the first day versus later in the wearhow fast your glucose is movingwhere the sensor is placedlying on it overnightwhether it has been knocked or is peelinghow your body settles a new sitethe specific device you use
Real-life examples

When to reach for a fingerprick

Examples, not instructions or doses.

The 3am low that was not real

Your alarm blares 3.1 and falling. You feel completely fine, and you are lying on your sensor arm. A fingerprick reads 6.2. It was a compression low, so you roll over and it climbs back on its own. Checking stopped you eating sugar you did not need.

Feeling low, sensor says fine

You feel shaky and sweaty but the CGM shows a steady 6. You trust your body and fingerprick anyway: it reads 3.6. The sensor was lagging behind a fast drop. You treat the real low rather than the reassuring number.

A wild first day

A new sensor reads a couple of points off your fingerprick all afternoon. Rather than act on it, you check by finger for the rest of the day, and by morning the sensor has settled and lines up. First-day wobble is normal, not a fault to panic over.

What to notice

Worth paying attention to

Keep a fingerprick kit and always have it available: a CGM does not replace it, it works alongside it.
Trust how you feel over the number: if you feel low, check and treat even if the sensor looks fine, because a real hypo will not wait.
Watch the trend arrow, not just the number, especially after meals, during exercise and while treating a low, when the sensor lags most.
Expect the first day of a sensor to be the least reliable, and lean on fingerpricks until it settles.
Check with a fingerprick before driving and follow the DVLA rules, which expect a confirmed, safe glucose before and during a drive.
What to ask your team

Questions that make an appointment useful

"When should I fingerprick rather than rely on my CGM, for driving, treatment decisions and odd readings?"
"My sensor keeps giving compression lows overnight: are there better places for me to wear it?"
"Should I be calibrating my device, and when is the right moment to do it?"
"The first day is always off for me: is that expected with my sensor, or worth reporting?"
"How do the DVLA glucose rules apply to me when I am using a CGM?"

When it's urgent

The reason the fingerprick rule matters so much is that a real low dismissed as a sensor glitch can become dangerous. If a hypo is not caught and someone becomes confused, cannot swallow safely, is fitting or passes out, that is a severe hypo and an emergency: whoever is with them should call 999, put them on their side, not force anything into their mouth, and use a glucagon kit if one is available and they know how. If you feel low and are at all unsure, treat it and check, do not wait for the sensor to agree. It is always safer to treat a low that turns out not to be real than to ignore one that is.

If this is happening now: what to do →
Sources