How to Read Now-and-Next Information Quickly
A now-and-next checksum turns two compact labels into a traceable service, clock, interval, sequence, and freshness decision.
In short: Verify six things in order: service, current clock, time zone, “now” interval, following event, and data freshness. The current event should contain the guide clock; the next event should follow it on the same service. If boundaries overlap, leave a gap, or come from stale data, treat the labels as uncertain rather than choosing whichever title looks familiar.
Now-and-next rows are designed for speed, but their compactness hides the calculation beneath them. A title under “Now” is only as reliable as the selected service, schedule boundaries, clock conversion, and refresh state.
Run the six-point checksum
| Check | Pass condition | If it fails |
|---|---|---|
| 1. Service | Correct channel or service variant | Re-select or identify the service |
| 2. Clock | Device or guide clock is plausible | Correct clock or compare another source |
| 3. Zone | Display zone is known | Resolve zone before comparing times |
| 4. Now interval | Start ≤ current time < end | Mark current event uncertain |
| 5. Next event | First valid event after now | Investigate gap or overlap |
| 6. Freshness | Data covers the current boundary | Refresh or qualify the result |
This can be completed in seconds once the fields are visible.
Check the service first
Make sure the row belongs to the intended service, region, and time-shift variant. Channel branding may look identical across variants. Keep service metadata distinct from the program with the channel-versus-program guide.
Anchor the clock and zone
Read the current time shown by the device or interface and identify the zone used for guide display. If one device says 19:58 and another 20:58, do not compare program titles until you know whether the difference is a clock problem or zone conversion.
At a daylight-saving or travel boundary, use the time-zone worksheet instead of manually adding a remembered offset.
Calculate “now” from the interval
Use the published start and duration to derive the scheduled end:
Scheduled end = published start + published duration
The event qualifies as scheduled now when the current guide time is at or after its start and before its end. At the exact end boundary, the following event normally becomes current.
The DVB-I specification distinguishes published timing from optional actual timing. When actual start or duration is supplied, label it clearly; do not silently mix one actual boundary with one published boundary.
For detailed arithmetic, follow the program-duration method.
Identify “next” carefully
The next event is not simply the next card in visual order. It should be the earliest valid following event for the same service after the current event. Check its start boundary and identity.
If it begins before the current event ends, use the overlapping-listings diagnostic. If it begins later, record the schedule gap. Neither condition proves which program will actually air.
Read the progress bar as an estimate
A guide may calculate progress as:
Elapsed proportion = (current time − scheduled start) ÷ scheduled duration
This is precise arithmetic over potentially imperfect inputs. A bar at 75% does not independently confirm the broadcast is 75% complete. It describes where the guide clock falls within the scheduled interval.
Check freshness at the transition
A useful quick test is the most recent boundary. Did “next” become “now” when its scheduled start arrived? Does the data window continue beyond the current event? If not, run the program-guide freshness audit.
Record the result as current, plausible, conflicting, or unknown. W3C labeling guidance supports explicit control and state names; “Schedule not refreshed since 18:00” is clearer than a spinning icon or an unchanged “Now” label.
Handle common edge cases
- No current event: preserve the gap; do not promote the next title early.
- Two current candidates: investigate overlap, duplicate service rows, or mixed zones.
- No next event: check coverage horizon and refresh state.
- Midnight boundary: compare full date and time, not time alone.
- Late schedule change: prefer a clearly identified actual-time update when the source supplies it.
Norva can display live guide information from compatible authorized sources. The quality, coverage, and update timing of event metadata depend on those sources, so now-and-next remains a source-backed schedule interpretation.
Common mistakes and limitations
- Checking the title before the service.
- Ignoring the date near midnight.
- Treating card order as event order.
- Assuming the progress bar monitors the actual program.
- Promoting “next” across a schedule gap.
- Trusting a label after its data horizon ended.
Frequently asked questions
What happens at the exact end time?
Using a half-open interval, the old event ends and the following valid event becomes current at that boundary.
Can “Now” be right when the synopsis is wrong?
Yes. Timing and descriptive metadata can have different errors. Report the affected layer precisely.
Why is there no next event?
The schedule may be incomplete, stale, intentionally sparse, or beyond its coverage window. Check freshness before deciding.