Home · Solutions · Legal & compliance
Solution · Legal & complianceThe last version in Word is not a template, and legal is not a proofreading service
Standard contracts generated, approved and e‑signed in a day
Standard contracts are assembled from approved clauses with data read from your systems, reach legal only when they deviate, and are signed electronically and filed with their metadata.
Executive summary
A two-page NDA takes ten days because it is copied, proofread, printed, scanned and filed by hand.
We start where the value is: separating the documents that are genuinely negotiated from the ones that are assembled.
A standard document is requested, approved and signed the day it is asked for, instead of moving between mailboxes and printers for a week and a half.
SharePoint contracts library; SharePoint eSignature; the contract register
Business problem
Contract operations
Every company has a layer of paper that is not really negotiated: non-disclosure agreements, framework agreements on the company's own terms, rate-change annexes, fixed-term extensions, assignment confirmations, statements of work against an agreed master. The wording was settled once. What changes each time is a name, a date, a rate and which approved clause option applies.
The work is done by copying. Someone finds a similar document, saves a copy and edits it, so every new contract inherits whatever was in the old one: a liability cap negotiated for a different client, a jurisdiction clause that was once a concession. Legal cannot see what was edited, so legal reads everything.
Then it has to be signed, and that is where the days go. The document is printed, walked to whoever holds signature authority, scanned, emailed and waited on, and the countersigned copy comes back as a scan in somebody's mailbox. At scale this stops being an inconvenience: an administrator cannot start a candidate whose annex is unsigned, a consultant cannot invoice against an unsigned framework agreement, and nobody can say what is in force with a client without opening files and comparing them.
How it works today
This is what the flow looks like in most organisations before it is redesigned.
- PersonA consultant or HR administrator opens the last similar contract from a shared drive and overwrites the names, dates and rates
- PersonThe draft is emailed to legal and read end to end, because there is no way to see what was changed
- WaitingThe request waits in the legal mailbox behind whatever arrived earlier, typically two to four working days
- PersonThe approved draft is printed, signed when someone with authority is free, scanned and emailed to the counterparty
- Risk of errorThe template used is whichever version the requester had, so obsolete clauses travel into new contracts unnoticed
- PersonA register row is added when somebody remembers, and the countersigned scan is saved wherever that person saves things
Why the current process costs more than it appears
The budget shows headcount, not what it is spent on.
- Legal capacity goes on proofreading. Reading the whole document is the only way to find out what the requester changed, so lawyers spend the day on paper that carries no risk.
- Every copied document carries its ancestor's concessions. A payment term extended once, a liability cap agreed under pressure, an indemnity added in a forgotten negotiation: all of it propagates through the next twenty contracts.
- Waiting is invisible in the budget and very visible to the counterparty. A candidate who cannot start, a project that cannot be invoiced: each delay is a commercial cost nobody books.
- What is in force cannot be answered without opening documents. The register is behind, the scan is in a mailbox, and the file on the shared drive is not necessarily the signed one, which is exactly what an auditor or a dispute will ask about.
Cost of inaction
The cost lands on the people who read 700 standard documents a month. The queue on the legal desk reforms every Monday, the next growth step is answered by adding an administrator, and the register keeps being reconciled after the fact. What accumulates quietly is drift: each contract copied from the last one moves the estate further from what legal approved.
The second cost arrives at the worst moment. Due diligence, a client audit or a dispute asks what was signed and on what terms, and the answer takes a fortnight of searching mailboxes because the signed originals were never filed in one place with their metadata.
A plausible organisation with realistic proportions. The figures are there to be recalculated on your data; they are not a client result.
A staffing and business-services group in four countries, roughly 1,900 people on assignment at any time, Microsoft 365 E3, a CRM for clients and a separate HR and payroll system for people and assignments.
700 standard documents a month: framework staffing agreements and their annexes, mutual NDAs, rate-change annexes, fixed-term extensions and assignment confirmations. Nine in ten should be a template with fields, not a new document.
Requests reach legal and HR administration by email and Teams chat. Documents are copied from previous ones, read in full by legal, printed for signature, scanned and returned. A shared Excel file is the register, reconciled at quarter end.
About 40 minutes of handling per document across drafting, legal reading, printing, scanning, chasing and filing, plus a queue on the legal desk that turns a two-page NDA into a ten-day item.
The request is made on a form, counterparty and assignment data is read from the CRM and the HR system by robots, the document is generated from an approved template and the clause library, legal sees only deviations, and approval and signature run through Microsoft Teams and SharePoint eSignature.
In the modelled case the standard majority moves from a ten-day round trip to same-day signature, legal review drops to the deviating minority, and the register is complete because nothing closes without it. The figures here are a model, not a measurement.
Proposed solution
We start where the value is: separating the documents that are genuinely negotiated from the ones that are assembled. With your legal team we fix the contract types in scope, the approved clause set for each, and the rules that define a deviation. That rule set is the product; the rest is plumbing around it.
The templates live in Word on SharePoint, owned by legal, with content controls marking the only fields anyone may fill, and beside them the clause library: approved alternatives for payment terms, liability, notice periods and jurisdiction. A request in Microsoft Forms or a Microsoft Teams card asks only the questions that type needs. A UiPath robot then reads the counterparty record from the CRM and the assignment record from the HR system, so names, addresses, rates and dates are never typed, and a documented Power Automate action populates the template with the clause set the rules selected.
Routing follows the same table. A request inside the approved set goes to the business approver in Teams Approvals with the draft attached; one that trips a rule, a longer payment term, a raised liability cap, a foreign jurisdiction, becomes a legal review task that names the deviating clauses instead of asking a lawyer to find them. Approved documents go for signature through SharePoint eSignature, the signed copy returns to the library, and the robot writes the metadata, retention label and register row. What happens to the contract afterwards, renewal alerts and obligation dates, belongs to the contract register solution already on this site.
Microsoft Forms with the Power Automate Forms trigger; Word content controls populated by the Word Online (Business) action "Populate a Microsoft Word template"; Microsoft Teams Approvals app; SharePoint libraries with content types, metadata and versions; SharePoint eSignature; Microsoft Purview retention labels and audit; UiPath Orchestrator queues and audit
The contract type catalogue and the request form; the template set and clause library; the rule table that decides template, clause set, approver, signature authority and what counts as a deviation; the generation and routing flow; the legal review task with its deviation summary; filing, metadata and the register update; cycle-time and deviation reporting
Robot reads of the CRM and the HR system through UiPath Integration Service where an API exists, or UI automation where it does not; bulk annex runs queued through Orchestrator when a rate change hits many people
How the automated process works
- AutomationA request in Microsoft Forms or a Teams card starts the flow and asks only the fields that contract type requires
- SystemA UiPath robot reads the client record from the CRM and the assignment record from the HR system, returning verified names, registration data, rates and dates
- AutomationThe rule table selects the template and the clause set, and the Word template is populated from the verified data
- AutomationStandard requests reach the business approver as a Teams approval with the draft attached; those that trip a rule go to legal with the deviating clauses named
- PersonLegal accepts the deviation, replaces the clause from the library or rejects it with a reason, in the same task
- AutomationThe approved document goes for signature through SharePoint eSignature; external signers use a link and the signed copy returns to the library
- SystemThe robot writes the metadata and retention label, creates the register row and tells the requester the contract is signed
Human-in-the-loop model
Automation handles
- Collecting the request and reading counterparty, employee and commercial data from the systems of record
- Selecting the template and the clause set from the rule table and generating the document
- Routing, reminders, signature dispatch, filing with metadata and retention, the register update
- The evidence trail: template version, clause set, approver, signatory, timestamps
People decide
- Whether a deviation from the approved clause set is acceptable, and on what terms
- Commercial content inside delegated limits: rate, term, notice period, volume commitment
- Who signs by contract type and value band, and when a counterparty's own paper is accepted instead
Before and after
Systems and integrations
The stack is deliberately short: one engine, one execution layer, one place where a person decides.
Inputs
- Microsoft Forms request
- Microsoft Teams request card
- client record in the CRM
- person and assignment record in the HR system
- template set and clause library on SharePoint
Automation layer
- Power Automate
- UiPath Robots
- UiPath Orchestrator
- UiPath Integration Service
Target systems
- SharePoint contracts library
- SharePoint eSignature
- the contract register
- Microsoft Purview retention labels
Human touchpoints: Microsoft Teams Approvals; the legal review task in Teams; the signing link for internal and external signatories
Technologies used
holds the approved templates and clause blocks; content controls mark the only fields the flow fills
Apopulates the template with the "Populate a Microsoft Word template" action; premium connector
Athe request form, with the questions that belong to each contract type
Abusiness approval and the legal review task, with the draft attached
Asends the document to internal and external signers using Microsoft's native provider, Adobe Acrobat Sign or DocuSign; pay-as-you-go
Aread the CRM and the HR system through connectors, file the signed copy, update the register; queues, retries, audit trail
Aretention labels on signed contracts and the audit record of signature events
AIllustrative economic model
Numbers you can check against your own data.
What is priced below is handling time, not the days a request waits on the legal desk; the ranges are typical rather than a measurement taken at a client. The 40 minutes covers the visible steps together: drafting from a previous version, the legal read, the email round trips, printing and scanning, chasing the countersignature and filing, blended across a one-page annex and a framework agreement. The €34 hourly cost is fully loaded across HR administration, sales support and in-house legal in Central Europe, above a pure back-office rate because legal time is part of the 40 minutes. We show capacity released, not headcount removed.
Run the numbers on your data
An illustrative estimate from your own inputs. It models released capacity; it is not a promise of savings.
Business benefits
- A standard document is requested, approved and signed the day it is asked for, instead of moving between mailboxes and printers for a week and a half
- Legal reads deviations rather than typing errors, and the released hours go to negotiation, disputes and the contracts where a lawyer changes the outcome
- The company knows what it signed: template version, clause set, approver and signatory travel with the document
- Start dates and invoicing stop waiting on paper, because signature no longer depends on who is in the office
- A busy month is absorbed by the flow instead of the legal desk, and a bulk rate-change run becomes a queue job rather than a week of copying
The management view
- Every document in flight is visible with its stage, owner and age, so a stuck signature is a fact rather than a complaint
- Approval limits and signature authority are applied every time, which makes the delegation policy enforced rather than remembered
- Deviation statistics show which clauses the market pushes back on, which is the evidence for the next template revision
- The process survives holidays, resignations and growth, because the clause knowledge sits in the library, not in two people
Board-level KPIs
Security and governance
Security is designed with the process, not after it.
- The robot uses read-only service accounts in the CRM and the HR system, with no rights to change a client or employee record; every read and write is logged in UiPath Orchestrator
- Templates and clause blocks sit in a SharePoint library where legal holds the edit rights, and every generated document records the template version it came from
- Signature events, from request through viewing to completion, land in the Microsoft Purview audit log, and the signed copy carries a retention label chosen by contract type
- A contract never leaves as an email attachment: external signers reach it through Microsoft Entra B2B while it stays in your Microsoft 365 tenant, the automation layer runs from the EU region of UiPath Automation Cloud, and secrets sit in a vault rather than in a workflow
Why now
Electronic signature has stopped being the exception in European B2B, and the tooling sits inside the platform you already pay for: SharePoint eSignature works with Microsoft's native provider, Adobe Acrobat Sign or DocuSign, and Microsoft documents it as complying with eIDAS, Regulation (EU) No 910/2014
Document generation is no longer a project: a Word template with content controls, a documented Power Automate action to populate it, approvals in Teams and a signature service that returns the signed copy to the library replace what used to be a contract lifecycle implementation
The modelled cost of leaving this alone is about €15,900 a month of capacity in HR administration, sales support and legal, spent on formatting, reading and chasing rather than on terms
Relevant executive roles
Legal time moves from proofreading standard paper to the deviations, negotiations and disputes where a lawyer actually changes the outcome.
Annexes, extensions and assignment confirmations stop being a paper chase, and a start date no longer depends on a printer and a scanner.
Contract turnaround becomes a measurable step in the sales and staffing cycle instead of an unpredictable wait between two mailboxes.
Common questions and objections
Some are, and those keep their full legal review. The rule table separates the two, so the standard majority stops consuming the attention the negotiated minority needs. Counted honestly, the split is rarely where companies assume.
It is assembled from clauses your legal team approved, with data read from your systems of record, and the template version, approvals and signature events are recorded. SharePoint eSignature returns the signed copy to the library and writes its audit events to Microsoft Purview.
Some will not, and that is a routing rule rather than an obstacle: those requests print with a signature sheet and rejoin the flow when the scan arrives. The share tends to shrink once counterparties get a link instead of a request to print and scan.
When this is not the right solution
- Fewer than about a hundred documents a month, where a well-kept template folder and a signing routine cost less than the flow
- Contracts genuinely negotiated clause by clause, such as large outsourcing agreements or transaction documents, where the value sits in the negotiation
- No agreed clause library. If legal cannot say today which clauses are approved, that decision comes first and cannot be automated around
A question for the next management meeting
Of the contracts we signed last quarter, how many were assembled from an approved template, and how many were copied from a document that nobody re-read?
Implementation approach
A scope without ambiguity, before anything is signed.
We deliver
- The template set in Word with content controls and the clause library on SharePoint, versioned and owned by legal
- The request form with its dependent questions, and a Teams entry point for people who live in chat
- The rule table for template, clause set, approver and signature authority, held where legal can change it without a developer
- Robot integration with the CRM and the HR system for counterparty and assignment data
- Signature dispatch through SharePoint eSignature, filing with metadata and retention labels, the register update
- A pilot on one contract type, then rollout with a runbook for requesters, legal and signatories
We need from you
- The contract types in scope and the documents used today, including the versions people really copy
- A named owner in legal for the clause library and the deviation rules
- Read access for a service account to the CRM and the HR system, and a SharePoint site for contracts
- The approval and signature authority matrix by contract type and value
Stages
Discovery
Contract types, volumes, current versions, deviation categories, who signs what
Design
Template and clause structure, the rule table, approval and signature authority, retention and metadata
Build
Templates, generation flow, robot integrations, Teams touchpoints, filing and register update
Validation
Generation tested against historical contracts, legal acceptance of the clause library, a signature test with a real counterparty
Go-live
One contract type first, with legal sampling standard documents during hypercare
Optimisation
Deviation statistics feed template revisions; further contract types are added
Quick win. Effort is driven by the number of contract types, how far the documents in circulation have drifted apart, and whether counterparty data can be read through an interface or has to be taken from a screen.
If a standard annex takes ten days, the delay is the copying, not the counterparty.
Send us three months of contract counts by type and the documents you use today. We come back with a written assessment of which types can be generated from a template and what your legal team would stop reading.
Assess three of your contract typesThe neighbouring process usually has the same problem
Deals close in the CRM, then wait a week for someone to set up the customer, the project and the billing.
View solution Sales & marketingTender documents turned into a compliance matrixYour bid team spends its best days reading tender packs, not deciding which ones to win.
View solution Legal & complianceData-subject requests answered in days, not at the deadlineStop answering GDPR requests by hand on day twenty-eight of a thirty-day clock.
View solution ProcurementIndexation clauses that get applied, and renewals decidedYour suppliers calculate your annual price increase. Nobody on your side checks their arithmetic.
View solution Case studyThe intelligent contract registerEvery new contract and amendment passes through IXP: parties, amounts, dates and clauses land in a living register.
View case study Case studyAutomated new-hire onboardingNew hires ready to work sooner — less paperwork for HR.
View case studyIndustries we deliver this in most oftenRetail & e‑commerceServices & ITShared services