You have been running weekly check-ins for months. Every Monday, the team gathers on a call and you ask how things are going. "Good," says the backend engineer. "Fine," says the designer. "Making progress," says the PM. The meeting ends and you know almost exactly as much as you did before it started. The questions you are asking are producing polished, low-information answers that sound professional but tell you nothing.

The problem is not that your team is hiding information. It is that your weekly team check-in questions are designed to produce exactly this kind of empty response.

Why Most Weekly Team Check-In Questions Fail

The default check-in question — "How's everything going?" or "Any updates?" — is too broad and too casual to generate useful answers. It invites a social response, not a substantive one. When you ask "how are things going," people give you the answer that ends the conversation fastest: "good."

Effective weekly team check-in questions are specific enough to require a real answer but open enough to capture the unexpected. They should make it easier to tell you the truth than to deflect.

The Specificity Problem

"What are you working on?" can be answered with "the usual stuff." But "What is the most important thing you need to finish this week, and are you on track?" requires a concrete commitment. The first question accepts vagueness. The second demands specificity.

The Safety Problem

Many check-in questions unintentionally penalize honesty. "Is everything on schedule?" pressures people to say yes. "What's at risk this week?" gives them permission to flag problems. The framing of your questions determines whether you hear about problems before or after they blow up.

According to research from Google's Project Aristotle, psychological safety is the single most important factor in effective teams. Your check-in questions either build that safety or erode it.

The Best Weekly Team Check-In Questions

Here are questions organized by what they surface. You do not need to use all of them — pick three to five that match your team's needs.

Progress and Priorities

These questions clarify what actually happened and what is coming next.

What did you accomplish this week that you're most satisfied with? This frames progress positively and encourages people to highlight meaningful work, not just busywork.
What is your number one priority for next week? Forces prioritization. If someone lists five things, they have not actually prioritized.
Is there anything you planned to finish this week but didn't? What got in the way? Surfaces delays and their causes without judgment.

Blockers and Dependencies

These questions catch problems before they escalate.

What is the biggest thing slowing you down right now? "Biggest" forces a choice instead of a generic "nothing really."
Are you waiting on anyone or anything to make progress? Dependency chains are invisible until someone names them. This question makes them visible.
Is there a decision you need from me or from leadership to move forward? Many teams stall because a decision is sitting in someone's inbox. This question surfaces those bottlenecks.

Workload and Wellbeing

These questions protect your team from burnout and overcommitment.

On a scale of 1-5, how manageable is your workload this week? A numerical scale is easier to answer honestly than "are you overwhelmed?" and lets you track trends over time.
Is there anything on your plate that you think should be deprioritized or delegated? Gives people permission to push back on scope without feeling like they are complaining.
What is one thing that would make next week better than this week? Open-ended but forward-looking. You will be surprised what people share when given a constructive framing.

Team Dynamics and Communication

These questions surface process problems and collaboration issues.

Did you have all the context and information you needed to do your work this week? Information gaps cause rework. This question catches them early.
Is there anyone on the team you need to collaborate with but haven't been able to connect with? Remote teams develop communication silos. This question identifies them.
What is one thing our team does well that we should keep doing? Balances problem-focused questions with reinforcement of what is working.

How to Structure Your Weekly Check-In

The best weekly check-ins use three to five questions max. More than that and response quality drops because people rush through them.

Here is a template that works for most teams:

What did you accomplish this week? (2-3 bullet points)
What is your top priority for next week? (1-2 items)
Any blockers, risks, or things you need help with?
Workload check: 1 (light) to 5 (overwhelmed)?
Anything else the team or I should know?

That takes about five minutes to answer thoughtfully and gives a manager everything they need: progress, direction, problems, and a wellbeing signal.

For teams that also run daily check-ins, the weekly version should be higher-level. Daily questions focus on "what did you do today." Weekly questions should focus on "what matters this week, where are we, and how are you doing." We explored the daily format in depth in our post on standup questions for engineering teams.

The Delivery Problem: Meetings vs. Async

Here is where most teams stumble. They have great questions but a terrible delivery format.

The Meeting Approach

You schedule a weekly call where everyone answers the questions verbally. With eight people, each taking three to five minutes, the meeting runs 25 to 40 minutes. Half the team zones out while others talk. The answers are not recorded. By Tuesday, nobody remembers what was said. And you have burned 40 minutes of everyone's week on a meeting that was really just a round-robin report.

The Shared Doc Approach

You create a Google Doc or Notion page with the questions. People fill it out during the week. Except some people forget. Others fill it out Monday and do not update it. The doc becomes a messy patchwork of partial updates with no clear timeline of when things were written. Compliance drops below 60% within a month.

The Slack Channel Approach

You post the questions in a Slack channel every Monday. Responses come in over the course of the day, interspersed with other channel messages. Some people respond in threads, some in the main channel. By Tuesday, the responses are buried. Searching for them later is a nightmare.

We covered why Slack falls short for structured updates in our post on Slack standup bot alternatives. The short version: Slack is built for conversation, not collection.

The Async Check-In Approach

This is what actually works at scale. A tool sends the questions to each team member at a scheduled time — say, Friday at 3 PM in their timezone. They reply directly from their email inbox. All responses land on a single dashboard, organized by person and date.

Zlorex handles this end to end. You configure your weekly check-in questions, set the cadence to weekly, and pick the day and time. Each person gets an email, replies inline, and you see every response on one screen Monday morning. No meeting required. No separate app for your team to log into. No chasing non-responders — Zlorex sends automatic reminders.

The difference in sustained compliance is dramatic. Email replies have a near-zero friction barrier. People who ignore a Slack channel or forget to update a doc will still reply to a direct email prompt because it is sitting in their inbox waiting for a response.

Before and After: Weekly Check-Ins That Work

Before: Marcus runs a weekly team meeting every Monday at 10 AM for his eight-person product team. He asks check-in questions verbally. The meeting takes 35 minutes. Two engineers in different timezones dial in at inconvenient hours. The conversation drifts off-topic frequently. Marcus takes notes but they are incomplete. By Wednesday, he has forgotten half of what was discussed and DMs three people for clarification.

After: Marcus sets up a weekly Friday check-in through Zlorex with five questions. Each team member responds on Friday afternoon in their own timezone — takes about five minutes each. Monday morning, Marcus opens the dashboard, reads all eight responses in twelve minutes, and immediately follows up on two blockers via short messages. The Monday meeting is eliminated. The team reclaims 35 minutes per person per week, and Marcus has better information than he ever got from the meeting.

Over a quarter, that is roughly 75 hours of meeting time eliminated for the team. The quality of information went up. The time investment went down. Nobody asked for the meeting back.

Tips for Getting Better Answers

Even with the right questions and the right delivery format, a few practices make a meaningful difference.

Rotate One Question Monthly

Keep your core three questions stable but swap in a new fourth or fifth question each month. "What process would you change if you could?" one month. "What skill do you wish you had more time to develop?" the next. This keeps the check-in from feeling stale and occasionally surfaces insights you would never have gotten otherwise.

Share a Summary Back

After reading everyone's check-in, send the team a brief summary: key wins, active blockers being addressed, and priorities for the week. This closes the loop and shows the team their input is being synthesized, not just collected. It also helps with cross-team awareness — people learn what others are working on without having to read every individual response.

Act on Blockers Fast

If someone reports a blocker on Friday and you don't address it until the following Thursday, you have taught the team that check-ins are performative. Respond to blockers within 24 hours, even if the response is "I see this and I'm working on it." Speed of response is the single biggest driver of check-in quality over time.

Don't Over-Question

Five questions max. Really. If you want more information, ask it in a one-on-one. The weekly check-in should take five minutes to complete and five minutes to read per person. Anything more and you are building a reporting burden, not a communication habit.

Conclusion

The right weekly team check-in questions do three things: they surface real progress instead of vague reassurances, they catch blockers and risks before they derail the week, and they give you a signal on team health and workload. Combine specific, well-framed questions with an async delivery format that eliminates the meeting overhead, and you have a weekly rhythm that gives you genuine visibility without consuming your team's time.

Ask better questions. Collect the answers asynchronously. Act on what you learn. That is the entire formula.

Are your weekly check-ins producing "everything's fine" answers that tell you nothing? The right questions delivered the right way change everything about team visibility.

Zlorex solves this. You create one update, your team responds from their inbox, and you see everything in one dashboard. No meetings, no follow-ups, no chasing.

Explore Zlorex. Free for up to 5 team members →