Trust methodology
Evidence before coverage
AbstractsDue is designed around one asymmetric risk: omitting a date is inconvenient; publishing the wrong date can cost someone a submission.
What counts as evidence
Only a page controlled by the organiser, or a submission platform linked from that page, can support a published deadline. Search results and conference directories can help locate a moved page, but their snippets never count as evidence.
How a date is confirmed
Today every published date is entered by hand from the organiser's own page, and each conference page shows when it was last confirmed. We are building an automated recheck that re-reads registered official sources; when it is running, two isolated extraction passes must agree, the date must pass edition, event-order and stale-page checks, and its exact supporting quotation must occur in the fetched text. Until it is reliable, anything it finds goes to a person before it reaches the site. The status page says whether it is currently working.
What happens when evidence changes
A changed or missing date enters rechecking. Near-term uncertainty is withheld sooner than uncertainty around a distant event. Conflicting official sources are suppressed immediately. We never publish a candidate date merely because it looks plausible.
What the labels mean
- Official source confirmed
- The date was read on the organiser's own page on the date shown.
- Corroborated
- Two distinct official pages support the same date.
- Rechecking
- The source changed and the previous date is inside its limited warning window.
- Temporarily withheld
- The evidence is unresolved, so the date is excluded from lists and feeds.
Limits
No automated system can promise perfect accuracy. Always confirm before submitting, booking or paying. The defensible promise is narrower: every displayed date retains official evidence, and uncertainty is withheld rather than guessed.