Migration Notice

Proctor migrates customers from the old version of the student web application to the new one.
The old version of the web application will no longer be developed or supported as of November 1.
New features and improvements are only being made in the latest version. We are giving time to test the new version and make a smooth transition.

Click here to read more

Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Project scoping

1. Learning Management System (LMS)

  • Which LMS will be used for exam delivery?

  • Specify whether the LMS supports integration via LTI, plugin, API, or requires SDK-level implementation.

  • Refer to the Proctor Inplementation Scoping Guide for detailed integration methods (Moodle, Blackboard, Canvas, custom-built systems).

  • Indicate whether a sandbox environment is required for testing purposes.


2. White Labeling (Brand Customization)

  • Is white labeling required?

  • Options:

    • Basic branding: Logo, colors, tab name (Learner interface).

    • Full branding: Custom domain hosting, server-side branding, and custom webapp.

  • Client must provide:

    • Logo

    • Brand guidelines (colors, fonts)

    • Domain details (for full whitelabeling)


3. Exam Sessions and Proctoring

  • How many exam sessions are planned?

  • Which proctoring mode will be used?

    • AI Review – Fully automated

    • Post-Exam Review – AI-assisted with human review

    • Live Proctoring – Real-time human monitoring

  • Expected number of learners per proctor?

  • Will mobile camera usage be required as a secondary angle?


4. Integration Type

  • What type of integration is planned?

    • API-based – Full flexibility, custom flow (longer implementation)

    • SDK – Embeds Proctor in a client’s custom app with lower development overhead

    • LTI or Plugin – For LMSs like Moodle, Canvas, Blackboard

5. Proctor WebApp Configuration

  • Are adjustments required to Proctor settings/UI?

  • Available configurations:

    • Security features: Developer tool blocking, process monitoring, minimal bandwidth enforcement

    • Anti-cheating settings: Clipboard blocking, window resizing detection, external screen detection

    • User experience: Chat visibility, finish exam button behavior, AI notification visibility

    • Custom support contact/email or help URL

  • Specify the exact changes required or request a consultation session to define these.

6. Translations and UI Text Modifications

  • Are translation overrides or button text modifications required?

  • You may request:

    • Language localization

    • Custom button names (e.g., "Start Exam", "Submit Test")

    • UI modifications based on accessibility needs

7. User Onboarding

  • Is onboarding required for exam participants or proctors?

  • Options:

    • Learners onboarding: System check walkthroughs, proctoring flow training (can be delivered via screencast or live demo)

    • Proctor onboarding: Live training session covering platform navigation, AI alerts, live monitoring, and post-review workflow

  • Standard delivery: 2-hour session (customized to customer’s exam scenarios)

8. Trial Plan (Optional)

  • Would you like to run a guided trial project before full deployment?

  • If yes:

    • Specify number of test-takers and trial exams

    • Confirm desired proctoring mode

    • Choose between no-integration or integrated pilot

    • Clarify if platform support is required during the trial