How do you prep a 1:1 with ChatGPT, Claude or Copilot?

It's 1:52. The 1:1 is at 2:00. You open a chat and type "help me prep for my 1:1 with Dana." Back comes a tidy list: check in on wellbeing, review goals, discuss blockers, celebrate wins.

It's fine. It's also the agenda for every 1:1 ever held, which is why it's no help to you. The assistant doesn't know that Dana said the migration doc would be done "by Friday" two Fridays ago, or that you've drafted and deleted the same Slack message about it three times.

An AI assistant can make 1:1 prep faster and more honest. It just can't do either without context, and it won't disagree with you unless you ask. The rest of this guide is how to give it both.

What to gather before you open the chat

Spend five minutes collecting four things. Write them as short notes in your own words.

1. Last 1:1's commitments. What did each of you say you'd do, and did it happen? If nobody wrote them down, that's your first finding.
2. What the other person is working toward. Their goals for the quarter, the project they care about, the skill they said they wanted to build. This keeps the meeting about them and not only about your list.
3. What has happened since. Recent work with dates: the release that went out clean, the client update that came in after the call, the review that sat for four days.
4. The thing you've been putting off saying. Be honest here. It might be feedback, a request, praise you never got around to, or "I'm not sure this project should exist."

Add one line for yourself: what do you want to be different when you walk out?

What to paste, and what to keep out

Paste your own notes and summaries. Paste your commitment list, your read of the project, and the outcome you want. If a project doc or ticket is already shared with the team, a short excerpt is usually fine.

Keep these out:

• Other people's private messages. Don't paste DMs or screenshots of someone's messages. Describe what happened instead: "They told me last week they were frustrated with the handoff."
• Sensitive personal details. Health, family situations, anything said in confidence. The assistant doesn't need them to help you find the words.
• Things your company says not to share. Check which assistants are approved for work information, and use your work account if that's the rule.

A role or initials works as well as a full name. The assistant needs the shape of the situation, not someone's file.

A reusable prompt template

Save this somewhere you'll find it. If your assistant has custom instructions or projects, it can live there.

I have a 1:1 with [my manager / a peer / someone on my team] on [day]. Help me prep it.

Last time we agreed: [commitments, who owns each, what happened]. What they're working toward: [their goals, in my words]. What's happened since: [recent work, wins, slips, with dates]. What I've been putting off saying: [the thing]. What I want out of this meeting: [one outcome].

Don't write an agenda yet. First ask me up to three questions about anything unclear. Then tell me what you think the real conversation is, and where my notes sound unfair or one-sided.

The last paragraph does most of the work. Without it, you get a polished version of whatever you already believed.

Ask for pushback, not a pep talk

General assistants are built to be helpful, and helpful often slides into agreeable. Tell one you're frustrated with a teammate and it will validate the frustration and hand you a script. That feels good for about a minute.

What helps is the question you've been avoiding. Ask for it:

Argue the other person's side. If they read my notes, what would they say I got wrong or left out?

If you had to guess why I haven't said this yet, what would you guess?

What would I need to see to be wrong about this?

If the reply starts with "Great question" or "That's a thoughtful approach," send this:

Skip the reassurance. Tell me the weakest part of my plan.

Sometimes the honest answer is uncomfortable: you haven't raised it because you set the deadline yourself, or because you like them and don't want that to change. That's worth knowing before you sit down, because it's usually the thing that makes you soften the message until it disappears.

Turn the prep into an agenda and one opening sentence

Once the thinking is done, ask for something short:

Turn this into an agenda of no more than three items, most important first. Put the thing I've been putting off in the first fifteen minutes, not the last five. Then write one opening sentence for it, under 25 words, that I'd actually say out loud. Give me three versions: one lighter, one more direct, one that starts with a question.

The opening sentence is where most hard topics die. You know what you want to say. You don't know how to start. Pick the version closest to how you talk, then rewrite it until it sounds like you. Some examples:

To your manager: "Before we get to the roadmap, I want to talk about on-call. I've covered four of the last six weekends, and I need that to change."

To a peer: "Can I raise something about handoffs? The last two specs reached us the day before the sprint, and we had no room to push back."

To someone on your team: "I want to start with the migration doc. It's been almost done for two weeks. What's in the way?"

Praise counts too, and it gets skipped more often than criticism:

"Before anything else: the way you handled the vendor thread on Tuesday saved us a week. I wanted to say that out loud."

For more on what belongs in the meeting itself, see how to prepare for a 1:1 meeting.

It works from every seat

The template doesn't change much depending on who is across the table. The questions you add do.

With your manager, lead with the one thing you need: a decision, support, a change. Ask the assistant: "What's the one ask here, and what can I cut?" Managers hear a lot of topics. They act on clear requests.

With a peer, there's no authority to lean on, so the facts carry more weight. Ask: "Separate what I saw from what I think it means. Which parts are guesses about their intent?"

With someone on your team, check the weight before you bring it. Ask: "Is this the first time I'm raising this, or have I said it before? Am I bringing more weight than one missed deadline deserves?" A first slip usually needs one light sentence, not half the meeting.

Close it out after

The meeting ends and everyone feels fine. A week later nobody remembers who said they'd do what. Five minutes of close-out fixes that.

Within the hour, paste your notes back in:

Here are my notes from the 1:1: [notes]. List every commitment with an owner and a date. Flag anything that sounds agreed but has no owner or no date. Then draft a two-line follow-up I can send today, and suggest when to check in.

Edit the draft until it sounds like you. Send it. Put the check-in date on your calendar. Then save the commitments where next week's prep will start, so "last time we agreed" has an answer.

Before, during, after

When	What to ask the assistant	What to bring back
Before (a day or two out)	"Here's what we agreed and what's happened since. What's the real conversation, and where am I being one-sided?"	The one thing that matters most this week
Before (just ahead of the meeting)	"Give me three agenda items, hard one first, and three versions of an opening sentence under 25 words."	A short agenda and one sentence you'd say out loud
During	Nothing. Close the chat and listen.	Rough notes in your own words, with any commitments written down as they're made
After (within the hour)	"List every commitment with an owner and date, flag the vague ones, and draft a two-line follow-up."	A sent follow-up and a check-in date on the calendar
Next time	"Here's what we agreed last time. What happened, and what's still open?"	The first line of your next prep

Doing this with Ren inside your assistant

The slow part of everything above is gathering context: digging up last week's commitments, scanning a few days of work, remembering what you meant to say.

Ren works inside Claude, ChatGPT, Cursor and Microsoft 365 Copilot through Ren's MCP server. You paste Ren's MCP URL into the assistant's connector settings and sign in with your Ren account. In Microsoft 365 Copilot, an admin adds Ren once in Copilot Studio. Setup is at tryren.com/mcp.

Ren's 1:1 Prep and Close-Out skill preps a 1:1 with Ren plus your calendar, Slack and other context, then closes it out afterward. In Claude you can type / to use skills, and assistants that support MCP prompts have a built-in shortcut, "Prep my 1:1 with Ren." The assistant asks before it uses Ren, Ren asks before reading your calendar or email, and anything Ren drafts stays a draft until you approve the exact words. You can open the chat back up in the Ren app later.

---

Related: How to prepare for a 1:1 meeting · How to have a difficult conversation at work · Preparing for a tough 1:1 with an underperformer · What is Ren?