Weekly team check-in questions for a small team

Ask four to six questions, the same ones every week, and keep each answer to a line or two. A check-in is about the person rather than the task list: how the week went, how full it was, what would help and what is unclear. Pick from the list below, start with the five-question set if you are unsure, and change one question at a time once you see which answers are useful.

Open items, blockers waiting on a decision and dates belong in the weekly review, which goes through them one by one. Keeping the two apart stops the check-in from turning into a second status report.

The questions, grouped by purpose

Choose one or two from each group. More than six questions and people start answering the form rather than telling you something.

How the week went

Workload and energy

Help needed

What is unclear

Team and process

A starter set of five

If you want to start this Friday, copy these. They cover the week, workload, help and anything unclear, and leave room for anything else.

  1. What went well this week, and what took longer than expected?
  2. How full was your week, from 1 (quiet) to 5 (too much)?
  3. What would help you most next week, and from whom?
  4. Is anything unclear: who owns a piece of work, what matters most, or where to find an answer?
  5. Anything else the team should know, or anything you would like to talk about one to one?

A template you can paste anywhere

The same set works in a document, a chat thread or a spreadsheet. In a sheet, use one row per person per week and one column per question.

Weekly check-in · [your name] · week of [date]

How the week went: [one or two lines]

How full was the week (1–5): [number, and a word if you like]

What would help, and from whom: [one line]

Anything unclear: [one line, or “nothing”]

Anything else: [optional]

Run a written check-in in ten minutes

Ten minutes per person is a suggested target for a team of three to ten, not a measured result: about five minutes to write and about five to read.

  1. Fix a day, a time and a reply deadline. For example, answers by Thursday at 15:00 so they can be read on Friday morning. In a team across time zones, write the zone next to the time.
  2. Each person answers on their own, in writing. One or two lines per question. Link to the item or thread instead of retelling it.
  3. One person reads every answer. Usually the founder or whoever runs the week. While reading, they mark three things: anyone who asked for help, anything someone said is unclear, and anyone who asked to talk or rated the week as too much.
  4. Reply to every request for help the same day. Even if the reply is “I will sort this out by Tuesday”. A request that gets no answer teaches people to stop asking.
  5. Post the answers in one place. A single thread or document per week, so next week’s reader can see what was said before.

What to do with the answers

A check-in is only worth the time if something changes because of it.

After four weeks, look back. Drop any question that keeps getting “same as last week” or no answer, and replace it with one from the list above. A check-in that has stopped producing decisions or conversations is a form, and can be shortened or stopped.

When to talk instead

Writing is good for facts and short requests. Talk when a written answer shows:

Finish any conversation by writing the result back where the work lives: the decision, the owner and the date.

Check-in, review or rhythm

A weekly check-in is about the person: how the week went, how full it was, what would help and what is unclear. A weekly review is about the items: open promises, blockers, dates and goals, one by one. Many small teams do both in the same Friday slot: the check-in for the conversation, the review for the list. The weekly planning template shows where both fit in the week, and the glossary has short definitions of each. When the result has to go to someone outside the team, a manager or a client, write it up with the weekly status update template. For the short daily version about the work itself, finished, today and blockers, use the daily standup template.

Sources and method

These questions are an Opitor editorial method for small teams, not the result of a study. The ten-minute routine and the four-week look back are suggestions to adapt.

Where Opitor fits

You do not need Opitor to run a check-in: the questions work in any document, thread or form. What matters afterwards is that each decision, owner and date lands where the team keeps its work. For what Opitor itself covers, see the FAQ.

Start with one real project.

Choose a project your team is already working on. Open a channel, invite a teammate, and capture the next commitment as a to-do.

Join Opitor