Employment Claim Collection Guide
This guide explains how Trua Cloud collects employment claims from your candidates — from the moment they receive an invitation to the point where their submission is ready for verification.
Overview
When you need to verify a candidate's employment history, Trua Cloud handles the data collection. You provide the candidate's contact information; Trua sends them a secure link to a guided wizard where they enter their employment history, complete biometric enrollment, and sign an attestation. The collected claims are then available to your team for verification.
You create invitation → Candidate clicks link → Completes wizard →
Claims collected → Ready for verification
The Candidate Experience
Receiving the Invitation
The candidate receives a single email or SMS with a link that contains their access code. They click once and land directly in the wizard — no manual code entry, no account creation, no app to download. The process works on any device (phone, tablet, desktop).
What They Complete
| Step | What's Collected | Time |
|---|---|---|
| Personal Information | Legal name and email address | ~1 min |
| Biometric Enrollment | Facial capture via device camera | ~30 sec |
| Employment History | Employers, dates, titles, supervisor contacts | 3–5 min |
| Review | Candidate verifies everything is correct | ~1 min |
| Signature | Electronic signature and attestation | ~30 sec |
Total time: 5–10 minutes for a typical candidate.
Employment History Details
This is the core of the collection. For each employer, the candidate provides:
- Company name and job title
- Start and end dates (month/year), or marks as current employer
- Location (city, state, country)
- Supervisor contact — name, email, and phone number
- "No contact available" option — accepted, but flagged for your review
The wizard enforces your configured requirements:
- Lookback period — How many years of continuous history (e.g., 3, 7, or 10 years)
- Gap detection — Gaps between employers are flagged so the candidate can fill them
- Timeline continuity — The system tracks whether the candidate's entries cover the required period
If requirements aren't fully met, the candidate sees a warning but can still proceed. Your team receives information about what was and wasn't met, so you make the final adjudication.
Creating Invitations
From the Admin Panel
- Go to Invitations → New
- Enter the candidate's name, email, and optionally phone number
- Click Create & Send
- The candidate receives their invitation immediately
Via API
curl -X POST https://trua.cloud/api/v1/invitations \
-H "Authorization: Bearer sk_live_xxxxxxxxxxxxxxxxxxxx" \
-H "Content-Type: application/json" \
-d '{
"candidate_email": "jane.doe@example.com",
"candidate_first_name": "Jane",
"candidate_last_name": "Doe",
"external_id": "YOUR-ATS-ID-456"
}'
See the Collection Customer API Guide for full details.
Tracking Progress
Invitation Statuses
| Status | Meaning |
|---|---|
| Sent | Invitation delivered, candidate hasn't started |
| Started | Candidate clicked the link and began the wizard |
| Submitted | Candidate completed and signed — claims ready for verification |
Monitoring
- Admin panel — Real-time status on the Invitations page
- API — Poll
GET /api/v1/candidates/:id/lifecyclefor progress - Webhooks — Receive
submission.completedevents in real-time
What You Receive After Submission
When a candidate completes the wizard, you get:
| Data | Description |
|---|---|
| Employment entries | Each employer with company, title, dates, location, and supervisor contact |
| Personal information | Name and email as entered by the candidate |
| Biometric confirmation | Proof that a real person completed the form |
| Electronic signature | Legally binding attestation with timestamp |
| Requirement status | Which timeline rules were met vs. flagged |
| PDF document | Chain-of-custody document with SHA-256 integrity hash |
All data is accessible through the admin panel or API.
Session Persistence
Candidates don't need to finish in one sitting. They can:
- Close their browser and return later using the same link
- Switch devices mid-process
- Take time to look up exact employment dates or supervisor contacts
All progress is saved automatically on the server.
Data Retention
- Incomplete submissions — Purged after 90 days. A new invitation must be issued.
- Completed submissions — Retained per your organization's configured retention policy (default: 90 days, with extension options available).
- Retention warnings — Sent at 60 days via webhook (
data.retention_expiring)
Customization
Your employment claim collection is configured specifically for your organization:
| Setting | What It Controls | Example |
|---|---|---|
| Lookback period | Years of employment history required | 3 years, 7 years |
| Gap detection | Whether continuous coverage is enforced | Enabled / disabled |
| Biometric enrollment | Identity verification step | Enabled / disabled |
| Language | Invitation and wizard language | English, Spanish |
| Delivery method | How candidates receive invitations | Email, SMS, or both |
| Branding | Your organization name in the candidate experience | "Gold Coast Staffing" |
Contact your Trua Cloud account representative to adjust these settings.
Next Steps
- Employment Verification Workflow — Detailed step-by-step candidate experience
- Collection Customer API Guide — API reference for programmatic integration
- UAT Guide — Testing procedures before go-live