NearPDF

2026-10-01

A new OPM rule and employer audits that remove 3-10% of dependents — how to build your health plan verification PDF

A federal rule most people have never heard of now covers every one of the roughly 8 million people enrolled in the Federal Employees Health Benefits program. Per compliance firm Hub International's July 2026 bulletin, it "requires enrollees to provide proof of family member eligibility to the employing office, carrier, or OPM whenever a family member is added" — checked "at initial enrollment, during open season, and" after a qualifying life event — and OPM built it, in Hub's reading, "explicitly to reduce waste and curb premium growth." Private employers have been running the same check for years on their own schedules, and the results aren't trivial: consulting firm Mercer puts the typical outcome at "3% - 10% dependents removed" once a full audit concludes, each one averaging more than "$4,570" a year in dependent medical costs the plan stops paying. None of that is a government form. It's a document packet, assembled by an employee, due by an employer- or vendor-set deadline, during the same autumn open-enrollment season this post is publishing in.

What a real audit's calendar and its red line actually look like

The University of Rochester's own Dependent Eligibility Verification Audit FAQ page lays out exactly how unforgiving the clock gets. Its 2026 cycle ran "January 12 through February 20, 2026," with every document owed by "2/20/26." Miss it, and the consequence isn't a warning — ineligible dependents are simply "removed from coverage when the verification audit concludes on March 31, 2026," after a short "March 2 through March 13, 2026" appeals window closes. The same page tells employees exactly how to handle sensitive fields before they submit anything: "any additional information, including financial details or Social Security numbers, should be redacted before submission." That instruction — redact first, then send — is the detail most people miss, and it sets up the harder problem underneath it: most dependents don't verify with one document. They verify with two or three, submitted together.

One dependent, several documents, one file Example: a step-child, per the City of Seattle's own verification guide Birth certificate government-issued, parents' names Marriage certificate government-issued, dated Tax return — page 1 only amounts + SSN blacked out first One merged PDF, right-side up, in order NearPDF's delete, rotate, merge, and organize tools build this one file entirely on your device — after you've blacked out amounts and SSNs by hand first. A spouse needs two documents the same way; some portals want every dependent in one upload.
Seattle's own dependent-verification guide lists a step-child as needing three separate documents merged into one file — a pattern repeated, with two or three documents, across most dependent types.

What the document instructions actually say

The City of Seattle's dependent-verification guide, administered by Alight Solutions, is blunt about the mechanics in a way most of these pages are: "SEND COPIES ONLY! Do not send original documents." For a tax return specifically: "only send the first page of your federal tax return (Form 1040) that shows your dependents" and "black out all monetary amounts appearing on the first page of your federal tax return." For every document submitted: "black out Social Security numbers appearing on any documents submitted." Then come the combinations. A legal spouse verifies with "a government-issued marriage certificate and federal tax return within last 2 years listing spouse" — two documents — unless proof of joint ownership substitutes for the tax return. A step-child needs three: the birth certificate, the marriage certificate, and that same tax-return page. None of this is unusual phrasing specific to Seattle — the same shape (copies only, first page only, black out the sensitive fields, combine documents by dependent type) shows up across the employer and public-sector verification guides this post checked for every dependent category above an infant.

Building the packet NearPDF actually helps with

What arrives at verification time is rarely upload-ready. A birth certificate is a phone photo taken at an angle because the original is a stiff cardstock that won't sit flat on a scanner. A federal tax return downloaded from a tax-prep site is ten or fifteen pages when only page one is wanted. A marriage certificate and the spouse's half of a joint utility bill are two separate files that need to travel as one. None of that is something NearPDF decides for you — blacking out a dollar figure or a Social Security number is a step you do yourself, with a marker before scanning or your scanning app's own markup tool, before any of these files reach NearPDF at all. Once that's done, NearPDF's delete tool drops every tax-return page except the first, rotate straightens the sideways birth-certificate photo, merge combines the two or three documents a single dependent needs into one file, and organize puts several dependents' packets into the order a portal's checklist expects when one combined upload covers an entire family. None of it uploads anywhere to do this — the file is built entirely in your browser, and the only submission that happens is the one you make yourself, to your employer's benefits team or verification vendor.

The honest limits

NearPDF doesn't decide whether a document you're submitting actually satisfies your plan's eligibility rules, doesn't verify anyone's identity or relationship, and doesn't submit anything to an employer, OPM, or a verification vendor on your behalf — this post isn't benefits or legal advice, and your plan's own instructions always win over anything written here. It also doesn't black out a dollar amount or a Social Security number for you; that redaction step happens before a file ever reaches NearPDF, and skipping it means the SSN or income figure is still sitting in the PDF you merge. And it adds no password or encryption to anything it builds, which matters more here than in most document packets this blog has covered — a merged file carrying a birth certificate, a marriage certificate, and a tax return page is exactly the kind of document that's dangerous to leave in an email thread or a shared folder. If that protection step is needed, the near family's separate tool, NearSeal, exists for it, since NearPDF deliberately doesn't do it. What NearPDF handles is turning scattered scans and phone photos into the single, correctly ordered file a dependent verification deadline actually asks for — entirely on your device, before that deadline, not the audit's, closes.