← The Clair Blog

    What to actually use ChatGPT for: the first five jobs to hand over

    Not fifty use cases, five recurring jobs that eat a working week, and what handing each one over actually looks like on an ordinary Tuesday.

    A note before the list. These five were chosen because they depend on nothing that changes between model updates, just the tool doing what it has always done well, so they hold in ChatGPT, Claude or Gemini alike.

    The lists of fifty amazing ChatGPT use cases have a way of describing someone else's life, half of them written for developers and the rest for people who apparently spend their days generating logos. Meanwhile your actual Tuesday sits there untouched, made of meeting notes you have not typed up, a chase you owe someone, and a thirty-page report you were sent "for visibility" and have been avoiding since.

    So this is a different kind of list, built from the ordinary Tuesday rather than the demo reel. Five recurring jobs that eat a working week, each one delegable today, chosen because they come around constantly, the tool is genuinely good at them, and you review the output anyway, which means a small error costs you seconds rather than credibility.

    Start with the recurring word-jobs already passing across your desk. Turning meeting notes into actions and a recap, drafting the emails you write on repeat, shrinking long documents into the version you can hold in your head, tidying messy text into structure, and getting a plain-English briefing on something before you have to sit in a meeting about it. Hand those five over with a sentence or two of context each, keep your eyes on what comes back, and the tool starts returning actual evenings.

    The five, and what handing them over looks like

    The handover itself is unglamorous in every case. You paste the raw material, say what you want back and who it is for, and read the result before it goes anywhere. That is the same arrangement you would have with a sharp assistant, and it carries the same rule: they draft, you decide.

    The job What you hand over What comes back
    Meeting notes into actions The raw notes or transcript, with a request for decisions, actions with owners and deadlines, and a short recap for attendees The 5pm typing-up job done in two minutes, with nothing lost to your handwriting giving up in minute forty
    The emails you write on repeat The situation and the tone you want, for the chases, status updates and polite declines that recur weekly A solid draft to edit for thirty seconds instead of compose for ten minutes, so the tenth chase of the month stops costing anything
    Long document into the version you can repeat The thirty-page report, with a request for the summary, the three things someone in your role needs, and the question worth asking about it The ability to walk into the meeting having read the thing without having read the thing
    Messy text into structure The bullet soup, the rambling transcript, the twelve scattered thoughts, with a request for headings and anything contradictory flagged A coherent shape for material you would otherwise have wrestled by hand, a job most people never realised was delegable
    The briefing before the meeting The concept you half-know, with a request for a plain-English explanation, the questions people usually ask, and what a sceptic would say Five minutes of preparation that replaces an hour of nodding along, and nobody has to know you asked

    The relief in each row comes from the same place. None of these jobs was ever the interesting part of your work, they were the connective tissue around it, and connective tissue is precisely what delegates well.

    The pattern, so you can spot the sixth

    Look at what the five share and you have the test for everything else on your desk. They recur, so the minutes saved compound weekly rather than once. They are made of words rather than exact numbers, which is the tool's home ground.

    And they pass under your eyes before going anywhere, so the occasional wrong detail gets caught in the review you were doing regardless. Any job with those three properties is a candidate, and any job missing them deserves more thought before it gets handed over, particularly where a wrong figure could travel.

    Where the line sits

    The same tool that shines on these five is unreliable with calculations, current facts you plan to quote, and anything confidential on the standard version. There is a companion piece on the jobs to keep off it entirely, and one on the tasks where AI is honestly slower than your own hands.

    Between the three sits the whole judgement, and it is less complicated than it sounds. Hand over the recurring word-work, keep your name on the checking, and let the tool earn the tab it has been occupying all this time.

    Not sure where to start?

    Five jobs, and the right tool for each one.

    The free finder tells you which AI to open for the task in front of you, in about 60 seconds, and the full "AI, sorted." reference lands in your inbox.

    Try the free finder →

    One question in, one answer out.


    Clair helps non-technical professionals know when to trust their AI, when to check it, and when to skip it.

    Common questions

    What should I use ChatGPT for at work?

    Start with the recurring word-jobs you already review anyway: turning meeting notes into actions and a recap, drafting repeat emails like chases and status updates, summarising long documents, restructuring messy notes, and getting a plain-English briefing before meetings. They recur weekly, the tool is genuinely good at them, and your normal review catches any small error.

    What is ChatGPT actually best at?

    Language work: drafting, summarising, restructuring and explaining. It is weakest where a single exact answer exists that it might not have, so precise calculations, current facts you plan to quote, and anything confidential on the standard version should stay off it or get checked properly.

    What tasks should I give AI first?

    Ones that recur, are made of words rather than exact numbers, and pass under your eyes before going anywhere. That combination means the time saved compounds every week and errors get caught in the review you were already doing, which makes those jobs the lowest-risk place to begin.

    Is it worth using ChatGPT for emails?

    For the recurring ones, very much so, since a chase or status update goes from ten minutes of composing to thirty seconds of editing. Delicate or high-stakes emails deserve a first draft at most, rewritten in your own voice, because your name carries the consequences.

    What should I not use ChatGPT for?

    Exact maths, current facts you will repeat as true, confidential or client material on the consumer version, final legal or financial decisions, and any topic you could not check yourself. It answers with the same confidence whether or not it is right, so the jobs where a wrong answer is expensive and hard to spot stay yours.

    The AI Starter Kit

    Set up ChatGPT and Claude properly. Once.

    The workflows, rules and habits that hand the boring recurring work to your AI and give you your evenings back.

    Get the Kit →