Why this history belongs in a hiring file
The federal health plan waiting period rule can be traced through three dated steps in one CMS FAQ page. A hiring file is stronger when it shows where that rule came from, not just what the current paperwork says. A short, dated history gives a reviewer a clear trail: what was proposed, when, and what the agencies said about timing.
This post walks through three dates from one official source, a set of frequently asked questions published by the Centers for Medicare & Medicaid Services (CMS) on its Affordable Care Act implementation pages. The source is the CMS "Affordable Care Act Implementation FAQs - Set 16" page. Each date below comes from that page, and the wording is kept close to the original so that you can check it yourself.
This post does not explain what a plan must do today. Rules can be amended, and the page you cite may not be the latest word on the subject. Treat this as a guide to building an accurate history, and confirm current requirements with your benefits administrator or legal counsel before making a decision that depends on them.
The first guidance in 2012
The CMS FAQ page states: "On February 9, 2012, the Departments issued guidance outlining various approaches under consideration with respect to PHS Act section 2708 and solicited comments."
Three details in that sentence matter for a hiring file.
The document was guidance, not a final rule. It described approaches that were under consideration. Writing that the rule took effect on this date would overstate what the page says. A more accurate note is that the agencies issued guidance on this date and asked for public comments.
The provision named is PHS Act section 2708. The page does not spell out every detail of that section in this passage, so your file should name the section exactly as the source does rather than paraphrasing it into a broader claim.
The phrase "solicited comments" shows that the process was open. Public comment is often part of how federal agencies develop a rule, which helps explain why the history contains more than one step.
A simple entry could read: "February 9, 2012: federal agencies issued guidance on approaches under consideration for PHS Act section 2708 and requested public comments. Source: CMS, Affordable Care Act Implementation FAQs - Set 16."
The proposed regulations in 2013
The second date comes from the same page, which describes what followed the first round of guidance. The same CMS FAQ page states: "After consideration of all of the comments received in response to the February 2012 and August 2012 guidance, the Departments published proposed regulations on March 21, 2013."
This sentence adds two points to the timeline.
The first is that there was a second round of guidance. The page refers to guidance from August 2012 alongside the February 2012 guidance. A complete history should show both rounds, because the agencies considered comments received in response to both before publishing the proposed regulations. Leaving out August 2012 would make the timeline look simpler than the record is.
The second is the difference between guidance and proposed regulations. Proposed regulations are a draft stage, published so that the public can respond before the agency settles the final text. The page uses "proposed regulations" here and "final regulations" in a later answer, so your file should keep those terms separate.
A useful entry could read: "March 21, 2013: the federal departments published proposed regulations after reviewing comments received on the February 2012 and August 2012 guidance.
This entry does not say what the proposed regulations required. The CMS sentence does not describe the content of the proposal, so the file should not supply it from memory. If the content matters for the hiring decision, pull the proposed regulation itself and cite it separately.
The timing statement about final regulations
The third date appears in a question and answer on the same CMS page. The question asks: "Q2: Will the Departments be issuing final regulations under PHS Act section 2708 that give plans and issuers sufficient time to comply with the waiting period limitation?"
The answer states: "To the extent final regulations are more restrictive on plans or issuers than the proposed regulations, they will not be effective prior to January 1, 2015 and the Departments expect they will give plans and issuers sufficient time to comply."
This answer contains a rule about timing, and its wording needs care.
The answer does not say that final regulations were issued on any particular date. It says that if final regulations were more restrictive than the proposed regulations, they would not take effect before January 1, 2015. That date is therefore a floor on the effective date in that situation, not a statement that a rule began on that day.
The answer also says the Departments "expect they will give plans and issuers sufficient time to comply." That is an expectation stated by the agencies, not a guarantee written into the answer. Describe it as an expectation in your file.
The question uses the phrase "waiting period limitation." That is the term the page uses for the subject of this history, so keeping it in your file helps the history stay consistent with the source.
A useful entry could read: "Stated in CMS FAQs: any final regulations more restrictive than the proposed regulations would not be effective before January 1, 2015, and the Departments expected to give plans and issuers sufficient time to comply.
How to cite these dates correctly
Accurate citation is what makes a history useful in a file. The following practices apply to any federal source, including this one.
Quote the source word for word when the wording matters. Where a date or term carries legal weight, paste the exact sentence in quotation marks and include the link. Paraphrasing can change meaning, especially with words like "guidance," "proposed," "final," and "effective."
Record the title, publisher, URL, and the date you viewed the page. Web pages change. A viewing date shows when you checked the source, and it lets a later reviewer understand what the page said at the time. Use the page's full title, which in this case is "Affordable Care Act Implementation FAQs - Set 16 | CMS."
Keep the stages separate. The history in this post includes distinct kinds of events: guidance that asked for comments, a second round of guidance, proposed regulations, and a timing statement about possible final regulations. Give each its own line and date. Combining them into one "rule date" hides steps a reviewer may want to see.
Distinguish "issued," "published," and "effective." These words are not interchangeable. A document can be issued on one day, published in an official publication on another day, and take effect later still. Use the verb the source uses. The CMS page says "issued" for the first guidance, "published" for the proposed regulations, and "effective" for the timing statement.
Do not add facts the source does not give. If you want to say what a rule requires, find the rule text and cite it separately. A hiring file should not rely on a summary that goes beyond the page it cites.
Note the source's limits. The CMS page is an FAQ that answers questions in plain language. Say so in your file, so a reader knows the entry summarizes what the page says rather than serving as legal text in its own right.
A sample citation block
One layout for the history in a hiring file is shown below. Adapt the wording to your own format, but keep the dates and quotations exact.
Health plan waiting-period rule history (sources checked on the date noted)
February 9, 2012
Federal agencies issued guidance on approaches under consideration
for PHS Act section 2708 and solicited comments.
Source: CMS, "Affordable Care Act Implementation FAQs - Set 16"
https://www.cms.gov/cciio/resources/fact-sheets-and-faqs/aca_implementation_faqs16
March 21, 2013
Federal departments published proposed regulations after considering
comments received on the February 2012 and August 2012 guidance.
Source: same as above.
January 1, 2015 (timing statement)
The CMS FAQ states that final regulations more restrictive than the
proposed regulations would not be effective before January 1, 2015,
and that the Departments expected to give plans and issuers sufficient
time to comply.
Source: same as above.
Date viewed: ____________
Viewed by: ____________
What these dates do not establish
A reader should understand the limits of this history before relying on it. The three dates show the sequence of federal steps as the CMS page describes them. They do not show:
- the full text of the guidance, the proposed regulations, or any final regulations;
- whether a particular employer's plan followed a particular rule in a particular year;
- what coverage a specific employee was entitled to on a specific day;
- any state law that may apply in addition to federal rules.
That last point deserves emphasis. Federal rules are one layer of the picture. Some states set their own requirements for employers, and this post does not cover any state. If a hiring file involves a state-specific question, cite the state's own official source and keep it separate from the federal history described here.
Employer documents matter too. A plan document, a summary of benefits, or a written offer letter may describe the waiting period in terms that matter more for an individual hire than any general history. The federal timeline gives context, and the plan documents give the operative terms. For a related guide on recording decisions, see Hiring Decision Debrief: Notes to a Recorded Decision.
Keeping the history current
Because rules change, a history written today can become incomplete later. Build a simple routine for keeping it accurate.
Check the source again before each use. Open the CMS page and confirm that the sentences you quoted still appear. If they have changed, update your file and note the date of the change.
Look for newer guidance and final rules. The CMS page is one source. When you work on a file, search for later documents that address the same provision, such as a later final rule, a later FAQ set, or an official notice.
Record the set number. The CMS page is titled "Set 16," which places it in a numbered series of FAQs. Include that number in your citation so a reader can find the same page even if the site is reorganized.
Assign an owner. A history that no one maintains will drift out of date. Name the person responsible for checking the sources, and have them sign off when the file is reviewed. A recruiting records audit can help check the file's contents.
Involve counsel for decisions with legal stakes. If a waiting period question could lead to a dispute, an audit, or a claim, counsel should review the history before anyone relies on it. A recruiter or HR professional can assemble the timeline, but legal conclusions belong to a qualified advisor.
Why the order of the dates matters
The order is part of the story. The February 2012 guidance came first and asked for comments, and the August 2012 guidance followed. The March 2013 proposed regulations came after the agencies weighed comments on those earlier documents.
The January 2015 timing statement is a separate answer about final regulations. It belongs apart from the 2012 and 2013 sequence rather than being read as a later step in it. Presented out of order, the dates can look contradictory. A reader might wonder why a 2015 date appears before a 2013 event, or assume a proposed rule was already in force. Keeping the sequence and the separate answer clearly labeled prevents that confusion.
Writing the summary line
Most hiring files benefit from a one-paragraph summary at the top of the history, followed by the detailed entries. A good summary is short and does not overstate anything. For example:
"Federal agencies issued guidance on PHS Act section 2708 in February 2012 and again in August 2012, published proposed regulations on March 21, 2013, and stated that any final regulations more restrictive than the proposed regulations would not take effect before January 1, 2015.
The summary repeats the source's wording where it matters and draws no conclusions about any employer or employee. The detailed entries below it supply the rest.
Common mistakes to avoid
Several errors come up often when people write up a regulatory history for a personnel file.
Treating a proposal as a rule. A proposed regulation is a draft. Write "proposed" and do not write "required" unless a later final source says so.
Treating a timing statement as a date of change. The January 1, 2015 date in the CMS answer is the earliest effective date for a certain kind of final regulation. It is not the date on which a rule was adopted.
Dropping the August 2012 guidance. The CMS page names it alongside the February 2012 guidance. Leaving it out makes the timeline look shorter than the source record.
Writing from memory. Recollections of rule dates are easy to get wrong. Check each date against the source before it goes into a file.
Citing a secondary summary as if it were official text. Blog posts, vendor newsletters, and articles like this one are useful for context, but a hiring file should cite the official source the summary relies on.
Forgetting to date the entry. A history without a viewing date can look current when it is not. Always record the date you checked.
A short checklist before you file
Before you add the history to a hiring file, run through this list:
- Each date matches the wording of its source.
- Each event uses the verb the source uses: issued, published, effective, or asked for comments.
- The February 2012 and August 2012 guidance both appear.
- The March 21, 2013 proposed regulations are not described as final.
- The January 1, 2015 date is described as a timing statement about more restrictive final regulations, not as the start of a rule.
- Every entry includes a link to the source.
- The viewing date and the name of the person who checked the sources are recorded.
- Any state-specific question is cited to a separate official state source.
- A note states that plan documents and counsel control current requirements.
If any item is missing, fix it before the file is reviewed. A short, accurate history is more useful than a long one that goes beyond its sources.
Summary
The health plan waiting period rule has a traceable history, and the CMS FAQ page gives a clear starting point for a hiring file. The first step is the February 9, 2012 guidance, which described approaches under consideration and asked for comments. The second is the March 21, 2013 proposed regulations, which followed review of comments on the 2012 guidance. Separately, the CMS page's timing statement gives January 1, 2015 as the earliest effective date for any final regulations more restrictive than the proposed regulations.
Cite each date with its source, quote the wording where it matters, keep the stages separate, and record when you checked. A history describes past steps and does not settle what a plan requires today. For that answer, go to the plan documents, the current official rule text, and a qualified advisor.
Source for all three dates: Centers for Medicare & Medicaid Services, "Affordable Care Act Implementation FAQs - Set 16".