MirmiWhat needs to stay synchronised
The clause, comments, status, decision and signed version need to return to the matter or CLM. An integration that only produces text in Word creates another documentary break.
A useful in-document path
The user selects a change, reviews precedents and the score, then chooses an action that is genuinely available. If the matter is outside policy, escalation includes the passage, evidence and question.
- analysis of the selected change;
- reviewable signed precedents;
- applicable position and threshold;
- decision synchronisation.
Security and permissions
The add-in should not decide capabilities locally. Access rights, available corpus and actions should come from the server and the relevant matter.
Word is the workspace, not the source of truth
The open file can be renamed, duplicated or sent outside its matter. The add-in should resolve matter and version identity server-side, then display the source and freshness of the information used. A recommendation should not silently survive a version or permission change.
Define the return path to the CLM or SharePoint before rollout: decision, comment, status, version and any escalation task. Without it, the tool may accelerate one negotiation but does not improve collective knowledge.
Legal add-in evaluation checklist
Test the integration on a real document and with a user who has limited rights. Check behaviour offline, after a version change and when no reliable precedent exists.
- authentication, permissions and scope of transmitted data;
- visible link to the source passage and document;
- version, tracked-change and conflict handling;
- abstention, escalation and decision logging;
- documented synchronisation with the system of record.