ConsentWave.

Contracts people actually understand.

ConsentWave turns a contract into a short comprehension check that your team approves. Signers answer it before they sign, signing stays locked until they pass, and every step lands in one evidence bundle.

No sign-up. The demo uses a fictional client and a simulated signature.

Ready-to-sign check

Preview
  • Parties named

    §1.1 names the venue and the client.

  • Dates set

    The event date and the balance due date are both filled in.

  • Amount missing

    §3.1 points to a written quote that isn't attached.

  • No conflicting terms

    The cancellation windows in §4.2 and §4.3 agree.

Not signable until §3.1 is fixed

Made for the moment before signing.

A signature shows someone signed. A comprehension check shows what they understood. ConsentWave checks the key terms with the signer, and signing stays locked until they pass.

Comprehension check
Scenarios in plain language, each linked to the clause it checks. The agreement stays one tap away.
Human approval
AI can draft questions. Only an authorized reviewer can approve them.
Evidence bundle
Agreement version, approved questions, every attempt, the attestation and the signature, in order.

How ConsentWave works

Six steps. The last three stay locked until the one before is done, and the server checks it every time.

  1. 1

    Supply the contract

    You upload the contract. ConsentWave freezes it as a numbered version.

  2. 2

    Draft the questions

    Five plain-language questions are drafted from that version. Each one cites the clause it checks.

  3. 3

    A person approves

    The reviewer checks every question, answer and explanation, then approves that exact revision.

  4. 4

    Locked until a person approves the set

    The signer answers

    They read the agreement and answer the approved questions. They can pause, ask, or decline at any point.

  5. 5

    Locked until every answer is correct

    Attestation

    They read a short statement and tick the box themselves. Nothing is prechecked.

  6. 6

    Locked until the attestation is accepted

    Signature

    Signing is a separate, deliberate step. The evidence bundle closes around it.

Software drafts. A person decides.

Generated questions can be wrong, so generation is only a drafting aid. It can't approve, publish, attest or sign. Four rules hold no matter what:

  1. 1

    No unapproved questions reach a signer.

    That includes replacement sets after a missed attempt. Each one is reviewed on its own.

  2. 2

    Every question cites the agreement.

    A question that points at a clause that doesn't exist can't be approved until someone fixes it.

  3. 3

    Approval covers exact content.

    Edit one word of a question, answer, pass rule or attestation and it needs approving again.

  4. 4

    A missed attempt never unlocks signing.

    The attempt is kept on record. The pass rule isn't lowered to get someone through.

Who can do what

The reviewer and the signer get separate views. The reviewer never answers, and the signer never sees the answer key.

ActionReviewerSigner
Choose the agreement version
Approve or reject question sets
See the answer key
Answer the questions
Ask for clarification or decline
Accept the attestation and sign
Download the evidence bundle

The evidence bundle

Which words the signer saw, which questions they answered, who approved those questions and when. Failed attempts stay on the record. If the agreement changes later, finished records keep their original version.

Venue Rental Agreement

Demo record
  1. 09:02Agreement version 3 frozen4be1…07
  2. 09:14Question set rev 2 approved by Dana Reyes9f2c…e1
  3. 10:31Attempt 1 submitted, not passed4 of 5
  4. 10:33Replacement set rev 3 approved2d70…9a
  5. 10:48Attempt 2 submitted, passed5 of 5
  6. 10:49Attestation acceptedatt-1
  7. 10:50Signature recorded (simulated)

What a pass means

It records

  • How the signer answered questions about the text in front of them
  • That a named reviewer approved those exact questions
  • The order of answers, attestation and signature

It doesn't establish

  • Legal validity or enforceability
  • The signer's capacity to enter a contract
  • Whether the agreement itself is fair or complete

ConsentWave checks comprehension of the supplied text only. It doesn't give legal advice or claim compliance with any standard.

Roadmap

We're starting with one fictional venue rental agreement. Everything after it follows the same rule: a person approves before anyone is asked.

Now

Next

  • AI-drafted question sets

    Questions drafted from your own contracts. Approval stays mandatory.

  • Ready-to-sign check

    Flags blank amounts, missing parties, missing dates and conflicting clauses. A contract that fails stays unsignable until it's fixed.

  • Team workspaces

    Sign-in for senders, reviewers and signers, with private storage.

Later

  • E-signature integrations

    Hand the final signature to a signing provider.

  • Analytics dashboard

    Comprehension, clarification requests and time spent waiting on approval.

  • Self-check mode

    Upload a contract you received and test your own understanding before you sign it.

“Nobody told me that” should never be the story.

Try the walkthrough as the reviewer, then as the signer. It takes about three minutes.

Try the demo