Skip to main content

Why AI policy matters now

AI tools are already in your organisation. Your team is using ChatGPT, Gemini, Copilot, and other AI assistants to draft emails, analyse data, and solve problems. The question isn’t whether to use AI—it’s how to use it responsibly. Without clear policy, you risk data breaches, compliance violations, and inconsistent quality. With the right framework, you enable confident adoption while protecting what matters most. This guide helps leaders create practical AI policy that builds trust with teams, clients, and stakeholders.

Understand requirements

Know what Australian law expects

Draft core principles

Create guidelines your team can follow

Set boundaries

Define what’s acceptable and what’s not

Assign ownership

Make someone responsible for oversight

Australian regulatory landscape

Australia doesn’t have specific AI legislation yet, but existing laws apply to AI use in business. The Australian Government is taking a “voluntary framework” approach while monitoring for future regulation.

What you need to know

Privacy Act 1988

Personal information handled by AI must comply with Australian Privacy Principles (APPs). This includes data collection, storage, and disclosure through AI tools.Your responsibility: Ensure AI tools don’t expose customer or employee data without consent.

Competition and Consumer Act 2010

AI-generated content and decisions must not be misleading or deceptive. Automated advice or recommendations must be accurate and fair.Your responsibility: Verify AI outputs before using them in customer-facing materials or business decisions.
The Office of the Australian Information Commissioner (OAIC) published guidance on AI and privacy in 2024. Review their recommendations at oaic.gov.au for detailed compliance requirements.

Voluntary AI Ethics Framework

The Australian Government’s AI Ethics Principles provide guidance for responsible AI use. While not mandatory, they represent best practice expectations.
AI systems should respect human rights, diversity, and individual autonomy. Decisions affecting people require human oversight.
AI systems should be inclusive and accessible, and should not involve or result in unfair discrimination.
AI systems should respect and uphold privacy rights and data protection, and ensure security of data.
AI systems should reliably operate in accordance with their intended purpose.
There should be transparency and responsible disclosure about AI systems to ensure people know when they are engaging with them.
When an AI system significantly impacts a person, there should be a timely process to allow people to challenge the use or output.
Those responsible for AI systems should be identifiable and accountable for the systems, and human oversight should be enabled.

Building your AI policy

Your policy doesn’t need to be perfect on day one. Start with core principles, test them with your team, and refine based on real use.

At a glance: Policy fundamentals

Before diving into details, establish these foundational elements for your organisation.
  • Organisation wide: Adopt enterprise-secure tools with deliberate roll-out and self-service support
  • Collaborate: Share wins, outcomes, and reflections so knowledge compounds
  • Narrow use cases: Pilot specific workflows, measure results, then expand
  • Stay current: Run quarterly briefings to track changes in the AI landscape
  • Leadership Team: Executive sponsors and decision-makers
  • AI Drivers: Cross-functional working group guiding programmes
  • Champions Group: Innovation cohort that pilots before roll-out
  • All staff: Employees and contractors using approved tools
  • Privacy and security: Never compromise safeguards
  • Employee experience: Deploy AI to remove friction and improve flow
  • Customer experience: Use AI to elevate outcomes for clients
  • Active driver: Lead responsible adoption rather than react to change

Step 1: Define your position

Before writing policy, answer these questions with your leadership team.

What's our stance?

Are we encouraging AI adoption, proceeding cautiously, or somewhere between? Be honest about where you sit.

What matters most?

Is it speed, quality, compliance, or innovation? You can’t optimise for everything. Pick your priority.

What's non-negotiable?

Identify absolute boundaries. Client data? Financial decisions? Legal advice? List what AI cannot touch.

Who's accountable?

Name one person responsible for AI oversight. Without ownership, policy becomes shelf-ware.

Step 2: Draft core principles

Here’s a starting framework. Customise the language and examples to match your organisation’s reality.
These principles work best when they’re specific enough to guide decisions but flexible enough to evolve with technology.
Copy the entire section above and customise it for your organisation. Replace bracketed placeholders with your actual details.

Step 3: Set practical boundaries

Policy works when people know exactly what’s allowed and what isn’t. The traffic light framework below provides clear visual guidance your team can remember and apply.

Traffic light guardrails

Use this simple framework to help your team make quick decisions about AI use.
  • Use approved enterprise AI tools on content you already have permission to view
  • Leverage AI outputs after reviewing them for accuracy and tone
  • Include customer or supplier names, job titles, company names, and work contact info in prompts
  • Share public information, anonymised examples, and non-confidential technical questions
  • Draft emails, summarise documents, and brainstorm ideas with approved tools

Detailed usage categories

The detailed framework below expands on the traffic light system. Use this when teams need specific guidance for edge cases.

Personal information guidelines

Understanding what counts as personal information helps your team make safe decisions quickly. PII (Personal Information) is information that can identify a person on its own or when combined with other data.
  • Names (e.g., “Jane Smith”), company, role/title, work email, work phone, meeting details
  • Business context such as project names and account IDs that are not regulated identifiers
  • Public business information already available through normal channels
  • Tax File Numbers and other national IDs (Medicare number, passport, driver’s licence)
  • Financial numbers (credit card, bank account, BSB, CVV)
  • Health or biometric data, medical details, genetic identifiers
  • Authentication data (passwords, MFA codes, API keys, secrets)
  • Sensitive personal attributes (racial/ethnic origin, religious beliefs, sexual orientation, political opinions)
  • Children’s personal data
  • Home addresses and personal phone numbers for customers or employees
Rule of thumb: Names and work contacts are OK in approved tools. Any government ID, financial, health, or secret data is not.

Practical examples

These examples show the boundaries in action. Share them with your team during training.
  • “Draft a follow-up email to Sarah Lee (Acme, Head of Ops, sarah.lee@acme.com) summarising our meeting notes”
  • “Summarise this statement of work for internal review (contains no restricted PII)”
  • “Generate bullet points for a client-safe status update using the attached PowerPoint”
  • “Help me rewrite this paragraph for a non-technical audience”
  • “Suggest a formula to split full names into first and last name columns in Excel”

Step 4: Document approval and oversight

Someone needs to be responsible for AI governance. Make it official.

Step 5: Build innovation capacity

The Champions Group approach allows controlled experimentation while maintaining security. This accelerates learning without increasing risk.

Champions Group framework

Purpose

Selected team members test new AI tools and workflows in a controlled environment before wider rollout.

Governance

Champions operate under additional oversight with enhanced monitoring and regular review of experiments.

Knowledge sharing

Champions document learnings and share wins, failures, and insights with the broader organisation quarterly.
The Champions Group experiments with AI in a secure, controlled manner before wider roll-out and is governed by a separate policy framework. Opportunities to join the Champions programme are offered periodically based on business need and individual interest.

Step 6: Create incident response process

When things go wrong, speed and clarity matter. Document your response process before you need it.
1

Stop the activity

Discontinue tool usage immediately and isolate the content involved. Don’t delete anything yet.
2

Notify leadership

Inform your manager and AI Policy Owner as soon as possible. For serious incidents (data breach, regulatory concern), escalate to Executive Sponsor immediately.
3

Document the details

Record what was shared, which tool was used, when it happened, and who has access. Be thorough and factual.
4

Preserve evidence

Retain screenshots, file versions, and prompt text for investigation. Don’t modify or clean up anything.
5

Wait for direction

Hold further action until guidance is provided by the response team. Don’t attempt to fix it yourself.
Incidents happen even with good policy. How you respond determines whether they become minor corrections or major crises. Train your team on this process during onboarding.

Tool-specific guidance

Different tools require different approaches. Provide specific guidance for the tools your organisation uses.

Microsoft Copilot 365 guidance

If your organisation uses Microsoft Copilot, these specific guidelines help teams use it safely.
1

Work within your permissions

Copilot respects Microsoft 365 access controls. Only use it on content you are allowed to view.
2

Review every output

Fact-check responses before sharing externally or relying on them for critical decisions.
3

Keep prohibited data out

Do not ask Copilot to summarise or transform content that includes prohibited PII.
4

Signal AI contributions

For external documents, add “Drafted with AI assistance; reviewed by [Your Name]” when the AI contribution is material.
5

Respect meeting notices

Turn on standard recording and notice practices before using AI features that generate meeting summaries.

Engineering team guidance

Technical teams need specific boundaries for code-related AI use.

Use approved tools for boilerplate

Tools like GitHub Copilot Business may assist with scaffolding and suggestions to speed up delivery.

Protect proprietary work

Never paste proprietary client code, secrets, or prohibited PII into prompts. Assume everything you input could become training data.

Own licence compliance

You are responsible for verifying dependencies, security posture, and intellectual property of generated code before using it.
Code generation tools can suggest code with security vulnerabilities, incompatible licences, or outdated dependencies. Always review generated code as if a junior developer wrote it.

Implementation roadmap

Don’t try to implement everything at once. Follow this 90-day rollout plan.
1

Week 1-2: Leadership alignment

Get executive agreement on principles and priorities. Assign the AI Policy Owner and Executive Sponsor. Set budget for tools and training.
2

Week 3-4: Draft and circulate

Customise the policy template. Share with department heads for feedback. Refine based on practical concerns and edge cases.
3

Week 5-6: Tooling and infrastructure

Select and implement approved AI tools with proper data protection. Set up monitoring and reporting systems. Prepare training materials.
4

Week 7-8: Team training

Run mandatory training sessions for all staff. Cover principles, boundaries, and practical examples. Provide hands-on practice with approved tools.
5

Week 9-12: Launch and monitor

Officially launch the policy. Monitor usage and incidents closely. Hold weekly check-ins to address questions. Document lessons learned.
6

Month 4+: Refine and scale

Review incident reports and feedback. Update policy based on real-world use. Share success stories. Plan advanced training and Champions Group expansion.

Practical resources

Use these templates to operationalise your policy faster.

Draft customer email

“Draft a polite follow-up to [Name, Company, Role, Work Email] about the action items from our 18 Sept meeting. Keep it under 150 words and propose two time slots next week.”

Summarise meeting notes

“Summarise the attached Teams notes into 5 bullets and 3 risks. Highlight decisions and owners.”

Rewrite for clarity

“Rewrite the paragraph for a non-technical audience at Grade 8 reading level. Keep all numbers.”

Excel helper

“Suggest a formula to split Last, First into two columns and trim spaces. Explain each step.”

Code review assistance

“Review this function for security vulnerabilities and suggest improvements. Focus on input validation and error handling.”
Use this template when team members request access to new AI tools or expanded permissions.Tool requested: [Tool name and version]
Use case (1-2 lines): [Specific business need]
Data types: [What data will be processed? Any PII? If yes, justify and confirm it excludes all prohibited PII]
Risk level: Low / Medium / High
Owner / Reviewer: [Who will oversee this use?]
Pilot duration & budget (if applicable): [Timeline and cost]
Success metric: [How will you measure if this works?]
Approval required from: [Manager / AI Policy Owner / Executive Sponsor]

Australian government resources

OAIC AI Guidance

Privacy compliance requirements for AI systems

Australia's AI Ethics Framework

Voluntary principles for responsible AI development and use

ACCC AI Guidance

Consumer law considerations for automated systems

Australian Cyber Security Centre

Security guidance for AI tools and systems

Next steps

Ready to build your policy?

  1. Copy the principle template and customise it for your organisation
  2. Set up a 2-hour workshop with your leadership team to align on priorities
  3. Assign your AI Policy Owner and set their first 30-day objectives
  4. Customise the traffic light guardrails for your team’s specific tools and context
  5. Schedule team training for month 2 of your rollout
Start small, learn fast, and refine as you go. Perfect policy on day one is impossible. Good-enough policy that you actually use is valuable.