01 · Observation
Read what was recorded
Review the process and available connection context. An observation does not establish why a tool was open or how it was used.
Interview protection
Surface signs of disallowed AI use before and during interviews.
Add a disclosed candidate check, protect meeting access, and give reviewers context for a considered follow-up.
Explore a prepared example. Sharing your own workflow is optional.
A finding, with the context to review it
What would your team do with this finding?
In this demonstration, the interview record contains an AI process and connection observation. The reviewer can inspect the record and clarify what happened before choosing a next step.
02 · Coverage
Check what was visible
Review session coverage and limitations. Supported observations depend on the active desktop agent and available checks.
03 · Follow-up
Ask, then record the decision
Clarify the finding with the candidate, consider the interview policy, and let the authorized team record the outcome.
A finding is a reason to review. No system detects every tool. A signal alone is not proof of intent
or an automatic reason to reject a candidate.
The practical journey
What candidates and interviewers actually do.
Set expectations before the call and keep an accountable reviewer involved throughout.
| Who | Before | During | After |
|---|---|---|---|
| Candidate | Read the notice, follow preparation instructions, and complete the required check before protected access is available. | Keep the required desktop agent active and follow the hiring organization’s interview policy. | Clarify any questions through the hiring organization’s stated contact route. |
| Hiring team | Explain permitted tools, preparation, support, and the accommodation or alternative route. | Review available observations and coverage. Address concerns with the candidate while context is fresh. | Consider the evidence, record follow-up, and decide the next hiring step. |
Candidate preparation
Make the requirements clear before interview day.
Candidates need preparation time and a person to contact when the required environment or check is unavailable.
Read the candidate privacy informationSoftware and readiness
The workflow uses a desktop agent. Confirm the currently supported device and operating-system requirements during rollout, and include the installation and readiness instructions in candidate communication.
Incomplete checks and support
Tell candidates whom to contact if a check cannot complete. The hiring organization owns exceptions, accommodations, and any alternative process.
Privacy and interpretation
Evidize does not record or stream the candidate’s screen. Explain the available observations and their limits, and keep candidate communication with the accountable hiring team.
Before you decide
Plan protection around your interview process.
What happens before the candidate joins the interview?
The candidate receives clear instructions and completes the disclosed check. The meeting link becomes available when the required steps are complete.
What can Evidize flag?
Evidize can flag signs that an AI assistant may be active, unusual interaction patterns, and checks with limited visibility. Reviewers see the available context; the product does not make an automatic employment decision.
Does a finding automatically reject a candidate?
No. A finding prompts review. Your team considers the context, records follow-up, and decides whether the candidate advances.
Can Evidize work with an existing interview process?
Yes. Recruiters can start from an Outlook appointment, employees can use their Microsoft work accounts, and Evidize adds protection around the existing remote interview process.
A complete example
See one interview from preparation to follow-up.
Walk through the candidate requirements, a finding in context, and the reviewer’s next step. We can use a prepared example; bringing your own workflow is optional.