Do not change your workflow at all in the first week. Keep your project tool, your meetings and your templates, and add AI to just two jobs you already do: turning a meeting transcript into decisions and action items, and drafting the weekly status update. Summarize a Meeting Transcript teaches the first one in about 9 minutes.
Those two jobs are a good start because they are frequent, they follow a pattern and you can check the output in a couple of minutes against what you heard. If AI gets something wrong, you will notice, because you were in the room.
Why start with recaps and status updates?
- They eat time every week. Writing up a meeting or chasing updates for a status report is the same work every time.
- They are low risk. The output goes to your team first, and you check it before it goes further.
- They feed your existing tools. An action items table pastes straight into Asana, Jira, Monday or a spreadsheet. Nothing new to adopt.
- They show value fast. Your team sees a cleaner recap the same day.
Save the bigger ideas, like risk forecasting or automated scheduling, for after you trust the basics.
What is the first-week plan?
Day 1: one meeting recap. After your next meeting, take the transcript from Teams, Zoom or Google Meet (or your typed notes). Ask for a short summary, the decisions, an action items table with owner and due date, and open questions. Tell it to write "Not stated" instead of guessing.
Day 2: fill the gaps and send. Add the dates nobody said out loud, ask for a short follow-up email, check every owner and date, and send it yourself.
Day 3: save the request. Keep the prompt that worked in a doc, so the next recap takes one paste. Prompt Writing 101 shows how to build it with Role, Context, Task and Format and save it as a template.
Day 4: the status update. Paste this week's task export or notes and last week's update. Ask for done, in progress, blocked and next, plus risks, in your usual template. Mark anything a vendor or another team has not confirmed in writing as "not confirmed".
Day 5: compare. Did it save time? What did you have to fix? Adjust the prompt once.
What does this look like in a real lesson?
In Summarize a Meeting Transcript you copy the transcript Google Meet saved after a bakery's Monday team meeting into ChatGPT, under a request for four things: a summary, the decisions, an action items table and open questions. Two due dates come back as Not stated. You tell ChatGPT the library quote is due Wednesday and Luis will call about the oven today, then ask for a short follow-up email to the team. Last, you start a new chat and upload the transcript as a file instead of pasting.
Run a Weekly Ops Review Where Every Task Has an Owner is the status-meeting version. Imani, operations manager at Fairline Supply Co., hands over the transcript of a review covering late deliveries, a box shortage and 140 returns. The request adds a risks to watch section and marks any vendor date that is not confirmed in writing as not confirmed, so "should be back in stock next week" never becomes a promise. You fill in two missing dates and send the team recap before lunch.
Which tools do I need?
Whatever chat assistant your company approves: ChatGPT, Claude, Copilot or Gemini all do recaps well. If your project tool has its own AI, use it too. Asana's AI summarizes status and suggests next steps inside the tool, so you may not need to copy anything out.
When you are ready to send action items straight to a task list, see how to send meeting action items to a task list. For more ideas by role, the project manager start guide and the prompts for project managers are the next stops.
What mistakes should PMs avoid?
- Sending the recap unread. Owners and dates are the part people act on. Check every one.
- Letting it guess dates. Always include "write Not stated instead of guessing".
- Turning "should" into "will". Mark unconfirmed vendor or partner dates clearly.
- Pasting confidential project details into a personal account. Use your company's approved tool, and check your rules before you share a transcript with private details.
- Rebuilding your process around AI in week one. Add it to what you do. Change the process later, if at all.
Key takeaways
- Start with two existing jobs: the meeting recap and the status update.
- Ask for a fixed set of sections and "Not stated" instead of guesses.
- Paste the action items into the tool you already use.
- Check every owner, date and vendor promise before you send.
Frequently asked questions
- Do I need an AI meeting bot to do this?
No. A transcript your meeting app already saves, or your own typed notes, is enough. A bot is optional, and some clients and teams prefer not to have one in the call.
- Can AI write my project plan?
It can draft a first plan or a work breakdown from a brief, which is useful for a start. Dependencies, estimates and who is available still need your judgment and your team's input.
- Is it safe to paste client meeting transcripts into ChatGPT?
Only into an account your company approves, ideally a business plan that does not train on your data. Remove details the recap does not need, and follow your client's confidentiality terms.