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
- What went well this week?
- What took longer than you expected, and why?
- What is one thing you are pleased with?
Workload and energy
- How full was your week, from 1 (quiet) to 5 (too much)?
- What took more energy than it should have?
- Does next week look lighter or heavier than this one?
Help needed
- What would help you most next week, and from whom?
- Is there something you have been meaning to ask for and have not?
- Is there anything you would like to talk about one to one?
What is unclear
- Is there any work you are not sure is yours?
- Was there a question you could not find an answer to?
- Did two people ask you for different things, or is a priority unclear?
Team and process
- What should we stop, start or keep doing?
- Who helped you this week?
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.
- What went well this week, and what took longer than expected?
- How full was your week, from 1 (quiet) to 5 (too much)?
- What would help you most next week, and from whom?
- Is anything unclear: who owns a piece of work, what matters most, or where to find an answer?
- 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.
- 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.
- Each person answers on their own, in writing. One or two lines per question. Link to the item or thread instead of retelling it.
- 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.
- 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.
- 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.
- A request for help gets a name and a day. Who will help, and when. If the help needed is really a decision on a blocked item, take it to the weekly review, which has a decision-request template.
- Something unclear gets answered where everyone can see it. If nobody is sure who owns a piece of work, settle it and write the owner on the item. If the team has no shared list yet, set one up first.
- A workload signal gets a private reply. If someone rates the week as too much twice in a row, talk to them on their own, not in the thread. Agree what to drop or move.
- A process idea goes on a short list. Pick one to try each month rather than changing everything at once.
- Next week starts with last week. Before reading new answers, check whether last week’s requests for help were answered.
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:
- A disagreement. Two people want different things, or one disagrees with a decision. A thread hardens positions; a short call usually settles it.
- Something personal or sensitive. Health, conflict with a colleague, or anything said in confidence. Move it to a private conversation and leave it out of the shared answers; what direct messages and groups are each for covers where it belongs.
- Several decisions that depend on each other. When answering one changes the next, get the people who decide in one conversation.
- Answers getting shorter and vaguer. It can mean the questions have gone stale or something is wrong. Ask, one to one.
- A new person in their first weeks. Read their written answers, and talk to them as well.
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.