Welcome to the second Month in Review. If the last edition was about removing distance between you and your work, this one is about giving you more control over how Plexus works for your organisation — starting with the biggest Counsel release since Multi-Document Awareness.
Playbooks for Plexus Counsel
In the last edition I flagged that we were working on giving admins more control over how Plexus Counsel responds. That's now live.
Playbooks let administrators define how Counsel applies your organisation's knowledge — your rules, standards, and risk appetite — so every interaction reflects how your legal team actually thinks.
Once a Playbook is active, it applies across every Counsel interaction for every user in your organisation. This is the foundation for something we've heard consistently from legal teams: "Counsel is useful, but I want it to think like us." Now it can.
If you're not sure where to start, try something simple:
A Playbook called "Payment Terms" with the objective "Payment terms should not exceed 30 days. Flag any contract where payment terms exceed this and recommend our standard 14-day position." That's enough for Counsel to start applying it across every conversation.
Counsel keeps compounding
Playbooks was the headline, but Counsel received a steady run of improvements throughout March that are worth calling out together.
Document awareness got another uplift. You'll spend less time crafting the perfect question — Counsel is better at understanding what you're asking and pulling the right context from the document without being led there.
Bulk uploaded documents are now fully supported. Counsel can reference and answer questions across your bulk uploaded files, which means a much larger share of your repository is available for analysis. This applies to both existing and future bulk uploads.
The pattern here is the same as last quarter: make Counsel more capable and easier to leverage.
Contracts: less friction in the details
A few contract management improvements this month that individually sound small, but collectively remove a surprising amount of daily friction.
Drumroll please... a simple one that you've all been waiting for -
Plexus remembers your DocuSign signature. Once you've signed for the first time, your adopted signature carries forward automatically. No re-entering it on every signing request. If you need to update it, you can reset from your user profile.
Set the real execution date on uploaded agreements. Previously, uploading an executed contract defaulted the execution date to the upload date. Now you can set it to reflect when the contract was actually signed — so your key facts tell the true story.
Print Key Facts as a PDF. You can now print or save Key Facts directly from the document page. Clean, formatted, ready to share with stakeholders who don't have Plexus access. No more screenshots.
Export Key Facts Changes as a CSV. A new option on the document list lets you select a date range and download a report of every key fact modification made to executed documents.
Notifications that respect your attention
Notifications are one of those areas where getting it slightly wrong creates outsized friction. We made several targeted changes this month to reduce noise and close gaps.
Reviewers stay informed after their stage completes. Assigned reviewers are now notified when a new version is uploaded or when someone comments — even after the document has moved past the review stage. You stay in the loop on changes that matter without manually checking back.
Minor version uploads now trigger reviewer notifications too. Previously, only major version uploads notified reviewers. Now, tracked-change redlines trigger notifications as well — closing a gap where important updates could be missed.
The goal across all of these: the right person gets the right notification at the right time, and nobody else does.
What's next
The thread connecting Playbooks, Knowledge attribution, and the notification work is the same: giving you more control and more clarity without adding complexity. That's the direction we're heading.
We're making progress on streamlining the document intake experience, reducing the manual effort involved in getting contracts into Plexus and moving through workflows faster. And on the AI side, we're exploring what it looks like for Plexus to automatically redline contracts — moving from flagging issues to proposing the fix, inline, so your team spends less time marking up and more time deciding.
More soon.
If you have feedback on any of these changes, or something you'd love to see next, reach out to your Customer Success Manager or drop us a note at [email protected].
— Cadell Falconer, Head of Product