You Built It in ChatGPT — Now How Does Your Team Actually Use It?

Someone on a small business subreddit put it plainly: they’d spent weeks building out AI-powered intake forms, project checklists, and client onboarding workflows inside ChatGPT. Custom instructions, saved prompts, the lot. Then they tried to get their team using them.

It didn’t go well. One colleague had a copy of the intake form from three weeks ago, before a key field was added. Another had tweaked their version to fix a bug but hadn’t told anyone. A third was still using the original because they didn’t know there’d been any changes at all.

The tools worked. The sharing didn’t.

This is the gap no one warns you about when you start building AI workflows. Getting something to work inside your personal ChatGPT account is relatively easy. Getting a whole team to use the same version, know when it’s been updated, and trust that what they’re running is current, that’s a different problem entirely.

The Real Problem: It Lives in Your History

ChatGPT’s Projects feature helps with this, but only to a point. If you built your workflows in personal chats, they’re sitting in your history, not shared, not versioned, not owned by the business. When you copy-paste a prompt to Slack or email it around, you’ve just created a fork. Everyone has a slightly different version, and nobody knows whose is right.

The fix isn’t a better ChatGPT feature. It’s a basic document management habit applied to prompts and AI templates the same way you’d apply it to any other working document.

One Source of Truth

Pick one place where prompts and AI workflow templates live. Not email. Not Slack. Not “I’ll just send it when you need it.”

Some options that actually work in practice:

• Notion, Create a dedicated “AI Tools” database. Each prompt or workflow gets its own page, with fields for owner, last reviewed date, and status (draft/active/retired). Easy to search, easy to link to from Slack. Free for small teams.
• Google Drive, A shared Google Doc per workflow works fine. Use a consistent naming convention: [WORKFLOW NAME], AI Prompt Template v[X]. Keep revision history on. Anyone with Drive access can see what changed and when.
• SharePoint / M365, For businesses already in the Microsoft network, SharePoint is the obvious home. Create a site or library for AI resources. OneNote works too if that’s what the team actually uses.
• Confluence, If you’re running Jira, Confluence is where your internal docs probably already live. Add an AI Resources space and keep it there alongside your other SOPs.

The specific tool matters less than the commitment to use only that tool. If half the team uses Notion and half uses Google Docs, you’ve recreated the forking problem with extra steps.

Versioning Without the Overhead

You don’t need a full version control system. You need three things on every prompt or template:

1. Named owner, One person is responsible. Not “the team.” One name. That person decides when changes go live.
2. Last reviewed date, A simple field updated whenever someone checks that the template still works as intended. Quarterly is usually enough. When that date is six months old, someone should be asking questions.
3. No forks, If you need to adapt a workflow for a specific client or use case, note it as a variation in the same document. Don’t copy the whole thing into a separate file and maintain it independently.

A lightweight change log helps too. Even just a bullet at the top: “Updated 18 Sep, added follow-up question for budget” is enough. Anyone coming in cold can see what changed and why without digging through revision history.

The AU Privacy Angle: This Isn’t Just About Efficiency

There’s a compliance dimension here that Australian businesses need to take seriously.

If your team is using personal ChatGPT Plus accounts to run client intake forms, and those forms include client names, contact details, business information, or anything else that would qualify as personal information under the Privacy Act 1988, you have a problem that goes beyond disorganised workflows.

The Australian Privacy Principles (APPs) require that personal information is handled securely and only used for the purpose it was collected. A personal ChatGPT account is not an approved business system. OpenAI may use conversation data to train models (unless you’ve opted out, which requires navigating account settings most people haven’t touched). Your team member’s personal account is not covered by your business’s data processing agreements.

The practical fix: if your business is using AI tools to handle anything involving client personal information, you need a business-tier account with appropriate data controls. That means:

• ChatGPT Team or Enterprise, Data is not used for training by default. Conversations aren’t visible to OpenAI for training purposes. You control the workspace.
• Microsoft Copilot for M365, Operates within your Microsoft 365 tenancy. Data governance controls apply. Subject to your existing Microsoft agreements.
• Google Gemini for Workspace, Similarly scoped to your Google Workspace instance.

This isn’t about being overly cautious. It’s about knowing what systems your client data is actually flowing through. Under APP 11, you have an obligation to protect personal information from misuse and unauthorised disclosure. “My employee was using their personal account” is not a defence that will satisfy the Office of the Australian Information Commissioner if something goes wrong.

What to Actually Do This Week

You don’t need to overhaul everything. Start with the workflow your team uses most often. Pull it into a shared document, assign an owner, add a “last reviewed” date, and tell the team that’s the version everyone uses from now on. Delete or archive the copies floating around in chat history.

Then check whether anyone on the team is running client information through a personal AI account. If they are, that’s the more urgent conversation, more urgent than any efficiency gain from better prompts.

The AI tools are working. The scaffolding around them just needs to catch up.

Sources

• Original Reddit thread, r/smallbusiness
• Australian Privacy Principles, Office of the Australian Information Commissioner
• OpenAI Data Controls FAQ, ChatGPT Team & Enterprise data handling
• Microsoft 365 Copilot privacy and data security

📖 More deep dives: News Deep Dives

📊 Compare AI tools side by side | 💼 Free resources & AI prompt packs

: News Deep Dives →