- To use ChatGPT at work reliably, write a work instruction with five parts: the task, the context, the source material, the output format and what to check.
- Pick a task you repeat every week and run the same instruction on it at least three times before calling it a workflow.
- Keep the instruction and the approved files in a ChatGPT Project so colleagues start from the same material; OpenAI describes Projects as holding files, instructions and chats together.
- Use a company workspace for company data: OpenAI states that it does not train on data from ChatGPT Business or Enterprise by default.
- A person checks every output against the source before it is sent, filed or put in a report. That step does not go away when the instruction gets better.
What self-taught ChatGPT use looks like
Our ChatGPT training page says it plainly: most self-taught users write short prompts and accept the first answer. That works for a one-off question. It does not work for the weekly report, the customer reply or the meeting summary, because next week the same person writes a slightly different short prompt and gets a slightly different answer, and nobody else on the team can repeat it.
Learning how to use ChatGPT at work is mostly learning to write down what you already know about the task, once, in a form ChatGPT can follow every time. We call that a work instruction. It is the first module of our ChatGPT sessions, and every person practises it on a task from their own week.
The five parts of a work instruction
The same five parts, every time:
- Task. What the output is and who it is for. “Draft the weekly operations update for the leadership team” beats “summarize this”.
- Context. What the reader already knows, what they care about, and what has gone wrong before. One or two sentences.
- Source. The material ChatGPT must work from, and an instruction to use only that material. An export, a policy document, last week’s approved version.
- Format. Headings, length, order, tone. Paste an approved past example if you have one; it does more than a paragraph of adjectives.
- Check. What ChatGPT should flag instead of guessing, and what the person will verify before the output is used.
Here is what that looks like for one of the workflows on our ChatGPT page, the operations team’s weekly report from a spreadsheet export:
Task: Write this week’s operations update for the leadership team, under 250 words.
Context: Leadership reads it on Monday morning and wants changes against last week, not totals they already know.
Source: Use only the attached export and last week’s update. Do not add numbers that are not in the export.
Format: Three headings: What changed, What is at risk, What we need decided. Same order every week.
Check: List every number you used with the cell or row it came from. If a figure looks wrong or is missing, say so instead of filling it in.
The last line matters most. It turns “is this right?” into a list the person can tick off against the spreadsheet in a few minutes.
How to turn one task into a team workflow
- Pick one task you repeat every week. Not the hardest part of the job, the most repetitive. If you are unsure which, the start-with-one-task method scores candidates on four questions.
- Write the five parts in a plain document first. If you cannot fill in the source and check lines, the task is not ready for ChatGPT yet.
- Run it three times on real work. Each time, note what you had to fix by hand. Most fixes belong in the context or format line, not in a longer prompt.
- Put it in a shared Project. OpenAI’s Projects in ChatGPT article describes a project as a place for files, instructions and related chats, and shared projects let colleagues work from the same files and instructions. A new hire then starts from the approved version, not from a blank chat.
- Write down who checks. One name per workflow. The AI workflow one-pager has a line for it, next to the input, the output and the review step.
- Review after two weeks. Was it used on real work, was the output good enough, and what still needed fixing? The two-week workflow review is that conversation on one page.
Which data goes in
Agree three lists before anyone pastes company material: never goes in (passwords, ID numbers, health data, anything a contract forbids), check first, and fine to use. Our AI data boundaries one-pager is a template for those lists.
Then use a company workspace for company work. OpenAI’s business data page states that it does not train its models on data from ChatGPT Business, Enterprise and its other business products by default. A personal account is governed by that person’s own settings, which is one reason the AI tool approval checklist starts by choosing one approved plan. Terms change, so read your plan’s current pages on the day you decide.
One more thing to know if your team built custom GPTs: OpenAI’s ChatGPT release notes announced plans to retire custom GPTs and offer a migration path. The dates reported differ by workspace, so check the notice in your own workspace. A work instruction written as plain text in a document moves to whatever replaces them without rework.
When this does not work
It does not work on tasks that never repeat. A one-off strategy question does not need a work instruction, and writing one is wasted effort.
It does not work when the source is the problem. If the export is wrong or last week’s approved version does not exist, ChatGPT will produce a tidy summary of bad material. Fix the input first.
And it does not work without the check. A work instruction makes the output more consistent; it does not make it correct. If nobody on the team can tell a right answer from a wrong one for this task, pick a different task. Where the job is really connecting several systems, our ChatGPT vs AI agents guide covers when an agent is worth the extra risk.
What to do in the next 14 days
- Pick one weekly task and write its five-part instruction in a document. Twenty minutes.
- Run it on real work three times and note every manual fix.
- Move the instruction and its approved files into a shared Project on a company account, and name the person who checks the output.
The approach in this post is what we teach in ChatGPT training for employees.
Questions people ask
How do I use ChatGPT at work without making mistakes?
Write a work instruction with five parts (task, context, source, format, check), tell ChatGPT to use only the material you give it and to flag anything missing, and have a person verify every output against the source before it is used. The instruction reduces mistakes; the check catches the ones that remain.
What is the difference between a prompt and a work instruction?
A prompt is usually one line written fresh each time. A work instruction is written once for a repeated task and states the reader, the source material, the format and what to check, so anyone on the team can run it and get comparable output.
Is it safe to use ChatGPT for work?
For some data, on the right plan. Agree what never goes in, what needs checking first and what is fine, and use a company workspace. OpenAI states it does not train on ChatGPT Business or Enterprise data by default; check your plan’s current terms before deciding.
Should our team use ChatGPT Projects or custom GPTs?
For a shared, repeated task, a Project holds the instructions, files and chats in one place. OpenAI has announced plans to retire custom GPTs, so check the notice in your workspace before building new ones, and keep each instruction in a plain document as well.
Do you teach ChatGPT at work in Dallas?
Yes. Sessions run onsite across Dallas–Fort Worth or live online anywhere in the U.S., in English or Chinese, and each person builds a workflow on a task from their own week. Each team gets a written quote.
Sources
- OpenAI Help Center: Projects in ChatGPT
- OpenAI: Business data privacy, security, and compliance
- OpenAI Help Center: ChatGPT release notes

