Plexus AI Knowledge, and why it matters
Knowledge is how you teach Plexus your organisation's positions. Several Plexus AI features draw on it to improve their recommendations, by better understanding your risk profile and the way your team likes to work.
The more Knowledge you add, the more the output starts to sound like your team, not a generic one.
You can build Knowledge from a few different sources:
General rules and policies — the positions and guardrails your legal team already applies
Precedents — your standard templates and previously agreed contracts
A customised file co-created with Plexus Counsel — built from scratch in a few minutes (steps below)
You don't need all three to start. One good file is enough to see the difference.
Start here: which do I have?
I already have documentation → Find the right file (see Where to find your Knowledge below).
I'm starting from scratch → No existing docs? Build a short but genuinely useful file with Plexus Counsel in a few minutes (see Create a file with Plexus Counsel), then upload it.
Where to find your Knowledge
If you have existing documentation, you probably don't need to create anything new – you just need to know where to look. Here's what each type looks like and the common places it tends to live.
Knowledge type | What it looks like | Where to look |
General rules and policies | Contract playbooks, delegation of authority (DOA) matrices, approval and escalation policies, risk appetite statements, preferred and fallback clause positions | Your team's shared drive or intranet, existing GC guidelines, onboarding or induction material, the "how we review" notes a senior lawyer keeps |
Precedents | Your standard templates, preferred clause libraries, previously negotiated agreements you're happy to reuse | Your document management system, contract repository, closed matter files, or a senior lawyer's saved templates |
Automation templates from Plexus | Ready-made starting points we provide | Available in Plexus, or ask your Plexus contact |
Quick tip!
Start with the document that best reflects how you really review.
Create a file with Plexus Counsel
No existing Knowledge documentation? You can create one from scratch with Plexus Counsel.
1. Open Plexus Counsel – see ("Using Plexus Counsel")
2. Copy and paste the prompt below.
I'd like to prepare a very brief policy document with guidelines for my legal team to review an [NDA]. Ask me a series of questions that would help you understand how I approach reviewing an [NDA] for compliance and safety for our company. I'll answer your questions, then reply to me with what you think that policy document would look like in a message. I can copy and paste it into a document myself.
3. Answer the questions from Plexus Counsel until it gives you the proposed content for your file.
4. Copy and paste the content into Microsoft Word.
5. Save as .docx or .pdf.
What's next?
Once you've written and saved the content in a Word file, upload it following the steps at Managing Knowledge Using Plexus AI. Run a quick test on:
Contract Review (for the selected document type)
Need support? Reach out to [email protected] for assistance.