eProcureAI / Platform / NDAs
NDAsAn NDA moves from draft to signature through the same five stages every time. Holding all of them in one place means you always know which suppliers have signed and which are still arguing about clause four.
This is the real screen. Stage progress, change requests and the assign rule.
Confidentiality agreements are simple documents that create disproportionate administrative mess, because they multiply.
A sourcing event needs six suppliers under NDA. Each one wants a small change. Now you have six documents at different stages, in different inboxes, and the honest answer to whether supplier four has signed is that somebody would have to check.
Holding all of them in one place with an explicit stage removes the checking. Draft, assigned, negotiating, accepted, signed. Anybody looking can see where each one is without asking.
An NDA either goes to a single supplier, or it attaches to a procurement so every invited supplier receives and negotiates it. The system requires you to choose, because doing both creates two versions of the same agreement that can drift apart.
That constraint sounds restrictive until the first time you avoid discovering that a supplier signed a version nobody else did.
Suppliers rarely reject an NDA. They ask for changes, usually the same handful. Handling those as structured change requests rather than a marked up document means each one is reviewed on its own and answered with a recorded reason.
Created from a template or from scratch, with sections drafted so you are editing rather than starting from nothing. Any draft can be saved back as a reusable template.
The fork. Send it to one supplier, or attach it to a procurement so every invited supplier negotiates it. One or the other, never both.
Change requests arrive individually rather than as a marked up file, each with a summary of what it does. You accept, counter or reject with a reason.
Both sides agree and the version locks. Deviations from the original template are listed, which is the question legal asks six months later.
Signature captured and stored against the supplier, then attached automatically to future orders so nobody signs the same agreement twice.
Used when the relationship is one to one. A specific supplier, a specific agreement, negotiated between the two of you.
Used before a sourcing event, where every invited supplier needs to be under NDA before seeing the specification.
Doing both creates two versions of the same agreement following different paths, which drift apart quietly and are then difficult to reconcile.
Most NDA negotiations are the same handful of requests. Knowing which are routine speeds up every one of them.
| Request | How common | Typical position | What to check |
|---|---|---|---|
| Shorter term | Very common | Usually acceptable | Whether it covers your likely engagement |
| Carve out for pre existing knowledge | Very common | Standard and reasonable | That it is genuinely pre existing |
| Mutual rather than one way | Common | Often fine | Whether you are actually sharing anything |
| Narrower definition of confidential | Occasional | Depends | That it still covers what matters to you |
| Governing law change | Occasional | Worth a legal view | Practical enforceability |
Because each change is handled as its own request with a recorded decision, the pattern across your supplier base becomes visible over time.
Not in a folder. The signed agreement lives on the supplier record where anybody with access can find it.
So a supplier who has signed does not sign again on the next purchase.
Which clauses moved and why, answered once rather than reconstructed later.
Agreements expire. The date is tracked like any other document expiry.
Who has signed, who is negotiating, and who has not started, as a list rather than a question.
Available when somebody asks what was in place at the time of a particular purchase.
Six agreements at five stages is a tracking problem, and tracking problems belong in software rather than in somebody's memory.
Decide on the changes suppliers ask for. Everything else is administration the system handles.
Tracks the stage, keeps the versions straight, and reuses the signature.
We will run it through the five stages on the call, including a change request.
Book your free demoNext in the chain: Vendor Hub