What it does
Application events cover more than twenty distinct types: the application itself, interview scheduling, starting, completing, or cancelling, scoring, a stage change, a review outcome change, a shortlist change, notes, tags added or removed, flags added or removed, a rating being set, a screening rule matching and its action firing, an email being sent, opened, or clicked, the application being viewed by an employer, an external-apply redirect, a general status change, and the full offer lifecycle from created through sent, viewed, accepted, declined, or withdrawn.
Each event records who or what triggered it, a candidate, an employer user, an admin, the system, or an automated rule. The log itself never blocks the action that caused it, if writing an event fails for some reason, that failure is caught and swallowed rather than breaking the actual pipeline action.
How it works
- 1
An action happens on an application
A candidate applies, an interview completes, a recruiter adds a note or changes a stage, a screening rule fires, or an email gets opened, any of these triggers a corresponding event.
- 2
The event is written with its actor
Each event records which type it was and who or what caused it, whether that's the candidate, an employer teammate, an admin, an automated rule, or the system itself.
- 3
Writing an event never breaks the underlying action
Event logging is designed to fail safely. If a write to the event log itself errors, that error is caught and discarded rather than propagating up and interrupting whatever action was actually happening.
- 4
The timeline is pulled per application
An employer can view the ordered event history for any application inside their own account. Admins can pull the timeline for any application across the platform when needed.
More than a pipeline stage log
Stage changes are one of over twenty event types recorded, alongside scoring, notes, tags, flags, ratings, rule matches, email engagement, and offer actions. A recruiter reviewing a candidate's timeline sees a full account of what happened, not just which column they're sitting in today.
Screening rules and email engagement show up too
When a screening rule matches a candidate and its action fires, that's its own logged event, rule_matched alongside rule_action_applied. When an email sent to that candidate gets opened or clicked, that's logged as well, so the timeline connects automated actions and communication history to the same record as manual pipeline changes.
The offer lifecycle is fully represented
Every stage of an offer, created, sent, viewed, accepted, declined, or withdrawn, writes its own event to the same timeline. A recruiter doesn't need to check the offer record separately to see when a candidate opened it or how they responded.
Logging is never a point of failure
Because a failed event write is caught rather than allowed to break anything, the timeline is a best-effort record, not a hard dependency the rest of the pipeline could fail because of. The tradeoff is explicit: reliability of the underlying action always wins over completeness of the log.
Who it's for
Who this is for
This is for a recruiter or hiring manager who needs to understand exactly what happened on a specific candidate, not just where they currently sit, and for an admin who needs to review a hiring process end to end, including automated rule actions and email engagement, without piecing it together from several different screens.
Frequently asked questions
What kinds of events show up in a candidate's timeline?
More than twenty types, including applying, interview scheduling and completion, scoring, stage changes, notes, tags, flags, ratings, screening rule matches, email sends and opens, and every step of the offer lifecycle from creation through accepted, declined, or withdrawn.
Who can see a candidate's event timeline?
An employer can view the timeline for applications within their own account. Admins can view the timeline for any application across the platform.
Does the timeline show who or what triggered each event?
Yes. Every event records its actor, whether that's the candidate, an employer teammate, an admin, an automated screening rule, or the system itself.
Can logging an event ever break the action it's recording?
No. Event logging is designed to fail safely, if writing the event itself errors, that error is caught and discarded rather than interrupting the actual pipeline action that triggered it.
Related pages
See the full history behind every candidate, not just their current stage
Pull up the event timeline for any application and see exactly what happened, and who or what caused it.