Which happened first? The answer can change a decision
A resident submits a form before midnight, but the processing database records it after midnight. Event sequencing reconstructs the order of relevant actions without confusing user events, network delays and later system processing.
Identify the events
Submission, receipt, validation, payment, acknowledgement and case creation may occur at different times.
Preserve event identifiers
Reliable references help connect records across systems and distinguish repeated attempts.
Interpret timestamps carefully
Time zones, clock synchronisation and processing delays can affect recorded times.
Use multiple evidence sources
Application logs, payment records and notifications may each describe a different stage.
Avoid assuming arrival order equals event order
Distributed systems can process messages late or out of sequence.
Apply the governing rule
Technical reconstruction informs decisions, but applicable policy or law determines which event matters.
Break-test: two events share the same displayed second
Can the agency identify whether more precise or independent evidence is available without inventing certainty?
Connected knowledge
See Timestamp Verification, Evidence Chain of Custody and GovTech.