Workflow-aware document review for regulated teams
Small regulated firms review high-touch documents — client reports, marketing materials, compliance filings — through email chains and disconnected PDFs. LOOM replaces that with an explicit approval workflow: every document moves through defined stages with role-based assignees, parallel sign-offs, and a full audit trail. The wedge: page-anchored markup tied to workflow state, automatic version tracking on every revision, and AI compliance pre-checks that post blocking issues an approver has to clear before signing off.
Define the document, the review sequence, and who is responsible at each stage. Stages can be sequential (one at a time) or parallel (multiple sign-offs required). Activate when ready — the first assignees are notified.
Reviewers upload revised documents, post comments, and raise issues against specific problems. Issues can block approval until resolved. A compliance pre-check runs automatically and creates suggested issues before human review begins.
Each stage assignee approves or requests changes — targeting any prior stage, not just the one before. Once all stages sign off, the workflow closes and the review packet preserves every file, decision, and timestamp.
Walks a Q1 market commentary through a four-stage approval workflow: content review, investment review, AI compliance pre-check, and parallel final approval. The AI pre-check pins blocking issues to the document; you clear them and watch readiness recover, a new document version get uploaded, and the workflow close into an audit-ready review packet.
See the workflow run end-to-end — content review, investment sign-off, an AI compliance pre-check that posts blocking issues you'll need to resolve, and parallel final approval.
The current pre-check is mocked. The real version extracts document text, runs an LLM review against a configurable rule template, and posts suggested issues — which reviewers can accept, dismiss, or convert into change requests.
Issues will become page- and region-anchored. Reviewers will be able to highlight text, draw attention to a figure, and thread replies — all tied to workflow state so markup feeds the approval decision.
Production target: Azure AD SSO, SharePoint document libraries via Graph API, and Teams notifications to replace the current JWT prototype auth, local file storage, and email service.
Completed workflows will produce a coherent audit package: final documents, markups, comments, approver identities, timestamps, and issue resolution records — suitable for regulatory evidence.