Review and Approve

Review company evidence and the buyer-facing revision together. Linked claims provide version and evidence context; manual and bespoke content still need an explicit review for the buyer's situation.

Review linked changes

Open the relevant Project to inspect affected linked work. Where a comparison is available, review Before Claim, Review target Claim, and Local Artifact, including any intentional local wording. Check the displayed Claim versions. Evidence for Claim belongs to the review target version; a separate notice identifies a newer Claim Pack version when one exists. Use Open Claim to inspect it. The review choices are:

• Update — apply the reviewed change when the action is available, then inspect the saved artifact.
• Keep exception — retain intentional local wording and record a reason.
• Defer — set a later review date and explain why the decision is deferred.

Use Assign to give an available teammate ownership of the review. If the comparison cannot be applied safely or a linked location is missing, inspect the artifact directly before deciding what to change.

Review the final artifact

Inspect the wording, evidence, figures, and buyer-specific commitments in the actual revision. A linked claim is not a certificate for every statement around it, and bespoke content is not automatically sourced or prevented from leaving the workspace.

Saving an edit or accepting a linked change is an internal decision. Publication is separate: Pinned links retain their published revision, while Current links follow the published channel. Check what you intend to publish and the resulting buyer revision in Share and Export.

Who reviews

Agree who owns the factual, technical, and commercial review for the deal, and complete your team's sign-off before publication. Available actions depend on workspace access and the current review state. See Members and Billing for workspace access.