AI at Work

10 Claude prompts for office work that actually save time

Ten prompts cover the office work that comes round every week: meeting notes to actions, replies in house tone, contract version comparisons, monthly report summaries, tender answers, spreadsheet data checks, plain-English policy rewrites, onboarding checklists, client letters and briefing notes. Each one gives Claude the source material, the audience and the limits, and tells it to flag gaps rather than guess. What you check afterwards matters as much as the prompt: figures, commitments and anything Claude says a document contains.

Before you use them

Each prompt below follows the same pattern: the material Claude should work from, who the result is for, the limits it must keep to and what to do when the material runs out. Replace the square brackets with your own details. The examples are fictional.

Give Claude the actual documents, by upload or through the Microsoft 365 connector, rather than describing them. Read the answer as a first draft from a capable colleague who has not seen the file before.

1. Turn meeting notes into actions

Prompt: Here are my notes from today's project meeting. List every action in a table with the owner, the due date and the sentence in the notes it comes from. If an action has no owner or no date, say so rather than guessing. Then list the decisions made and any open questions.

  • Give Claude: the notes or transcript, and the list of who attended.
  • Check: that each action traces back to the notes, and that the owners agreed to them in the room.

2. Draft a reply in house tone

Prompt: Draft a reply to the email below. Use our house style: short paragraphs, plain English, Irish spelling and 'Kind regards' as the sign-off. Keep it under 150 words. Answer the two questions she asks and do not promise a delivery date. Here is a reply we sent last month that shows our tone: [paste].

  • Give Claude: the incoming email, one good past reply and the facts the answer depends on.
  • Check: every fact and date, and that the draft makes no commitment you have not agreed. You send it from your own mailbox.

3. Compare two versions of a contract

Prompt: Compare version 3 and version 4 of this supply agreement. List every change in a table: clause number, old wording, new wording and what the change means in plain English. Put changes to price, liability, termination and notice periods first. Do not give legal advice; mark anything a solicitor should review.

  • Give Claude: both versions as files, not pasted extracts.
  • Check: open each listed clause in both versions, and look at schedules and definitions yourself, since a missed change there can matter most. Legal judgement stays with your solicitor.

4. Summarise the monthly report

Prompt: Summarise this month's management report for the board in no more than 250 words. Lead with the three figures that moved most against last month and give the reason the report states for each. List anything the report says is behind plan. Quote figures exactly as they appear, with the page number.

  • Give Claude: the full report, and last month's if the comparison is not in it.
  • Check: each figure against the page cited, and whether a stated reason is really in the report or has been inferred.

5. Draft a tender answer

Prompt: Draft an answer to tender question 4.2 below, within the 500-word limit. Use only the project examples and policies in the attached documents and name the document behind each claim. Where the question asks for something our documents do not cover, write [GAP] and say what is missing.

  • Give Claude: the question and scoring criteria, plus the approved project sheets and policies.
  • Check: that every claim matches its source, that the [GAP] markers are resolved by the bid owner and that the word count is within the limit.

For the evidence work behind tender answers, see check the evidence before drafting the tender.

6. Check a spreadsheet before you use it

Prompt: Check this customer list before we import it. Look for duplicate customers, missing Eircodes, email addresses that look wrong and VAT numbers that do not follow the usual Irish format. Give me a table of the rows with problems, the row number and the reason. Do not change the file.

  • Give Claude: the file itself, with column headings intact.
  • Check: a sample of the flagged rows and a few unflagged ones, and the total row count against the file.

7. Rewrite a policy in plain English

Prompt: Rewrite this remote working policy in plain English for staff. Keep every rule and every number of days, but cut the legal phrasing and use short sentences. Add a short 'What this means for you' section at the top. List anything you could not simplify without changing the meaning.

  • Give Claude: the current approved policy.
  • Check: rule by rule against the original. The policy owner signs off the new version before it goes to staff.

8. Build an onboarding checklist

Prompt: Using the attached staff handbook and IT setup note, build a first-week onboarding checklist for a new accounts assistant. Group it by day and say who is responsible for each item: manager, IT, payroll or the new starter. Mark any step the documents do not explain.

  • Give Claude: the handbook, the IT note and the role description.
  • Check: that the documents are current, that system access matches the role and that every unexplained step has an owner.

9. Write a client letter

Prompt: Draft a letter telling a client that their annual fee will rise by 4% from 1 January. Give the two reasons in our notes below and keep it to one page, warm but direct. Do not apologise for the increase and do not mention discounts.

  • Give Claude: the notes, the client's current fee and a past letter in your style.
  • Check: the percentage, the new amount and the date, then put the letter on your own letterhead in your document system.

10. Prepare a briefing note

Prompt: Write a one-page briefing note for our managing director before Thursday's meeting with a new supplier, using the attached emails and proposal. Include who they are, what they propose, the price as stated, three questions to ask and any points where the emails and the proposal disagree.

  • Give Claude: the email thread and the proposal.
  • Check: the price and dates against the proposal, and each disagreement Claude lists, since those are often the most useful part.

Make the good ones reusable

Once a prompt works, save it where the team can reuse it. A shared project holds the instructions and reference documents for a recurring job. A skill packages the steps so Claude applies them whenever the task comes up.

How a team builds and shares one is in Claude skills: a guide for business teams.

Practise on your own work

Prompts like these work best when people try them on their own recurring tasks and compare the result with how they do the job now. That is the core of our sessions.

See Claude training in Ireland for formats and what people take away.

Common questions

What makes a good Claude prompt for office work?

The source material, the audience, the length or format, the limits Claude must keep to, and an instruction to flag gaps rather than fill them. A prompt with those five parts usually needs less rework than a short request.

Can I use these prompts with client documents?

Use them on a business Claude plan, such as Team or Enterprise, under your firm's own policy on client data. Avoid personal accounts for client work.

Should we save prompts somewhere shared?

Yes. Put a working prompt in a shared project or turn it into a skill, so the whole team uses the same tested version.

For help putting this into practice, see Claude implementation and training for Irish businesses.

Editorial guidance informed by Acuity's work with teams. Examples are fictional and client materials stay private. To record who owns an AI use and when it is reviewed, see AI Register.