Tracking progress in Konfir is straightforward: each verification has an overall verification status, and (once submitted) each employment/gap in the timeline has an activity status.
Track progress in Konsole
1) Find the verification you need
Use your Konsole dashboard to locate the verification by searching for the applicant and opening the relevant request.
2) Check the verification status (overall request)
At the top of the verification page you’ll see the verification status bar. This tells you whether the applicant has submitted and whether results are ready.
Status | What it means | What to do next |
| The applicant hasn’t submitted yet. | Follow up with the applicant using your normal process (or resend the link via your workflow). |
| The applicant has submitted. Results are ready. | Open the timeline and review activity outcomes. |
| The verification ended before completion (a reason is usually shown). | Decide whether to retry or switch to your fallback process. Client Help Center (Current)v1 |
For definitions of cancellation reasons, see Understanding verification statuses.
3) If the verification is Completed, review the timeline
The Employment History Timeline is the main way to understand what has (and hasn’t) been verified. Activities are shown most-recent first, and each has an activity status.
If you are tracking operational progress (rather than interpreting results), the key thing to note is whether activities are Verified, Connected, or Not Connected.
For more information, see the Understanding Results collection
Track progress via API
If you create verifications via API, you can track progress in two complementary ways:
Webhooks (recommended)
Konfir can post lifecycle events to your webhook endpoint when key steps happen, such as when a verification is completed.
Polling (fallback)
If you do not use webhooks, you can still retrieve verification data via API and determine the latest status from the response.
For technical details (events, schemas, delivery expectations), see Webhooks overview in the API documentation section.