How to run a candidate system check before online assessment?

Online skills assessments have become a common part of evaluating candidates. But even the best assessment won’t do its job well if the candidate’s system (computer, network, browser, etc.) is not ready. Technical glitches, incompatible software, and blurry webcams can distort results, hurt candidate experience, or even force postponements.

Ensuring candidate system readiness is not just about smoother assessments, it reflects on employer brand, fairness, efficiency, and security.

In this guide, you’ll learn:

• What a system check is and why it matters
• Key components of a candidate system check
• Step-by-step process to run system checks before assessments
• Best practices and policies to enforce consistency
• Common pitfalls and how to avoid them

Why do a candidate system check?

Before we dig into the “how,” let’s be clear on why you need this.

Minimizing technical disruption

If a candidate’s system isn’t ready, slow internet, incompatible browser, broken webcam, the assessment may suffer. They may get cut off, get errors, or produce poorer results simply because of technical issues. That can lead to inaccurate judgments.

Ensuring fairness

Assessments should measure the candidate’s skills, not their system quality. If one candidate has audio issues and another doesn’t, that’s unfair. Running a system check ensures everyone starts on equal technical footing.

Protecting your assessment environment

Online assessments often need secure environments. If a candidate’s device lacks required security (e.g. proper browser lockdown, outdated software, non-secure network), it may pose risk of cheating or data leaks.

Better candidate experience

Nothing frustrates a candidate more than starting a test, then struggling with setup issues. By running system checks before, you reduce anxiety, avoid rescheduling, and improve the perception of your company as organized and caring.

Operational efficiency and cost savings

Fewer support tickets, fewer assessment reschedules, fewer lost time. That adds up. For large organizations, even modest improvements in assessment readiness save significant admin and operational cost.

What is a candidate system check?

A “system check” (or “system diagnostic” in this context) is a process (often automated) that validates whether a candidate’s computer and environment meet the technical requirements for your online assessment platform.

It can be done via a web tool or small script, and typically covers:

• Hardware (computer, audio, video, peripherals)
• Operating system and required software versions
• Browser compatibility and permissions
• Internet speed, stability, latency, etc.
• Security settings or required security software
• Any platform-specific tools (e.g., secure browser, proctoring tools)

What things (components) should be checked while running a system diagnostic?

Here is a checklist of all the components your system check should include. You can adapt thresholds depending on your assessment type (coding test, video interview, timed knowledge test, etc.).

Depending on your assessment context, some components will be more critical than others.

How to run a candidate system check: Step-by-step

Here’s a full process you can implement in your hiring workflow to ensure candidates pass system checks before their actual assessment.

Step 1: Subscribe to a system check tool

You’ll need a tool (web-based or downloadable) that can test the components reliably. Consider:

• Tools that let candidates run quick checks online
• Tools that detect hardware, browser, OS, network speed, and permissions automatically
• Tools that integrate with your assessment platform or candidate journey

Talent assessment and interview tools like Testlify offer system diagnostics in simple steps that candidates can take before starting their assessment.

Step 2: Define the technical requirements

Before implementing system checks, decide and document what your minimum and recommended requirements are. This includes:

• Hardware baseline: e.g. at least 8 GB RAM, modern CPU, working cam and mic
• OS and software requirements: Supported OS versions, browser versions, any required applications
• Network requirements: minimum speed, latency, stable connection
• Security requirements: whether a secure browser, antivirus, etc are mandatory

These should be communicated clearly to candidates.

Step 3: Integrate system check early in candidate journey

Best practices:

• With Testlify, you can incorporate the system check before candidates take the assessment
• Make it part of the onboarding/test readiness instructions

Step 4: Let the candidate run the system check

• Candidate downloads and runs a one-click system check
• The check should test all components: hardware, browser, internet, permissions, etc.
• It should present results in a user-friendly way and show pass/fail for each component.

Step 5: Analyze results and provide remediation support

• For each candidate, you get a report of which checks passed and which failed
• For failed items, suggest fixes: e.g. “Update browser to latest version,” “Use wired internet instead of WiFi,” “Allow mic/cam permissions”
• Maybe provide “help articles” or chat/IT support for common issues

System diagnostic check policies and best practices for large organizations

Having the technical setup is only part of the story. For large organizations, consistency, fairness, privacy, and policy matter.

Clear communication

• Send the system requirement document early (job post, email)
• Use clear language, avoid overly technical jargon
• Provide visuals/guides to help with setup

Accessibility and accommodation

• Some candidates may need special tools (e.g. captions, screen readers, microphone adjustments). Make sure the system check accommodates this
• Offer support or flexibility (e.g. longer allotted time) if someone has accessibility needs

Privacy, consent and data handling

• System check tools gather technical data, clear privacy policy needed
• Say what data is collected, how stored, who can see it, and how long you’ll keep it
• Anonymize where possible; only keep what’s essential

Security and proctoring

• If using proctoring or secure browsers, define when they’re mandatory
• Ensure security tools are tested and do not violate privacy laws

Escalation and support

• Have a support team ready to help candidates with system issues
• For common problems, maintain FAQ, videos, quick fix guides

Tracking and analytics

• Track system check pass rates (by region, by candidate type)
• Identify commonly failed checks to improve communication or troubleshooting tools
• Measure impact: fewer assessment dropouts, better candidate satisfaction

Common system issues and how to handle them

Even with good planning, candidates often run into specific problems. Here are frequent issues and how to avoid them.

Checklist: Candidate system-check before assessment

Here’s a summarized checklist you can use or share. You can adapt it to your organization.

• Device: At least XX GB RAM, CPU meets requirement
• Free disk space enough (e.g. ≥ YY GB)
• Working webcam and microphone; headset if needed
• Screen resolution and multiple displays (if relevant)
• Latest OS version; system updates applied
• Supported browser installed + updated
• Camera/microphone permissions granted in browser
• Internet speed test: download/upload > threshold; latency acceptable
• Stable connection; minimal packet loss
• No conflicting software (e.g. remote tools, screen recorders, blocking extensions)
• Secure browser / proctoring tool installed if required
• Environment: quiet, well-lit, good audio, minimal distractions
• System clock and timezone set properly
• Power supply reliable (laptop plugged in / battery sufficient)
• Backup plan (hotspot, alternate device)

System diagnostics implementation suggestions and tips

To embed this in your hiring system, especially in large-scale settings:

• Use an automated system check tool integrated with your assessment portal
• Make the system check responsive: can adapt to the candidate’s locale, OS, and internet context
• Provide mock tests and video/or textual guides with screenshots
• Make the system check mobile-friendly if candidates may use mobile (if your assessment supports mobile)
• Offer remediation support (FAQs, live chat) so candidates aren’t stuck

Conclusion

Running a candidate system check before online assessment is not optional, it’s essential for fairness, efficiency, candidate satisfaction, and risk mitigation. For large organizations, having a clear, reproducible, and candidate-friendly process ensures that your assessments measure what they should: candidate ability, not their tech setup.

By defining clear technical requirements, integrating system checks early, providing resources and remediation, and analyzing results, you can dramatically reduce technical issues, improve candidate experience, and maintain assessment integrity.

If you’re evaluating tools to support this process (or want help building your own), get in touch, we can help you design system checks that work reliably at scale for your hiring volume and candidate diversity.

Frequently asked questions (FAQs)