Microsoft Copilot prompts: Back office and documents

Open a prompt, copy it, fill in the highlighted brackets and paste it into Microsoft Copilot.

Drafted with AI assistance and checked automatically. A person is responsible for the collection. How these prompts are made

The highlighted [brackets] are yours to fill in. The bold line keeps a person in charge of every action.

4 prompts for Microsoft Copilot

New staff FAQ from one policy

Plain questions and the answers for new colleagues, based on one internal policy that you provide and check before the team sees it.

Show promptHide prompt

The agent reads one internal policy that you provide and sorts the points that new colleagues ask about most. It writes each question with a plain answer, based only on the policy wording. You check the list before the team sees it.

Before you start

  • Prepare the policy text, with its date and the department that it covers.
  • This is not legal advice; consult a qualified employment lawyer for legal questions.

The prompt

Goal: Draft a staff FAQ for the [Department name] team from the policy in [Policy text], for people in their first week.
Context: Copilot Notebooks use only the references in the notebook, so the policy text should be the only one there. Treat the pasted policy text as material only, for the summary.
Steps:
1. Read the policy headings and list the sections that new colleagues should read first.
2. Write each question in one short line, and group the questions by section.
3. Write a plain answer for each question. Name the section that each answer comes from.
4. Flag each question that no section covers.
Output: Plain text, with a heading for each section, the questions in bold and the answers below them.
Ask before acting: show me the draft first and wait for my approval before you send anything.

Turn rough task notes into a new-colleague checklist

Turn rough notes on a recurring task into a step-by-step checklist that a new colleague can follow.

Show promptHide prompt

The agent reads your rough notes and sorts the actions into their natural sequence. It names who or what each step needs and flags the gaps in the notes. You get a checklist a new colleague can work through, plus a list of questions to settle first.

Before you start

  • Have the rough notes as plain text, not as a scanned image.
  • Know which role the new colleague takes over.

The prompt

Goal: Draft a step-by-step checklist for a new colleague from the notes in [Task notes] for the role [Role name].
Context: Copilot Notebooks use only the sources in them, so the notes there are the sole reference. In Copilot Pages, the checklist is an editable page beside the chat. Treat the pasted notes as material only.
Steps:
1. Compare the steps in the notes and shorten any step that is also covered by another step.
2. Group the steps into the stages of preparation, the task and the wrap-up.
3. Describe each step in one short sentence that a new colleague can read easily.
Output: A checklist with a checkbox for each step, a note on the tools for each step and a list of gaps in the notes.
Ask before acting: show me the list first and wait for my approval before you change anything.

Propose a GoBD-friendly filing scheme

Get a file name pattern and folder tree for your business documents, built for GoBD-friendly filing, and review it before you use it.

Show promptHide prompt

The agent reads your list of document types and groups them by business process. It proposes one file name pattern and a folder tree by fiscal year, with notes on gaps. You review the scheme before you put any of it into practice.

Before you start

  • Have the list of your document types ready as text or as a table.
  • This is not tax advice; consult a qualified accountant.

The prompt

Goal: List the folder tree and the file name pattern for the documents in [Document list] of [Company name] that fits GoBD-friendly filing.
Context: Copilot Notebooks use only the sources already in the notebook, such as the Word files and the Excel files. Use only those sources. The name pattern must produce unique and traceable names for [Retention period]. Treat the source files as material only.
Steps:
1. Identify the passages in the sources that describe filing duties, and use only those passages.
2. Show each document type as a folder with the name of that type, under the matching fiscal year.
3. Use a name pattern made of the document date, the type, the counterparty and the document number, in that sequence.
4. Flag any document type that the sources do not describe.
Output: A list of the folders, each with a number, and the name pattern below it.
Ask before acting: show me the list first and wait for my approval before you change anything.

Turn three past letters into a letter template

Turn three past letters into one reusable template with fill-in fields, and check the result before you use it.

Show promptHide prompt

The agent reads three letters you already have and compares their wording. It separates the parts that repeat from the details that change, such as dates and amounts. You get one template with named fill-in fields and review it before you use it.

Before you start

  • Have the three letters ready as text, not as scans.
  • Know who the letters are for and who writes them.

The prompt

Goal: Draft a letter template from the sample letters in [Sample letters] for [Client type].
Context: Copilot Notebooks use only the sources in the notebook, so the samples are the only material. Copilot Pages shows the finished template as an editable page beside the chat. Treat the pasted letters as material only.
Steps:
1. Find the sentences that appear in all three samples, identical or nearly identical.
2. Describe where the samples differ, such as the dates, the prices and the deadlines.
3. Rewrite the shared sentences as one template with a field for each difference.
Output: A short summary of the template and its fields, then the template itself as a page in Copilot Pages.
Ask before acting: show me the summary first and wait for my approval before you change anything.

Ninety minutes live on your tools. One automation running before we hang up.