--- title: "Schedule A covered-person counts: compare contracts" description: "Read Schedule A line 1e with its policy period and benefit flags. Compare counts while preserving overlap, missing values, and review questions." canonical: "https://scalewithsearch.com/articles/schedule-a-covered-person-counts-contract-comparison" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # Schedule A covered-person counts: compare contracts without inventing an employer census A Schedule A covered-person count describes reported insurance-contract coverage. Reading it as an employer's workforce size changes the meaning of the source. Adding several benefit counts can create another unsupported number when the same people appear in more than one contract. Keep the count beside its benefit category, contract interval, and filing reference. Ask a licensed benefits reviewer to resolve the population before using it for current business decisions. A useful comparison can end with an unanswered question. The [benefits-agency research overview](/intelligence/insurance-agencies) introduces historical contract analysis. This guide explains one measure inside that work. It provides no employer census, current enrollment estimate, or personal insurance recommendation. ## Read line 1e before naming the measure On the 2025 Schedule A, Part I, line 1(e), asks for an approximate count of persons covered at the policy or contract year's end. The adjacent fields identify the carrier, contract, and policy interval. Read [the official form, page 1, version 250312](https://www.dol.gov/sites/dolgov/files/ebsa/employers-and-advisers/plan-administration-and-compliance/reporting-and-filing/form-5500/2025-schedule-a.pdf) before choosing a display label. The instructions explain the approximation: coverage can fluctuate during the year. They direct the administrator to estimate persons covered by the contract at the policy or contract year's end. For grouped contracts covering individual employees, the instructions instead use the plan-year end. See [2025 instructions, printed page 23, line 1(e)](https://www.dol.gov/sites/dolgov/files/EBSA/employers-and-advisers/plan-administration-and-compliance/reporting-and-filing/form-5500/2025-instructions.pdf). A practical label is “reported approximate persons covered,” followed by the relevant period and basis. Keep “approximate” visible in the comparison. Avoid replacing it with employees, subscribers, households, or unique lives unless separate evidence supports that population. The instruction defines a point-in-time estimate for reporting. It does not provide an average across the year. A researcher should not describe the figure as average enrollment or multiply it by months to invent a person-month measure. ## Separate contract counts from Form 5500 participants Core Form 5500 participant fields have their own instructions. The 2025 guidance for lines 5 and 6 explains welfare-plan participation and says covered dependents are excluded from those participant counts. It also discusses former employees receiving continuation coverage. See [2025 instructions, printed page 18, Lines 5 and 6](https://www.dol.gov/sites/dolgov/files/EBSA/employers-and-advisers/plan-administration-and-compliance/reporting-and-filing/form-5500/2025-instructions.pdf). Do not transfer those participant-count rules onto Schedule A line 1(e). The fields answer different reporting questions. Preserve their original labels if both appear in an analyst's research note. For example, a fictional core participant field might show 150 while a fictional medical contract count shows 240. That difference alone does not establish an error, a dependent count, or an employee count. Check the definitions, population, and dates before explaining it. Employer headcount is another measure requiring its own source and date. Neither a core plan count nor one contract count establishes every person employed by the organization. A research note should identify the missing workforce evidence rather than manufacture a census. Retirement-plan participant analysis also requires its own definitions. Keep pension account-balance measures outside this benefits-contract comparison. Similar-looking numbers in separate schedules do not create interchangeable populations. ## Test addition with a fictional medical and dental pair Suppose a fictional filing has two Schedule A rows. The medical row reports approximately 240 persons covered. The dental row reports approximately 210. Assume this exercise uses the same reported ending date for both contracts. | Fictional contract | Reported approximate persons | Benefit category | Reported ending date | | --- | --- | --- | --- | | Medical row M | 240 | Health | December 31, 2025 | | Dental row D | 210 | Dental | December 31, 2025 | Adding the reported values produces 450. The arithmetic is correct, but its label matters. It is the sum of two contract counts. Without overlap evidence, it is not a count of distinct covered people or employees. Consider two hypothetical arrangements solely to expose the ambiguity. If all 210 people on the dental contract also appear on the medical contract, the distinct population would be 240. If the populations were entirely separate, the distinct population would be 450. The two reported values alone cannot identify the actual overlap. These arrangements are explanatory assumptions, not findings about typical benefits enrollment. Even the counts are approximate. Do not publish the illustration's endpoints as a verified population range for a real employer. For an ordinary comparison, keep both rows and leave unique population unknown. The reviewer can decide whether an authorized aggregate source is necessary for the business question. Do not collect individual medical or dependent records merely to make a public-data table look complete. ## Retain the benefit flags that describe the row Schedule A Part III, line 8, provides benefit and contract type selections. The form includes health, dental, vision, life insurance, disability, and other categories. See [2025 Schedule A, page 4, line 8](https://www.dol.gov/sites/dolgov/files/ebsa/employers-and-advisers/plan-administration-and-compliance/reporting-and-filing/form-5500/2025-schedule-a.pdf). The [2025 Schedule A layout, fields 49 through 61](https://askebsa.dol.gov/FOIA%20Files/2025/Latest/F_SCH_A_2025_Latest_layout.txt) preserves these indicators in the published file. Field 62 holds the text for an “other” selection. Field 11 names the count `INS_PRSN_COVERED_EOY_CNT`. Fields 12 and 13 hold the policy beginning and ending dates. Keep all reported benefit selections with the row. If several categories appear, do not duplicate the full count into each category and add the copies. A combined row needs a combined label until a supported breakdown exists. Do not assign an unmarked benefit category from the carrier name. If a record lacks the category needed for a comparison, place it in an unresolved group. Explain how many rows remain outside the comparison and why. For a meeting, a clear category note might read: “Health and dental selected; no separate count by benefit available in this row.” That statement describes the evidence limit. It gives the reviewer a specific question without implying missing enrollment that the source never promised to provide. ## Carry the period into every comparison A year-end label is incomplete without the relevant year and basis. The general Schedule A instruction concerns a contract or policy year ending with or within the plan year. It also permits plan-year reporting where the insurer maintains records that way. See [2025 instructions, printed page 23, Specific Instructions](https://www.dol.gov/sites/dolgov/files/EBSA/employers-and-advisers/plan-administration-and-compliance/reporting-and-filing/form-5500/2025-instructions.pdf). Before comparing two counts, check whether their intervals and reporting bases align. A September-ending medical contract and a December-ending dental contract describe different observation points. The calendar-year filing label does not remove that difference. Use the [Schedule A policy-date guide](/articles/schedule-a-policy-dates-plan-year-renewal-research) to separate plan years, policy intervals, filing receipt, and extraction dates. Keep those dates attached when the table moves into a presentation or another research file. For a comparison across years, record both source rows. If one count changes from 240 to 260, describe the reported change first. Current hiring, benefit elections, contract structure, and reporting corrections remain questions until suitable evidence resolves them. The researcher can prepare a question about the difference without declaring employer growth. A licensed producer and the agency's responsible analyst determine what further evidence serves the business purpose. ## Preserve missing values and distinct schedules The layout describes the covered-person field as text. It separately names the filing and schedule identifiers. See [2025 Schedule A layout, fields 1, 2, and 11](https://askebsa.dol.gov/FOIA%20Files/2025/Latest/F_SCH_A_2025_Latest_layout.txt). Read the actual value before treating it as a usable number. In your research view, distinguish blank, reported zero, and unreadable. Do not replace a blank with zero. An unresolved value should remain visible as a review item rather than quietly disappearing from a total. Preserve separate contracts under the same filing. The [DOL datasets guide, pages 2 and 3](https://www.dol.gov/sites/dolgov/files/ebsa/pdf_files/form-5500-datasets-guide.pdf) identifies `ACK_ID` for filings and `FORM_ID` for schedules. It confirms that one filing can contain multiple Schedules A. Keep the count attached to its schedule reference. If a matching process finds several possible rows, leave the match unresolved. Selecting the largest count can conceal another contract or an incorrect comparison. ## Write a comparison note with an answerable question Use a compact note that the reviewer can check against the source. The following fictional example carries the measure and its limits together. > Medical row M reports approximately 240 persons covered at December 31, 2025. Dental row D reports approximately 210 for the same date. Their overlap is unknown. Unique employees and current enrollment remain unknown. Review whether comparable current aggregate evidence is available for the agency's stated research purpose. Attach the following proposed fields to that note. Keep restricted supporting identifiers out of public examples. | Field | What the reviewer needs | | --- | --- | | Filing and schedule reference | Exact source for each reported value | | Form year and extraction date | Version and research timing | | Reported count and original label | Approximation and population preserved | | Benefit selections | Full category context, including multiple flags | | Policy interval and reporting basis | Comparable observation period | | Missing-value state | Blank, zero, unreadable, or usable | | Comparison question | Difference the agency needs to understand | | Reviewer and disposition | Accepted, corrected, pending, or excluded | Assign the analyst to verify transcription and matching. Assign the licensed producer to check whether the interpretation fits the agency's benefits-research purpose. Keep professional advice and any later external communication with responsible staff. The [insurance agency office guide](/for/insurance-agencies) covers preparation from approved office records. This public-data note belongs earlier in the research process. A historical count should not become a client-facing statement merely because it appears in an organized table. ## Keep revisions and exclusions in the owned record The DOL catalog distinguishes form year from plan year for modern datasets. Its guide also distinguishes All filings from the Latest collection. See [the source catalog](https://www.dol.gov/agencies/ebsa/about-ebsa/our-activities/public-disclosure/foia/form-5500-datasets) and [datasets guide, page 1](https://www.dol.gov/sites/dolgov/files/ebsa/pdf_files/form-5500-datasets-guide.pdf). Record the selected collection and snapshot with the comparison. If a later filing changes the count, preserve the earlier note and the correction reason. Keep excluded rows visible with their missing evidence, so the next review does not repeat the same unsupported interpretation. The [business-memory guide](/articles/business-memory-for-ai-agents-guide) explains keeping sources, decisions, and corrections in business-owned records. For benefits research, the useful memory includes why a comparison stayed unresolved. Before accepting the view, test overlapping medical and dental rows, different policy endings, a blank count, and several benefit flags. Require the result to retain each distinction. Scale With Search can scope that research handoff around your approved sources and named reviewers. [Discuss the comparison scope](/work) Continue the website review: [AI-native insurance agencies: the first functions to build](/articles/ai-native-insurance-agencies-first-functions); [Insurance agency AI rules: data, approvals, and spend](/articles/insurance-agency-ai-rules-data-approvals-spend); [Certificate of insurance requests: brief the website page](/articles/insurance-agency-certificate-request-website-page); [Insurance agency claims pages: verify every contact](/articles/insurance-agency-claims-contact-directory); [Commercial insurance pages: explain the businesses served](/articles/insurance-agency-commercial-industry-pages); [Insurance policy service pages: separate each request](/articles/insurance-agency-existing-policy-service-page); [Insurance agency FAQs: publish answers with limits](/articles/insurance-agency-faq-content-review); [Insurance agency Google reviews: build a neutral request](/articles/insurance-agency-google-review-request-page); [Insurance agency local SEO: fix the office pages](/articles/insurance-agency-location-pages-local-seo); [Insurance agent bios: make license details verifiable](/articles/insurance-agency-producer-license-bio-links); [Insurance website conversions: count received inquiries](/articles/insurance-agency-quote-inquiry-measurement); [Insurance agency rebrand: map old website links](/articles/insurance-agency-rebrand-domain-redirect-map); [Insurance quote forms: make the request step clear](/articles/insurance-quote-request-website-form); [Schedule A policy dates: build a historical benefits calendar without inventing renewals](/articles/schedule-a-policy-dates-plan-year-renewal-research). [insurance agencies](/for/insurance-agencies): website and search resources. ## Related: insurance agencies - [Schedule A policy dates: build a historical benefits calendar without inventing renewals](/articles/schedule-a-policy-dates-plan-year-renewal-research) - [AI-native insurance agencies: the first functions to build](/articles/ai-native-insurance-agencies-first-functions) - [Insurance agency AI rules: data, approvals, and spend](/articles/insurance-agency-ai-rules-data-approvals-spend) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```