AI Policies in the Workplace

Every organisation that uses AI tools needs a policy governing how they are used. This is not optional and it is not something that can wait until "AI becomes more mature." Employees are already using AI tools today. The question is whether they are doing so with guidance or without it.

AI tools are already being used by employees across every department, whether the organisation has approved them or not. A 2024 Microsoft/LinkedIn survey found that 75% of knowledge workers use AI at work, but more than half are reluctant to admit it for fear of being seen as replaceable. Without a clear policy, organisations face uncontrolled data exposure, inconsistent quality, legal risk and no way to measure the value AI is delivering.

What Happens Without a Policy

Organisations without an AI use policy face predictable risks:

Confidential data leaks

An employee pastes client contract details into a public AI tool. The data is now on a third-party server, potentially in another country, with no data processing agreement in place.

Inconsistent quality

One team uses AI to draft client communications, another prohibits it entirely. The organisation has no shared standard for when AI output is acceptable.

Legal exposure

AI-generated content is included in a deliverable without review. It contains a hallucinated statistic or plagiarised passage. The organisation is liable.

Compliance violations

Personal information (employee records, customer data, patient files) is processed through a cloud AI tool without POPIA-compliant safeguards.

Reputational risk

A client discovers their sensitive information was processed through a public AI tool. Trust is broken, regardless of whether actual harm occurred.

These are not hypothetical scenarios. They are happening in South African organisations right now, in every sector. The organisations that have a clear policy are managing these risks. The ones that do not are accumulating them.

What a Good AI Policy Covers

An effective workplace AI policy addresses eight areas:

Scope and purpose

Define who the policy applies to (all employees, contractors, third parties) and what it covers. State the organisation's position: AI tools are permitted/encouraged within defined boundaries, not banned outright. Banning AI is impractical and drives usage underground.

Approved tools and tiers

List which AI tools are approved for use and categorise them by data sensitivity. For example: Tier 1 (public data only): ChatGPT free, Gemini free. Tier 2 (internal data): organisation's enterprise AI subscription with a data processing agreement. Tier 3 (confidential/personal data): local models only or no AI tools permitted.

Data classification rules

Define what data may and may not be entered into AI tools. At minimum, prohibit entering personal information (as defined by POPIA), client-confidential data, credentials, API keys, proprietary source code and any information covered by NDAs. Provide clear examples employees can reference.

Disclosure and transparency

Specify when AI-generated content must be disclosed. For client-facing deliverables, internal reports, published content, academic submissions and legal documents, state whether disclosure is required, recommended or not needed.

Quality review requirements

AI output must be reviewed by a human before it is used in any decision, deliverable or communication. Specify who is accountable for the accuracy of AI-assisted work. The person who submits the work is responsible, not the AI tool.

Intellectual property

Clarify ownership of AI-generated content created using company tools and data. Address whether employees may use AI-generated code in proprietary projects. Note that AI-generated content may not be copyrightable in all jurisdictions.

Monitoring and compliance

Describe how compliance will be monitored. This could include periodic audits, tool usage logs or self-reporting. State the consequences of policy violations, aligned with existing disciplinary procedures.

Review cycle

AI capabilities change rapidly. Commit to reviewing the policy at least every six months or when a significant new tool or capability is released.

The Data Classification Model

The most practical framework for AI policy is a tiered data classification model. Employees do not need to memorise a 20-page document. They need to answer one question: what kind of data am I about to put into this tool?

Tier 1: Public data

Data that is already publicly available or carries no confidentiality.

Permitted tools: Any approved AI tool, including free-tier cloud services.

Examples: General knowledge questions, publicly available research, brainstorming with no sensitive context, drafting generic marketing copy.

Tier 2: Internal data

Data that is not public but is not highly sensitive. Disclosure would be embarrassing but not legally actionable.

Permitted tools: Enterprise AI subscriptions with a signed data processing agreement. No free-tier consumer tools.

Examples: Internal process documentation, non-sensitive meeting notes, draft strategies without financial details.

Tier 3: Confidential data

Data where disclosure could cause legal, financial or reputational harm.

Permitted tools: Local AI models only (Ollama, LM Studio). No cloud AI under any circumstances.

Examples: Client contracts, financial records, employee personal information, salary data, health records, proprietary source code, NDA-covered information.

Tier 4: Prohibited

Data that must never be processed by any AI tool, local or cloud.

No AI tools permitted.

Examples: Passwords, API keys, encryption keys, authentication tokens, biometric data where processing is not explicitly consented to.

The decision is always about the data, not the tool. A cloud AI tool is not inherently unsafe. A local AI tool is not inherently safe. What matters is the sensitivity of the data being processed and whether the tool's data handling matches that sensitivity level.

AI Acceptable Use Policy: A Working Template

The template below is designed to be adapted to your organisation's size, industry and risk profile. A five-person startup and a 500-person financial services company will have different needs. Use this as a baseline and adjust the tiers, tool lists and disclosure requirements to match your context.

AI Acceptable Use Policy Template

Version: 1.0
Effective date: [Date]
Review date: [Six months from effective date]
Owner: [Role, e.g. Chief Information Officer / Head of IT / Operations Director]

1. Purpose

This policy establishes guidelines for the responsible use of artificial intelligence tools by [Organisation Name] employees, contractors and third parties. It aims to enable the productive use of AI while protecting confidential information, ensuring compliance with POPIA and maintaining the quality and integrity of our work.

2. Scope

This policy applies to all employees, contractors and third-party service providers who use AI tools in connection with [Organisation Name] business, whether on company devices or personal devices.

3. Definitions

AI tool: Any software that uses artificial intelligence or machine learning to generate, analyse or process content. This includes but is not limited to ChatGPT, Claude, Gemini, Copilot, Midjourney, local LLMs and any AI features embedded in existing software.
Cloud AI: An AI tool where data is sent to an external server for processing.
Local AI: An AI tool that runs entirely on the user's device, with no data transmitted externally.
Personal information: As defined by the Protection of Personal Information Act (POPIA): any information relating to an identifiable living natural person or juristic person.

4. Approved Tools

[List your organisation's approved tools here, categorised by tier]

Tier 1 (public data): [e.g. ChatGPT free tier, Gemini free tier]
Tier 2 (internal data): [e.g. Organisation's ChatGPT Enterprise / Claude Team subscription]
Tier 3 (confidential data): [e.g. Ollama with approved models on company hardware]

Use of unapproved AI tools for work purposes is not permitted.

5. Data Classification and Handling

Before using any AI tool, classify the data you intend to input:

Public data: May be used with any approved Tier 1, 2 or 3 tool.
Internal data: May only be used with Tier 2 or Tier 3 tools.
Confidential data: May only be used with Tier 3 tools (local AI). If no local tool is available, the data must not be processed by AI.
Prohibited data: Must never be entered into any AI tool. This includes passwords, API keys, encryption keys and authentication tokens.

6. Prohibited Uses

The following uses of AI tools are prohibited:

Entering personal information (as defined by POPIA) into any cloud AI tool without a valid data processing agreement
Entering client-confidential information into any cloud AI tool
Submitting AI-generated work as a final deliverable without human review
Using AI to make employment, credit, legal or medical decisions without qualified human oversight
Using AI to generate content that impersonates a specific individual
Disabling or circumventing safety controls on any AI tool

7. Disclosure Requirements

Client deliverables: [Specify: must disclose / disclose on request / not required]
Internal reports: [Specify]
Published content: [Specify]
Code contributions: [Specify]

8. Quality and Accountability

AI-generated content must be reviewed for accuracy, completeness and appropriateness before use. The person who submits or publishes AI-assisted work is responsible for its accuracy. "The AI wrote it" is not an acceptable explanation for errors.

9. Intellectual Property

Any content generated using AI tools in the course of employment belongs to [Organisation Name] in accordance with existing IP policies. Employees should be aware that AI-generated content may not be copyrightable in all jurisdictions.

10. Compliance and Enforcement

Violations of this policy will be addressed through [Organisation Name]'s standard disciplinary procedures. Employees who are unsure whether a specific use is permitted should consult [designated contact/department] before proceeding.

11. Policy Review

This policy will be reviewed every six months or sooner if significant changes in AI capabilities or regulations require it. The next scheduled review is [date].

Acknowledgement: I have read and understood this AI Acceptable Use Policy and agree to comply with its requirements.

Name: __________________ Signature: __________________ Date: __________________

Implementing the Policy: A Practical Roadmap

Writing the policy is step one. Making it work in practice requires deliberate implementation:

Audit current usage

Before writing the policy, find out what AI tools employees are already using. Send a short anonymous survey. You will almost certainly discover usage you did not know about. This is not about catching people; it is about understanding the baseline.

Classify your data

Map your organisation's data types to the four tiers. Involve legal counsel for anything touching POPIA. Most organisations find that 80% of daily AI use involves Tier 1 or Tier 2 data, which makes the policy easy to comply with for most tasks.

Choose and approve tools

Select specific tools for each tier. For Tier 2, negotiate an enterprise agreement with a data processing addendum. For Tier 3, set up Ollama or LM Studio on company hardware and test with approved models.

Draft and consult

Use the template above as a starting point. Adapt it to your organisation. Have legal review the POPIA implications. Circulate the draft to department heads for input.

Train and communicate

A policy that nobody reads is a policy that nobody follows. Run a 30-minute training session. Provide practical examples for each tier. Make the policy accessible (not buried in a 200-page handbook).

Monitor and iterate

Track compliance informally for the first three months. Collect feedback: are the tiers clear? Are the approved tools sufficient? Adjust the policy based on real-world experience, not theory.

For South African SMEs

Most AI policy guidance is written for large enterprises with dedicated legal and compliance teams. Small and medium businesses need something practical. The template above is designed to be usable by an SME with no dedicated compliance function. The key principles are the same: classify your data, match tools to sensitivity levels, require human review and document your approach. Even a one-page version of this policy protects your business better than having no policy at all.

POPIA Considerations for AI Usage

POPIA applies whenever personal information is processed and AI usage is no exception. Key compliance points:

Lawful basis for processing

If AI processes personal information, ensure there is a lawful basis: consent, contractual necessity, legal obligation or legitimate interest.

Cross-border data transfers

Cloud AI providers typically process data outside South Africa. POPIA Section 72 requires adequate protections for cross-border transfers. Enterprise AI subscriptions usually include data processing agreements that address this.

Data minimisation

Only input the minimum personal information necessary. If you can anonymise or pseudonymise data before sending it to an AI tool, do so.

Right to object

Data subjects have the right to object to automated decision-making. If AI is used in decisions affecting individuals (hiring, credit, service eligibility), ensure a human review mechanism exists.

Information Officer obligations

Your organisation's Information Officer should be aware of AI tool usage and include it in POPIA compliance assessments.

Disclosure: When to Tell People AI Was Involved

Always disclose

Academic or educational submissions
Legal opinions or advice
Medical or clinical recommendations
Content attributed to a specific human author
When a client or contract explicitly requires it

Disclose on request

Client deliverables (unless contract specifies otherwise)
Published content where the organisation is the author
Internal reports used in decision-making

Disclosure optional

Internal brainstorming and ideation
Drafting that will be substantially rewritten
Code generation reviewed and tested by a developer
Personal productivity (email drafts, note organisation)

When in doubt, disclose. Transparency builds trust. Concealment, when discovered, destroys it.

Common Mistakes in AI Policy

Banning AI outrightEmployees will use it anyway, just without guidance. A ban drives usage underground and eliminates all organisational oversight. Regulate, do not prohibit.

Making the policy too complexA 30-page policy that nobody reads is worse than a 2-page policy that everyone follows. Keep data tiers simple, provide clear examples and make the approved tool list easy to find.

Treating all AI tools the sameA free-tier consumer chatbot and an enterprise subscription with a data processing agreement are fundamentally different in terms of data handling. The policy must distinguish between them.

Not updating the policyAI capabilities change faster than most organisational processes. A policy written in January may be inadequate by July. Commit to a six-month review cycle at minimum.

Choosing the Right AI Model

Policy decisions should include guidance on which AI models to use for which tasks. Not all models are equal in capability, cost or data handling. Giving employees access to the most expensive model for every task is like giving everyone in the office a first-class plane ticket for a trip across town.

Match the model to the task

Not every task requires a frontier model. Summarising meeting notes, drafting email templates and answering general knowledge questions work well with smaller, cheaper models. Reserve frontier models (GPT-4o, Claude Opus) for complex reasoning, nuanced analysis and tasks where accuracy is critical.

Test before committing

Before rolling out an AI tool across the organisation, run a structured pilot. Give a small team access for two weeks with specific tasks. Compare the output quality, speed and cost against doing the work without AI. Measurable results inform better policy decisions than assumptions.

Consider open-weight alternatives

For Tier 2 and Tier 3 data, open-weight models running locally (Llama, Mistral, Qwen) can deliver 80% of the capability at zero per-token cost. The upfront hardware investment may pay for itself within months for organisations with high AI usage.

Evaluate multi-model strategies

Mature organisations use different models for different tasks. A fast, cheap model for routine classification. A capable model for complex analysis. A local model for confidential data. Your policy should allow for this flexibility rather than mandating a single tool for everything.

Understanding and Controlling AI Costs

AI tools are not free. Whether your organisation uses API access, subscriptions or local hardware, the costs need to be understood, monitored and controlled. An AI policy without a cost framework is incomplete.

How Token Pricing Works

Most cloud AI APIs charge per token: a chunk of text roughly equivalent to 0.75 words. A 1,000-word document is approximately 1,300 tokens. Pricing is typically quoted per million tokens, with separate rates for input (what you send) and output (what the model generates).

As of 2025, typical pricing ranges:

Budget models (GPT-4o mini, Claude Haiku): R1 to R5 per million tokens
Mid-tier models (GPT-4o, Claude Sonnet): R20 to R80 per million tokens
Frontier models (Claude Opus, GPT-4 Turbo with extended context): R150 to R500+ per million tokens

These costs compound quickly. A team of 10 people each making 50 API calls per day with a mid-tier model can generate a monthly bill of R5,000 to R20,000. Without visibility into usage, costs can escalate without anyone noticing until the invoice arrives.

Pricing Models Compared

API (pay per token)

Best for: Variable usage, development/testing, small teams.

Cost model: Pay only for what you use. No commitment.

Risk: Costs scale linearly with usage. No cap unless you set one. A runaway script can generate a large bill quickly.

Typical range: R500 to R20,000/month depending on usage volume and model tier.

Subscription (per seat)

Best for: Predictable usage across a team. Non-technical users who need a chat interface.

Cost model: Fixed monthly fee per user. Includes a usage allowance.

Risk: Paying for seats that are underutilised. Some subscriptions throttle heavy users.

Typical range: R300 to R700 per user/month for ChatGPT Team/Enterprise or Claude Team.

Local models (hardware cost)

Best for: High-volume usage, confidential data, organisations with technical staff.

Cost model: One-time hardware investment plus electricity. Zero per-token cost.

Risk: Requires setup and maintenance. Model quality may be lower for complex tasks.

Typical range: R15,000 to R50,000 for hardware capable of running 7B to 32B models.

Practical Cost Controls

Set spending caps

Most API providers allow monthly spending limits. Set these before giving any team access. A hard cap prevents surprise bills. A soft cap (alert at 80% of budget) gives time to investigate before hitting the limit.

Monitor usage by team or department

Use separate API keys for different teams. This makes it possible to see who is using how much, identify unusually high usage and allocate costs accurately. Most providers offer usage dashboards.

Choose the cheapest model that works

For 80% of tasks, a budget-tier model produces acceptable results. Route only complex tasks to expensive models. Some API providers offer automatic model routing: sending simple prompts to cheaper models and complex ones to capable models.

Cache repeated queries

If your application makes the same API call repeatedly (e.g. classifying incoming emails against a fixed set of categories), cache the results. Paying to process the same input twice is waste.

Watch context length

Sending a 50,000-token document as context for a simple question costs 50 times more than sending a 1,000-token extract. Teach teams to send relevant excerpts, not entire documents, unless the task genuinely requires full context.

AI Budget Planning Template

Use this template when presenting AI tooling costs to management or budgeting for the next quarter:

Item	Monthly estimate	Notes
Cloud AI subscriptions (per seat)	R ___ x ___ users	ChatGPT Team / Claude Team / other
API usage (variable)	R ___	Based on pilot usage data, with 30% buffer
Local AI hardware (amortised)	R ___	One-time cost / 24 months
Training and onboarding	R ___	Initial training session + materials
Spending cap buffer (10%)	R ___	Safety margin for usage spikes
Total monthly AI budget	R ___

Compare this total against the estimated time saved (hours x hourly cost of employee time) to calculate return on investment.

Vendor and Operational Risks

AI policy should address the operational risks of depending on external AI providers:

Vendor lock-in

If your workflows depend on a single provider's API format, switching providers becomes expensive. Where possible, use standard interfaces (OpenAI-compatible API format, which Ollama and most providers support) so you can switch without rewriting code.

Terms of service changes

Providers can change pricing, data policies and capabilities with limited notice. Enterprise agreements offer more stability than consumer terms. Read the terms and track changes.

Uptime and reliability

Cloud AI services experience outages. If your business process depends on an AI API, have a fallback plan. This could be a local model, a secondary provider or a manual process for critical tasks.

Rate limits

API providers impose rate limits (requests per minute, tokens per day). During peak usage, your team may hit these limits and experience degraded service. Understand the limits of your plan before building them into production workflows.

The multi-provider principle. Where budget allows, maintain access to at least two AI providers. If one experiences an outage, changes terms unfavourably or increases prices, you have an alternative. For confidential data, a local model serves as the ultimate fallback: no external dependency at all.

Key Takeaways

1Every organisation using AI needs a written policy, regardless of size. Uncontrolled usage creates data, legal and reputational risk.
2The core of any AI policy is data classification: match data sensitivity to permitted tools using a tiered system.
3Tier 1 (public, any tool) through Tier 4 (prohibited, no AI) gives employees a clear, practical framework for daily decisions.
4The person who submits AI-assisted work is accountable for its accuracy. AI is a tool, not a shield.
5POPIA applies to AI usage: personal information processed through cloud AI requires the same safeguards as any other cross-border data transfer.
6Match the model to the task: use budget models for routine work and reserve frontier models for complex analysis.
7Understand token-based pricing: costs scale with usage volume and model tier. Set spending caps and monitor by team.
8Compare API, subscription and local options: the cheapest choice depends on your usage volume, data sensitivity and team size.
9Manage vendor risk: avoid lock-in, track terms of service changes, maintain fallback options and understand rate limits.
10Start with the template, adapt it to your context, train your team and review every six months.
11For SMEs: even a one-page policy with clear data tiers and approved tools is better than no policy at all.