Our goal at Almanac is to provide more structured, transparent, and integrated ways for teams to collaborate without needing a Zoom meeting or Slack message.
For important, high-risk docs where mistakes can be vey costly, our latest enhancements to the "Approval Request" workflow add more guardrails, clearer options, and enhanced context so that you can keep track of every edit and eliminate opportunities for error.
The Approval workflow now only has one "approver" so that there's a clear, single decision maker in your process. In the flow, the approver can either make changes and "approve" the doc, or "send back" the doc to you for more revisions.
All edits in an Approval Request now happen on a branch—a temporary, linked version of the main doc—so that it's clear what was changed over the base.
While the Approval Request is open, the main doc is locked in read-only mode, and the workflow concludes when the approver agrees to all the edits made and merges their branch into the main doc.
In Approval Request, you can compare the changes on the branch to the main doc, and use the activity feed to see exactly who edited what, where, and when—great for compliance and legal redlining.
Finally, we added in graphics to explain the process at every step, so all stakeholders understand where the approval is, who is "holding the ball," and what happens next.
And lastly, we added a fun confetti animation once a doc has been approved 🎉
