PrenupsAI

50-state evidence matrix

Acknowledgment and notarization sources

Catalogued authorities that address acknowledgment, notarization, or recordable-instrument formalities.

6 states have 7 separately catalogued authority records for this topic. 44 states show a visible coverage gap.
50states shown
6with evidence records
7matching authorities
44visible gaps

Manual editorial field guide

Acknowledgment and notarization are often treated as decorative proof of seriousness. They are better understood as specific acts with specific records: who appeared, what identity was established, what document was acknowledged, and whether the certificate belongs to the instrument under review.

768 manually authored words · evidence tables continue below

Read the certificate as evidence

A seal is not the analysis. Read the venue, date, signer name, notarial act, commission information, and attachment language. Confirm that the certificate is physically or electronically connected to the agreement it purports to authenticate. A loose certificate with no document description, a date that predates the final draft, or a signer name that differs from the agreement deserves investigation even when the page looks official.

The same discipline applies to witnesses. Identify whether the witness attested a signature, an acknowledgment, or some other act. Preserve addresses and contact details if they appear. Do not infer what the witness observed beyond the certificate language and available testimony.

Distinguish the prenup from connected property papers

A state may impose one rule on the premarital agreement and another on a deed or recordable instrument used to carry it out. If the agreement promises a transfer of real property, the deed’s acknowledgment and recording history may matter independently. A clean review therefore follows the transaction outward instead of stopping at the four corners of the prenup.

This distinction also prevents overclaiming. The fact that a package has a separately catalogued acknowledgment authority means the topic has an evidence record; it does not mean every prenup in that state must be notarized in every circumstance. The linked authority, instrument type, and current law must be read together.

Investigate anomalies without declaring fraud

Certificate defects can have innocent explanations: scanning omitted an attachment, a notary used a separate compliant form, or parties signed counterparts on different days. They can also point to a genuine execution dispute. Record the anomaly precisely and seek the surrounding records before assigning motive.

A useful report might say that the reviewed PDF contains an acknowledgment dated two days before the final version’s metadata and that the notarial journal has not been obtained. It should not say the agreement was backdated unless evidence establishes that fact. Precise language preserves credibility and makes the next investigation step obvious.

Account for remote and counterpart execution

Modern signing records can involve remote notarization, electronic signatures, separate counterparts, and certificates generated by a platform. Preserve the platform’s audit trail, identity-verification result, consent record, time zone, IP history where lawfully available, and the final hash or completion certificate. Do not assume that an image of a handwritten signature proves wet-ink execution, or that electronic execution is defective simply because the agreement was drafted in an older style.

Counterparts create another assembly risk. One party’s signed pages may have been combined with the other party’s copy after execution, and each certificate may use a different date or venue. The review should determine whether the documents identify themselves as counterparts, whether the operative text was identical, and how the final set was delivered and retained. This is evidence work, not aesthetic judgment about how a closing package should look.

Write a finding that can survive scrutiny

The best output separates observation, source, inference, and open question. Observation: the PDF contains a New York acknowledgment naming one signer and dated June 4. Source: the linked state authority describes the relevant acknowledgment formality. Inference: the certificate appears directed to that signer’s execution. Open question: the reviewed file does not contain the other signer’s certificate or an original. This structure lets a reader challenge any step without losing the underlying record.

Avoid boilerplate conclusions such as ‘properly notarized’ unless the necessary elements were actually checked under current law. Also avoid ‘invalid notary’ when the system has only detected an incomplete scan or formatting anomaly. A narrow, sourced finding is more credible, more useful to counsel, and less likely to mislead a person making a high-stakes decision.

For publication, show the authority date and package version beside the finding. That makes later checking possible and prevents a polished paragraph from disguising stale research.

Questions for the document

What to ask before drawing a conclusion

  • What exact notarial or acknowledgment act does the certificate state occurred?
  • Is the certificate attached to and consistent with the final agreement or a different version?
  • Did the parties sign together, separately, by counterpart, or through a remote process?
  • Are separate deeds or recordable instruments needed to implement any property promise?

Outside evidence

What the agreement cannot prove alone

  • Complete certificate pages and high-resolution copies showing seals, embossing, or electronic marks
  • Notary commission details, journal entry, platform audit log, and identity-verification record
  • Witness names, contact details, declarations, and contemporaneous correspondence
  • Related deeds, recording receipts, rejection notices, and title records
StateCoverageCitations and scoped summariesNext step
Alabama (AL)
al-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open AL checklist →
Alaska (AK)
ak-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open AK checklist →
Arizona (AZ)
az-2026-07-20.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open AZ checklist →
Arkansas (AR)
ar-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open AR checklist →
California (CA)
ca-2026-07-18.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open CA checklist →
Colorado (CO)
co-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open CO checklist →
Connecticut (CT)
ct-2026-07-21.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open CT checklist →
Delaware (DE)
de-2026-07-21.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open DE checklist →
Florida (FL)
fl-2026-07-18.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open FL checklist →
Georgia (GA)
ga-2026-07-22.3
1 source
O.C.G.A. § 19-3-62
One of the at least two attesting witnesses required for a current Georgia antenuptial agreement must be a notary public.
Open GA checklist →
Hawaii (HI)
hi-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open HI checklist →
Idaho (ID)
id-2026-07-22.3
1 source
Idaho Code §§ 32-918–919
When a marriage-settlement contract grants or affects real estate, Idaho requires recording in each county where that real estate is situated; a qualifying signed and acknowledged summary may be recorded, and recording or nonrecording has the same effect as for a real-property conveyance.
Open ID checklist →
Illinois (IL)
il-2026-07-18.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open IL checklist →
Indiana (IN)
in-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open IN checklist →
Iowa (IA)
ia-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open IA checklist →
Kansas (KS)
ks-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open KS checklist →
Kentucky (KY)
ky-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open KY checklist →
Louisiana (LA)
la-2026-07-23.3
2 sources
La. Civ. Code art. 1833
An authentic act requires execution before an authorized notary or officer in the presence of two witnesses and signatures by each executing party, each witness, and each notary, subject to the article's separate-execution rules.
La. Civ. Code art. 1836
A party may duly acknowledge a private signature by recognizing it before a court, notary, or other authorized officer in the presence of two witnesses, or in another legally authorized manner.
Open LA checklist →
Maine (ME)
me-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open ME checklist →
Maryland (MD)
md-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open MD checklist →
Massachusetts (MA)
ma-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open MA checklist →
Michigan (MI)
mi-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open MI checklist →
Minnesota (MN)
mn-2026-07-23.3
1 source
Minn. Stat. § 519.11, subds. 1(d), 1b(b)(3)
Duly acknowledged and attested agreements provide prima facie proof of acknowledged matters, while current execution independently requires two witnesses and acknowledgment.
Open MN checklist →
Mississippi (MS)
ms-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open MS checklist →
Missouri (MO)
mo-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open MO checklist →
Montana (MT)
mt-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open MT checklist →
Nebraska (NE)
ne-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open NE checklist →
Nevada (NV)
nv-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open NV checklist →
New Hampshire (NH)
nh-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open NH checklist →
New Jersey (NJ)
nj-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open NJ checklist →
New Mexico (NM)
nm-2026-07-22.3
1 source
N.M. Stat. § 40-3A-3
New Mexico adds acknowledgment to the writing and signature formalities, so the execution file should preserve the notarial or other legally sufficient acknowledgment evidence.
Open NM checklist →
New York (NY)
ny-2026-07-18.3
1 source
N.Y. Dom. Rel. Law § 236(B)(3)
An agreement made before or during marriage must be written, subscribed, and acknowledged or proven in the manner required for a deed to be recorded.
Open NY checklist →
North Carolina (NC)
nc-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open NC checklist →
North Dakota (ND)
nd-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open ND checklist →
Ohio (OH)
oh-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open OH checklist →
Oklahoma (OK)
ok-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open OK checklist →
Oregon (OR)
or-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open OR checklist →
Pennsylvania (PA)
pa-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open PA checklist →
Rhode Island (RI)
ri-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open RI checklist →
South Carolina (SC)
sc-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open SC checklist →
South Dakota (SD)
sd-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open SD checklist →
Tennessee (TN)
tn-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open TN checklist →
Texas (TX)
tx-2026-07-18.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open TX checklist →
Utah (UT)
ut-2026-07-22.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open UT checklist →
Vermont (VT)
vt-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open VT checklist →
Virginia (VA)
va-2026-07-21.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open VA checklist →
Washington (WA)
wa-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open WA checklist →
West Virginia (WV)
wv-2026-07-23.5
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open WV checklist →
Wisconsin (WI)
wi-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open WI checklist →
Wyoming (WY)
wy-2026-07-23.3
No separate recordThe package does not encode this as a standalone topic. No legal absence is inferred.Open WY checklist →

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.