feat(background-check): redesign overview and report to surface real verification methodology#2836
Merged
Merged
Conversation
…verification methodology
Replaces generic benefit bullets ("Required for Compliance",
"Social media verifications") with a marketing-forward methodology block
that names what we actually do: biometric ID + liveness, HR-confirmed
employment, structured reference questionnaires, AI-augmented
public-source research, and FCRA-style adjudication.
The completed report now opens with a methodology banner and each section
shows its verification method as a subtitle. Renames "Social and media
research" to "Public-source research" so LinkedIn stops reading as the
whole product.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
🎉 This PR is included in version 3.54.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The customer perception that our background check is "just LinkedIn scraping" is wrong — but our own UI was making it look that way. This PR rewrites the customer-facing copy and structure of the Employee Background Check overview + completed report to name what we actually do.
What the system actually does (verified against the
trycompai/background-checkrepo):partially_verifiedstatus)What changed
New —
BackgroundCheckMethodology.tsxShared methodology components reused by both wizard overview and report so the copy stays in sync:
MethodologyTrustSignals— four trust signal chips (Biometric / Human-verified / FCRA / AI-augmented)MethodologyIncluded— five detailed "What's included" cards with one-line method explanationsMethodologyComplianceNote— FCRA adverse-action calloutMethodologyReportBanner— compact banner for the top of the completed reportUpdated —
BackgroundCheckWizardParts.tsxUpdated —
BackgroundCheckReport.tsxUpdated — tests
EmployeeBackgroundCheck.test.tsxandBackgroundCheckStatusView.test.tsxassertions updated to match new copy.Verification
audit-design-systemclean — no@trycompai/uiorlucide-reactimports, noclassNameon DS components that reject itrenders methodology overview…,skips the overview…, status view section labels)EmployeeBackgroundCheck.test.tsx(PointerEvent is not definedfrom a Switch component) are unrelated — confirmed by stashing my changes and re-running.