How to use ChatGPT at work: a practical guide

Start with one task you can check

Choose a piece of work you already understand: an internal update, a meeting agenda or a summary of your own notes. You should be able to spot a missing fact without asking another AI. That makes the first attempt useful and gives you a fair way to judge the answer.

OpenAI’s Use ChatGPT guide documents working with prompts and files. Feature names, limits and access can vary by account, platform and workplace settings. Begin with the tools visible in your account; this guide does not require a particular paid plan.

Turn rough notes into a useful email

Here is a fictional operations example: a supplier delivery is late, two jobs may move, and your team needs a decision by Thursday. The useful output is a clear update with a specific request.

1. Open a new chat and describe who will read the email and what they need to decide.
2. Paste approved notes or use the fictional facts in the prompt below. Keep names and sensitive customer details out of a practice exercise.
3. Request a short draft and a separate list of missing information.
4. Compare each factual statement with the notes. Correct the facts first, then adjust the tone.
5. Copy the checked draft into your email application and review the recipients before sending.

Draft an internal email in Australian English, under 160 words. Audience: our operations team. Purpose: decide how to handle a delayed delivery. Facts: delivery expected Tuesday, supplier now expects Friday, two customer jobs may be affected, manager needs a plan by Thursday at noon. No revised customer dates are agreed. Include a clear request for options. Do not invent names, commitments or causes. After the draft, list any facts I should confirm before sending.

Choose the feature that fits the job

OpenAI’s feature documentation describes several ways to extend a conversation. These are starting points for your own workflow, not a guarantee that every feature appears in your account.

• Files: attach an approved document or spreadsheet and specify the questions you want answered. Ask for source locations and check the original.
• Projects: group related chats, reference files and instructions for recurring work, such as weekly operations reports. Keep the project’s source material current.
• Web search: request current information with citations. Open important sources and check their dates before repeating the claims.
• Documents and other outputs: when file creation is available, request a useful format and inspect the downloaded file. A convincing preview does not prove its numbers are correct.
• Plugins and connected services: add relevant tools only when you understand the access you are granting. Availability and approval can depend on your workplace.
• Scheduled tasks: where available, make the required outcome, timing and notification clear, then check the schedule was actually created. A request in an ordinary chat is not proof of a recurring task.
• Voice: where supported, talk through a problem or rehearse an explanation. OpenAI’s desktop voice guide lists eligible plans and rollout conditions; check the current guide for your device. Avoid speaking confidential details in a shared space.

Give better instructions without learning special language

OpenAI’s prompting guide recommends clear requests and useful context. For everyday work, give five things: the task, the audience, the source material, the constraints and the output format.

Instead of asking for a better report, name the improvement: put the decision first, keep the three supporting figures, remove repetition and preserve uncertainty. If the answer is wrong, point to the particular error and provide the correction. Repeatedly asking it to try harder gives it little new information.

For a weekly update, supply last week’s approved structure and this week’s notes. Ask it to separate completed work, delays and decisions needed. Reuse the structure; replace the facts.

Review the result before it becomes work

Use a small acceptance checklist that matches the task. For an email: correct facts, suitable tone, clear request and no invented commitment. For a spreadsheet: correct rows, units, formulas and totals. For research: sources actually support the conclusion.

Our recommendation is to measure the whole job: preparing the input, correcting the answer and checking the final output. An instant first draft is only useful if the checked result takes less effort. These examples are suggested exercises, not measured productivity results.

Keep up with changing features

Use the official ChatGPT changelog for announcements, then read the feature’s help page for access requirements. A release announcement can describe a gradual rollout. If a control is missing, check your account, app version and workplace permissions before changing your workflow.

For help applying this to your team’s actual work, use the workshop enquiry form on the Clearer With AI homepage.

Common questions

Do I need a paid ChatGPT plan for this exercise?

The email exercise only needs a chat that accepts text. File tools, usage allowances, connected services and other features depend on your account and workplace settings.

Can ChatGPT send the email for me?

Drafting text and sending a message are different actions. This exercise ends with you checking and sending it. Connected tools may offer actions, but require the right access and a clear instruction.

How do I know whether ChatGPT saved me time?

Compare the time needed to produce a checked, usable result, including corrections. Use the same kind of task over several attempts before judging the benefit.