Walkthrough: negotiation
Walkthrough: the other party’s paper, against your rules
2
Versions sent back at most, each change tracked
4
Possible answers for each change

About
Follows an NDA that arrives on the other party’s own paper, through review and up to two versions sent back. Written from how Colibit works; it is not a customer story.
Contract type
NDA, other party’s paper
Who takes part
Requester, lawyer, the other party
Stages
Review, changes, agreement
Share

Colibit does not judge a change by feel. Each one is matched to a row of your playbook.
Rule
,
Your playbook
The paper arrives
The other party sends its own NDA
The requester uploads the NDA the other party sent. Nobody retypes it. Colibit splits the document into clauses and numbers them, whether it is written in Spanish, English or Portuguese.
Then it matches each clause to one place: a row of the company’s playbook, a list of clauses that never need attention, or a list of clauses that always go to a lawyer. The AI reads the text and quotes the exact words it relied on. It does not decide what happens next.
The same checks run as for any request: who the other party is, restricted countries and sanctions lists. They are described in the walkthrough of the checks.
The rules
Each change meets a row of your rules
The playbook is a table. Each row covers one topic, such as how long the duty of confidentiality lasts, and says what to do in four cases:
Approve. The clause is acceptable as written.
Negotiate. Propose the change the playbook specifies.
Accept a counter-proposal. When the other party answers, accept a fallback the playbook allows.
Escalate. Send it to a lawyer.
Colibit compares what the other party wrote with each row. The result for the whole document is one of three: approve as received, negotiate, or hand to a lawyer. If anything is unclear, the answer is the lawyer. Doubt is never counted as a yes.
The playbook also limits how many substantive changes Colibit will make for each row, so a reply never rewrites the whole document.

Edits go back as tracked changes with your standard comments, so the other side sees what changed and why.
Method
,
Tracked changes
The reply
Edits go back as tracked changes
When the outcome is to negotiate, Colibit turns the playbook’s plan into edits. A fixed program writes them, not a model, and it changes only the words the plan names. Every edit is a tracked change in the company’s name, and each comes with a standard comment from the company’s own library that explains it in the company’s words.
Before the reply is released, one last check runs: rejecting every change must give back the other party’s original text, word for word. If it does not, the reply is not sent.
The agreed version
When both sides agree, it goes to signature
The other party answers, usually with changes of its own. Colibit reads that answer change by change, with the same rules, and sorts each comment: a concrete change, a courtesy, an operational note or a legal point. A legal point always goes to a lawyer.
Colibit sends at most two versions back. Whatever is still open after that is a decision for a lawyer. When the text is agreed, the request continues as in an NDA from request to signature: approvals, signature, record.
When a lawyer settles something the rules did not cover, they can turn their decision into a new row. The first cases that use a new row are confirmed by a lawyer before it runs on its own.

Before anything leaves, a check proves that rejecting every change restores the other party’s text, word for word.
Check
,
Nothing lost

