Before you begin
- Access to the matter, review request and document.
- The role and license required for the proposed action.
What to do
- Open the pending review from the matter or Your Day. Confirm the document, matter and requested action. Follow the review request to the saved version it names. If a colleague is still editing, establish which version is being submitted before beginning the approval.
- Read the document and inspect its sources. Review unresolved citation holds, changed-fact notices and omissions that could affect the decision. Approval should follow substantive review, rather than relying on a status label or the presence of source links.
- If changes are needed, return the work for revision or save the corrections through the document workflow. Inspect the resulting saved version. Where a review request exists, an approval attached to an earlier version does not carry forward to those edits.
- Approve only the version and action shown in the confirmation. Check recipients, attachments and other material details when they are part of the act. An approval token covers the exact action, matter, user and arguments presented; it is not standing permission for later actions.
- Read the result after confirming. A document can be approved while a send or filing remains pending. If the action reports an unknown or failed outcome, check the recorded status before retrying so an uncertain delivery does not become an unintended second send.
What you should see
The review record identifies the saved version and decision. Any outside action has its own result, and later edits return for the review they require.
Limits and unresolved problems
Version-specific approval applies where the document has a review request. Approval, sending, filing and service are different states; the approval record alone does not establish the others.
Product scope and requirements
Related guides
Still need a hand?
Record the screen, time, displayed status and steps you tried. Use your signed-in support route or contact your firm administrator. Do not include credentials or confidential documents in a public message.
Support contacts