Share on LinkedInShare on LinkedIn

ARTICLE · 08 APRIL 2026

Beyond The NDA: Contractual Considerations For IT Proof Of Concept Engagements

When evaluating a new IT vendor or technology solution, a proof of concept ("POC") is a natural first step. Because a POC is typically short in duration and provided at nil cost, many organisations assume that a simple non-disclosure agreement ("NDA") is sufficient to get started.

South AfricaMedia, Telecoms, IT, Entertainment

When evaluating a new IT vendor or technology solution, a proof of concept ("POC") is a natural first step. Because a POC is typically short in duration and provided at nil cost, many organisations assume that a simple non-disclosure agreement ("NDA") is sufficient to get started. That assumption is not correct.

An NDA serves an important but narrow purpose: it governs the confidentiality of information shared between the parties. It was never designed to address the full spectrum of risks that arise when a vendor is given access to an organisation's data, systems, or environment. A typical NDA will not address what data the vendor may access and for what purposes, what security standards it must maintain, what happens to the data when the POC concludes, who owns any intellectual property created during the engagement or what liability the vendor bears if something goes wrong. These gaps exist regardless of whether the data in question is personal data, commercially sensitive

We operate a free-to-view policy, asking only that you register in order to read all of our content. Please login or register to view the rest of this article.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

See more popular content from