Before the launch window
The candidate sees that the exam is not open yet, with the scheduled time and support guidance.
Workflow
How ProctorEdge works.
From training-provider eligibility to a scheduled, browser-controlled exam attempt with owner-visible review records.
The complete exam delivery flow.
ProctorEdge connects the business workflow before the exam with the secure browser experience during the exam.
01
Candidate becomes a student
A candidate may come through marketing, inquiry, certification body, university, or training provider.
02
Provider confirms eligibility
The training provider confirms exam eligibility based on enrollment, completion, or approved readiness criteria.
03
Voucher is requested or assigned
The provider requests a voucher or assigns one from a prepaid bulk voucher inventory.
04
ProctorEdge schedules the attempt
Provider, candidate, exam, voucher, date, time, timezone, and launch window are bound into a scheduled attempt.
05
Candidate receives instructions
Browser installation steps, exam rules, timing, support information, and reminders are delivered before exam day.
06
Exam link activates
The exam URL becomes usable only during the approved launch window.
07
ProctorEdge Browser starts the exam
Normal browsers show instructions only. ProctorEdge Browser starts the exam after backend launch checks pass.
08
Events are reviewed
Browser events, continuity signals, blocked actions, and review notes become visible to authorized owners and reviewers.
Operating model
Who does what.
A clean operating model keeps candidates, providers, and ProctorEdge aligned before exam day.
| Stage | Candidate | Training provider | ProctorEdge |
|---|---|---|---|
| Enrollment | Joins course or exam pathway | Creates student context | Captures provider relationship where required |
| Eligibility | Completes required training | Approves student for exam | Validates exam and provider workflow |
| Voucher | Receives exam access through provider | Requests or assigns voucher | Confirms voucher validity and audit trail |
| Scheduling | Confirms availability | Coordinates with candidate | Creates scheduled attempt and launch window |
| Exam day | Installs browser and opens link on time | Supports candidate readiness | Validates launch and records session events |
| Review | Receives approved next step | Receives authorized status or result handoff | Runs owner/proctor/reviewer workflow |
Launch control
Exam link behavior.
The exam link is controlled by time, candidate, provider, voucher, browser, and policy.
In a normal browser
The page explains that the exam must be opened in ProctorEdge Browser and does not deliver exam content.
In ProctorEdge Browser
The backend validates the attempt and returns the approved exam route when all launch checks pass.
Expired or invalid link
The candidate sees a safe recovery path for rescheduling, support, or provider escalation.
Platform surfaces
Implementation surfaces.
The workflow is delivered through connected website, provider, backend, browser, and dashboard surfaces.
Marketing Website
Explains ProctorEdge, captures provider inquiries, and gives candidates clear exam-day instructions.
Provider Workflow
Manages provider-led student eligibility, voucher requests, scheduling coordination, and authorized visibility.
View voucher workflow →ProctorEdge Browser
Opens authorized exam links, enforces approved navigation, and records minimized browser events.
Secure Browser product →Exam Engine
Delivers MCQ exam sessions, voucher scheduling, launch validation, and candidate submission workflows.
Exam engine portal →Owner Dashboard
Shows attempt timelines, event review, notes, status, and audit records for authorized roles.
Monitoring dashboard →
Next steps
See the complete ProctorEdge workflow in action.
Talk to our team about provider vouchers, secure browser launch, and review-ready exam operations.