MN · evidence preparation
Use these prompts to collect the agreement, schedules, timeline, and outside records needed for an evidence-based first review.
Package mn-2026-07-23.3 · checked 2026-07-23 · editorially verified.State-specific manual editorial
Minnesota Statutes section 519.11 contains detailed formalities involving disclosure, opportunity for counsel, writing, witnesses, acknowledgment, and execution before the day of marriage.
Minnesota also distinguishes procedural and substantive fairness, making the complete execution file more important than a signature-only checklist.
Questions people actually ask
Each answer is tied to source IDs in the current state package. Open the citations and check for later authority before relying on a proposition.
The current statute includes a writing, two witnesses, acknowledgment, opportunity for legal counsel, financial disclosure, and execution before the day of marriage.
Section 519.11 identifies property-related scope and other statutory limits for antenuptial contracts.
The package identifies both procedural and substantive fairness within the current enforcement framework.
Worked issue-spotting examples
These examples do not predict an outcome. They show the boundary between a fact pattern, a source-backed issue, and the legal judgment still required.
The parties sign on the day of the ceremony. Minnesota's current statute identifies execution before the day of marriage as a specific formality.
Question to carry forward: Does the signing date satisfy the current Minnesota statute, and which version applies?
The agreement has both party signatures and a notary certificate but only one witness. Minnesota's enumerated formalities make the witness record a threshold issue.
Question to carry forward: Was the agreement witnessed and acknowledged in the manner section 519.11 requires?
Confirm the complete agreement and every incorporated schedule use the required form and signatures.
Check whether the agreement or a related instrument uses an acknowledgment, notarization, witness, or recording formality.
Identify the event and date on which the agreement says it becomes effective.
Map each material clause to a subject the cited authorities address and flag terms requiring separate authority.
Reconcile property labels with title, income, appreciation, debt, and disposition terms.
Identify every support waiver, cap, formula, review event, and enforcement-time safeguard.
Flag any term that attempts to predetermine child support, custody, or another child-related decision.
Confirm every claimed amendment or revocation is complete and follows the applicable form.
Build a factual timeline of drafts, negotiations, pressure, capacity, language access, and signing.
Compare the agreement and schedules against assets, debts, income, business interests, trusts, and any waiver.
Record who advised each party, when advice occurred, and which draft was reviewed.
Measure the time between first draft, material revisions, legal review, wedding, and signing.
Identify support terms that could interact with public-benefit eligibility at enforcement.
No separate source record is catalogued for this topic. That is a research-coverage statement, not a claim that no applicable law exists.
Identify whether the agreement addresses a marriage later determined to be void.
No separate source record is catalogued for this topic. That is a research-coverage statement, not a claim that no applicable law exists.
Identify severability, limitations, public-policy, choice-of-law, and other enforcement boundaries.
Matrix and list placement describes the records in PrenupsAI's current evidence packages. It does not rank legal strictness, predict enforceability, or mean that an unlisted state has no applicable rule. Open the cited sources to inspect the underlying authority.
Method, not a verdict
331 words of shared evidence methodology accompany the state-specific editorial and authority records above.
Work from the complete agreement outward. Preserve the best available signed copy, every incorporated schedule, and any amendment or revocation before answering individual questions. For each checklist row, distinguish three things: what the document says, what an outside record can prove, and what the cited authority addresses. Those categories overlap, but they are not interchangeable. A recital may identify the parties’ stated understanding without proving delivery; a bank statement may prove an account existed without deciding its legal classification; a statute may identify a standard without resolving disputed facts.
Mark an item complete only when the underlying record is identified, not merely because the agreement contains reassuring language. If a source is absent, record the gap and route it for research. Do not convert ‘not separately catalogued’ into ‘no law exists.’ That discipline is what makes the checklist useful across both dense statutory packages and states whose rules depend more heavily on cases or adjacent bodies of law.
Record the package version and effective-through date shown above, the date each authority was opened, and whether a later-authority search was performed. Save exact clause quotes with page or section references. When facts change—through relocation, marriage, amendment, property transfer, separation, death, or litigation—create a new review snapshot rather than overwriting the old one. The resulting trail lets another reviewer understand which document, facts, and legal source set supported each observation.
A checklist can identify missing evidence and research questions; it cannot certify validity, predict enforcement, select governing law, or replace a time-sensitive professional judgment. Use narrow language such as ‘the reviewed file does not contain the referenced schedule’ instead of ‘no disclosure occurred.’ That difference is not defensive filler. It is the basic quality control that keeps evidence reporting accurate.
End each review with a dated list of unresolved facts, assigned follow-up work, and the authority that made each question material. A visible open item is safer than an unsupported green check.