Weekly Check-In: A Practical Guide for Small Business
Weekly check-ins for small business: 15-25 min structure, question banks, cadence decisions, common mistakes, and how they differ from 1:1 meetings.
Weekly Check-In
A practical guide for small business managers
The first time I introduced weekly check-ins at a company I was running, I made the mistake almost every founder makes. I scheduled 60-minute meetings with each direct report, called them check-ins, and ran them like miniature performance reviews. Within four weeks, two of my direct reports had quietly stopped preparing for them, one was dreading them on the calendar, and I was getting the kind of cautious, polished updates that signal an employee has stopped trusting the conversation.
The fix took me another three months to figure out: weekly check-ins are not 1:1 meetings, they are not performance reviews, and they should not be 60 minutes. They are short, structured, status-focused conversations that produce alignment without producing meeting fatigue.
Most advice on weekly check-ins falls into two camps. Vendor articles treat the check-in as a feature of their performance management software, so they focus on the tool more than the practice. Generic management articles offer abstract advice (be a good listener, ask open-ended questions) without a specific structure you can actually run with a small team. Both miss the operational reality: in a small business, the founder or owner usually runs these check-ins personally and needs a clear 15-25 minute structure that works without enterprise tooling.
This guide is for small business owners and managers who want weekly check-ins to work as a practical management tool, not as another corporate ritual that produces meetings nobody finds useful. You will get the honest distinction between weekly check-ins and 1:1 meetings (most articles confuse them), the 15-25 minute structure with five segments, question banks for six different contexts, cadence decisions for different employee situations, the template structure that produces useful written records, advice for first-time managers, and the common mistakes that turn check-ins into status reports. I built FirstHR for this audience because most performance management content assumes a level of organizational sophistication small businesses do not have.
What a Weekly Check-In Actually Is
Put simply, a weekly check-in answers four questions every week. What happened? What is in the way? What comes next? What do you need from me? The answers come from the employee; the manager listens, asks clarifying questions, surfaces context where useful, and commits to specific follow-ups. The whole conversation should fit in 15-25 minutes; longer than that usually means the conversation has drifted into 1:1 territory.
Three things are true about every weekly check-in that produces useful results. First, the cadence is consistent. Skipping weeks erodes the practice faster than reducing the duration; once check-ins become optional, employees stop preparing and the conversation loses its productive structure.
Second, the employee drives the agenda. Check-ins run by the manager turn into directive sessions, while check-ins driven by the employee surface the information the manager actually needs. Third, the conversation produces a written record. Without written priorities and commitments, check-ins become conversations that everyone forgets within days.
Most check-in failures happen because at least one of these three is missing. The cadence breaks. The manager talks too much. Or no notes get taken. Each missing piece takes a large bite out of what the practice is worth; missing all three produces what most teams call "check-ins that did not work."
Weekly Check-Ins vs 1:1 Meetings
The most common confusion on this topic is between weekly check-ins and 1:1 meetings. Many articles treat them as synonyms or use the terms interchangeably; they are different practices serving different purposes, and combining them produces meetings that fail at both.
In short, weekly check-ins are operational and 1:1s are developmental. Check-ins keep work flowing; 1:1s build the relationship and the career. Both matter, and they need different cadences and different conversation structures. The strongest setup for a small business: run weekly check-ins as the operational rhythm, plus separate biweekly or monthly 1:1s for development conversations.
Some small teams successfully run only weekly check-ins, but they usually do so by intentionally extending one check-in per month to cover broader development topics. This is a reasonable simplification when calendar time is tight; it works less well as the team grows and development conversations need their own dedicated space.
Why Weekly Check-Ins Look Different for Small Business
Most weekly check-in articles are written for enterprise companies with formal performance management infrastructure, dedicated HR teams, and check-in software. The frameworks assume that someone other than the manager is providing structure, prompts, and accountability. None of that applies at small business scale, where the founder or owner is usually running check-ins themselves without supporting infrastructure.
Three implications for small business check-ins. First, the practice has to be self-sustaining. There is no HR team reminding the manager to run check-ins, no software prompting the employee to fill out a form. The cadence depends entirely on the manager's discipline, so build the practice into a calendar block that is harder to skip than to keep.
Second, the founder is usually doing more check-ins than they think. A founder with 8 direct reports doing weekly 25-minute check-ins is committing 3+ hours per week to this practice. Treat that time as one of the most important blocks on the calendar, not as overhead to be optimized away. Founders who compress check-ins below 15 minutes or skip them under deadline pressure usually pay for it later: in retention, in alignment, and in problems that surface too late.
Third, the relationship density is higher. In a small business, the founder's check-ins shape most employees' direct working relationship with leadership. A bad check-in pattern affects a large share of the team; a strong pattern compounds across the whole company. That effect cuts both ways.
The 15-25 Minute Check-In Structure
The structure below produces useful check-ins consistently. It fits in 15-25 minutes and surfaces the information that matters most: status, blockers, and alignment for next week. Skip a segment or let one run long, and the check-in gets weaker.
Two rules for running the structure. First, the time allocations are guidelines, not deadlines. If blockers need 8 minutes one week, take the 8 minutes and compress somewhere else. The total should stay within 15-25 minutes, while the balance inside it flexes with what the conversation needs.
Second, the segments run in this order for a reason. Personal connection first sets a productive tone; status before blockers gives context for what is at risk; priorities last anchor next week's work in the conversation you just had. Reorder the segments and the check-in usually gets less useful.
If you are a first-time manager, expect your check-ins to get faster within 4-6 weeks. The first few check-ins feel awkward and run over time; by week 8, the structure feels natural and the conversations start paying off. Stick with it through the awkward early weeks.
The research backs the regular rhythm itself. Gallup reports that employees whose managers hold regular meetings with them are almost three times as likely to be engaged as employees whose managers do not. The same research found that engagement runs highest among employees who have some form of daily communication with their manager (Gallup).
Questions by Context
Generic check-in questions every week produce generic answers. The questions should match the context: new hires need different prompts than established employees, OKR check-ins focus on key result confidence, retention conversations surface different signals than performance recovery. Below are six question banks for the most common situations.
Two rules for using question banks. First, do not ask all five questions every week. Pick 2-3 that match what the employee actually needs to talk about, and leave room for them to raise what is on their mind without forcing every prompt.
Second, rotate the question bank as situations change. A new hire moves to the default questions around day 60-90; when an OKR cycle ends, the check-in reverts to the default set; a high performer showing disengagement signals warrants the retention bank for a few weeks. Static question sets become ritual; rotating sets stay productive.
Questions only produce engagement if the manager acts on the answers. Gallup finds employees are 3.6 times more likely to strongly agree they are motivated to do outstanding work when their manager gives daily rather than annual feedback. The same research found that 80% of employees who received meaningful feedback in the past week are fully engaged (Gallup).
When Daily, Weekly, Biweekly, or Monthly
Weekly is the right cadence for most working relationships, but specific situations call for more or less frequency. The table below maps the common situations to a cadence.
| Situation | Cadence | Reasoning |
|---|---|---|
| New hire, first 30 days | Daily or every other day | First weeks have the highest information density. New hires need quick course-correction, not weekly waiting |
| New hire, days 31-90 | Twice weekly tapering to weekly | By day 31 the basics are clear; by day 90 they should be on the standard team cadence |
| Established employee, project active | Weekly | Default for most working relationships; matches OKR cycle and natural project rhythms |
| Established employee, stable role | Weekly check-in plus monthly 1:1 | Status weekly, broader development monthly. Both serve different purposes |
| Senior/strategic role | Biweekly check-in | Strategic work has longer feedback loops; weekly status creates noise without signal |
| Remote employee | Weekly minimum | Remote employees need more, not less, structured connection. Skipping weeks compounds isolation |
| Performance concerns | Twice weekly to daily | Performance issues require closer cadence to catch and correct before they compound |
| High performer trajectory | Weekly check-in plus quarterly career conversation | Status keeps work flowing; quarterly career time addresses the retention factor |
Three rules for cadence decisions. First, default to weekly unless the context clearly calls for something else. Most employees in most situations benefit from a weekly rhythm, and deviating without a clear reason usually lets the practice degrade over time.
Second, when the situation is uncertain, increase the cadence rather than decrease it. New hires, performance concerns, project transitions, and remote employees all benefit from more frequent check-ins, not fewer.
Third, the cadence is a manager decision, not an employee preference. Employees who say they can skip check-ins are usually wrong, even when they mean it, because the meeting exists for the working relationship and not only for the needs they state.
A Practical Check-In Template
The template below fits in a single page (any shared document tool). Each row represents what should be captured in the running document week-over-week. The whole template is intentionally simple because complexity does not produce better check-ins; consistency does.
| Field | Why include it |
|---|---|
| Date and attendees | Basic record-keeping; useful for tracking cadence consistency over time |
| Wins this week | What got accomplished; gives the conversation a positive anchor before moving to challenges |
| Status on each priority from last week | Did last week's priorities ship? If not, why not? Direct accountability for stated commitments |
| Blockers and risks | What is in the way; what could derail; what concerns are surfacing. Highest-value field |
| Confidence on goals (1-10) | Subjective signal of how the employee is feeling about their key work; trend over weeks reveals issues |
| Priorities for next week (2-4 items) | Clear written list of what gets focused next week; shapes how the employee spends their time |
| Manager commitments | Specific things the manager will do (introduce to X, follow up on Y, decide Z by Wednesday) |
| Open questions or topics to discuss | Items the employee wants input on; ideas they want to surface; concerns to raise |
| Next check-in date | Confirms the cadence continues; never skip the scheduling |
Three rules for using the template. First, share the document between manager and employee, with both able to edit. Single-owner templates produce single-owner check-ins; shared templates produce shared check-ins.
Second, the document accumulates week over week rather than getting overwritten. Each new check-in adds a dated section at the top, above the previous one. Over time, that running record of priorities, blockers, and commitments becomes one of the most useful management documents you have.
Third, give manager commitments special attention. Anything the manager says they will do should be written down explicitly; without the writing, commitments evaporate within days and the employee learns that manager promises are not reliable.
Copy the section below into a shared document, one per direct report, and paste a fresh copy at the top each week. The employee fills in This Week, Blockers and Risks, Confidence, and Open Questions before the meeting; Next Week and Manager Commitments get written during it, while you are both still in the room.
For First-Time Managers
The first 6-8 weeks of running weekly check-ins as a new manager are awkward. The structure feels rigid; the conversations run over time; the employee may seem unsure of what to bring. The habits below help first-time managers get through the early period and turn the practice into a sustainable rhythm.
The single most useful piece of advice for first-time managers: the practice gets better with time and consistency, not with cleverness. Stick with the basic structure for the first 8-12 weeks, and resist the urge to redesign the format every few weeks.
The early conversations will feel uneven, and that is normal. By week 8, the rhythm becomes natural, both parties know what to expect, and the conversations start producing real value. Most first-time managers who give up on weekly check-ins do so within the first month, before the practice has had time to mature.
The stakes for getting this right sit with the team rather than with the manager. A 2023 survey of 2,066 employees found that among workers who had a negative experience with a poor manager, 34% wanted to leave the organization and 41% were stressed or anxious about reporting to work (SHRM, 2023).
A predictable weekly conversation is one of the cheapest ways to keep people from leaving over something nobody surfaced in time. The investment compounds; the practice pays back across years of tenure.
Weekly Check-Ins for Remote Teams
Remote teams need more, not less, structured check-in practice than in-person teams. The informal hallway conversations that happen in offices do not exist remotely; without weekly check-ins, remote employees can go entire months without meaningful manager interaction. Here is how each part of the practice adapts for remote check-ins.
| Aspect | In-person practice | Remote adaptation |
|---|---|---|
| Format | Often happens at desk or quick walk | Always video call (not audio only); audio loses much of the signal |
| Document sharing | Sometimes paper notes or laptop | Always shared screen with check-in document during call |
| Cadence flexibility | Easy to add ad-hoc check-ins | Calendar discipline matters more; ad-hoc rarely happens remote |
| Personal connection | Naturally surfaces in office | Must be intentional; ask the personal question, do not skip it |
| Body language signals | Visible naturally | Must read facial expressions on video; harder than in-person |
| Distraction risk | Lower (in shared physical space) | Higher (employee may have other windows open); video on helps focus |
| Documentation discipline | Sometimes informal | Critical; written records are the primary continuity |
| Frequency under pressure | Easier to skip | Should not skip; remote isolation compounds faster |
Three rules specifically for remote check-ins. First, video on, always. Audio-only check-ins lose facial expression, body language, and most of the engagement signals. Both parties should have video on; if the employee resists video, address it directly rather than accepting audio-only as the new norm.
Second, share the screen with the check-in document during the call. Both parties should see the same notes being updated in real time. This anchors the conversation in writing and prevents the "what did we agree to" ambiguity that emails are bad at resolving.
Third, do not skip remote check-ins because of timezone difficulty or busy weeks. With no informal interaction to fall back on, the structured check-in carries more weight, so skipping a remote check-in compounds isolation faster than skipping an in-person one.
The feedback gap on remote teams is measurable. Gallup reports that only 22% of employees strongly agree they received meaningful feedback in the past week, and that just 54% of managers who supervise remote employees strongly agree they trust their team to be productive. Its recommended fix is one meaningful conversation a week (Gallup).
Weekly Check-Ins During OKR Cycles
When the team is running OKRs, weekly check-ins become the engine that translates quarterly OKRs into weekly behavior. Without the check-in cadence, even well-written OKRs become forgotten documents within weeks. The check-in structure adapts to make OKR progress the central thread.
| Standard check-in element | OKR-cycle adaptation |
|---|---|
| Personal connection (2-3 min) | Same; do not skip even during goal cycles |
| Status (5-7 min) | Reframe around key results: which moved, which did not, which require attention |
| Confidence score | Add explicit 1-10 confidence on each key result; track trend over weeks |
| Blockers (3-5 min) | Focus on what is at risk for specific key results; what could derail this quarter |
| Next week priorities (3-5 min) | What specifically moves each key result; commit to 2-3 measurable actions |
| Manager commitments | What the manager will do to unblock or support specific key results |
| Wrap (1-2 min) | Confirm OKR adjustments if reality has shifted significantly |
OKR cycles, in other words, do not require a different check-in structure; they require the same structure with key results as the explicit anchor. Without this anchor, weekly check-ins drift away from OKRs and the cycle becomes disconnected from daily work. With the anchor, OKRs stay alive across the full quarter.
Weekly Check-Ins With New Hires
New hire check-ins follow a different cadence pattern than established employee check-ins. The first 90 days have higher information density than any other tenure stage; the cadence should reflect that. The table below lays out the cadence across the first 90 days.
| Period | Cadence | Focus |
|---|---|---|
| Week 1 | Daily 15-minute check-ins | What is becoming clear, what is still confusing, who have they met, immediate blockers |
| Week 2-4 | Every other day, 15-25 minutes | Onboarding milestones, role clarity, integration with team, first project progress |
| Days 31-60 | Twice weekly, 20-25 minutes | Project ownership, scope expansion, deepening relationships, surfacing structural questions |
| Days 61-90 | Weekly, 25 minutes | Standard check-in cadence, transitioning to full team rhythm |
| Day 91+ | Weekly, 15-25 minutes | Standard team cadence; new hire is now fully integrated |
New hire check-in cadence starts at daily and tapers to weekly over 90 days, and skipping the taper produces predictable failures. New hires put on a weekly cadence from day one usually accumulate confusion, miss early integration opportunities, and disengage before week 6. New hires kept on a daily cadence past week 4 usually feel micromanaged. The taper is what matches the cadence to the actual information density of each period.
The Weekly Team Meeting and the Group Check-In
A weekly team meeting is a different practice from the one-to-one check-in, and running one does not remove the need for the other. The team meeting handles what everyone needs to hear at the same time. The individual check-in handles what a person will only say when nobody else is listening.
At small business scale the split is usually 30 to 45 minutes once a week for the whole team, plus 15 to 25 minutes per person. Founders who try to save calendar time by keeping the team meeting and dropping the individual check-ins lose the blockers first, because almost nobody raises a real one in front of eight colleagues.
| Segment | Time | What happens |
|---|---|---|
| Check-in round | 5 min | One short answer per person to the same question. Gets every voice into the room in the first five minutes |
| Numbers and last week's commitments | 5-10 min | The two or three measures the team watches, and what happened to what was promised last week. Facts first, discussion after |
| Blockers worth the whole group | 10-15 min | Anything one person is stuck on that another person in the room can unstick. Everything else belongs in the individual check-in |
| One decision or one topic | 10 min | A single item that genuinely needs the group. More than one and the meeting runs long every week |
| Commitments for next week | 5 min | Who is doing what by when, said out loud and written where everyone can see it |
The check-in round at the top is the segment most teams either skip or let sprawl. Keep it to one question, the same question for everyone, and thirty to sixty seconds each. It is the cheapest read on how the team is doing, and on a remote team it is often the only moment in the week when every person speaks. This is a working meeting, not an all-hands, so keep the audience to the people whose work actually connects.
Check-In Questions for Team Meetings
Group check-in questions work differently from the ones you ask one to one. Everyone hears the answer, so anything requiring vulnerability or a complaint about a colleague gets a polished non-answer. Ask something short, specific, and safe to answer honestly in front of the team.
| What you want to surface | Question to open with |
|---|---|
| A read on energy and workload | What is one word for how you are arriving at this meeting? |
| Momentum, at the start of a week | What is one thing that went right since we last met? |
| Hidden dependencies between people | Who are you waiting on this week? |
| Focus, when priorities are drifting | What is the one thing you have to finish this week? |
| Risk, before it turns into a surprise | What is most likely to slip this week, and why? |
| Recognition, without a formal program | Who helped you last week that the rest of us did not see? |
Rotate the question rather than asking the same one every week, and answer it yourself first while the team is new to the practice. Whatever length you model, everyone matches. If your answer runs three minutes, the round takes twenty and the meeting is already off track. Keep yours to a sentence and ask for the same.
One caution on staff check-ins that happen in a group setting: they surface signal, not detail. If someone gives a one-word answer that sounds off, do not pursue it in the room. Note it, and open the next individual check-in with it. Handling it in front of the team is how people learn to give the safe answer every week.
Common Mistakes in Weekly Check-Ins
The mistakes below appear consistently across managers running weekly check-ins for the first time. All are avoidable once you understand the patterns.
What these mistakes share is treating check-ins as a one-way transfer of information rather than a structured two-way conversation that surfaces what the manager actually needs to know. The fix for most check-in failures is not better questions or better software. It is more discipline about what makes the practice useful: consistent cadence, an employee-driven agenda, balanced talk time, and written records.
The agenda point has research behind it. Writing in Harvard Business Review, Steven Rogelberg found no one-size-fits-all approach to one-on-ones, but reported that they are most successful when the meeting is dominated by topics of importance to the direct report rather than issues that are top of mind for the manager (HBR, 2022).
Measuring Whether Check-Ins Are Working
Most managers run weekly check-ins without ever measuring whether they are actually working. The signals below let you assess whether the practice is producing value or has degraded into ritual.
| Signal | What it tells you |
|---|---|
| Cadence consistency | Are check-ins actually happening every week, or being skipped frequently? Track over a quarter; below 80% cadence consistency means the practice is failing |
| Blockers surfaced per check-in | Healthy check-ins surface 1-2 blockers most weeks. Zero blockers consistently means the employee is not surfacing real issues |
| Employee preparation | Does the employee come ready with status and questions, or does the manager have to extract information? Preparation level signals whether the practice is producing value for the employee |
| Time to resolution on blockers | How long between a blocker being raised and being resolved? Long resolution times suggest the manager is not actually acting on what surfaces |
| Quality of priorities | Are next-week priorities specific and measurable, or vague? Specificity over time signals the practice is producing real planning |
| Employee engagement signals | Does the employee bring up retention concerns, growth questions, hard problems? Open conversation signals trust; closed conversation signals the practice has lost value |
| Manager commitment follow-through | Are the things the manager said they would do actually happening? Pattern of unfulfilled commitments destroys the practice faster than almost anything else |
The federal government makes the case for measuring on a regular rhythm. The Office of Personnel Management (OPM) defines monitoring in the performance management cycle as consistently measuring performance and providing ongoing feedback on progress toward goals, so that problems get identified and resolved early rather than at the end of the appraisal period (OPM).
For a small business, two signals carry most of the diagnostic value: cadence consistency and time to resolution on blockers. If both are healthy (80%+ cadence, blockers resolved within 1-2 weeks), the practice is working. If either is failing, fix the underlying issue before adding more sophisticated measurement.
Both numbers are easy to produce and almost nobody has them, because the evidence sits inside individual check-in documents where no one ever adds it up. One line per person per week, and one line per blocker, is enough to see the pattern by the end of a quarter.
| A | B | C | D | E | F | G | H | I | J | |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Week of | Employee | Held? | Date held | Minutes | If skipped or moved, why | Blockers surfaced | Manager commitments made | Last week's commitments kept | Employee came prepared |
| 2 | ||||||||||
| 3 | ||||||||||
| 4 | ||||||||||
| 5 | ||||||||||
| 6 | ||||||||||
| 7 | ||||||||||
| 8 | ||||||||||
| 9 | ||||||||||
| 10 | Check | One line per person per week, including the weeks it did not happen. The skipped weeks are the data | ||||||||
| 11 | Check | At the end of the quarter, count check-ins held divided by check-ins due, per person | ||||||||
| 12 | Check | Someone whose blockers column reads zero most weeks is not raising them, which is a different problem from having none | ||||||||
| 13 | Check | A run of commitments made and not kept damages the practice faster than anything else. Read that column first |
Tools and Software for Weekly Check-Ins
The tooling for weekly check-ins at small business scale should be lightweight. Most teams over-engineer the tooling and under-invest in the discipline of running the practice consistently. Here are the realistic options.
| Tool | Best for | Tradeoffs |
|---|---|---|
| Shared document (any docs tool) | Most small businesses | Simple, flexible, accessible. Each employee gets one ongoing doc updated week-over-week |
| Spreadsheet template | Teams that prefer structured fields | Easier to track patterns over time; less flexible for narrative content |
| Internal wiki page | Teams already using a wiki | Integrates with other team docs; useful for cross-referencing |
| Dedicated check-in software | Larger teams with formal performance management | Built-in prompts and reminders; adds cost and complexity often unjustified at small scale |
| Calendar block only (no document) | Teams just starting | Simple to start; degrades over time as commitments are forgotten; not recommended past month 2 |
For most small businesses, one shared document per direct report, with a new section added at the top each week, covers everything. Resist the temptation to buy check-in software before the practice is established. Software amplifies what is working, but it does not fix what is broken.
How FirstHR Fits
The honest disclosure: FirstHR is not a dedicated weekly check-in or 1:1 platform today. It has no built-in check-in scheduling, prompt automation, or check-in template features. The platform handles onboarding, employee profiles, document management, org charts, and the operational HR foundations that most small businesses need. For now, weekly check-ins live in your shared documents alongside your other planning notes rather than inside FirstHR.
That said, weekly check-ins work better when the underlying people operations are working. A team running check-ins on top of broken onboarding will spend most of the check-in time compensating for unclear role expectations the new hires never had.
A team running check-ins on top of consistent onboarding, clear documented roles, and structured employee profiles will produce check-ins that actually drive alignment and growth. FirstHR exists to handle the operational HR foundation at flat, predictable pricing, so that owners can focus on the higher-impact work of running consistent weekly check-ins that produce real outcomes.
Whatever tool you settle on, the next step is the same: copy the check-in record into a shared document for each direct report and put the first round of check-ins on the calendar this week.
Frequently Asked Questions
What is a weekly check-in?
A weekly check-in is a short, structured conversation of 15-25 minutes in which an employee walks their manager through the week: the progress made, the obstacles in the way, and the priorities for the week ahead. Its job is operational. It keeps the work pointed in the right direction, brings problems into view while they are still small, and gives the working relationship a steady rhythm. A 1:1 meeting is a different tool, usually longer and centered on career and development rather than this week's work. Regularity is where the value comes from; held only now and then, check-ins cost most of the time and deliver little of the benefit.
How long should a weekly check-in be?
Plan on 15-25 minutes for most situations. A check-in that regularly ends in under 15 minutes is probably skipping segments; one that keeps running past 25 minutes has usually slid into topics that belong in a 1:1, so split those out. A typical allocation: 2-3 minutes on personal connection, 5-7 on status, 3-5 on blockers, 3-5 on next week's priorities, and 1-2 to wrap up. An hour-long weekly meeting is really a different practice that mixes the check-in with the 1:1 and does neither job well. Keep the weekly slot short and give development its own, longer 1:1.
What is the difference between a weekly check-in and a 1:1?
Weekly check-ins focus on operational alignment: status, blockers, priorities. They are 15-25 minutes weekly. 1:1 meetings focus on career growth, broader development, and the manager-employee relationship. They are typically 30-60 minutes biweekly or monthly. Both practices serve different purposes; combining them produces meetings that are too long for status updates and too rushed for real development conversations. The healthy pattern: weekly check-ins for ongoing work, plus separate biweekly or monthly 1:1s for development. Some teams run only check-ins or only 1:1s; the strongest pattern uses both at different cadences.
What questions should I ask in a weekly check-in?
Five questions handle most weeks: what did you accomplish this week that you are proud of, what is blocking your progress right now, what are your top 2-3 priorities for next week, what do you need from me to be successful, and on a scale of 1-10 how confident are you about hitting your current goals. Beyond that default set, tailor the prompts to the person and the moment. A new hire needs questions about clarity, surprises, and hesitations; an OKR check-in centers on confidence in each key result; a retention conversation asks about energy and growth. Repeating one identical list every week gets you flat, rehearsed answers, so change the set to fit what the employee actually needs to discuss.
How often should you have weekly check-ins?
Once a week is the right default for most working relationships. New hires are the main exception: in their first 30 days they do better with daily or every-other-day check-ins, then taper to weekly across days 31-90. People in senior or strategic roles can sometimes move to every two weeks with nothing lost, while remote employees should never drop below weekly. When performance is a concern, tighten the rhythm to twice weekly or even daily until the issue is resolved. The rule underneath all of this: match the frequency to how fast things change in the work and how experienced the employee is. Start weekly and adjust only when the situation clearly asks for it.
What should be in a weekly check-in template?
Nine fields produce a useful template: date and attendees, wins this week, status on each priority from last week, blockers and risks, confidence on goals (1-10), priorities for next week (2-4 items), manager commitments, open questions or topics to discuss, next check-in date. The most important fields are blockers (highest-value content), priorities (shapes next week's work), and manager commitments (creates accountability). Without a written template, check-ins become conversations that fade within days; with the template, they build on each other week over week.
Should I have weekly check-ins with new hires?
Yes, but the cadence should be more frequent than weekly for the first 30 days. New hires have the highest information density of any employee tenure stage; daily or every-other-day check-ins for the first 2-4 weeks let issues surface and resolve before they compound. By day 30, most new hires can transition to twice-weekly check-ins; by day 90, they should be on the standard weekly team cadence. Weekly check-ins from day one are too infrequent for new hires; the first month produces too many questions and unclear moments to wait a full week for resolution.
How do you do weekly check-ins with remote employees?
Use the same structure you would in person: 15-25 minutes, a shared notes document, and at least one check-in every week, held on video rather than as an audio-only call. Remote staff actually need more structured contact than office staff, because nobody bumps into them in a hallway or catches them after a meeting. For the same reason, a skipped week leaves a remote employee more isolated than it would leave someone in the office. Two adaptations matter most. Keep cameras on, since an audio-only call drops much of the signal, and share your screen with the notes document so you both watch the record being written as you talk.
What is the biggest mistake managers make in weekly check-ins?
Letting the meeting turn into a status report. If the employee spends most of it narrating completed work, the conversation has lost its purpose, because a written update in chat or email would have delivered the same information in a fraction of the time. What only a live conversation produces is the part managers skip when the clock runs out: what is in the way, what is at risk, and what the employee needs from them to move. The second most common failure is dropping check-ins in busy weeks. That teaches everyone the meeting is optional, and it lets problems grow unseen until they arrive as surprises. Reschedule rather than cancel.
How do you make weekly check-ins effective for high performers?
High performers usually do not need help with status; they need help with growth, scope, and engagement. The weekly check-in for high performers should still cover blockers and priorities (everyone needs alignment) but should leave room for retention-focused questions: what kind of work do you want more of, what is one thing the company does that frustrates you, where do you see yourself growing. Without these questions, high performers' check-ins become routine status updates and the manager misses signals of disengagement until the resignation arrives. High performers leave for opportunity, not for problems; weekly check-ins are where opportunity gets created.
Should weekly check-ins replace 1:1 meetings?
No. They do different jobs, so swapping one for the other leaves a gap. The weekly check-in handles operational alignment (status, blockers, and priorities) in 15-25 minutes, while the 1:1 covers career, growth, and the working relationship in 30-60 minutes every two weeks or once a month. Drop the 1:1s and development conversations lose their protected time. Swap the check-ins for weekly 1:1s and you get hour-long meetings that slide back into status updates. The strongest setup uses both: a weekly check-in for the work and a separate, less frequent 1:1 for development. A small team that runs check-ins alone usually makes it work by deliberately stretching one check-in a month to cover development topics.
How do you handle weekly check-ins when there are performance issues?
Increase cadence first, not check-in length. Performance issues require closer feedback loops: twice weekly check-ins to daily check-ins until the issue resolves. The structure stays the same (status, blockers, priorities) but the rhythm tightens to catch problems earlier. Two rules apply specifically to performance situations. First, document the check-ins more explicitly than usual; written records of priorities and commitments matter when performance conversations escalate. Second, do not use the regular check-in to deliver formal performance feedback; that should happen in a separate, scheduled conversation. Mixing performance feedback into routine check-ins damages the practice for everyone.