AI-assisted evidence capture for scalable exam programs
Human review before an integrity decision
Real-time invigilation with AI-assisted prioritisation
Connect Proctor to an existing assessment workflow
Constructor Proctor is AI-assisted online proctoring software for secure exams and assessments. It supports automated monitoring, post-exam review, and live oversight. Institutions choose the mode for each program, and their designated reviewers apply policy and make integrity decisions. Connect through LTI, the Moodle plugin, or APIs, or use Proctor with Constructor Assess.
Start with the stakes of the exam or assessment, the evidence your policy requires, and who must review it. Constructor Proctor lets institutions configure the operating model around those decisions.
| Decision | What to confirm | Constructor Proctor approach |
|---|---|---|
| Level of oversight | Whether the exam needs automated monitoring, review after submission, or real-time intervention | ✓ Automated monitoring, post-exam review, and live oversight configurations |
| Review responsibility | Who applies institutional policy and makes the integrity decision | ✓ Institution-designated reviewers can examine evidence and confirm findings |
| Candidate setup | Required devices, identity checks, accessibility needs, and permitted resources | ✓ Guided system checks and configurable exam rules before the session starts |
| Assessment workflow | How the proctoring step connects to exam delivery and result review | ✓ Connect through LTI, the Moodle plugin, APIs, or Constructor Assess |
| Evidence and reporting | Which events, recordings, and reports reviewers need to reach a defensible decision | ✓ Session evidence and integrity reports are available according to the selected configuration |
| Privacy and deployment | Data processing, hosting, retention, support, and implementation responsibilities | ✓ Confirm the required controls and service scope in the institutional proposal |
Configure identity checks, monitoring, browser controls, evidence, and reviewer workflows around the stakes of each exam or assessment.
Detect and organise potential session events for review, with checks configured around exam policy.
Apply device restrictions and allow-listed resources where the selected exam configuration requires them.
Use a candidate smartphone as an optional second view where that exam configuration is enabled.
A dispatching interface helps designated proctors monitor active sessions and prioritise alerts.
Chat and audio-video channels support proctor-to-candidate communication in live oversight configurations.
Confirm supported browsers, operating systems, and optional smartphone use during implementation.
Configure exam rules, time allowances, and permitted resources around approved candidate accommodations.
Review recorded evidence, session events, and integrity reports according to the selected configuration.
System checks and clear instructions help candidates prepare before the exam or assessment begins.
A typical Constructor Proctor workflow, adapted to the selected monitoring and review configuration.
Connect an exam from your LMS or Constructor Assess, select the oversight mode, and define the permitted resources and checks.
Give test-takers clear instructions and a guided system check before the scheduled session.
Use the identity and environment checks selected for the exam policy and candidate group.
The selected monitoring configuration records relevant session events and supporting evidence.
Where human review is enabled, institution-designated reviewers assess evidence against the institution’s policy.
Use the resulting report and available evidence in the institution’s decision and audit workflow.
Best for scalable, on-demand programs
AI-assisted monitoring records potential events and presents evidence in the institution’s configured workflow. Confirm when human review is required for the exam policy.
• Configurable monitoring
• Evidence for review
• Scales with scheduled demand
Best when evidence must be assessed before an integrity decision
Monitoring captures session evidence. A reviewer designated by the institution examines flagged events after the exam and applies institutional policy.
• Review after submission
• Institution-designated reviewers
• Integrity reports and supporting evidence
Best when support or intervention may be needed during the exam
Designated proctors monitor active sessions, with AI assistance to prioritise alerts and support candidate communication.
• Real-time oversight
• AI-assisted prioritisation
• Direct candidate communication
Support secure remote or hybrid exams and assessments, connect Proctor to the LMS or assessment platform, and give designated staff evidence for policy-based review.
Use configurable monitoring and reviewer workflows for professional certification, licensing, and public-sector exam programs.
Protect skills assessments and certification exams across employee, partner, and customer training programs.
Build a Proctor setup around the exam, review policy, integration, candidate requirements, and support model. Document the final service scope in the proposal and implementation plan.
Monitoring and review
Select the workflow that matches the exam stakes and institutional policy.
• Automated monitoring
• Post-exam review
• Live oversight
• Configurable identity and environment checks
• Session evidence and integrity reports
Platform and integration
Connect Proctor to the assessment workflow and document the operating responsibilities.
• LTI connections
• Dedicated Moodle plugin
• APIs for custom workflows
• Constructor Assess integration
• Candidate setup, support, hosting, and retention agreed during implementation
Connect Constructor Proctor to an existing learning or assessment workflow through LTI, the dedicated Moodle plugin, or APIs. Validate the exact platform, version, data flow, and support responsibilities during implementation.
• LTI connections for supported learning and assessment platforms
• Dedicated Moodle plugin
• Canvas, Blackboard, and D2L Brightspace scope confirmed for the institution’s environment
• Constructor Assess integration
• Document supported browser and operating-system requirements
• Add Secure Browser controls where the exam configuration requires them
• Use a smartphone as an optional second view where enabled
• Confirm SSO and identity flows during implementation
• APIs for custom workflows
• Product documentation and implementation guidance
• Integration testing before rollout
• Hosting, data processing, retention, and support responsibilities confirmed in the institutional proposal
For each deployment, confirm the current security evidence, data-processing terms, hosting, retention, accessibility support, subprocessors, and human-review responsibilities. Requirements vary by jurisdiction and exam configuration.
Review the current DPA, subprocessors, data locations, retention, and deletion terms.
Request the current certification scope, technical and organisational measures, and security-review evidence.
Document how the selected configuration supports the institution’s FERPA responsibilities.
Validate the current accessibility statement, supported accommodations, and known limitations for the candidate workflow.
Confirm age, parental-consent, school-data, and monitoring requirements where applicable.
Document the monitoring purpose, human oversight, risk assessment, and institutional decision policy.
Review the data-protection and AI rules that apply to the institution, candidate location, and hosting model.
Define who reviews evidence, who can intervene, and who makes the final integrity decision.
• Use the least intrusive controls that meet the exam’s integrity requirements.
• Tell candidates which devices, checks, recordings, and permitted resources apply.
• Assign who monitors, who reviews evidence, and who makes the integrity decision.
• Pilot the full workflow under realistic exam conditions before scaling it.
• Reconfirm current security, privacy, accessibility, hosting, retention, and support evidence during procurement.
Data processing depends on the selected exam configuration and service scope. Institutions should review the current DPA, technical and organisational measures, subprocessors, hosting, retention, access controls, and deletion process before rollout.
Candidates receive instructions and a system check before the session. Identity checks, environment checks, recordings, browser controls, and support channels depend on the selected configuration; institutions should disclose those requirements before exam day.
Responsibility depends on the operating model. Automated workflows surface evidence for the configured process. Post-exam and live oversight use institution-designated reviewers or contracted staffing where agreed. The proposal should name who monitors, reviews, and makes the final integrity decision.
Pricing is volume based. A quote depends on exam volume and the selected monitoring, review, implementation, and support scope.
Constructor Proctor connects through LTI, a dedicated Moodle plugin, and APIs, and can also be used with Constructor Assess. Confirm the exact platform, version, data flow, and implementation responsibility for your environment.
