Your company needs to hire a new vendor. Before you can start working together, three things must happen: an NDA must be signed, a contract must be negotiated, and a compliance review — KYC, due diligence, background check — must be completed.
In theory, these three processes run in parallel. In practice, each one lives in a different silo.
Legal handles the NDA. Procurement negotiates the contract. Compliance runs the risk analysis. Each department has its own spreadsheet, its own email thread, its own pace. And nobody has visibility of the whole picture.
The result is predictable: duplicated information, overlapping deadlines nobody notices, and a vendor who should have been operational in two weeks but only starts working two months later.
This article shows how to solve this problem by treating NDA, contracts and compliance as orchestrated processes — not isolated tasks.
The silo problem
Duplicated data collection
When each department manages its process independently, the same vendor fills out similar forms three times. Legal asks for company name, tax ID and legal representative for the NDA. Procurement asks for company name, tax ID and bank details for the contract. Compliance asks for company name, tax ID and corporate structure for KYC.
Three forms, three emails, three folders. And if the vendor changes their legal representative midway, only one department finds out.
Lack of visibility
The manager who needs to approve starting operations with the vendor has no single place to check status. They must ask legal if the NDA was signed, ask procurement if the contract is closed, ask compliance if the review is complete.
Three conversations, three response times, three versions of reality. The consolidated information exists only in the mind of whoever asked the questions — and it becomes outdated the next minute.
Invisible delays
Without cross-visibility, nobody notices the contract is stalled waiting for the NDA, or that compliance is waiting for a document procurement already has. Each process moves at its own pace, unaware it is blocking or being blocked by another.
These delays do not appear in any report. They simply accumulate until someone asks: "why is this vendor still not operational?"
The solution: orchestration with linked cases
The idea is simple: instead of treating NDA, contract and compliance as three independent processes, you treat them as three cases that belong to the same flow.
Each process keeps its identity. The NDA has its stages (draft, review, signature). The contract has its own (proposal, negotiation, approval, signature). Compliance has its own (document collection, analysis, opinion). Each follows its template, with its fields, rules and responsible parties.
The difference is that they know about each other. Each case references the others. A change in one is visible to those following the rest. And a single dashboard shows the vendor status across all three processes.
How it works in practice
1. Create a template for each process
You need three templates:
- NDA: stages such as Draft, Legal Review, Sent to Vendor, Signature, Active
- Contract: stages such as Commercial Proposal, Negotiation, Legal Review, Internal Approval, Signature, Active
- Compliance (KYC/Due Diligence): stages such as Document Collection, Risk Analysis, Opinion, Approved/Rejected
Each template has its own fields. The NDA has confidentiality type, validity period, involved parties. The contract has value, payment terms, SLA. Compliance has risk level, required documents, analysis result.
2. Link the cases
When a new vendor starts the onboarding process, you create three cases — one for each template — and link them. In CaseFy, linked cases appear in the timeline and dashboard of each case, allowing direct navigation between them.
If legal needs to know the compliance status before finalizing the contract, they just look at the linked case. No emails, no questions, no waiting.
3. Use a consolidated dashboard
With all three cases linked, the manager sees the complete onboarding status in one place:
- NDA: Signed
- Contract: In negotiation (stage 3 of 6)
- Compliance: Awaiting documents (stage 1 of 4)
Instead of three conversations to understand the situation, one look at the dashboard is enough.
4. Automate dependencies
Some steps depend on others. The contract cannot be signed without an active NDA. Operations cannot start without the compliance opinion. Automations notify responsible parties when a dependency is resolved, eliminating manual follow-up.
Concrete benefits
Elimination of rework
Vendor data is collected once and shared across cases. If the tax ID, company name or legal representative changes, the update appears in all processes.
Real-time visibility
Anyone involved — legal, procurement, compliance, management — sees the current status of all related processes. No follow-up emails, no alignment meetings, no tracking spreadsheets.
Cycle reduction
When processes can see each other, blockers become visible before they turn into delays. Compliance can start its analysis while the NDA is still under review. The contract can advance on commercial clauses while waiting for the risk opinion.
The total onboarding cycle, which took two months in silos, can drop to three to four weeks with proper orchestration.
Complete audit trail
Each case timeline records every event: who created it, who moved it between stages, who approved it, who commented, when each action happened. In case of an audit, you have the complete history without searching through emails or asking people.
Beyond vendor onboarding
Orchestration with linked cases is not limited to vendors. The same pattern applies to any scenario where multiple processes must converge:
- Employee onboarding: employment contract + documentation + training + IT access
- Product launch: regulatory approval + distributor contracts + marketing campaign
- M&A operations: legal + financial + labor + tax due diligence
- Incident management: investigation + communication + remediation + regulatory report
In all these scenarios, the problem is the same: overlapping processes managed by different departments with no cross-visibility. And the solution is the same: independent templates, linked cases, consolidated dashboard.
How to get started
CaseFy was designed for multi-template orchestration. You create each process as an independent template with its stages, fields and automations. Then you link the cases that belong to the same flow.
The result is a platform where each department works on its own process with its own rules, but everyone sees the whole picture. No parallel spreadsheets, no lost emails, no meetings to ask "what is the status."
Start by creating the three templates — NDA, contract and compliance — and link the first vendor's cases. In one week, your team will have more visibility than it had in the last six months.