Legal
A register of what you actually signed
Finance tracks what a vendor costs. Legal needs to know what you promised them, what they promised you, and which of those promises has a date on it.
What the worker does
An AI worker in Polaris maintains a vendor agreement register by reading signed agreements in Google Drive and amendment mail in Gmail, pulling out the terms that bind you with each clause quoted and located, and dating every deadline into Google Calendar. It flags agreements it cannot find a signed version of. A lawyer decides what any term means and what to do about it.
- Connections
- Google Drive · Gmail · Google Calendar
- Per agreement
- Terms quoted, located, dated
- Biggest first finding
- Agreements with no signed copy
Two registers, one set of contracts
Finance keeps a vendor list because it cares about money and renewal dates. Legal needs a different cut of exactly the same documents: what liability was accepted, what data terms apply, what happens on termination, whether there is an auto-renewal, and which of those has been amended by a side letter nobody filed.
When these are two lists in two tools they disagree within a quarter, and the disagreement is discovered during diligence, at the worst possible moment.
Running both cuts off one register in one workspace is the cheap fix. The worker reads the same files and produces the fields each side needs.
The legal fields on each register entry
Each is quoted from the document with a file name and a location, never paraphrased.
| Field | Why it is on the register | How the worker records it |
|---|---|---|
| Term and renewal mechanism | Auto-renewal is the term that costs the most and is read the least | Clause quoted, renewal date computed and dated in the calendar |
| Notice requirement | The real deadline sits before the renewal date | Quoted verbatim with the required form of notice |
| Liability position | The number a lawyer will want to compare across agreements | Quoted, with the file and page |
| Data terms | Where a data processing addendum exists, and where it does not | Present or absent, stated plainly |
| Termination rights | What you can actually do if the relationship goes wrong | Quoted |
| Amendments and side letters | The document that quietly changes everything above | Listed with dates, or flagged as none found |
Retrieval and judgment
The worker
- Finds the executed version, or reports that it cannot
- Quotes each register field with its location
- Computes renewal and notice dates and puts them in the calendar
- Cross-checks the mail for amendments
- Reports agreements that differ from your standard position
The lawyer
- Decides what a term means
- Decides whether a position is acceptable
- Advises on exposure
- Negotiates the change
- Approves and signs
The findings a first run usually produces
In a company that has never done this, the first delivery is rarely about clause wording.
Agreements with no signed copy anywhere
The most common finding, and the one that matters most in diligence.
The version in the folder is not the version that was signed
Found by comparing the file to what the mail thread actually attached.
A side letter that changes a term on the main agreement
Filed separately, never cross-referenced, invisible until someone reads both.
Notice windows already inside 30 days
These go straight into the Focus lane with an owner.
Questions people ask
+How is this different from the finance vendor page?
Same contracts, different fields. Finance tracks spend, renewal dates and whether the charge matches the agreement. Legal tracks the terms that bind you and the notice mechanics. Run them as one register in one workstream so the two views cannot drift apart.
+Can the worker compare a supplier's terms to our standard position?
It can put them side by side and name where the wording differs, quoting both. Whether a difference is acceptable is a judgment, and the register exists to get that question in front of someone qualified with the evidence already assembled.
+What if agreements are scattered across mailboxes and drives?
Point it at all of them in the brief. It reads what its connections expose, and it reports gaps rather than filling them in. The gap list from the first run is usually the most valuable output.
+Does anything get signed in Polaris?
No. There is no e-signature in the product and no signing capability for a worker. Execution happens wherever you do it today, and the executed file gets filed and registered.
Related
Legal operations work an AI worker can carry
Tracking, chasing, assembling and watching. Everything a legal team spends time on that is not actually practicing law.
Knowing where every contract is, without asking three people
The question that eats a legal team's week is "where is that one now?". A worker keeps the answer current and ages every stalled agreement.
Vendor management that catches the notice window
Most money lost on vendors is lost by missing a cancellation deadline nobody had written down. A worker keeps the register and dates the deadlines.
Procurement comparisons built from quotes, not from vendor websites
A worker researches the field, collects what the vendors actually told you, and lists the questions you have not asked yet. You choose.
Hire an AI paralegal
It organises the paperwork and surfaces the dates and clauses, and it stops well before the point where anything becomes advice.
Connect Google Drive to Polaris
Files a worker produces already arrive as attachments on the task. Files your team already keeps in Drive are the part still waiting.
Connect Google Calendar to Polaris
Scheduling is the one thing an assistant is asked for first, and it is the one connection still waiting on Google sign-in.
Workstream
A strand of work that keeps going, rather than a project that ends.