Home · Solutions · Other solutions
Solution · Other solutionsA standard NDA does not need a lawyer; it needs a route that does not run through one
NDAs and standard contracts signed and filed in a day
Standard NDAs and agreements are requested in Microsoft Teams, assembled from approved clauses, checked, signed and filed within a day, and lawyers see only the documents that deviate.
Executive summary
A two-page NDA on your own template waits nine days behind a tender review and a dispute.
The design question is not how to write contracts faster.
Standard NDAs and agreements are signed within a day, because assembly and dispatch no longer queue behind the difficult matters.
SharePoint contract library with metadata and retention; SharePoint eSignature or DocuSign; contract lifecycle management system where one exists
Business problem
Legal
Requests for NDAs and standard agreements arrive by mail, chat and corridor, without the information needed to prepare them, so the first step is always a question back. Templates exist, but in several versions across personal drives, and the clause options for each country and entity live in the lawyers' heads.
Preparation is copy, paste, rename and proofread. Signature is a separate tool with a separate login, chased by the requester. Filing is wherever the signed PDF lands, usually a mailbox, so the contract register is incomplete and renewal dates are unknown until somebody needs them.
The queue is the real problem. A legal team is measured on risk rather than throughput, so it handles every request with the same care, and nothing in the process distinguishes a two-minute document from a two-week negotiation. Both wait in the same line, and the short one waits longest in relative terms.
That is why the business stops asking. It sends its own template, accepts the counterparty's paper, or signs something that was never reviewed, and the legal team finds out during due diligence.
How it works today
- PersonA seller or buyer mails the legal mailbox or posts in the legal Teams channel asking for an NDA
- PersonA paralegal asks back for counterparty details, purpose and term, because the request arrived without them
- WaitingThe request waits behind whatever came earlier, usually a tender review or a dispute
- PersonA lawyer picks a template version from the shared drive, pastes in the party details and proofreads
- WaitingThe draft goes to the requester, then to the counterparty, and comments come back by mail
- Risk of errorComments on standard terms are read as carefully as real negotiations, because nothing marks them as standard
- PersonThe document is sent for signature from a separate tool and chased by the requester
- Risk of errorThe signed PDF lands in a mailbox, and the register learns about it only if somebody remembers
Why the current process costs more than it appears
The cost grows where nobody is looking.
- Deals and project starts wait for paperwork. A meeting held without an NDA, a subcontractor who cannot begin, a bid submitted without a signed teaming agreement: each delay is a commercial cost that never reaches the legal budget.
- Business users route around the queue. They reuse an old template from a laptop or accept the counterparty's paper unread, which is how outdated liability caps and the wrong governing law enter the portfolio.
- Nobody can list what is in force. Obligations, expiry dates and which counterparties hold confidential information are questions auditors, insurers and buyers all ask, and answering takes a fortnight of searching.
- Lawyers doing clerical work cost twice: once in the rate paid for the hour, and once in the negotiations and disputes that got less attention because templates ate the week.
- Incomplete requests force a round trip before work begins, and that round trip appears in no measure of legal performance.
Cost of inaction
The queue does not fail; it reforms every Monday. Requests keep arriving from every new partnership, subcontractor and market, and from every regulation that wants a contract where a handshake once served, while the legal team stays the size the budget allows. What changes is where the work goes: more of it around the process rather than through it, on templates nobody checked and paper nobody read.
The bill arrives at the least convenient moment. Due diligence, a client audit or a dispute asks what was signed, on whose terms and until when, and the answer is assembled from mailboxes over a fortnight. By then the terms are what they are, and the only variable is how fast the company can find out.
A plausible organisation with realistic proportions. The figures are there to be recalculated on your data; they are not a client result.
An engineering and construction consultancy with 1,300 employees working in Poland, the Nordics and the DACH region through several legal entities, with Microsoft 365, Teams and SharePoint in place, DocuSign licensed and no contract lifecycle management system.
About 210 document requests a month: mutual NDAs before bids and partnerships, subcontractor agreements on the company's own template, and consulting framework agreements with a small set of negotiable options.
Four lawyers and one paralegal take every request through the same queue. Templates live on a shared drive in several versions, and signed contracts end up in project folders and mailboxes.
Roughly 50 minutes of legal and paralegal time per request for clarification, template selection, assembly, reading standard comments, chasing signature and filing, plus 35 minutes of the requester's own time on chasing and forwarding.
The request is raised on a card in Microsoft Teams, rules select the template and clause options and decide whether it is standard, a robot assembles and dispatches the document, and only deviations reach a lawyer as a task with the context attached.
In the modelled case standard documents are signed on the day they are requested, lawyer hours move to deviations, and every signed contract is filed with an owner and an expiry date. The figures are a model on stated assumptions, and your own mailbox will correct them.
Proposed solution
The design question is not how to write contracts faster. It is how to stop a two-minute document queueing behind a two-week negotiation, and everything else follows from separating the two at the moment of the request.
The requester opens a card in Microsoft Teams and answers only what that document type needs: counterparty name and registration number, country and legal entity, purpose, term, value where it matters, and any special terms being asked for. Rules written with your legal team select the entity, the template and the approved clause options, and decide whether the request is standard. A robot assembles the Word document from the clause library on SharePoint, fills the party data and runs the counterparty checks, registry lookup and sanctions screening, before anything leaves the company.
A standard request then goes to the business approver in the Teams Approvals app where the policy requires one, and out for signature through SharePoint eSignature with the native service or DocuSign. Anything outside the rules, counterparty paper, an unusual governing law, a raised liability cap, a value above the threshold, becomes a UiPath Action Center task for a lawyer in Teams, with the request context and a comparison against the company template attached. The lawyer edits, negotiates or refuses, and the workflow continues from that decision.
Signed documents return to the contract library with metadata, a Microsoft Purview retention label and an expiry date, and the requester receives a status message instead of another mail thread. What happens to a contract after signature, obligation tracking and renewal alerts, belongs to the intelligent contract register already on this site; this workflow is what fills that register correctly. Where a contract lifecycle management system exists, the robot creates the record there instead.
Microsoft Teams Workflows app with Adaptive Cards and the Approvals app; Word templates with content controls on SharePoint; SharePoint eSignature with the native service or DocuSign; Microsoft Purview retention labels and audit; UiPath Action Center tasks completed in Microsoft Teams; UiPath Orchestrator queues, triggers and audit
The request card and its validation per document type; the rule set for entity, template, clause options, thresholds and the definition of a standard request; document assembly and party data; the counterparty check step; signature dispatch and reminders; filing with metadata, retention and expiry; the register and the Power BI workload view
Company registry and sanctions sources through UiPath Integration Service or Connector Builder; record creation in a contract lifecycle management system where one exists
How the automated process works
- PersonThe requester opens the card in Microsoft Teams and answers only the questions that document type needs
- AutomationRules select entity, template and clause options and classify the request as standard or exception
- AutomationThe robot assembles the Word document from the clause library, fills the party data and runs the registry and sanctions checks
- PersonThe business approver decides in Teams Approvals where the policy requires it
- PersonAn exception becomes an Action Center task for a lawyer in Teams, with the context and the comparison against the template
- AutomationThe approved document goes out for signature through SharePoint eSignature, with reminders on a schedule
- AutomationThe signed copy is filed with metadata, retention label and expiry date, and the register is updated
- AutomationThe requester is notified, and the named owner receives the expiry alert ahead of the date
Human-in-the-loop model
Automation handles
- Intake with the information legal needs, validated as it is entered
- Template and clause selection by entity, country and document type
- Assembly, counterparty registry lookup and sanctions screening before dispatch
- Signature dispatch, reminders, filing with metadata and retention, register and expiry alerts
People decide
- Every deviation and all counterparty paper, reviewed by a lawyer as today
- The commercial decision, by the business approver, where the policy requires one
- What counts as standard: the templates, clause options and thresholds stay owned by legal
- What to do about a counterparty the checks flag before dispatch
Before and after
Systems and integrations
Everything below runs on licences and systems you already hold, or would need anyway.
Inputs
- request card in Microsoft Teams
- counterparty details and registration number
- approved templates and clause library on SharePoint
- company registry and sanctions sources
- the approval policy
Automation layer
- UiPath Orchestrator
- UiPath Robots
- UiPath Action Center
- UiPath Integration Service
Target systems
- SharePoint contract library with metadata and retention
- SharePoint eSignature or DocuSign
- contract lifecycle management system where one exists
- Power BI
Human touchpoints: Teams Approvals for the business approver; Action Center tasks in Teams for the lawyer; status messages to the requester
Technologies used
request intake as an Adaptive Card and the business approval step
Aassemble, check, dispatch, file, schedule, retry and log every document
Alawyer review of deviations with assignment and due dates
Amail, template library and contract library without UI automation
Aapproved templates with content controls and the versioned clause library
Asignature inside the tenant, tracked and audited
Aretention labels on signed contracts and the audit of approvals and signature events
Alegal workload, turnaround by document type and register completeness
AIllustrative economic model
A model, not a promise.
Six in ten is the assumption that decides this page. 210 requests a month at 50 minutes of legal and paralegal time is 175 hours, and 0.6 of that is claimed for the standard majority, which is why the calculator starts from 126 requests: the automatable share is folded into the volume. Deviations keep their full review. The €88 hourly cost is an assumed fully loaded rate for in-house counsel, higher than a back-office rate because the time released is a lawyer's. Nothing here was measured at a client, and the requester's own time is counted separately below.
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
- Standard NDAs and agreements are signed within a day, because assembly and dispatch no longer queue behind the difficult matters
- Lawyers see deviations with the context attached, so their hours go to risk instead of to templates
- One current template and clause library, so laptop copies stop circulating and old liability caps stop travelling into new contracts
- Counterparties are checked before the document leaves the company, not after the signature
- Every signed document is filed with metadata, a retention label and an expiry date, so the register is complete by construction
- Sales and procurement stop waiting for paperwork whose status nobody could see
The management view
- Request volume by type, the share handled without a lawyer and the hours spent on the rest, which is the first credible basis for legal staffing this team has had
- Turnaround per document type becomes a service level legal can actually hold, because standard volume no longer competes with the difficult work
- Every deviation carries a record of who decided what, so the non-standard terms in the portfolio are known rather than suspected
- A template change reaches every new document the same day, without a mail asking people to use the new version
Board-level KPIs
Security and governance
Trust in automation is built on the audit trail, not on a promise.
- Templates and clause options are changed only by legal in a versioned SharePoint library, and the robot assembles from that library alone, so nothing leaves the company on an unapproved text
- The definition of a standard request is a rule set owned by General Counsel; anything outside it routes to a lawyer, and the robot cannot override that route
- Signature runs through SharePoint eSignature with the audit trail in Microsoft Purview, and signed contracts carry retention labels that block deletion during the retention period
- Counterparty data on the request card is limited to what the contract needs and stays within the Microsoft 365 EU Data Boundary and the UiPath Automation Cloud EU region
- Registry, sanctions and CLM credentials are held in a secrets store rather than in the workflow, and every assembly, dispatch and filing event is logged with the identity that triggered it
Why now
SharePoint eSignature signs and files inside the tenant with a Purview audit trail, so signature stops being a separate tool with its own login, its own chasing and its own copy of the document
Outsourcing and third-party risk rules keep raising the number of agreements a company must hold and produce on request, and that volume lands on a legal team that does not grow at the same rate
A CLM purchase on the roadmap is an argument for fixing intake first rather than later, because CLM projects fail at intake; the modelled cost of leaving it as it is runs at €13,110 a month
Relevant executive roles
Lawyers see only deviations, the approved template is the only one in circulation, and the register answers portfolio questions on demand
Legal capacity is spent on risk rather than clerical work, and contractual obligations and expiry dates stop being unknowns
NDAs and teaming agreements stop delaying meetings, bids and deals, and the requester can see where a document is
Subcontractor agreements are signed in days on the company's own terms, with the counterparty checked before dispatch
Common questions and objections
The ones on your own paper are not, and one month of the mailbox settles the argument. Deviations reach a lawyer exactly as today, with the request context already gathered and the differences from your template listed.
Then fix intake first. This workflow is the request, triage and assembly layer that CLM projects usually lack, and when the CLM arrives the robot creates the record there and uses its templates.
Nothing is dispatched outside the rules: approved template, approved clause options, approval thresholds. The easy route becomes the compliant one and every document is recorded, which is the opposite of what a laptop copy does.
When this is not the right solution
- A few dozen requests a month that one paralegal handles well with a template folder and a calendar
- No agreed templates and no appetite to standardise, because assembly rules need something to assemble from
- Almost everything on counterparty paper, as in public tendering, where intake still helps but assembly adds little
A question for the next management meeting
Last month our lawyers touched more than two hundred documents: on how many did anyone change a word of our own template, and what did the queue behind them cost sales and procurement?
Implementation approach
The first week looks the same at every client: we look at the data.
We deliver
- A classification of one month of legal mailbox requests into standard and exception, done with your lawyers
- The consolidated template and clause library on SharePoint, owned and versioned by legal
- The rule set that selects entity, template and clause options and defines what counts as standard
- Intake in Teams, assembly, counterparty checks, signature dispatch, filing, register and expiry alerts
- Integrations: eSignature, registry and sanctions sources, and the CLM record where a CLM exists
- Testing on past requests, deployment, training for legal and requesters, support after go-live
We need from you
- Current templates and the clause options each entity and country allows
- The approval policy: who approves what, at which value, in which entity
- A lawyer as product owner and a paralegal for the pilot documents
- eSignature licences and access to the registry and sanctions sources you use
Stages
Discovery
Classify one month of requests and agree the definition of a standard document
Design
Templates, clause options, thresholds, routing rules and the security model
Build
Teams intake, assembly, checks, signature, filing, register and reporting
Validation
Mutual NDAs for one entity end to end, with lawyers reviewing every document
Go-live
Controlled start per document type and entity, with hypercare
Scale-up
Further entities, subcontractor and framework agreements, CLM record creation
Departmental. Effort follows the number of legal entities and countries, how far the templates have diverged, and whether the registry, sanctions and eSignature services are reachable by API.
Your sellers already send the template themselves; a nine-day queue taught them that.
Send us one month of requests from the legal mailbox and your NDA template. We come back with the split between standard and exception and the turnaround a rule set would hold.
Split one month of legal requestsThe neighbouring process usually has the same problem
A two-page NDA takes ten days because it is copied, proofread, printed, scanned and filed by hand.
View solution Other solutionsNo payment to a vendor nobody verifiedA bank account changed because an email asked is the cheapest way to lose a six-figure payment.
View solution Other solutionsQuotes built, discounts approved and signed within the dayYour margin floor is enforced by a thumbs-up in a chat and audited three weeks later.
View solutionIndustries we deliver this in most oftenManufacturing & industryPublic sectorServices & ITShared services