Negotiate the clause, not the attachment
Redline ping-pong is a filing problem disguised as a legal one. In Paqt a negotiation is attached to the clause itself: both sides' proposals, the reasoning, the decision and the resulting version all live on the text they concern.
Why redlines take three weeks
Not because the terms are hard. Because the process loses state on every handoff.
- Redline ping-pong: Each round is a new attachment with a new filename convention
- Redline ping-pong: Comments argue about language that has already changed twice
- Redline ping-pong: Someone merges two sets of tracked changes by hand, at night
- Redline ping-pong: The reasoning behind a concession lives in an email nobody can find
- Redline ping-pong: Nobody is certain which version was actually agreed
- Redline ping-pong: Signing starts a fresh round of "is this the final final?"
- Clause-level negotiation: One living document; every version addressable and diffable
- Clause-level negotiation: Proposals attach to the clause they change, in place
- Clause-level negotiation: Accepting a proposal writes the version — no manual merge
- Clause-level negotiation: The reasoning for each move is recorded with the move
- Clause-level negotiation: The agreed version is a fact, not a recollection
- Clause-level negotiation: Signature runs against that exact version, in the same room
Four steps from disagreement to a signed version
- Highlight the clause — Select the text that is wrong and open a negotiation on it. The clause becomes the subject of its own thread, visible to every party in the room.
- Propose language — Each side proposes actual replacement text, not a description of a change. Proposals sit side by side so the difference is the thing you are discussing.
- Resolve — Accept, counter or withdraw. Accepting applies the language and writes a new document version automatically, with the negotiation attached to it.
- Sign the result — When the open negotiations close, the document moves into signing in the same room — against the version the negotiations produced.
State that survives the handoff
- Versions you can trust — Every accepted proposal writes a version. Diff any two, and see which negotiation produced the change.
- Context stays attached — The discussion that produced a clause lives on that clause — not in a thread someone has to go find in six months.
- Multi-party by default — More than two parties can negotiate the same instrument with per-party visibility, so brokered deals stop needing a middleman to relay.
- A complete turn log — Who proposed what, when, and what was accepted — timestamped into the tamper-evident agreement history.
- Structured documents — Clauses are real structure, not formatting. That is what makes a negotiation addressable and a diff meaningful.
- Approval where it matters — Gate specific clauses so a proposal on them routes to a named approver before it can be accepted.
Or let an agent run the round
Because negotiations are structured, an agent can participate in them properly — proposing, trading and holding a line within a mandate you set, with every turn in the same log a human would have written.
- The agent proposes real language — It submits replacement text into the same negotiation structure, so its moves are reviewable exactly like a person's.
- Trades inside a mandate — Concessions follow a ladder you authored. The agent gives ground only where you said it may, and records what it got in return.
- Escalates, never improvises — A move outside the mandate stops the run and opens a review item instead of guessing at your tolerance.
- Hands back a signed deal — When terms converge the agent moves the agreement into signing, and you approve the outcome rather than every step.
How it behaves in the awkward cases
- What if we need to negotiate several clauses at once? Each clause gets its own negotiation and they run in parallel. The document shows which clauses are open, and signing is held until the open ones resolve.
- Can the counterparty use Paqt without an account? They join the room by invitation. Paqt is built around invited counterparties rather than assuming both sides have already bought the same software.
- What happens to a clause we negotiate but then abandon? Withdrawn proposals stay in the turn log. The history records what was asked for and not agreed, which is often the part you need later.
- Do we still get a document we can file? Yes. The executed agreement exports with its version history, negotiation log and signature audit as a single court-ready package.