To automate background checks with VERISafe, start by making the screening workflow consistent: define who needs checking, collect the approved information, assign a reviewer and track completion. Use instant screening at the agreed stage, then route findings for human review. Confirm any technical integration with Verity before connecting other systems or relying on unattended searches.
For Malaysian businesses, the most useful first improvement is often a reliable handover between recruitment, screening and onboarding. A fast search provides limited value if the request sits in an inbox, the wrong person is checked or a report never reaches its authorised reviewer. Build the process around those practical failure points.

What does automating background checks actually mean?
Automation can refer to several different activities: creating a screening task, reminding someone about missing information, updating a status or running a search through a supported connection. These are separate capabilities. A reminder in your existing recruitment system does not mean that the system can submit a VERISafe search or retrieve a report.
This guide describes a workflow you can standardise around VERISafe. It does not claim that every step is a built-in VERISafe feature. Confirm available account functions, permissions and integration options directly with Verity. Where a supported connection is unavailable, keep the search and review as assigned manual steps within an organised process.
Where does VERISafe fit in the screening process?
VERISafe provides instant screening of available integrity-related records. It can support an initial review before an organisation decides whether further verification is needed. It should be used with an appropriate scope, reliable identity information and a process for reviewing possible matches.
Education, employment and reference verification are different tasks. Where these are relevant, discuss Verity BGC rather than assuming an instant search verifies every claim in a CV. The right workflow separates the initial screening result from any additional evidence needed for the particular role.
A useful design question is: what must be complete before the next hiring step can proceed? The answer may differ between a shortlist review, a conditional offer and access to a sensitive system. Write that rule down before choosing tools, so technology supports the agreed process.
How do you build a repeatable screening workflow?
1. Choose a clear trigger
Select a defined event, such as approval of a conditional offer or confirmation of a contractor assignment. Decide who owns the trigger and how it is recorded. Avoid relying on an informal message that says “please check this person” without the assignment, screening scope or responsible reviewer.
Give each request a unique reference linked to the recruitment or onboarding record. Check for an existing request before creating another. This prevents two coordinators from commissioning the same work independently, particularly when a candidate changes teams or a recruiter resends an email.
2. Check readiness before submitting a search
Create a short checklist for the information and permissions needed for the agreed scope. Verify spelling and identifiers, complete the applicable privacy and authorisation steps, and resolve incomplete details. A task should remain awaiting information until it meets the checklist, even if the intended start date is approaching.
3. Assign the screening and review steps
Name an operator who can carry out the screening and a reviewer who can assess the result. Smaller organisations may allocate both responsibilities to one authorised person, with a backup for absence. Keep the responsibilities explicit so a completed search does not become an unreviewed report.
4. Record the outcome without distributing the full report
The onboarding tracker usually needs the request reference, scope, completion date, reviewer and next action. Store detailed reports in an appropriately restricted location. Do not copy adverse findings into a spreadsheet available to everyone involved in recruitment when those people only need to know whether a review is complete.
5. Escalate exceptions to a person
A possible match, identity mismatch, missing source or request for clarification needs a defined queue. State who handles it and how the affected person can provide relevant corrections. Workflow rules should help the right person act promptly, rather than turn an uncertain result into an automatic rejection.

Which steps can your existing tools help organise?
Depending on the functions already available in your organisation’s systems, you may be able to create tasks, send internal reminders or flag overdue reviews. Check the actual capability and access arrangements before relying on it. The examples below are proposed process rules, not a list of VERISafe integrations.
| Stage | Proposed workflow rule | Responsible person | Evidence to record |
|---|---|---|---|
| Request approved | Create one screening task using a unique reference | Recruitment coordinator | Scope and assignment |
| Information missing | Remind the assigned coordinator | Coordinator | Missing item and follow-up date |
| Ready for screening | Route to the authorised operator | Screening operator | Readiness check completed |
| Result available | Assign a review task | Authorised reviewer | Review date and next action |
| Exception identified | Pause progression and escalate | HR or designated decision-maker | Clarification and reasoned outcome |
| Assignment ended | Review access expiry and retention actions | IT and record owner | Closure confirmation |
What privacy safeguards should the workflow include?
Follow the applicable data protection requirements throughout collection, screening, storage and disclosure. The Personal Data Protection Commissioner’s principles provide a starting point for notice, security, retention, accuracy and access. A convenient connection between systems should not silently widen the audience for personal information.
Confirm the lawful basis and any consent or authorisation needed for the proposed checks. Offence-related information may involve sensitive personal data and needs particular care. Limit user permissions, decide where reports belong and set a retention process. This article is general information, not legal advice; obtain advice for your specific workflow where needed.
Before connecting a third-party tool, establish what information it receives, who can access it, how long it keeps copies and how errors are corrected. Prefer status-only notifications when that meets the operational need. A message saying a review is ready is often more appropriate than attaching a complete report to every notification.
How should possible matches and incomplete checks be handled?
Keep “search completed”, “review completed” and “approved for the next step” as separate statuses. A completed search may still need clarification. Equally, an incomplete check is not evidence of wrongdoing. The tracker should make these distinctions clear to the people responsible for onboarding.
The reviewer should establish whether the information relates to the correct individual and is relevant to the role. Consider the source, date, status and available explanation. Give appropriate opportunities to correct errors, and record the decision without spreading unnecessary personal detail. Screening supports judgement; it does not remove accountability for the outcome.
Worked example: organising a weekly intake
Imagine a hypothetical employer onboarding fifteen people each week. Previously, recruiters emailed documents to different colleagues, and managers asked for updates in group chats. The business introduces one request reference, a readiness checklist and a named review owner. Existing task reminders are configured only where the organisation’s tools support them.
The authorised operator carries out the VERISafe step, and any role-specific verification is tracked separately. A possible match stays in review while identifiers are checked. Hiring managers see the progress status, while the detailed report remains restricted. The improvement is a visible process with fewer ambiguous handovers, rather than a promise that every check or decision runs automatically.
How do you measure whether the workflow is improving?
Measure elapsed time at each handover: request to readiness, readiness to screening, and result to review. Count incomplete requests, duplicate submissions and overdue decisions. These measures show where work stalls. A fast search can coexist with a slow onboarding process when the delay happens before submission or after the report is available.
Review a small pilot before expanding. Include an incomplete request, a duplicate request, a possible match and an absent reviewer in the test. Check that notifications reach the correct person and contain only the necessary information. Keep a manual fallback so the process remains workable if an internal tool or connection is unavailable.

Frequently asked questions
Does VERISafe automatically connect to our HR system?
Do not assume an integration is included. Ask Verity to confirm the available options for your account and the system you use, including supported data flows and permissions. Until that is verified, treat screening as an assigned step and use your existing tools only for functions they demonstrably support.
Can background screening be fully automated?
Some administrative steps can be organised using rules and reminders, subject to the capabilities of the systems involved. Identity issues, possible matches and decisions affecting people still need an accountable review process. Distinguish the automation of task handling from technical search integration and from the final decision about an individual.
Does instant screening verify education and employment?
Instant integrity screening and verification of a qualification or previous employment answer different questions. Where your role requires those checks, agree a separate verification scope with Verity. Track all required components so a completed instant search is not mistaken for completion of a broader background screening package.
What should we store in our screening tracker?
Store the minimum operational information needed to manage the process: request reference, agreed scope, readiness status, completion date, reviewer and next action. Keep full reports and identity documents in an appropriately restricted location. Set access and retention rules, and avoid placing sensitive findings in broadly shared notes.
What is the best first step for a small team?
Map the current process from request to reviewed outcome, then identify the most common missed handover. Introduce one owner and a simple checklist before adding technical complexity. Pilot the process with a limited intake, review exceptions and confirm any VERISafe integration requirements directly before making further system changes.
Make your screening process easier to run
Start with a clear trigger, complete information and an accountable reviewer. Then add supported workflow improvements where they reduce repetitive administration without weakening privacy or review. Trust, but Verify.
Contact Verity Intelligence to discuss VERISafe, the checks your business needs and the available options for your screening workflow.