An HRA plan document is the written record of how a health reimbursement arrangement works. It should say who can join, what the employer will reimburse, and how a claim is handled. For a Washington employer, the useful question is not where to download a template. It is whether the papers match the plan the company intends to run.
This guide is a planning aid for that review. It is not legal, tax, or ERISA advice, and it does not replace counsel. Washington Health Insurance Agency (WHIA) helps employers compare the design choices that those papers have to describe.
Book a conversation about your benefits plan
What does an HRA plan document do?
A health reimbursement arrangement is an employer-funded benefit. The employer sets the terms and reimburses eligible expenses. The governing document is where those terms live. A brochure, an enrollment email, or a vendor dashboard is not a substitute for it.
People use the same name for different papers. The governing document sets the rules. A summary plan description, when one is required, explains those rules to participants. A notice tells someone about a choice or a deadline. A claim form tells them how to ask for money. Those jobs can overlap, but they are not the same job.
The IRS overview of health reimbursement arrangements describes the main HRA designs and the rules that grew around them. Which papers you need depends on the design. Do not assume a vendor template covers every duty. Ask which records apply, and who drafts, approves, sends, and stores each one.
WHIA's guide to how an HRA works covers the arrangement itself. This article stays on the document set. Write a short design note first: who is eligible, what you will pay, when it starts, and who runs each step. That note is not the plan. It is the list you use to test the plan.
Which records belong with an HRA plan document?
Start with an inventory. One HRA can need a different set of papers than another, based on who is eligible and how the benefit sits next to other coverage. A benefits adviser or counsel should confirm the list for your facts.
- Governing plan document. The terms that create the arrangement. Look for eligibility, dates, limits, covered expenses, claims, amendments, and how the plan ends.
- Summary plan description or participant summary. The version employees read. Confirm that an SPD is required, and that this copy matches the governing terms. WHIA's note on summary plan description requirements is the place for that duty. This article does not restate it.
- Notices and enrollment materials. Papers that explain a choice, a deadline, or how this benefit works with other coverage. The right notice depends on the HRA type.
- Claims and substantiation steps. How someone files, what proof is required, who decides, and how a denial can be reviewed.
- Administrative agreements. The contract with an administrator, plus the internal steps for eligibility files, payments, privacy, and recordkeeping.
- Related plan documents. The medical plan or other benefit that works alongside the HRA. Read them together so dates and eligibility language do not clash.
Name an owner for every row. The employer still approves the design when a vendor supplies the form. For each item, write who prepares it, who checks it, who signs off, when it goes out, and where the current copy is kept.
What should the governing document address?
Do not stop at the title page. Read whether the clauses describe the decisions you already made. The prompts below are not a legal checklist.
Eligibility and participation
Name the groups that can join and when they become eligible. Check new hires, part-time or variable-hour staff, waiting periods, leave, status changes, and the end of employment. If classes are treated differently, that split should be intentional and should match the enrollment file.
Effective dates and the plan year
Confirm the start date, the period used for limits, and how a person's hire date or coverage date affects participation. If the HRA launches next to a medical plan, line the dates up before you announce an enrollment deadline.
Reimbursement terms and limits
Check the amount, any difference by class or coverage tier, and whether unused amounts carry forward. State which expenses qualify and what proof the administrator needs. A line that says "medical expenses are covered" is too vague unless the document defines it and the administrator can apply it.
Designs do not share one set of words. An individual coverage HRA, a qualified small employer HRA, and a group-integrated HRA can have different notice and coordination rules. Do not paste one design's language into another. Use WHIA's guide to HRA types to frame the question, then let an adviser confirm the fit.
Claims, proof, and review
Say how a person submits a request and what proof is required. Name who reviews it, what happens when a file is incomplete, how the decision is sent, and what review is available. Do not promise a turnaround time until the administrator agrees the workflow can meet it.
Reimbursement uses health information, so decide who may see a file, where it is stored, and what the employer is allowed to receive. Ask the administrator and counsel to review privacy and retention for this arrangement. The IRS Publication 969 is a useful background source on employer health plans, but it is not a substitute for a review of your document.
Changes and the end of participation
Read the clauses on amendments, renewal, carryover, and termination. Know how a change is approved, written down, told to employees, and put into daily use before anyone announces it. Also check how a claim incurred before someone leaves is handled.
How do the papers fit together?
Use this table to see what each record is for. It does not decide which documents the law requires for your company.
| Record | Main job | What to verify | Who to confirm |
|---|---|---|---|
| Governing plan document. | Sets the formal terms. | Eligibility, limits, expenses, dates, claims, and termination match the design. | Employer with adviser or counsel. |
| SPD or participant summary. | Explains the benefit. | Plain language matches the governing document and says how to get help. | Document provider, as assigned. |
| Notices and enrollment pieces. | State choices and deadlines. | Right audience, right timing, and current terms. | Employer and administrator. |
| Claims instructions. | Guide requests and decisions. | Proof required, incomplete files, decision notices, and review. | Claims administrator. |
| Admin and related-plan records. | Keep daily work consistent. | Roles, privacy, payments, and fit with other benefits. | Employer and service providers. |
A short map of duties helps the handoff stay visible. The employer may approve eligibility and the reimbursement amount, a document firm may draft the plan, and an administrator may take in claims. List those jobs instead of assuming one vendor owns the whole process. Name a backup for time-sensitive work, such as an enrollment fix during a vendor change.
What review steps make an HRA plan document practical?
A side-by-side read finds most conflicts faster than a legal memo. If the plan says eligibility starts on one date and a handout says another, fix that before enrollment. If a claim guide says a receipt is always enough, but the plan asks for more proof, change the guide and tell the people who answer questions.
- Describe the benefit. Write who is eligible, the start date, what you will reimburse, and how this sits with other coverage. Mark open choices instead of letting a template decide them.
- Confirm the HRA type. Ask an adviser which design you are using and which notices go with it. WHIA's HRA setup guide can organize the questions. It does not replace a review of your design. QSEHRA setup lives in a separate QSEHRA guide.
- Assign each document. Decide whether the employer, adviser, administrator, or counsel drafts it. Name who has final approval and who updates it later.
- Compare the versions. Set the governing terms next to the summary, the enrollment sheet, the claim steps, and any related medical plan. Look for clashes in names, dates, limits, expenses, and contacts.
- Walk through a sample claim. Follow a fake request from filing to proof, decision, payment or denial, and review. Use no real employee data. This shows a missing handoff before anyone relies on the process.
- Check delivery. Confirm who must get each paper, how it is sent, and how someone can get a copy later. Keep proof of delivery when you should.
- Set a review date. Check the set at renewal, when the design changes, or when a vendor changes. Keep dated copies so staff know which terms apply.
Try one claim from start to finish
Pick a made-up request. Suppose the supporting record does not show the expense or the date. The instructions should say what else is needed, where to send it, and how the next step is communicated. The operating note should say who tracks an incomplete file and how the final decision is stored.
Then try a second path. The file is complete, but the expense is not eligible. Can the reviewer find the rule? Does the person get a clear reason and any review steps? Does the employer avoid getting medical details it does not need? A stale email address or a payment step with no owner shows up here, not in a skim of the title page.
Keep a version log
Store the current set with an index: owner, effective date, and last review. Archive old copies instead of writing over them. Label them so nobody uses the wrong one. When a clause changes, note who approved it, which papers must change with it, and whether the administrator has the same instructions.
A short change log is enough. Record the reason, the approver, the papers that changed, and the date new materials went out. That log matters at renewal and when a vendor changes midyear. A new HR contact can see the live terms without hunting through old email.
What should Washington employers ask before launch?
Bring these questions to the adviser, the document provider, the administrator, and counsel. Mark each one decided, assigned, or not applicable before the meeting ends.
- Which HRA design is this, and which documents and notices go with it?
- Who is the plan administrator, and which duties stay with the employer?
- Do the terms match our eligibility, dates, funding, and reimbursement rules?
- How will we confirm eligibility, and any required coverage, for this design?
- What proof is needed for each kind of request, and who reviews it?
- How are incomplete files, denials, and review requests explained?
- Which notices go out, to whom, by what date, and by what method?
- How is health information handled, and what will the employer see?
- What happens when status changes, the plan is amended, or it ends?
- Who checks that forms are current after a renewal or a vendor change?
For each follow-up, name an owner and a date. Bring the answer back into the documents, not only the meeting notes. If a design choice changes, check notices, enrollment steps, and the administrator's setup again. Employers comparing a broader benefits review can start with WHIA's page for Washington employer industries. The ERISA compliance checklist covers the wider duty list. Do not treat this article as that checklist.
For individual coverage designs, HealthCare.gov's CHOICE arrangement page explains the notice and individual-coverage ideas at a high level. Confirm the current rule with an adviser before you rely on a template from a prior year. CMS also keeps an HRA overview that points employers to those notice tools.
How do you keep the document set current?
A document set works only while it matches daily administration. Keep one controlled copy and a date for each version. Tell the administrator when an amendment takes effect. Send updated participant materials when you must. Do not let an old slide deck become the source of truth.
Put a short review on the benefits calendar. First, read the written terms: dates, limits, eligibility, and amendment language. Second, check operations: administrator contacts, claim steps, how employees get copies, and the path for an appeal. A clause can stay the same while the phone number around it goes stale.
Also sample a few real questions from the last year, with private details removed. If people keep asking when coverage starts, the summary and the plan may not say the same thing. Fix the paper, then fix the script the team uses on the phone.
Changes with tax or legal effects need a qualified reviewer before you adopt them. WHIA's HRA rules guide is background for that conversation. The document review itself should stay tied to the design you chose.
Talk with WHIA before you launch
Frequently Asked Questions
Is an HRA plan document the same as an SPD?
No. The governing document sets the terms, while an SPD or participant summary explains those terms to employees. Confirm which papers you need, and make the employee version match the governing one.
Can an employer use an administrator's template?
Yes, as a starting point. Check that it reflects your design, your actual decisions, and the duties that apply to your company. Name who reviews it, who approves it, who updates it later, and who sends it to employees.
What if two HRA documents disagree?
Stop before you administer the conflicting term. Find the approved rule, ask the adviser or counsel, correct the papers and the daily process, and tell participants when they need a clarification.
How often should HRA documents be reviewed?
Review them before launch and again when the design, the eligibility rules, the administrator, or the daily process changes. A check at renewal also catches old phone numbers and stale handouts.
Does this guide replace legal advice?
No. It helps a Washington employer prepare questions and compare drafts, but a benefits adviser or counsel should confirm which documents and notices apply to the specific arrangement.
Ready to review your HRA papers?
A careful pass through the HRA plan document gives you a clearer way to explain the benefit, assign the work, and run the plan as written. Bring the open questions to a conversation before enrollment starts.