Open the contract
Upload the contract or create it in the client project where the surrounding documents already live.
Contract review workflow
Review a contract with the file and context together
Contract edits are easier to trust when the document, comments and version history live together. Review internally first, then bring the client into the same file.
Create a contract workspaceWhat this workflow is for
Contract review is for resolving terms before anyone signs.
Use contract review when the substance of an agreement still needs to be checked: scope, dates, obligations, fees, liability language or any clause the parties need to discuss. The objective is not simply to circulate a PDF. It is to make sure the current document and the reasoning around it can be understood before the final signing request is sent.
A contract may pass through internal review and client review, but it should remain the same document record. That gives the person preparing the final version a clearer job: resolve the comments, save the agreed language and know exactly which file is ready for signature.
The workflow
One document, every next step.
- 01
Your team - 02
Your team Mark up the document
Add text, annotations or comments directly on the PDF during internal review.
- 03
Client Invite the client to review
Use a client review link to make the current version available for feedback.
- 04
Both Keep the final revision
Save the agreed version and move it to a signature request when the review is complete.
Choose the right next step
Use review before the contract becomes a commitment.
Terms still need discussion
Use this workflow when the document needs review and changes, whether that means a single clarified clause or a more substantial revision to the agreement.
Several people need the same context
Internal colleagues and the client can work from the current document rather than comparing independent attachments and annotations.
Signature should only follow a settled version
Do not begin the signing process until the parties have agreed the language. Review keeps the negotiation separate from the final signing record.
Why keep it together
The file is the shared context.
- PDF annotations and comments do not need to be restated in email.
- Earlier drafts remain available after a revision.
- The document can continue directly into its signing step.
Keep the process clear
Keep negotiation and execution as two clear stages.
Review the version that is actually under discussion
When a term changes, save a new version before asking people to respond. That prevents a comment from being accidentally applied to the wrong draft.
Make unresolved points visible
Use comments and annotations to keep questions attached to the clause or page they concern. This reduces the risk of a separate email thread becoming the only explanation of a change.
Create one final signing version
Once the review is complete, prepare the agreed document and use that exact version for the signature request. The earlier review history remains available without being confused with the final agreement.
Questions, answered
Contract review questions
Is contract review the same as signing a contract?
No. Contract review is the stage for discussing and revising terms. Signing is the formal request sent once the final version is ready.
Can we annotate a contract PDF during review?
Yes. The PDF editor supports document annotations and comments so the discussion can stay close to the relevant part of the file.
What if a clause changes after the client has reviewed it?
Save the revised contract as a new version, then make sure the next reviewer is looking at that current version before the document progresses.
Will the review history be lost when the contract is signed?
No. The document record keeps the contract, its prior versions and the context that preceded the signature request together in the project.
Start the workflow
Give the next document a place to go.
Free to start with one project and no card needed.
Create a contract workspace