Pay & Benefits
A Dependent Eligibility Audit: Submit the Right Evidence Without Oversharing
Match each dependent to the evidence your plan requests. A filled minimum-document map and complete follow-up distinguish receipt, readability and verified eligibility while keeping unnecessary family information out of the packet.
For each dependent named in the audit notice, match the evidence to the stated requirement, use the authorized submission route and retain its receipt. Redact only information the plan says is unnecessary; preserve the fields needed to establish the relationship. Then obtain a dependent-by-dependent review status. A file upload, a received packet and verified eligibility are different events, and a question about missing documents does not automatically extend the deadline.
This guide concerns a review of dependents already enrolled in an employer's health benefits, rather than adding a new spouse or child. It does not determine anyone's eligibility or guarantee continued coverage. LandOffer.ai publishes this as a workplace administration guide. Every household, document and message in the worked example is fictional; no real identity, medical or financial documents were used or uploaded.

Read the notice before collecting a family's records
Identify the plan, audit administrator, dependents listed, final filing date and the consequences described for missing or unacceptable evidence. Verify the request through your employer's established benefits contact or portal. Do not send a family document to a new address solely because a message uses the employer's logo.
Check which benefits are being reviewed. Health, dental and vision enrollment may involve different administrators or confirmations. Ask whether one packet covers all named benefits and dependents. An old enrollment confirmation does not establish that the current audit has been completed, but neither should you assume every prior document must be submitted again.
CalPERS's employer DEV guidance is a named program example. It describes recurring verification, relationship documents and notices with a final filing date, and directs employees to their employer's personnel office. Its cycles and consequences are not a universal employer-health-plan rule. Use your actual notice to establish the dates and route.
If the notice includes a dependent who is no longer eligible, ask how to report the actual change through the appropriate process. Do not submit an outdated record as proof of a current relationship. Conversely, a missing document is not itself a factual admission that the relationship is invalid; ask what evidence is deficient and how to address it.
Separate special situations from the ordinary checklist. Disability-related coverage, guardianship, domestic partnerships and other relationships can require different documentation. Ask the administrator which category applies and what evidence it accepts without sending a broader medical or family history in anticipation of a request.
Build a requirement-to-document map
Create one row for each requirement, not a folder called “family documents” with no explanation. Record the dependent, requested evidence, acceptable alternatives, fields that must remain visible and the document's date. Add the actual submission and review status after they occur. This lets a reviewer identify one missing requirement without asking you to send every sensitive family document again.
Some requirements establish a past event; others establish that a relationship remains current. A marriage certificate can show the marriage event without satisfying a separate current-relationship requirement. The distinction is explained in the CalHR re-verification FAQ, a named-program document. It also describes providing copies and redacting sensitive information unnecessary for that program's verification.
Follow the plan's own instructions about copies, dates, translations, document alternatives and required forms. Do not assume an online family photograph, a birth announcement or an insurance card proves the requested relationship. If the requested certificate is unavailable, ask about an accepted alternative or replacement before substituting a document yourself.
Submit enough evidence for the stated requirement and leave out unrelated information. It does not mean making every document nearly unreadable. Ask what may be redacted if the notice is unclear. Keep required names, relevant relationship fields, dates and issuing information visible when those are needed for verification.
Prepare a submission copy rather than modifying your only original. Check that any approved redaction removes the information from the submitted copy, rather than merely covering it with a removable shape. Confirm that the final file still shows the required names, relationship details and issuing fields clearly. Review every page for legibility and unnecessary attachments. This article does not perform a redaction test or recommend a particular software tool.
Worked packet: two dependents, three evidence requirements
This authored case concerns fictional employee Coralie at Vela Survey Systems. Notice V-28, received November 9, 2026, asks her to re-verify an already enrolled spouse and child by November 30. The invented plan's instructions require a marriage certificate plus current relationship evidence for the spouse, and a birth certificate naming Coralie as the child's parent. These are case assumptions, not a statement that every plan requires the same documents.
The notice permits a joint household statement dated within 60 days as the current evidence and explicitly allows unrelated account and transaction details to be redacted while retaining the names, shared address, issue date and document issuer. The permitted portal is confirmed through Coralie's existing employer benefits contact. She does not borrow a retiree portal route or a different employer's document policy.
| Dependent and requirement | Prepared evidence and minimum visible fields | Initial status and next action |
|---|---|---|
| Spouse: marriage event | Copy of government-issued marriage certificate. Keep both spouses' names, event date and issuing details legible under the fictional instructions. | Prepared as S-1; no unnecessary additional identity document included. |
| Spouse: current relationship | Joint household statement issued November 1 showing both names, shared address, date and issuer. Remove unrelated account number and transactions as expressly permitted. | Prepared as S-2. It is 15 days old at the November 16 submission, within the case's 60-day limit. |
| Child: parent relationship | Copy of birth certificate naming Coralie as parent, with required issuing information. No school record or medical history attached. | Prepared as C-1 revision 1, but the later review finds its scan clipped the issuing details. Replacement scan required; not verified. |
| Packet control | Completed audit checklist and V-28 case reference, using the plan's required employee identifier through its secure route. | Cover record P-1. It organizes the evidence but is not a fourth relationship proof. |
There are three relationship-evidence files and one cover record: four files in the initial packet. The spouse needs two distinct proofs; the child needs one. Calling the packet “four files uploaded” would say nothing about whether all three evidence requirements were accepted.
Coralie does not attach her entire tax return because the case's notice permits the chosen current household statement. She does not assume that this alternative would be accepted under another plan. If the administrator had required a different document, she would need that plan's accepted alternatives or a written clarification.
She retains unmodified originals in her own appropriate secure storage and a copy of the exact submitted packet through the permitted process. The working checklist identifies documents by reference rather than reproducing a child's full identifying details in ordinary email or shared work chat.
Submit through the required workflow and save its receipt
Follow the steps all the way to final submission. SFHSS's DEVA page provides a useful named-program example: it warns that selecting files alone does not complete its online process; the user must continue and submit. Its portal, fax and other routes belong to that program. The lesson is to verify the final event in your own administrator's process, not to use SFHSS's route for a different employer.
Keep the confirmation reference, submission date, filenames or document inventory and any stated review timeframe. A screenshot without the final submission status can be ambiguous. If the upload fails, report the failure through an established contact and ask for an authorized alternative. Do not turn a failed upload into “submitted” in your log or use a personal file-sharing link without approval.
Continue the fiction: on November 16, Coralie submits all four files and receives confirmation U-73. On November 18, reviewer Bran reports that S-1 and S-2 are accepted for the spouse, while C-1 cannot be reviewed because its issuing details are clipped. P-1 is received as the cover. The child's verification remains incomplete.
Coralie asks whether the existing certificate can be rescanned and whether a deadline extension is available if a replacement is delayed. The reviewer says a clear scan is needed but does not grant an extension. These are authored case events, not an observed portal outcome or an administrator response to a real employee. November 30 therefore remains the stated filing date in her record; the request has not changed it.

Worked request: confirm receipt and the remaining deficiency
Here is Coralie's completed fictional follow-up dated November 20. It uses references and statuses instead of attaching the sensitive files again. No real email or portal message was sent.
Subject: V-28 / U-73 — confirm replacement C-1 and dependent status
Hello benefits review team,
Please confirm the current status of the dependent re-verification packet for V-28, due November 30. I submitted S-1, S-2, C-1 revision 1 and cover P-1 on November 16 under U-73.
Your November 18 response states that S-1 and S-2 were accepted for my spouse, and that the child's C-1 scan was deficient because the issuing details were clipped. I understand that receipt of the packet did not complete the child's review.
I submitted C-1 revision 2 through the same authorized portal on November 19 under receipt U-81. The replacement is a clear scan of the same certificate with the required parent and issuing details visible. Please confirm that it is linked to the child and replaces the deficient revision rather than being treated as a new dependent or an unrelated attachment.
Could you confirm separately whether the replacement file has been received, whether it is readable and whether the child's eligibility verification is complete? If anything remains missing, please identify the specific field or requirement and the permitted correction route.
I requested a deadline extension on November 18 but have not received one. I am therefore still tracking November 30 as the notice's filing date. Please confirm any approved change in writing rather than leaving me to infer it from a pending review.
Please also confirm whether the accepted spouse documents complete that dependent's review for each benefit named in V-28. I have not assumed that one document status automatically updates every coverage record.
I can provide further required evidence through the authorized secure route. Please avoid returning sensitive document images in ordinary email; the case and file references should identify the packet.
Thank you, Coralie
The request asks for receipt, readability and eligibility verification separately. It preserves the deadline and the already accepted spouse evidence while identifying one precise deficiency. It does not demand an unnecessary second full-family packet or claim the replacement has already passed review.
Close each dependent's review without assuming coverage status
Continue the authored record: on November 20, the portal shows U-81 received. No reviewer has yet marked the child verified. The status is therefore “spouse evidence accepted; child replacement received, verification pending.” Two of three evidence requirements were accepted before the replacement; counting the new upload does not make that three of three accepted.
Coralie follows up on the outstanding review before the stated deadline. She asks what to do if processing is still pending, without assuming that upload receipt guarantees continued coverage or that a cancellation notice can be ignored. If a notice identifies a removal or coverage date, she requests the applicable review, correction or appeal process promptly and keeps the dated notice.
When the administrator issues a final result, compare it with each dependent and benefit listed in the audit. Retain the written outcome and verify any consequential coverage update through the authorized plan or carrier route. If the records disagree, send the specific mismatch and case references rather than resubmitting unrelated personal information. Ask who owns the correction and how you will receive a written result; keep the unresolved dependent or benefit listed until that result is available.
Further workplace guides are available through LandOffer.ai. The useful result here is a minimal, sufficient and traceable evidence packet, plus a clear written status for every dependent. Until the reviewer makes the remaining determination, keep that determination visibly pending.
Sources and Further Reading
- CalPERS: Dependent Eligibility Verification — Employers — updated February 18, 2026; checked October 27, 2026. Named state/CSU program example; documents, cycle and employee route are not universal.
- CalHR: Dependent Re-Verification FAQs for Human Resource Offices — September 2024 file; current public five-page document checked October 27, 2026. Program-specific copies, unnecessary-information redaction and relationship evidence guidance.
- SFHSS: DEVA Audit — posted February 9, 2026; checked October 27, 2026. Its final-submit warning illustrates why uploaded and submitted are distinct; no account workflow was tested.


