Research
Reading EEOC Background Check Guidance for Offshore Hiring
What a support-team lead should know about job-relatedness, disclosure, adverse action, vendor oversight, and record handling when screening offshore candidates.
On this page
Key stats
The U.S. Equal Employment Opportunity Commission explains that when an employer uses a third party to obtain a background report, the federal Fair Credit Reporting Act requires a disclosure, written authorization, and specific steps before taking adverse action.
Methodology
This note reviews EEOC background check guidance, Federal Trade Commission resources on consumer reports, and U.S. Department of Labor guidance. It asks how a team hiring Philippines-based support staff can make screening decisions that are job-related, consistent, documented, and respectful of the candidate. It is not legal advice and does not substitute for counsel in the hiring location.
Evidence summary
Start by identifying what the check is for. A criminal record check, an employment verification, and a credit report are different products with different rules. The role may justify one and not another. Write the purpose before choosing a vendor. A check that cannot be tied to the job is hard to defend.
Use a clear and separate disclosure. The federal consumer reporting rules require a standalone disclosure that the employer may obtain a consumer report for employment purposes. Do not bury it in the application or add unrelated waivers. Give the candidate a copy and obtain written authorization. Keep the signed form with the hiring record.
Apply the same standard to every candidate for the role. A check applied only to some applicants can create a discrimination risk even when the intent is benign. Write the rule and the exceptions before the search starts. Record who approved an exception. Consistency is easier to show when the rule is written.
Consider the job-relatedness of the check. The EEOC guidance asks whether a screening criterion is relevant to the position and whether a less discriminatory alternative exists. A support role may need a confidentiality check but not a credit history. Document the reasoning. Do not copy a check from another role without review.
Follow the adverse action process if the report may lead to a decision. The candidate usually gets a pre-adverse notice, a copy of the report, and a chance to respond before the final decision. The exact steps depend on the law and the vendor. Build the sequence into the hiring workflow. Do not improvise it in an email.
Protect the report and the decision record. Background reports contain sensitive data and should be visible only to the people who need them. Store them in the hiring system, not in a shared drive or a chat thread. Set a retention period with counsel. Delete the report when the period ends.
Check the vendor's practices as carefully as the candidate's record. Ask how the vendor obtains data, how it handles disputes, and where it stores reports. A vendor that cannot explain its process creates risk for the employer. Review the contract and the security terms. Record the review date.
Account for the hiring location and the candidate's location. A Philippines-based candidate may be subject to local data privacy rules as well as the client's policy. The vendor may not have coverage in every country. Confirm the scope before promising a check. Consult local counsel when the answer is unclear.
Separate the client's requirement from the employer's obligation. A client may ask for a check that the employer cannot lawfully run or that is broader than the role needs. Discuss the requirement before the search. Offer a lawful alternative when possible. Record the client's decision and the advice received.
Write a short candidate communication. Explain what is checked, how long it takes, and who to contact with a question. Avoid jargon and do not promise an outcome. A clear note reduces anxiety and support requests. Keep it consistent with the disclosure and the adverse action steps.
Audit a sample of hires each year. Check that the disclosure was signed, the report was stored correctly, and the adverse action steps were followed when needed. Look for checks that were run without a recorded purpose. Fix the process, not just the file. Keep the audit note with the hiring policy.
Close with a review and a named owner. Assign one person to keep the policy current and to answer questions from recruiters and clients. Review the policy when the role, the vendor, or the law changes. Record the review date and the change. A background check process is a compliance system, not a one-time form.
Keep the screening criteria in the job description and the interview guide. A criterion that appears only in a vendor portal is hard to explain to a candidate or a reviewer. Write the requirement in plain language and link it to the task. Remove criteria that the role does not need. A short, visible list is easier to apply consistently.
Tell the candidate how to dispute an inaccurate report. The vendor usually has a process, and the employer should be able to point to it. Keep the contact information with the disclosure and the adverse action notice. A dispute that cannot find a path becomes a complaint. Record the question and the answer in the hiring file.
Review the process when the client changes, not only when the law changes. A new client may add a screening requirement, a new market may change the vendor's coverage, and a new role may make an old check irrelevant. Revisit the purpose, the disclosure, and the vendor scope together. Record the decision. A policy that is never revisited slowly stops matching the work.
Keep the candidate experience in view. A long silence after a check can feel like a rejection, and a vague request for documents can create avoidable anxiety. Send a short status note with the expected timeline and a contact for questions. Do not ask for more information than the process requires. A clear process protects the employer and respects the candidate.
Classify the check
Write the purpose and the product, such as a criminal record check or employment verification. Confirm it is relevant to the role. Note the vendor and the geography. Review the choice when the role changes. Do not bundle unrelated checks.
Use a compliant disclosure
Keep the disclosure separate from the application. Give the candidate a copy and obtain written authorization. Store the signed form. Do not add unrelated waivers. Review the form with counsel.
Apply one standard
Write the rule before the search. Record exceptions and the approver. Apply the check to every candidate for the role. Keep the evidence. Review the rule each year.
Handle adverse action
Build the pre-adverse notice, report copy, response window, and final decision into the workflow. Follow the vendor and legal steps. Record dates and recipients. Do not improvise by email. Keep the file.
Protect the record
Store reports in the hiring system with restricted access. Set a retention period with counsel. Delete on schedule. Keep only the decision note. Audit a sample each year.
Review the vendor
Ask how data is obtained, disputed, and stored. Check coverage in the candidate's country. Review security terms and the contract. Record the review date. Replace a vendor that cannot explain its process.
FAQs
Does EEOC guidance apply to hiring in the Philippines?
The guidance explains U.S. federal standards for employers covered by those laws. A Philippines-based hire may also be subject to local rules, and the client's policy may add requirements. Treat the guidance as one input and confirm the applicable law with counsel.
Can I run a background check without telling the candidate?
The federal consumer reporting rules require a clear disclosure and written authorization before a third party obtains a report for employment purposes. Some checks and jurisdictions have additional rules. Build the notice and consent into the process rather than adding them later.
What is adverse action?
It is the step that follows a report that may lead to a decision not to hire or to withdraw an offer. The candidate usually receives a notice, a copy of the report, and a chance to respond before the final decision. The exact sequence depends on the law and the vendor.
Should every support role require the same check?
No. The check should be tied to the job and applied consistently to candidates for that role. A role that handles sensitive data may justify a different check from one that does not. Document the reasoning and review it when the scope changes.
