Insights

What to Check in a Data Processing Agreement Before Procurement Signs Off

by Harvey Team•Nov 18, 2026

A data processing agreement (DPA) sets the contractual rules for how a vendor processes personal data on another organization’s behalf. Procurement may have agreed on the price and service levels, but the DPA still needs a separate check. What data will the supplier handle? Can it use that data for anything else? What happens if a breach or compliance request comes in?

However, a DPA can contain every expected heading and still leave the organization exposed. Before signature, your legal department needs to confirm that the document reflects the actual processing arrangement, includes the protections required by applicable law, and sends any material deviation from approved standards to the person authorized to decide it. Here’s what to check before procurement moves forward.

When is a Data Processing Agreement Required?

Under Article 28 of the GDPR, a controller engaging a processor to handle personal data on its behalf needs to put a binding processing contract or other legal act in place. The controller determines why and how personal data will be processed and the processor acts on the controller’s instructions. The Irish Data Protection Commission’s guidance makes it clear that the agreement must identify the processing and include specific contractual duties, not just a general promise to comply with privacy law.

The need for a particular agreement depends on the parties’ actual roles and the laws or jurisdictions that apply. For example, a vendor might be a processor for the service it provides and an independent controller for a separate activity. U.S. rules can also require specific vendor terms, such as California’s CCPA regulations, which prescribe contractual restrictions and specified business purposes for service providers and contractors. Those provisions aren't the same as GDPR Article 28 mentioned above.

Additionally, a nondisclosure agreement protects confidential information but does not replace a required DPA. Likewise, standard contractual clauses used for international data transfers address a different legal question and may be required on top of processor terms.

Check What the Vendor Will Actually Process Before Reviewing the Clauses

Start with the processing annex and the business’s intended use, not the vendor’s liability cap. The most polished DPA isn’t very useful if its description of the service is wrong. Compare the agreement and its schedules with the order form, statement of work, vendor questionnaire, and what the business sponsor has actually asked the vendor to do.

Information to verify

Check against

Why it matters

Purpose, services, and duration

Processing annex, order form, SOW

It defines scope and permitted use

Personal data and affected individuals

Data inventory, intake questionnaire

It surfaces sensitivity and exposure

Contracting parties and roles

DPA definitions, entity list

It clarifies who gives instructions

Storage, support, and access locations

Hosting map, security documentation

It identifies transfer and access risks

Subprocessors and onward processing

Current subprocessor list, service diagram

It enables authorization and oversight

For example, a DPA that only refers to business contact details needs another look if the deployment will give the vendor access to customer records or employee files. Update the description and risk assessment before debating narrower drafting points because the rest of the review depends on getting these facts right.

Eight DPA Provisions Legal Should Review Before Sign-Off

For each provision, ask three things:

  1. Does it meet the applicable legal requirement?
  2. Does it match the organization’s approved position?
  3. If it doesn't, what evidence or change would make it acceptable?

Some clauses are mandatory under the relevant law while others allocate commercial risk and can be negotiated within your authority framework.

1. Processing Instructions and Permitted Data Use

The processor should be bound to process personal data on documented instructions, subject to applicable legal exceptions. Check that the DPA limits use to defined services and addresses disclosures, onward processing, and any separate role the vendor takes on. A broad right to use customer data for “business purposes” might say much less than the business believes it says.

For an AI-enabled supplier, review any permission to use inputs, outputs, or personal data for model training, product improvement, or unrelated analytics. That use isn't automatically prohibited in every arrangement, but it needs to be assessed against the parties’ roles, applicable law, and company policy. If it isn’t intended, narrow the permitted purposes and confirm the restriction carries through the related terms.

2. Security Measures and Confidentiality

We recommend reviewing the technical and organizational measures the processor commits to maintaining, including access restrictions, encryption where appropriate, incident response, resilience, and confidentiality obligations for personnel. The description should be specific enough for security to assess whether the controls fit the sensitivity and scale of the data.

The reason for this is that a basic promise to use “industry-standard security” may be too vague to support that decision. Ask for the relevant security schedule, current assurance reports, and clarification of any material exclusions. Legal checks what the supplier is contractually committed to, but security tests whether the actual controls and evidence are sufficient; neither review replaces the other.

3. Breach Notification and Incident Cooperation

The contract should say when the processor needs to tell the controller about a personal data breach, who it should contact, what initial facts it shares, and how it will support investigation, mitigation, and required notifications. Terms that allow a vendor to delay notice until it has completed an internal investigation can leave the customer without the information it needs.

The timing matters, too. Under GDPR Article 33, a processor must notify the controller without undue delay after becoming aware of a personal data breach. The GDPR’s potential 72-hour deadline for a controller to notify its supervisory authority is a different obligation, not a universal 72-hour processor-to-controller deadline. You should negotiate a workable contractual notification window and escalation contacts based on your organization’s response needs.

4. Subprocessor Authorization and Changes

Check whether the controller grants specific or general written authorization for subprocessors, whether the current list is accessible, and how the vendor announces additions or replacements. Where general authorization applies, the controller needs an opportunity to object to intended changes under GDPR Article 28. The vendor also has to impose appropriate downstream protection obligations and remains responsible to the controller for the subprocessor’s performance of those obligations.

A missing subprocessor list or a right to make changes without meaningful notice is a reason to ask questions. Confirm the services each subprocessor performs, where processing happens, and whether your vendor-risk process can assess significant changes before they go into effect.

5. Data Location and International Transfers

Data location isn't limited to the region named in the hosting description. Remote support, backup services, and subprocessors can create access or transfers across borders. Compare those arrangements with the DPA, security materials, and the organization’s restrictions on where personal data may be processed.

Where GDPR transfer rules apply, determine whether appropriate safeguards are in place and whether further assessment is needed. The European Data Protection Board distinguishes standard contractual clauses for controller-processor relationships from clauses designed to provide safeguards for international transfers. On its own, signing a DPA doesn’t settle the international transfer question.

6. Data Subject Rights and Regulatory Assistance

A processor may hold records the controller needs to answer access, correction, deletion, or other rights requests. Check the vendor’s duty to assist, how requests reach the right team, and what information or system access it can provide. The contract should also cover assistance with applicable security, impact-assessment, consultation, and regulatory duties.

Keep an eye out for language that promises cooperation in principle but doesn’t provide a workable route to obtain it. The review should establish who responds, how quickly the parties communicate, and any operational limitations that could make an otherwise acceptable clause hard to perform.

7. Retention, Return, and Deletion

Make sure to also confirm what happens to personal data when the services end. Under GDPR Article 28, the agreement needs to address return or deletion at the controller’s choice, subject to applicable legal retention requirements. Verify that the treatment of archived copies, backups, and subprocessors is explained instead of left to assumption.

For a material vendor, ask how the organization will prove that return or deletion took place and whether a transition period is needed to retrieve data. An unclear offboarding obligation can become a costly problem long after procurement has closed the deal.

8. Audit Rights, Accountability, and Liability

Review whether the vendor must provide the information needed to demonstrate compliance and allow or contribute to required audits and inspections. The practical question is whether the organization can obtain useful evidence when its own audit, regulator, or incident response requires it. Security reports can support this process, but shouldn't automatically erase a contractual duty to cooperate.

Then, read the DPA alongside the master services agreement (MSA). Check which document takes precedence, whether the liability cap covers privacy incidents, what indemnities and termination remedies apply, and whether related terms conflict. The Irish Data Protection Commission distinguishes Article 28 minimums from additional provisions that parties might negotiate, including liability and indemnities. Treat those commercial protections as important risk decisions without describing every preferred term as a universal statutory requirement.

Which DPA Issues Should Prevent Procurement From Signing?

Not every discrepancy deserves the same response. An unresolved mandatory term or missing legal basis for a required transfer is different from a negotiable fallback that the right person can accept. We recommend using a risk-based decision framework that’s tied to the data involved, the law that applies, and the organization’s delegation of authority. We’ve outlined some examples below to illustrate a useful starting point, but they shouldn’t act as an automatic legal verdict for every supplier:

Finding

Pre-signature action

Decision owner

Required processor provisions are missing

Hold — correct the DPA before clearance.

Legal and Privacy

Transfer safeguards are missing where required

Hold — verify the transfer mechanism and any necessary measures.

Privacy

Security commitments lack adequate evidence

Pause for a security assessment and documented remediation.

Security and Legal

Secondary-use or AI-training rights exceed policy

Negotiate limits or seek lawful, authorized exception approval.

Privacy, Legal, business owner

Subprocessor or breach terms exceed approved fallback

Escalate — agree on revisions or record authorized risk acceptance.

Privacy and Legal

Variation falls within an approved playbook position

Record the fallback and proceed under delegated authority.

Legal Ops and Procurement

A “hold” means the relevant issue needs to be resolved before the agreement is cleared, not necessarily that the purchase has failed. A negotiated deviation should name the person who approved the residual risk and the version of the DPA they reviewed. NOTE: Internal permission to accept a commercial risk can’t replace a mandatory legal requirement.

Build a DPA Review Process That Doesn’t Slow Down Procurement

The highest-value step is a consistent first-pass comparison against the legal department’s own positions, followed by clear escalation. Our guide to vendor contract management explains the broader division of work between Procurement and Legal. For DPAs, the sequence can stay fairly simple:

  1. Collect a complete request: Procurement supplies the DPA, MSA, data-use description, contracting entity, target signature date, and supporting security materials. Harvey Intake can capture and route supplier DPA requests, gather missing context, and keep ownership visible.
  2. Run the first pass against approved positions: Harvey’s Contract Intelligence can review an incoming DPA using the organization’s playbook, identify deviations, and give counsel a review-ready starting point. A reviewer still checks each flagged clause and any issue the playbook doesn’t cover.
  3. Assign each exception to the right decision-maker: Privacy handles transfer and data-use questions, security validates controls, counsel addresses legal drafting, and the business accepts permissible residual risk within its authority. Legal Work Orchestration in Harvey can assign tasks, coordinate reviews, and show which work remains open.
  4. Close the loop before signature: Recheck revisions against the approved version, record conditions and reviewer decisions, confirm who has signing authority, and send Procurement the actual signature-ready documents. An exception shouldn’t disappear because an email thread was marked complete.

The goal isn't to force every low-risk supplier through the same lengthy process. It’s to make the minimum checks reliable and the escalation path predictable when a clause really needs judgment.

What Should the Final DPA Approval Record Include?

A documented approval is only useful if someone can reconstruct what was approved. Keep the record with the executed agreement and identify the owners of any duties that continue after signature. A practical sign-off checklist should include:

  • The final DPA, MSA, processing annexes, and version or document IDs actually approved.
  • The intended processing purpose, data categories, key locations, and business owner.
  • Privacy and security review results, including evidence or assessments relied on.
  • Material deviations, negotiated language, and any conditions that must be met before onboarding.
  • The decision, approver, and date for each accepted residual risk.
  • Confirmation of legal clearance, separate commercial approval, and authorized signing authority.
  • Post-signature owners for subprocessor notices, renewal checks, retention, and eventual deletion.

Legal sign-off, business risk acceptance, and the authority to bind the organization are distinct decision checkpoints. Our guide to a contract approval workflow explains how those decisions can be assigned without restarting an entire review whenever one clause changes.

Make DPA Review Consistent Without Slowing Your Business

A DPA is ready for signature when it accurately describes the processing, contains the protections the relationship requires, and leaves no material exception without an owner and a decision. That standard gives Procurement a clear answer while reserving Legal’s attention for the issues that warrant it.

For in-house legal teams managing repeat supplier reviews, Harvey connects playbook-based contract analysis with intake and coordinated work. The result is a more consistent first pass and clearer handoffs, while lawyers and business owners retain authority over legal judgments and approvals. Explore how Harvey supports in-house legal teams, or request a demo to see how the review process could fit your organization today.

Sources