--- title: "Schedule A policy dates: plan year and renewal research" description: "Separate Schedule A policy periods, plan years, receipt dates, and research dates. Build a historical benefits calendar with producer confirmation." canonical: "https://scalewithsearch.com/articles/schedule-a-policy-dates-plan-year-renewal-research" --- ## 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 policy dates: build a historical benefits calendar without inventing renewals A benefits research calendar needs a label that explains what each date proves. A reported contract end belongs to a historical interval. Turning that interval into an upcoming renewal requires current evidence from the agency's responsible reviewer. Start with separate fields for the plan year, policy period, filing receipt, and research extraction. Keep the original dates beside any month used for sorting. Give a licensed producer a clear question to resolve before a historical pattern enters the agency's working calendar. The [public-signals overview for benefits agencies](/intelligence/insurance-agencies) describes the broader research function. This guide focuses on the dates within one filing and its insurance contracts. The proposed calendar below is an internal research aid, with no automatic reminders or outreach. ## Read the plan year and policy period separately The 2025 Schedule A header identifies the calendar or fiscal plan year. Part I, line 1(f) and line 1(g), separately request the policy or contract year's beginning and ending dates. These labels appear on [the official 2025 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). The distinction affects which interval a researcher describes. Under the general instruction, Schedule A information concerns the insurance contract or policy year ending with or within the plan year. The instructions also permit reporting on a plan-year basis when the insurer maintains its 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). Read the dates before writing an interpretation. Do not impose a calendar-year assumption because the file carries a year in its name. The [DOL dataset catalog](https://www.dol.gov/agencies/ebsa/about-ebsa/our-activities/public-disclosure/foia/form-5500-datasets) says datasets from 2009 onward represent the form year. That is the year printed on the form, rather than a substitute for its reported plan-year dates. For the agency's note, preserve the reporting basis when it is known. When the basis is unclear, ask the reviewer to resolve it. A tidy month grouping cannot supply the missing explanation. ## Use a non-calendar example to test the labels Consider a fictional plan whose reporting year begins April 1, 2025, and ends March 31, 2026. One fictional medical contract runs from October 1, 2024, through September 30, 2025. A fictional dental contract runs from January 1, 2025, through December 31, 2025. Both contract end dates fall within this example's plan year. Their beginning dates differ from the plan-year beginning date. These intervals illustrate the general reporting instruction, without establishing any real employer's arrangements. | Date label | Fictional medical row | Fictional dental row | | --- | --- | --- | | Plan-year beginning | April 1, 2025 | April 1, 2025 | | Plan-year ending | March 31, 2026 | March 31, 2026 | | Reported policy beginning | October 1, 2024 | January 1, 2025 | | Reported policy ending | September 30, 2025 | December 31, 2025 | | Historical end-month group | September | December | | Confirmed current renewal | Unknown | Unknown | If the calendar groups these rows by the plan-year end, both land in March. That sorting loses the reported September and December distinctions. If the calendar advances each policy end by one year, it creates future dates unsupported by this example's evidence. Keep the historical interval intact. Ask whether the current contract still follows that cycle. A producer might confirm a different current arrangement, or might leave the question unresolved. Either result belongs in its own field. ## Keep filing receipt and extraction outside the contract period A filing receipt date answers a different question from a policy date. The [DOL datasets guide, pages 1 and 2](https://www.dol.gov/sites/dolgov/files/ebsa/pdf_files/form-5500-datasets-guide.pdf) identifies date received as a system-generated field. The [2025 core-file layout, field 102](https://askebsa.dol.gov/FOIA%20Files/2025/Latest/F_5500_2025_Latest_layout.txt) names it `DATE_RECEIVED`. In the research note, label that value as the filing's received date. Avoid calling it a policy effective date, renewal date, or producer confirmation. A later receipt does not move the reported contract interval forward. Add an extraction date for the day your agency obtained the source snapshot. This is a recommended research field maintained by your team. It is separate from the filed values. Store the snapshot location with it so another person can inspect the same evidence. For example, a fictional extraction performed October 28, 2026, might retrieve a filing received October 15, 2026. Neither date changes the fictional September 30, 2025, policy end above. The extraction is recent; the contract evidence still describes an earlier interval. A research meeting should be able to answer both questions: when did we inspect this source, and which period does it describe? Put both answers in the row rather than expecting staff to reconstruct them from a filename. ## Preserve several contracts within one filing Do not reduce every filing to one carrier row or one month. The Schedule A form directs filers to provide separate schedules for contracts, with a stated exception for individual contracts grouped as a unit. See [2025 Schedule A, Part I heading](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 [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` as the filing identifier. It identifies `FORM_ID` as a schedule identifier where several schedules occur within a filing. Its Schedule A table confirms that one filing may have multiple Schedules A. For a business review, the practical requirement is traceability. Retain the filing reference and the individual schedule reference with each calendar row. Keep both medical and dental rows in the fictional example. A shared sponsor or carrier does not justify replacing their different intervals with one date. Keep contract identifiers in the restricted supporting record when needed for verification. Use a neutral row label in meeting materials. The calendar can show that two historical contracts differ without exposing contract numbers in a public demonstration. When comparing years, ask whether the rows describe the same contract arrangement. Similar carrier names and nearby dates are comparison clues. Require the analyst to record the match basis before the producer interprets an apparent change. ## Handle the grouped-contract exception without filling blanks The instructions contain an exception that a calendar must preserve. For line 1(f), the beginning date stays blank when separate contracts covering individual employees are grouped. See [2025 Schedule A instructions, printed page 23, lines 1(f) and 1(g)](https://www.dol.gov/sites/dolgov/files/EBSA/employers-and-advisers/plan-administration-and-compliance/reporting-and-filing/form-5500/2025-instructions.pdf). A blank beginning date therefore needs inspection. Do not copy the plan-year beginning into it to complete the display. Keep the original blank and a review question about the applicable reporting treatment. Use separate states for a present date, a blank field, and an unreadable value. A date that staff cannot interpret should not enter a month group as if it were verified. Place that row in a date-review list with its source reference. For the permitted plan-year reporting exception, retain any supporting explanation the reviewer finds. Do not silently relabel a plan-year-based interval as the commercial contract's actual term. The calendar's caption should state the reporting basis that the source supports. ## Prepare a historical-date calendar staff can review Choose a small fictional sample before adopting the format for business research. Give the benefits principal a view that answers which rows deserve current confirmation. Use the following proposed fields as a starting point. | Calendar field | Purpose | | --- | --- | | Filing and schedule reference | Locate the exact source row | | Form year and plan-year interval | Explain the reporting context | | Reported policy beginning and ending | Preserve the source interval | | Benefit category and carrier | Distinguish the contract arrangement | | Receipt and extraction dates | Show filing timing and research timing | | Historical end month | Support historical sorting | | Reporting-basis question | Preserve exceptions or uncertainty | | Current-confirmation status | Separate pending work from checked timing | | Confirmation source and date | Support the producer's current finding | | Licensed reviewer | Name responsibility for the working date | Use explicit confirmation states such as pending, confirmed, conflicting, and unavailable. Define what each means in your agency. A row can remain useful historical evidence while its current timing remains unavailable. The licensed producer should record what was confirmed and the evidence used. Confirmation of employer identity alone does not confirm the current contract date. Confirmation of one benefit line does not settle every other line in the filing. Keep the agency's approved working calendar linked to this evidence rather than overwriting it. The [insurance agency office overview](/for/insurance-agencies) describes preparing renewal notes from approved date lists. Historical filing research needs that additional confirmation before supporting those office notes. When staff also compare reported coverage, use the [covered-person count guide](/articles/schedule-a-covered-person-counts-contract-comparison). Its population question is separate from confirming the contract date. Carry the same schedule reference into both notes so reviewers can trace each interpretation. ## Keep source revisions visible The DOL publishes both All and Latest datasets. All can contain amended or duplicate filings. Latest includes only the latest received filing for a plan with status `FILING_RECEIVED`. See [the datasets guide, page 1, All Versus Latest Datasets](https://www.dol.gov/sites/dolgov/files/ebsa/pdf_files/form-5500-datasets-guide.pdf). Record which collection the analyst used. Preserve the snapshot reference and any replaced filing reference. When a later source changes a policy date, show the change for review. Do not erase the prior finding or automatically replace a producer-confirmed current date. This approach leaves a useful question for staff: did the source change, or did our understanding change? Record the correction with its reason. The [business-memory guide](/articles/business-memory-for-ai-agents-guide) explains how owned source records and corrections support repeatable work. ## Accept the research view before using it Ask the analyst to demonstrate the fictional non-calendar example, two contracts under one filing, and a grouped-contract blank. Add a changed filing and an unresolved current date. Each case should preserve its evidence and produce a readable review question. Have the producer check the labels without relying on an explanation from the builder. The historical calendar should communicate its limits on its own. Keep quoting, binding, coverage advice, and external communication within the agency's responsible processes. Scale With Search can scope the research view around your approved sources, calendar fields, and named reviewers. Bring the sample rows and the decisions staff need to prepare. [Discuss the calendar 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 covered-person counts: compare contracts without inventing an employer census](/articles/schedule-a-covered-person-counts-contract-comparison). [insurance agencies](/for/insurance-agencies): website and search resources. ## Related: insurance agencies - [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) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```