What Minnesota law actually gives you after an injury
Almost everything you find in the first week is advertising. This is not. Every legal statement here is checked against the statute or the opinion that says it, quoted, linked, and dated — and the page tells you when it was last checked.
Minnesota Injury Guide is organised around where you are in the problem rather than around what a lawyer would call your case. Someone three days after a collision and someone eleven months into a denied claim need different pages, and they should not have to read each other's.
Where are you?
- It just happened
The first days. What to do, what not to say, and which clocks have already started. — 2 guides.
- Who pays the bills
No-fault, health plans, liens, and the layers of coverage most people do not know they have. — 2 guides.
- Making the claim
Fault, thresholds, damages, and what the adjuster on the other end is actually doing. — 2 guides.
- When it goes wrong
Denials, lowball offers, disputed fault, and the deadlines that end a claim quietly. — 1 guide.
- Background
The statutes and doctrines the rest of the site refers back to. — in preparation.
What makes this different
- Nothing is written from memory
Not a statute number, not a deadline, not a dollar threshold. Every source is retrieved and read before the sentence is written, and a separate pass confirms each authority actually stands for what it is cited for. Both dates are printed on the page.
- No results, no predictions, no estimates
This site publishes no verdicts, no settlement figures, and no guess at what a claim is worth. Those numbers belong to someone else's injuries, coverage, and venue.
- A contact form that asks for almost nothing
There is no "tell us what happened" box, on purpose. A rule about prospective clients makes collecting your story at this stage bad for you and bad for us, and the page explains exactly why.
- No tracking of any kind
No analytics, no cookies, nothing loaded from anyone else's server — enforced by the site's security policy and by a check that fails the build, not by a promise.
Guides publish as each one clears source verification, which is slower than writing them and is the only thing that makes them worth reading. The index lists everything published so far.