Quick answer
Prepare one indexed review bundle containing every proposed contract document and the evidence needed to test it. Include the editable draft, schedules, statement of work, proposal, service levels, pricing and tax assumptions, change-control form, authority records, intellectual-property inventory, data-flow summary, insurance evidence, existing licences, negotiation history and any document said to be incorporated by reference.
How to use this guide
Keep originals separate from working copies. A missing schedule or old version can change the meaning of the agreement, and a polished main document does not cure an undefined service, unresolved price or absent data-processing arrangement. The purpose of the bundle is to show the complete proposed deal—not to produce as many files as possible.
1. The full contract set and version history
Save the draft in its native format and as a stable PDF. Add every annexure, statement of work, specification, policy, rate card and linked online term. If a document is not attached, capture the exact URL and access date, then ask whether the online version can change after signature. Create a version table showing the sender, date, file name and main changes.
Include prior heads of terms, quotations and proposals where they explain the transaction. Mark them as background rather than silently treating them as binding. The Constitutional Court's interpretation approach in University of Johannesburg v Auckland Park Theological Seminary confirms why text, context and purpose can matter together. A lawyer needs to know which material was exchanged and which documents the draft says form part of the agreement.
2. Entity and signatory material
For each party, collect a current disclosure certificate or comparable registration record, registered and trading names, addresses, tax details and the contact responsible for contractual notices. If a trust, partnership, sole proprietor, non-profit or foreign entity is involved, identify its legal form instead of forcing it into a company template.
Add the proposed signatory's job title, board or member resolution if available, delegation, power of attorney or procurement approval. The Companies Act provides the governance setting for South African companies, but a registry printout is not a substitute for transaction-specific authority analysis. Do not attach confidential constitutional records indiscriminately; provide what is proportionate and flag the rest for secure review.
3. Scope, technical and acceptance documents
Supply the service specification, implementation plan, milestone table, dependencies, customer responsibilities, staffing assumptions, support hours, escalation path and acceptance test. If the provider relies on a product roadmap, proof of concept or demo, keep the recording, screenshots and written limitations. Separate what exists now from what is promised later.
For technology or managed services, add architecture diagrams, hosting regions, subprocessor or subcontractor list, recovery commitments, migration plan, security standard and exit/export format. For professional services, include the brief, required qualifications, named personnel, expected work product and review cycle. The scope pack should let a reviewer trace each fee to an obligation and each obligation to an acceptance method.
4. Pricing and financial assumptions
Prepare the rate card, quotation, unit volumes, minimum commitments, deposit, expenses policy, currency terms, escalation formula and VAT treatment. Add a sample invoice and calculation for a normal month, a high-usage month and a change request. If discounts depend on term or volume, show the condition and what happens if it is missed.
Include payment security, guarantee or debit-order documents only if actually proposed. If charges are deferred or attract fees and interest, flag the arrangement for National Credit Act classification; do not assume every delayed business payment falls inside or outside that Act. Preserve any tender or procurement pricing rule that limits amendments.
5. Intellectual-property and licence inventory
Create three lists: customer materials, provider background materials and project outputs. For each item, state the current owner, third-party licence, proposed use, format and required post-termination access. Add open-source or stock-content terms where they are material. Identify trademarks, datasets, templates, code, methods, designs and documentation rather than using “all IP” as an unexplained category.
The Copyright Act contains different first-ownership rules for different works and requires a signed writing for an assignment. Bring employment and contractor agreements where ownership of key inputs depends on them. Do not promise the other party rights that your business may not own.
6. Confidentiality and personal-information documents
Provide any existing non-disclosure agreement, information-classification policy, retention schedule, security questionnaire, incident plan and proposed data-processing addendum. Make a short data map showing whose personal information is involved, the purpose, source, system, access roles, location, recipient, retention period and deletion or return method.
POPIA applies according to the actual processing. Where one party operates for another, the written arrangement and security obligations need to match those roles; cross-border transfers and incident cooperation may require specific treatment. Redact irrelevant personal data from the review copy and send sensitive material through the lawyer's approved secure channel.
7. Risk, insurance and regulatory evidence
Add the requested insurance types and limits, current certificates, material exclusions known to the business, licences or accreditations required for performance, and any regulator or customer approval. A certificate shows that a policy exists at a point in time; it does not prove that every contractual indemnity or cyber event is covered.
If the service is sold to consumers or a juristic person that may fall under the Consumer Protection Act threshold, include the customer's status and the figures needed for coverage analysis. If electronic ordering is central, keep the checkout or acceptance flow and supplier disclosures relevant to ECTA. For sector-regulated work, list the licence and source rule rather than saying “fully compliant.”
8. Negotiation and approval trail
Export the material emails, platform comments, meeting notes and redlines in date order. Preserve native messages, attachments, authors and timestamps. The Electronic Communications and Transactions Act gives data messages legal and evidential recognition, but weight depends on reliability, integrity and context. Screenshots alone may omit headers, threads or attachments.
Add an internal approval table: commercial owner, legal reviewer, security, finance, tax, procurement and final signatory. Record each unresolved decision and who has authority to close it. Do not hide side promises because they are embarrassing or commercially inconvenient; undisclosed assurances are exactly what the reviewer must reconcile with the integration and variation clauses.
Build a usable index
Number the bundle by topic rather than file arrival order. For each item, show its source, date, version, status and the clause it supports. Add a missing-document list and a five-line commercial summary: purpose, value, start date, critical dependency and worst credible failure.
Give the reviewer both a clean set and a marked set. That allows legal work to concentrate on contradictions and risk allocation instead of spending the first hour locating the operative schedule.
Important limitation
This is general South African information about preparing documents for review. It does not establish which document is binding, who has authority, or which statutory regime applies.
FAQs
Should I include proposals and emails if the service agreement has an entire-agreement clause?
Yes. They can reveal scope assumptions, representations, versions and contradictions that the reviewer must address. Their legal effect still depends on the final wording and transaction.
What authority documents belong in a company service-agreement pack?
Include entity records and the proposed signatory's position, plus any proportionate board resolution, delegation, power of attorney or procurement approval. Registry information alone does not settle authority.
Why prepare a data map before signing a services contract?
It shows the real personal-information roles, systems, recipients, locations, retention and deletion needs. That lets the agreement allocate POPIA and security duties to the actual processing arrangement.
Is an insurance certificate enough for contract review?
No. It confirms limited policy information at a point in time. Relevant limits, exclusions, deductibles, territory and claim conditions should be checked against the risks the agreement allocates.
Related Lexuno paths
Related articles
Source notes
Legal note
This article is general legal information for South African readers. It is not legal advice. Speak to a qualified legal professional about your specific facts before taking action.