In this guide
A dependent record audit is a narrow accuracy check. Its purpose is to compare the people and fields involved in a benefits request with the resulting administrative record. It should not become a collection of every family document you can find.
The City health benefits resource page, checked October 2, 2026, is an official starting point for current administrator contacts and plan materials. Confirm the correction process and evidence requirements there. This independent checklist does not decide dependent eligibility or authorize a coverage change.
Define the scope before opening records
Write down what you are checking: the spelling on a confirmation, the people listed after an approved change, or whether a requested update was processed. If the question concerns eligibility rather than accuracy, label it as an eligibility question and send it to the administrator.
Choose only the fields necessary for the comparison. A private worksheet can use labels such as “dependent A” while the official form uses the information it requires. Do not place full birth dates or identification numbers in a general to-do list or shared calendar.
Compare request, acknowledgment, and result
Start with the submitted request. Next, read the acknowledgment to see what it actually confirms. Finally, compare the final response or current record. If one stage is missing, record it as missing rather than assuming that the latest screen replaces the earlier evidence.
Classify discrepancies in plain language: misspelling, missing person, unexpected person, unconfirmed effective date, or record not yet available. Avoid diagnosing the cause. The correction may require the benefits office, the plan, or another record owner to investigate.
Use a restrained checklist
- State the exact record and field being reviewed
- Locate the submitted version and relevant confirmation
- Describe the mismatch without attaching unrelated records
- Ask which office owns the correction and which evidence it accepts
- Retain the correction reference and verify the final response
If a screenshot would help, ask whether it is appropriate and remove unrelated account content through an approved method. Do not conceal a field the office needs to evaluate. A written description may be sufficient for the initial routing question.
A hypothetical spelling discrepancy
Suppose an employee notices that a dependent’s surname is spelled differently on a confirmation from the submitted request. The employee preserves both documents and asks the appropriate office how to correct that specific field. They do not submit a second enrollment election merely to try to force the spelling to change.
After receiving correction instructions, the employee records the case reference and follows the designated process. When the updated record arrives, they check that the corrected spelling did not coincide with an unintended change to the people listed. This is an accuracy example, not a statement about plan processing.
Connect the audit to the original event
If the discrepancy followed a household change, the family-status evidence guide helps identify the supporting record’s purpose. If it arose during a broader review, return to the enrollment question list so the correction does not get confused with a new coverage decision.
When the responsible office confirms the outcome, note the date and the exact field corrected. Retain records according to applicable instructions in a private location, and dispose of unneeded working copies through an appropriate method. The goal is a clear correction trail with as little duplicated family information as possible.
Related reading: Match family-status evidence to the question being asked, Turn benefits materials into a clear enrollment question list.