System compatibility check: how to prevent online assessment failures
What a system compatibility check covers, the thresholds to set, the tools to use and how to fix failures before an online assessment.

A system compatibility check is a short automated test that confirms a candidate's device, browser, camera, microphone and internet connection meet the technical requirements of an online assessment before it starts. Run it a day or two ahead, on the same setup the candidate will use, and most exam-day failures never happen.
TL;DR
- A system compatibility check tests device, operating system, browser, camera and mic, network, screen and proctoring tools against the requirements you set, with a pass or fail for each item.
- Send the check 24 to 48 hours before the assessment and run a short launch check again on the day, because updates and network changes can break a setup that passed.
- Set thresholds by assessment type. Published proctoring requirements range from 1 Mbps for a basic proctored exam to 10 Mbps download and 1.5 Mbps upload for strict live invigilation.
- Most failures come from blocked camera or mic permissions, unsupported browsers, VPNs and unstable Wi-Fi. Each has a known fix and an owner.
- A built-in check inside your assessment platform beats standalone utilities, because results land next to the candidate's scores and no one has to install anything.
- A failed check is a task to fix, not a reason to reject. Pew Research found 16% of US adults rely on a smartphone with no home broadband, so plan a fallback.

What is a system compatibility check?
A system compatibility check is a pre-assessment diagnostic that compares a candidate's hardware, software, network and environment with the minimum requirements of the test platform, then reports a pass or fail for each item. Recruiters see who is ready before the test link opens, and candidates fix problems before the clock starts.
The check is different from a general PC benchmark or a "can I run this game" tool. It measures only what the assessment needs: a working camera for proctoring, enough upload speed for recorded video answers, a supported browser for coding tasks, and a single screen when extra monitors are not allowed.
You will also see it called a system requirement check, a system diagnostic, a tech check, or a pre-exam system check. All of these names describe the same step.
Why does a system compatibility check matter before an assessment?
A system compatibility check matters because a technical failure turns a skills test into a test of the candidate's equipment. When a webcam drops or a browser crashes mid-test, the score no longer reflects ability, the candidate has a bad experience, and the hiring team loses days to reschedule.
- Fair results: Every candidate takes the assessment under comparable technical conditions, so one person's slow laptop does not decide the outcome.
- Exam integrity: Proctoring relies on camera, microphone, and screen access. If any of them fails, the session cannot be recorded or reviewed properly.
- Candidate experience: "I could not join" and "my mic did not work" are the complaints candidates remember. Early warnings remove last-minute panic.
- Fewer support tickets and reschedules: Problems are found days before the test, not in a flood of exam-day tickets. For volume hiring, that is the difference between one support agent and ten.
- Employer brand: Repeated technical failures read as poor planning, and candidates share that view with others.
Access is not even. The Pew Research Center broadband fact sheet reports that 78% of US adults had home broadband in 2026, while 16% were smartphone-dependent. Only 57% of adults in the lowest income group had home broadband, against 92% in the highest. A clear check, with a fallback, keeps capable candidates in the process.
What does a system compatibility check cover?
A system compatibility check covers seven areas: the device, the operating system, the browser, the camera and microphone, the network, the screen setup, and any proctoring or secure browser tools. The physical room matters too, although software can only check part of it.
Component | What to check | Why it matters |
|---|---|---|
Device | Processor, number of cores, RAM, free disk space | An under-powered device lags or freezes during video and coding tasks |
Operating system | Supported version, recent updates, correct date, time and time zone | Unsupported or outdated systems fail to launch secure browsers; a wrong clock breaks timed tests |
Browser | Supported browser and version, pop-ups allowed, cookies on, conflicting extensions off | Most assessments run in the browser, so this is the most common failure point |
Camera and microphone | Device present, permission granted, frame rate, audio input and output working | Proctoring and video or audio answers depend on both |
Network | Download and upload speed, latency, jitter, stability, VPN, proxy or firewall | Weak upload drops recorded video; VPNs and corporate firewalls block proctoring traffic |
Screen | Number of monitors, screen resolution | Extra monitors are often not allowed; low resolution hides parts of the test |
Proctoring and security | Secure browser or extension installed, screen sharing and recording allowed, no remote-control or screen-recording apps | Controlled test conditions only work if the tools launch before the test |
Environment | Quiet, well-lit room, power plugged in | Noise, poor light and a dying battery trigger proctoring flags or end sessions |
Pro tip: Ask candidates to run the check on the exact device, browser and network they will use on the day. A check passed on a home laptop says nothing about the office PC behind a corporate firewall.
What thresholds should you set for a system compatibility check?
System compatibility check thresholds should follow the assessment type, not a single company-wide standard. A written test with light proctoring needs a working browser and a basic connection. Recorded video answers, AI interviews, and live proctoring need far more upload speed, a steady connection, and a better camera.
Published requirements from proctoring providers show how wide the range is:
Requirement | Basic proctored exam | Strict live invigilation | Secure browser with recording |
|---|---|---|---|
Source (published requirements) | Pearson OnVUE, for GMAC's Executive Assessment | ProctorExam, for the FIA's online exams | RM Assessment Master with Talview Secure Browser |
Download speed | 1 Mbps | 10 Mbps | 5 Mbps dedicated |
Upload speed | 1 Mbps | 1.5 Mbps | 5 Mbps dedicated |
Latency (ping) | Not stated | Under 25 ms | Under 150 ms (80 ms recommended) |
Jitter | Not stated | Not stated | Under 30 ms (20 ms recommended) |
RAM | Not stated | Not stated | 4 GB, 2 GB free (8 GB recommended) |
Webcam | 640x480 at 10 fps | Working webcam | Webcam at 15 fps |
Screen | 1024x768, no extra monitors | 1280x768 or higher | Depends on exam content |
Browser | Current Edge, Safari, Chrome or Firefox | Latest Chrome | Chrome or Edge, recent versions |
Other rules | No corporate VPN, no mobile hotspot, plug in power | Wired connection recommended | Automatic browser updates on |
Use these as a starting point, then set two levels for each item:
- Minimum: The level below which the assessment will not run reliably. A miss blocks the test until it is fixed.
- Recommended: The level that gives a smooth experience. A miss shows a warning, not a block.
Keep the minimum as low as the assessment allows. Every extra requirement removes some capable candidates, especially those on mobile data or shared connections.
How do you run a system compatibility check for candidates?
Running a system compatibility check takes six steps: set requirements per assessment, send the check early, have candidates test on their real setup, show fixes for every failure, log the results, and repeat a short check when the test launches. The whole loop should take a candidate a few minutes.
- Set requirements per assessment: Agree minimum and recommended levels with IT, security, and the hiring team. Decide which failures block the test and which only warn.
- Send the check early: Put the check link and the requirements in the invitation email, 24 to 48 hours before the assessment. Say what happens if a check fails and where to get help.
- Test on the real setup: Candidates run the check on the same device, browser, and network they will use and grant camera and microphone access when the browser asks.
- Show the fix for every failure: A useful check does not stop at "failed." It says what to do: update the browser, allow the camera, close other apps, switch to a wired connection, or turn off the VPN.
- Log the results: Store the pass or fail per item against the candidate's record, so recruiters can see readiness at a glance and spot patterns later.
- Check again at launch: Run a short camera, microphone, connection, and screen check when the assessment starts. A setup that passed two days ago can fail after an overnight update.

For a candidate-side walkthrough with permission screenshots, see how to run a candidate system check before an online assessment. If the assessment is proctored, pair the check with the steps in how to set up a proctored exam.
Which tools can run a system requirement check?
System requirement check tools fall into five groups: checks built into the assessment platform, proctoring providers' device checkers, operating system diagnostics, standalone utilities, and in-house builds. For remote candidates, a check built into the assessment platform is usually the best fit, because nothing has to be installed and results sit next to the scores.
Tool type | Best for | Strengths | Limits |
|---|---|---|---|
Built into the assessment platform | Remote candidates at any volume | One link, results next to scores, thresholds per test | Only covers that platform's tests |
Proctoring provider's device checker | Exams delivered through that provider | Matches the provider's own requirements | Separate step, results often outside your hiring tools |
Operating system diagnostics | Company-issued devices and test centres | Deep hardware and driver detail, can be scripted | Heavy to set up, not candidate friendly |
Standalone utilities (memory, disk, network tools) | IT teams troubleshooting one machine | Free, detailed | No pass or fail against your thresholds, no reporting |
In-house build | Large programmes with unusual requirements | Fully branded, exact thresholds | Build and maintenance cost across every browser and OS |
Built-in check: the Testlify system compatibility check
The Testlify system compatibility check is a one-click diagnostic that runs in under a minute before a remote assessment. Each parameter is checked against the standards you set and shown as pass or fail, and recruiters see the outcome in the Testlify dashboard.

- What it checks: Processor vendor, series, generation and cores, RAM, operating system and version, internet type, download and upload speed, network location, monitor count and resolution, sound card and audio output.
- Why it helps: Weak connections and incompatible setups show up before the test, which cuts drop-offs, troubleshooting requests, reschedules and retakes.
- Where it fits: It sits alongside Testlify's 20+ proctoring checks, such as the internet speed check, live environment check, multi-monitor restriction and full-screen enforcement, covered on the anti-cheating and proctoring page.
Operating system diagnostics and standalone utilities
For company-issued laptops or test centres, IT teams can go deeper. The Windows Assessment Toolkit, part of the Windows ADK, assesses the performance, reliability and functionality of a Windows machine and can run jobs across many devices. Built-in tools such as Windows Memory Diagnostic, CHKDSK and Performance Monitor, or network tools like Wireshark, help troubleshoot one machine. None of them gives candidates a simple pass or fail against your thresholds, so they suit internal certification more than public hiring tests.
In-house builds
Some organizations build their own web-based check inside the candidate portal. The result can match the exam's requirements exactly, but the team then owns every browser update, every OS release and the candidate support that comes with it. If you build, include every item in the coverage table above, plus reporting.
How do you choose a system check tool?
Choosing a system check tool starts with your candidates and your assessment types: how many people you test, where they are, which devices they use and whether the tests are proctored. Then compare tools on coverage, candidate experience, fix guidance, reporting, integration and privacy.
- Define your scenario: Candidate volume, regions, device mix, proctoring or secure browser use, and where the check should live (invitation email, candidate portal, assessment platform).
- Rank the capabilities: Globally spread candidates make network checks the priority; proctored tests make camera, screen and secure browser checks the priority.
- Pilot two or three tools: Run them with real candidates on a range of devices. Score clarity of results, quality of fix guidance and candidate feedback.
- Check the reporting: Look for pass rates and failure causes by device, browser, operating system and region, so you can spot patterns.
- Check the fit with your stack: Results should reach your applicant tracking system or assessment platform without manual export.
- Check privacy, support and total cost: Ask what device data is collected and how long it is kept, who supports candidates, and what licences and integration work cost.
How do you fix common system check failures?
Common system check failures come from six places: blocked camera or microphone permissions, an unsupported browser, a VPN or corporate firewall, unstable Wi-Fi, an under-powered or busy device, and extra monitors. Each has a standard fix and a clear owner, so the check should show the fix the moment it fails.
Failure | Usual cause | Fix | Owner |
|---|---|---|---|
Camera or mic blocked | Permission denied in the browser or the OS privacy settings | Allow camera and mic for the site, then reload | Candidate |
Camera or mic in use | Another app such as a video call holds the device | Close the other app and run the check again | Candidate |
Browser not supported | Old version or an unsupported browser | Update or switch to a supported browser | Candidate |
Connection blocked | VPN, proxy or corporate firewall | Turn off the VPN, use a personal network or ask IT to allow the platform | Candidate or IT |
Slow or unstable network | Shared Wi-Fi, mobile hotspot, others streaming | Use a wired connection, pause other downloads, move closer to the router | Candidate |
Device too slow | Low RAM, many open apps, low disk space | Restart, close apps and tabs, free disk space, or switch device | Candidate |
Extra monitor detected | Second screen connected | Disconnect the extra monitor before the test | Candidate |
Check cannot fix it in time | Hardware or access gap | Loan device, test centre or reschedule | Recruiter |
Browsers report camera and microphone problems in a predictable way. According to MDN's documentation on camera and microphone access, a page must ask permission before it can use either device, a denied request returns a "not allowed" error, a missing device returns "not found", and a device held by another app returns "not readable". Camera and microphone access also only works on secure HTTPS pages. A good check turns each of these into a plain-language fix.
Key takeaway: Treat a failed check as a task with an owner and a deadline, not a verdict. Set a rule such as "fix at least 2 hours before the test" and offer a reschedule when the gap is outside the candidate's control.
How do you keep a system compatibility check fair, accessible and private?
A fair system compatibility check uses the lowest requirements the assessment allows, offers alternatives to candidates who cannot meet them, supports accommodations, and tells candidates exactly what device data it collects. The check prepares people for the test. It should never become a hidden screen.
- Minimum versus recommended: Block the test only on true minimums. Show everything else as a warning.
- Alternatives: Offer a loan device, a test centre, a different time or a mobile-friendly format where the role allows it.
- Accessibility: Candidates with disabilities may use screen readers, other input devices or extra time. The ADA.gov guidance on AI and disability discrimination in hiring says employers should tell applicants which technology will be used, so they can ask for an accommodation, and offer an accessible alternative when a tool screens someone out.
- Privacy and consent: A check collects system data such as device specs, browser version, IP address and network location. Say what is collected, why and how long it is kept, store it securely with limited access, and follow GDPR and local data protection rules.
- Proctoring rules: If you require a secure browser or proctoring, the policy should cover approved versions, permissions, privacy and what happens when proctoring fails mid-test.
Which metrics show a system compatibility check is working?
The metrics that show a system compatibility check is working are completion rate, first-time pass rate, the most common failure causes, time to fix, exam-day support tickets, exam-day disruptions and candidate satisfaction with the setup. Track them after every assessment round and set targets from your own baseline.
Metric | What it tells you | What to do when it is weak |
|---|---|---|
Completion rate | How many candidates run the check before the test | Make the link prominent in every email and send reminders |
First-time pass rate | Whether your requirements match real candidate setups | Review thresholds and lower any that are not needed |
Top failure causes | Which items fail most (browser, permissions, network) | Add browser-specific steps or a short permissions video |
Time to fix | How fast candidates recover from a failure | Show automatic fix suggestions and offer chat support |
Exam-day support tickets | Whether the check catches real problems | Add the missing item to the check or the launch check |
Exam-day disruptions | Delays, interruptions and reschedules caused by tech | Look for skipped checks and last-minute updates |
Candidate satisfaction | How easy the setup felt | Ask one or two questions after the test and act on them |
Cost of reschedules | Hours spent on troubleshooting and rebooking | Use it to show the value of the check to leadership |
Put these on one dashboard for HR, IT and assessment operations, split by region, device and browser. A region with a low pass rate usually points to a network threshold that is too strict, not to weaker candidates. For more on running tests at a distance, see remote assessments in remote hiring.
Ready to check every candidate's setup before the test?
Testlify runs a one-minute system compatibility check before each remote assessment and shows the pass or fail for every item in your dashboard, next to the candidate's scores. Start a 7-day free trial of Testlify, no credit card required, and add the check to your next assessment.
Frequently asked questions (FAQs)
Content Writer
Yashika Khandelwal is a Content Writer with 3+ years of experience creating research-backed content on hiring, talent assessment, and HR technology. She is a registered Organizational Psychologist and subject matter expert who combines behavioral science with practical recruitment insights to produce accurate, evidence-based content.
LinkedInRelated resources
View all
Remote hiring
How to foster team cohesion and engagement in a remote workforce

Remote hiring
Remote Hiring Tools: Build Your 2026 Hiring Stack

Remote hiring
How to overcome geographical and cultural barriers in remote hiring

Remote hiring
5 practical ways to evaluate job candidates remotely

Remote hiring
Best practices for remote employee management

Remote hiring
How to manage a remote team?
Get started.
Hire on proof, not resumes.
Run your first skills-based assessment free — no credit card required.