Use actual delivery as the origin
Synthetic recipient R13 received M0 at 14:00. Local scheduling rule permits at least 60 minutes between actual deliveries. Candidate M1 at 14:20 is held; M2 at 15:15 is then evaluated. Held M1 has no delivery event. This is a fictional spacing choice, not consent, spam law or provider behaviour.
| Message | Time | Decision |
|---|---|---|
| M0 | 14:00 delivered | Clock origin |
| M1 | 14:20 candidate | Hold:20min gap |
| M2 | 15:15 candidate | Eligible:75min from M0 |
Evaluate candidates in order
- Read last actual M0 delivery
- Hold M1 for insufficient gap
- Retain 14:00 as origin
- Evaluate M2 at 75 minutes
Eligibility is a scheduling result, not proof M2 was actually delivered.
Does M2 meet the spacing rule?
Show the worked answer
Yes,75 minutes since M0. Measuring 55 minutes from held M1 would use an event that never happened.
Keep held candidates out of delivery history
| Case | Decision or result | Reason |
|---|---|---|
| Use held M1 as last delivery | Reject clock origin | No delivery event |
| M2 gap 75 from M0 | Eligible | At least 60 |
Keep candidate decisions and actual delivery records in separate columns. Apply the real organisation’s contact rules independently before any actual campaign operation.