The CV looks perfect. Is the translator real? Build a verification workflow.
A polished application can hide an unverifiable credential. Build a repeatable review process that checks the claim, records the evidence and gives genuine linguists a fair path forward.
On this page
- The application is convincing. The claim still needs checking.
- Ask three separate questions about the application
- Check what the credential actually certifies
- Use automation to organize review without inventing a fraud verdict
- A small capability check needs a clear rubric and limited access
- Measure the review process instead of rewarding fast rejection
- Questions we hear
The short version
- Verify the specific credential and language direction with its issuer. A membership number and a certification number are different evidence.
- Treat inconsistencies as review signals. Names, nationality, location and polished writing do not establish fraud.
- Separate identity, claimed credentials and delivery capability; one successful check cannot replace the others.
- Keep sensitive evidence and duplicate signals restricted to authorized staff, with human decisions and a correction route.
The application is convincing. The claim still needs checking.
A vendor application arrives with a polished CV, relevant language pairs and an impressive credential. An urgent project needs capacity, so the temptation is to approve the profile and let the first job prove the rest. By then, client material may already have left your controlled workflow.
The useful question is what evidence supports the claims your assignment depends on. A professional-looking document is one input. It is not independent confirmation of the person, certification or ability to deliver the required work.
A translation-agency discussion of sophisticated applications describes the limits of surface presentation. A separate firsthand credential-check account describes a claimed certification that did not verify. Both support a repeatable evidence process, not a demographic profile of a suspicious applicant.
Design the process to distinguish a missing document, a misunderstood claim and a substantiated misrepresentation. Those states require different responses. Automation can organize the evidence; an accountable person should make the decision.
Ask three separate questions about the application
- Identity and contact: are you communicating with the person or authorized organization represented?
- Claimed credentials: does the issuer confirm the stated qualification, language pair and direction?
- Delivery capability: does the available evidence support this person's work on your required subject matter and workflow?
A valid credential does not establish expertise for every domain. A strong work sample does not validate ownership of a stolen CV. A directory listing may confirm membership while saying nothing about a separate certification claim.
- Capture relevant claims
Record only the qualifications and experience needed for the intended work.
- Verify independently
Use issuer records and independently established reference contacts.
- Assess capability
Review a suitable sample or other permitted evidence against explicit requirements.
- Decide and record
An authorized reviewer approves, requests clarification or rejects with a documented basis.
Define the required evidence per service rather than making every applicant complete the same oversized process. Rare language combinations may lack a particular formal credential. Provide an appropriate alternative path when the role does not require that credential.
Check what the credential actually certifies
Record the issuer, credential type, holder name, identifier and claimed language direction. Navigate to the issuer's official verification route rather than relying only on a link or screenshot supplied by the applicant. Keep the result and the date checked.
The ATA verification tool asks for a certification number and returns certification and language-pair information. It explicitly distinguishes that number from a membership number. The ATA exam information describes certification by language pair and direction.
Use the current issuer information when evaluating a claim. Do not maintain an unreviewed hardcoded list of available language combinations and assume it stays accurate forever. If the issuer's tool is unavailable, record verification as pending and route the case to a person.
Connect the verified credential to the applicant too. A stolen CV can contain a genuine certification number. Where an official directory provides an established contact route for the credential holder, use that route for a relevant confirmation rather than relying only on the application email. When independent contact is unavailable or details differ, keep the check pending for human clarification.
If you contact a reference, establish the contact route independently and ask only about relevant work with an appropriate basis. A personal email address alone does not make a reference false. Check the relationship and the evidence rather than using the address format as a verdict.
Use automation to organize review without inventing a fraud verdict
Software can identify missing fields, normalize credential IDs, detect an exact duplicate application and show whether a required check is complete. It can also surface potentially related records for staff review. Those are workflow aids, not conclusions about the applicant.
Shared phone numbers or addresses can belong to an agency, household or shared office. Different contact-country codes can reflect travel or remote work. Never substitute nationality, a name, language background or location for evidence about a specific claim.
- A number substitutes for the evidence.
- Shared details can become automatic rejection rules.
- Applicants have no route to correct an error.
- Each relevant claim links to a check and its outcome.
- Potential duplicates remain internal review signals.
- A person decides and can request or accept clarification.
Keep suspected duplicate links, staff notes and verification material out of candidate-facing pages and unrelated staff access. Show each reviewer only the information required for their role. Define retention and correction rules for the evidence your organization actually needs.
An audit trail should record who checked what, when, the source used and the decision. Avoid storing unnecessary identity documents or copying sensitive material into unrestricted project notes. Decide the minimum evidence and access policy before building an upload workflow.
A small capability check needs a clear rubric and limited access
Use a permitted, appropriately scoped sample and disclose how it will be evaluated. Provide the context, terminology and quality expectations a competent linguist would need. Avoid turning a recruitment sample into unpaid production delivery.
Score against the agreed rubric and preserve the reviewer's rationale. If tools assist scoring, require human review of ambiguous results and any adverse decision. Test keys and model prompts that reveal expected answers belong outside applicant-accessible interfaces.
- Flag a specific mismatch
Record the claim and the independent evidence that needs reconciliation.
- Request clarification
Explain what is missing without exposing other applicants or internal signals.
- Recheck the relevant evidence
An authorized reviewer records the corrected or still-unresolved result.
- Make a bounded decision
Approve suitable work, hold the application or reject under the documented policy.
When a vendor is approved, match access to the assignment. Approval to join a pool should not automatically grant access to every client's files, glossaries or historical jobs. Reassess permissions when the vendor's role or assignment changes.
For a synthetic pilot, deliberately include an unverifiable credential, a mistyped identifier, a legitimate shared agency contact and a candidate with suitable evidence but no applicable certification. The goal is to expose false accusations and missed checks as well as obvious misrepresentation.
Measure the review process instead of rewarding fast rejection
- Define the evidence required for the actual service.
- Separate identity, credential and capability checks.
- Use the issuer's official verification route.
- Check language pair and direction where the credential specifies them.
- Keep unavailable checks pending, with an owner.
- Treat discrepancies and related records as human-review signals.
- Provide clarification and correction routes.
- Restrict evidence, notes and client access by role.
- Audit decisions and review false-positive cases.
Track missing evidence, pending-check age, clarification turnaround and reviewer overrides. Review both legitimate applications wrongly held and claims that passed without the required evidence. Faster rejection is not the same as a better process.
For broader dispatch and assessment concerns, see translation vendor management. This workflow focuses on the evidence supporting the applicant's claims before assignment.
If your vendor managers repeat the same checks across email and spreadsheets, bring a sanitized onboarding map to a discovery call. A focused workflow review can identify which checks can be organized or integrated and which decisions must stay with your team.
Questions we hear
Can an LSP automatically reject applications with inconsistent details?
A mismatch can have a legitimate explanation. Keep it as a review signal and ask for relevant clarification. An authorized person should decide under the organization's policy using the specific evidence, with a route to correct mistakes. Avoid demographic proxies and unexplained risk scores.
Does ATA membership prove that someone is ATA certified?
No. ATA's official verification page distinguishes membership numbers from certification numbers. Verify the specific certification claim and its language pair and direction through the issuer's current tool. Membership and other professional experience can be relevant, but they are separate evidence.
Does every good translator need the same certification?
No. Available credentials and requirements vary by language, service and client. Define the evidence appropriate to the work. Where a particular credential is not required or available, use relevant experience, references and a fair capability assessment rather than treating its absence as fraud.
Sources
- Firsthand discussion of sophisticated translator applicationsLinkedIn
- Firsthand account of checking a claimed translator credentialLinkedIn
- Verify ATA-certified translator statusAmerican Translators Association
- About the ATA certification examAmerican Translators Association