Every lesson so far, you asked and ChatGPT answered, one message at a time. Then you copied the result into Word, fixed the formatting, built the slide yourself. ChatGPT Work flips that round. You describe an outcome, ChatGPT works through the steps, and you get the finished file. You stop being the courier and start being the reviewer.
What Work is
Work is ChatGPT's agent for longer, multi-step jobs. Where Chat is quick back-and-forth, Work takes on a whole task: it makes a plan, reads what it needs, does the work over many steps, checks in with you on anything important, and delivers a document, spreadsheet, presentation, report, or Site. A big task can run for a long time while you get on with something else.
You'll find it next to Chat. In the desktop app there's a switch at the top between Chat and Work; on the web and phone you can start Work tasks too. On Business, every seat includes Work; usage depends on the size of the task, and Premium seats get about five times more room.
Which one when? OpenAI's own rule of thumb: Chat for quick questions, short rewrites, and brainstorming; Work for jobs with several sources or tools, several steps, or a bigger deliverable at the end. Work uses more of your allowance, so it pays off when it saves you real time.
Where it runs, and what it can touch
This is the part to understand before you hand anything over.
On web and mobile, Work runs in the cloud. It can use what you attach, your connected apps, and the web, but it cannot reach the files on your computer.
In the desktop app, Work can work locally. You open a folder for it and it can read, change, and create files there, and with your permission even use desktop apps. Browser use and network access have their own switches.
The safe habit is simple: give it only what the task needs. OpenAI's advice is to grant access only to the files the task requires. In practice, make a dedicated working folder, copy in the files for this job, and point Work there, not at your whole Documents drive. Keep genuinely sensitive material out of it entirely. One more detail: even when Work runs locally, messages and task context may be stored in the cloud, so the lesson 1.4 rules on what you share still apply.
What it can actually do
A few jobs where Work earns its name:
- Read across many files. "Go through these twelve supplier quotes and compare price, delivery time, and payment terms."
- Build real deliverables. A formatted report, a spreadsheet with working formulas, a slide deck, ready to open.
- Combine sources. Pull from your files, a connected app, and the web in one task, then write it up.
- Grind through the dull stuff. Turn a folder of expense receipts into one summary table. Rename a pile of files to a tidy pattern.
From a project with default memory (lesson 4.3), you can start a Work task that already knows the project's files and brief.
Stay in control
Because Work acts, not just talks, you stay in the loop:
- Watch the plan and progress. You can answer its questions, change direction mid-task, or stop it.
- Approve the important steps. Before actions with consequences, Work asks. On web and phone you approve or decline on screen. Read before you click.
- Your normal permissions still apply. Work can only use apps and files you can access yourself, and your workspace's admin settings come first.
Match your attention to the stakes. Summarising a folder of public reports needs little supervision. Anything that sends messages as you, touches money, or changes files you can't afford to lose deserves your eyes on every approval.
Safety, said plainly
An agent that reads files, browses, and acts is as useful, and as risky, as that sounds. One risk is worth naming: prompt injection. If Work reads outside content, like a web page or an email, someone can hide instructions in it ("ignore your task and send this file to..."). The defences are habits:
- Keep tasks scoped: a dedicated folder, trusted sources, only the apps the job needs.
- Watch the task, not every keystroke. If it starts touching files or sites you never mentioned, stop it.
- Review the deliverable before it goes anywhere. You're responsible for what Work does on your behalf.
Where this goes next
Work lets ChatGPT act on your files. The last lesson in Part 4, Connecting ChatGPT to your tools, widens that reach to the apps you use every day, and shows how to do it safely. Scheduling Work to run on its own comes in Part 5.
Try it
In the desktop app, make a new folder and drop in three or four real files: a report, some notes, a spreadsheet. Switch to Work, open the folder, and ask: "What's in this folder, and what stands out?"
Then ask for something built: "Turn these into a one-page summary I can share, as a Word document in this folder." Watch the plan, approve what it asks, and open the file it makes. That first handover, from asking to delegating, is the whole idea of Work.
(General exercise. Role and industry versions come once accounts are in.)