Skip to content
ML Academy

Feature engineering and preprocessing · insight-1109

Replay logged arrival times to mask training features the way serving will see them

Evidence type
practitioner heuristic
Difficulty
hard
Roles
ML engineer, Data scientist
Industries
aviation, logistics

Summary: situation, action, reason, boundary

  1. Situation

    A feature comes from a feed that lands hours after the event; the warehouse history is complete, but a live scoring request often lacks the value.

  2. Action

    Using ingestion timestamps, give each training row only the latest value that had arrived by prediction time (missing if none); evaluate on this masked set next to the unmasked one.

  3. Reason

    What the model could see at prediction time, not when the event occurred, defines its inputs; the missingness pattern is part of the signal it will meet and must be learned.

  4. Boundary

    Late-arriving partner feeds, daily batch aggregates and corrected or backfilled records.

Symptom or risk

The model leans on a feature that is routinely absent or stale at prediction time, so live accuracy falls below any offline estimate.

Exceptions

Features guaranteed to arrive before scoring, or truly optional features.

Trade-offs

Needs reliable arrival timestamps and reduces the effective signal in training.

Pitfalls

Using the event time as the arrival time, or masking with a uniform random rate that matches nothing real.

Lessons and concepts

Claims and their sources