Skip to content

Look up a member's benefits and dependent history

As an H&W Staff member, I want to see a member's dependents, beneficiaries, H&W Benefits History, and H&W contribution/invoice ledger in one place, so that I can answer a benefits eligibility or enrollment question without guessing at which record is current.

Screen: Members > (open a member record) > Dependents, Beneficiaries, BenefitsHistory, H&W History tabs.

H&W Staff is the only non-Super-User role with all four of these tabs — they're fund-gated to the H&W fund axis, not tied to a specific security role, so don't expect Business Agent, Management, or Membership Staff to see what you're looking at.

Fund-gated tabs: Dependents, Beneficiaries, BenefitsHistory, H&W History, HRA History

What each tab is for

Dependents — Relationship, First/Last/Middle Name, Phone, SSN, Emergency Contact, DOB, Effective Date, Termination Date. Add Dependents is available to you (Add/Update).

Beneficiaries — Beneficiary (type), Fund, Relationship, First/Last/Middle Name, SSN, Address, City, State, Zip. Add Beneficiary is available to you.

BenefitsHistory — Benefit (H&W), JobSite, Start Date, End Date, Status (e.g. "Enrolled"), Status Date, Reason (e.g. "Full Time"), Comment, By. Add/Edit Benefit is available to you.

BenefitsHistory is the source of truth for enrollment — not Member+

The Benefits History tab replaced Member Plus's old checkbox-style enrollment flags (CO 3219). New or transferred staff may still expect enrollment flags and Medical ID to live on Member+ — check BenefitsHistory first whenever enrollment data looks missing or wrong, rather than assuming the Member+ tab is still authoritative. (IUOE-2411)

H&W History — Coverage (period), Date Posted, Contribution, Employer/Jobsite, Transaction Type (HW), Contribution Paid by, Invoice Number, Invoice Amount, Invoice Balance, Invoice Date, Paid (by). Print H&W History is the only action here — this tab is a ledger, not an entry form.

For adding a new HRA transaction specifically (a related but separate ledger), see Add a new HRA record for a member.

Things to watch out for

\"Enrolled\" vs. \"Eligible\" vs. \"Pending\" is a migration mental-model gap, not a data error

Migration defaulted members to a BenefitsHistory Status of "Enrolled" from a single legacy date field — even for members who were really only "Eligible" (coverage available, paperwork not yet signed). No "Eligible" status option existed to assign during migration at all. Don't treat a migrated "Enrolled" row as proof the member actually enrolled; cross-check the Authorization Card checkbox, which is normally sticky (stays checked) and is only unchecked when coverage has lapsed long enough that new paperwork is required. (IUOE-2795)

A duplicate BenefitsHistory record usually means Status wasn't selected

Adding a record to the H&W Benefits History tab without selecting a Status value has produced duplicate records in testing. If you see two near-identical BenefitsHistory rows for the same member/jobsite, check whether Status was left blank on one of them before assuming it's a data-migration artifact. (IUOE-2581 — Phase 1 stub, spin-off of IUOE-2411)

Fields that used to live on Member+ may have moved — or gone missing in migration

The H&W Enrollment Requirements ("Missing-H&W" / "Enrolled-H&W") flags and Medical ID that used to live on Member Plus were affected by the cutover to the Benefits History tab — some of this is a deliberate move (check BenefitsHistory first), but some is a documented, not-yet-resolved migration gap (IUOE-2607, IUOE-2606 — Phase 1 stubs). If a Medical ID or enrollment flag a member should have is genuinely absent from both Member+ and BenefitsHistory, treat it as a known migration casualty worth flagging rather than a new bug.

A wrong employer on an H&W/HRA report can be a duplicate-jobsite-number migration artifact

If an H&W or HRA report shows the wrong employer for an otherwise-correct transaction, check for two Union Solutions jobsites that shared the same number before assuming it's a Prizm display bug — this was the confirmed root cause for the HRA Interest column showing the wrong employer. A jobsite renumber fix only applies to new transactions going forward; old historical rows keep showing the old (wrong-looking) employer permanently. (IUOE-2647)

A missing H&W invoice is often a mixed jobsite/employer invoicing-level gap

If H&W History shows a member missing an invoice you'd expect, the dominant confirmed cause on this project is an employer where some jobsites invoice separately and others roll up to the employer level — the employer-level invoice for the roll-up portion can fail to generate. Confirm the employer's invoicing-level setup before filing a new missing-invoice ticket. (IUOE-2734)

The H&W coverage-code mapping is tribal knowledge, not guesswork

When reconciling a Member Plus-era coverage code against Benefits History / import data, the confirmed mapping is: CS → ABC Jobsite/Cobra Single, C2 → Cobra Member +1, CF → Cobra Family. NONE-vs-blank semantics are still unresolved, so don't assume a blank value and an explicit "NONE" mean the same thing. (IUOE-2262)

COBRA work records need their own handling, not the normal-record assumption

COBRA work records have repeatedly behaved like a normal work record in reports that should exclude or special-case them (dues assessments, payment history). If a report touching assessments or payment history looks off for a member with COBRA coverage, check for COBRA handling explicitly rather than assuming the record behaves like any other. (IUOE-2742)

Beneficiary Fund/Type assumptions from the Union Solutions migration

Beneficiary records migrated from Union Solutions are assumed to all belong to the H&W fund, not Union — Membership doesn't use U$ to manage Union beneficiaries directly, so don't assume a Beneficiary's Fund value on an older record is wrong just because the member looks like a Union-side case. Separately, Beneficiary Type is a hardcoded, non-user-maintainable enum — adding a new type value (e.g. the "Union" type needed for the Union Death Benefit) requires a JayStar dev ticket, not a config change on your end. (IUOE-2513, IUOE-2584)

Dependent Relationship and Dependent Type are different fields for different reports

On the Dependents tab, Relationship and Type aren't the same concept wearing two names — they serve different downstream reporting needs (IRS dependent lists, the newsletter baby list, etc.). A dropdown cleanup or data fix requested for one doesn't automatically carry over to the other; check which field a request is actually about before treating it as already handled. (IUOE-1541)

If a feature here silently won't save or open, check the Security Matrix before assuming a bug

Three separate tickets in this project's history traced an H&W-role feature that "just wouldn't open" or finish, with no error message, back to a Roles & Security Matrix gap rather than a functional defect (hidden Accounting tab access, a disabled Submit button on a Management Company Contact form, an uneditable communication record). (IUOE-2443, IUOE-2444, IUOE-2109)