Bill Commons

MN HF 3560

dead

Uniform Electronic Estate Planning Documents Act enacted.

Minnesota · 2025-2026 · lower

Follow this bill’s action updates (Atom)

Subscribe in a feed reader. The feed covers recorded actions from the last 30 days; Bill Commons may record an action after it happened at the legislature.

Quick answers

Did MN HF 3560 pass?

No. MN HF 3560 did not pass — it was defeated or died in the legislative process. Latest recorded action (2026-03-25): HF indefinitely postponed

What is MN HF 3560 about?

MN HF 3560 is a bill in the 2025-2026 titled “Uniform Electronic Estate Planning Documents Act enacted.”.

Who sponsors MN HF 3560?

Niska is the primary sponsor of MN HF 3560, joined by 1 cosponsor.

Introduced
2026-02-23
Latest action
2026-03-25 — HF indefinitely postponed
Bill type
bill
Last updated
—

Subjects

Sponsors

  • Niskaprimary
  • Feistcosponsor

Committees

Not provided by source.

Action timeline

Newest first

  1. 2026-03-25

    HF indefinitely postponed

  2. 2026-03-25

    Bills identical, SF substituted on General Register

  3. 2026-03-23

    Referred to Chief Clerk for comparison with SF3602

    referral-committee

  4. 2026-03-16

    Second reading

    reading-2

  5. 2026-03-16

    Committee report, to adopt

    committee-passage

  6. 2026-02-23

    Introduction and first reading, referred to Judiciary Finance and Civil Law

    introduction,referral-committee

Versions

Documents

Votes

Not provided by source.

Related bills

Official source

Attribution

Data from openstates_api_sync, retrieved 2026-10-10T04:33:01.744121Z

Inspect retained evidence for changes recorded after evidence tracking began:

Session-wide evidence can include changes to other bills:

Use this data

Every field on this page is available from the free public API — no key or licence required. Fetch this bill as JSON: GET /api/v1/bills?jurisdiction=MN&identifier=HF 3560. See the API docs or the MCP server for AI assistants.

Known limitations

  • Sponsor party and chamber affiliation are not yet captured by this API.
  • Committee referrals are not yet captured.

See the methodology page for data sources and limitations.