Split Dose and Post-Meal Learning: What iSpike Sees After a Late-Spiking Meal

When you tick the split option for a meal that tends to spike your blood sugar late — pizza, pasta, a big bowl of rice — it is natural to wonder whether iSpike is watching your whole response curve or just a snapshot at two hours.

This is a great question. Here is an honest, detailed answer about what iSpike currently does, and how to get the most accurate learning from meals that peak later than the two-hour mark.

What the Split Option Actually Does

The split option splits your mealtime units into two parts. You take the first part before eating, and iSpike sends a push notification to remind you to take the second part after a set delay — typically 30 minutes. This pattern can be useful for meals that are very high in fat or protein alongside carbohydrates, because the slower digestion means glucose rises more gradually and over a longer period.

The split option also adds a follow-up nudge if the second part has not been logged 15 minutes after the reminder fires, so you do not miss it.

How iSpike Learns from Your Post-Meal Glucose

Here is the important part: iSpike learns from a single post-meal glucose reading that you log yourself. The app sends a push notification at the two-hour mark reminding you to check your glucose and record it. Whatever value you enter at that point becomes the outcome iSpike uses to score the meal and update its memory for those foods.

This is the same behaviour whether or not split is ticked. The split option changes your dosing reminders — not the post-meal check timing.

So if you feel fine at two hours and your CGM shows you in range, but your glucose climbs further at three hours, iSpike does not automatically see that later rise. It scored the meal based on what you logged at two hours.

What To Do if Your Meal Peaks Late

If you know a particular meal tends to peak later — a lot of people find this with pizza, creamy pasta dishes, or large starchy meals — there is a simple workaround right now.

When the two-hour reminder arrives, you can ignore it or dismiss it and instead log your glucose at the point where you actually see your peak. iSpike uses whatever reading you enter and records that as the outcome, regardless of exactly when you log it. Over repeated meals, this gives iSpike a more representative outcome to learn from for foods that digest slowly.

You can also add a note to the meal to remind yourself that this was a late-peak meal.

What This Means for Your History

When iSpike has seen a food produce a high outcome in the past, it factors that into the analysis the next time you eat the same food. It can suggest a small adjustment to the estimate — slightly higher to account for a meal that tends to run high. The more times you log an outcome, the more confident that pattern becomes.

The key is making sure the outcome you log is the one that actually reflects how the meal affected you — not just how you happened to feel at exactly two hours.

A Note on These Records

Everything iSpike records is meant to be a log and an estimate for you to review with your diabetes care team. The app does not make clinical recommendations. The patterns it surfaces are a starting point for a conversation, not a prescription.

If you find that a particular type of meal consistently catches you out at three or four hours, that is worth raising with your team — they may have strategies beyond timing your split that are worth exploring.

What We Are Looking At for the Future

Automatically capturing the full post-meal curve from your CGM — not just a single snapshot — is something the team is aware of as a potential improvement, particularly for people who use a CGM full-time. For now, the manual log gives you full control over which reading becomes the outcome.

If you have thoughts on how post-meal learning could work better for your patterns, the feedback link in the app goes straight to the team.