Sync Meeting Template: Daily and Weekly Syncs That Fix Blockers, Not Report Status

A sync meeting is a short, regular check-in between people or teams whose work depends on each other. Its job is to find what is blocked, who needs what from whom, and what changed, then fix it fast. Copy the daily and weekly sync templates below. The rule that keeps a sync useful: status goes in writing before the call, so the call is only for dependencies and blockers.

Daily Sync Template (15 minutes)

Before the call (written, by [time]): each person posts one line: done yesterday, doing today, blocked by.

1. Blockers (7 min) Only items marked "blocked". Name an owner for each.

2. Handoffs (5 min) Who needs something from whom today?

3. Changes (3 min) Anything that changed priorities or deadlines.

Rule: if there are no blockers or handoffs, cancel the call.

Weekly Sync Template (30 minutes)

For two or more teams that share work, such as product and engineering, or sales and customer success.

Before the call: each team posts a short written update: progress, risks, what they need from the other team.

1. Last week's commitments (5 min) Done or not done. Only "not done" gets discussed.

2. Cross-team blockers (15 min) One owner and one next step for each.

3. Next week's dependencies (5 min) What each team will need from the other.

4. Actions (5 min) Owner, task, due date.

Sync vs Standup vs Status Meeting

If your "sync" is mostly people reading updates aloud, it is a status meeting. Move it to writing. For the team-level version, see the daily standup template.

Why Syncs Turn Into Status Meetings

Researchers Joseph Allen, Tammy Beck, Cliff Scott, and Steven Rogelberg asked 491 working adults what their last meeting was for. The two most common answers were discussing ongoing projects (11.6%) and routinely discussing the state of the business (10.8%). Status, in other words, is what most meetings already are.

The problem with status-heavy meetings is what they crowd out. Simone Kauffeld and Nale Lehmann-Willenbrock coded 92 real team meetings statement by statement. Teams that spent their time on problem-solving and action planning were more productive. Their meeting behavior was even linked to company success 2.5 years later.

A good sync is built for exactly that kind of talk: one blocker, one owner, one next step. See more numbers on our meeting statistics page.

How to Run a Sync That Stays Short

Written updates first

Post updates in a shared doc or channel before the call. People read them in two minutes instead of hearing them in twenty.

Only talk about what is blocked

If an item is on track, skip it. The sync exists for the exceptions.

Take deep dives offline

When two people start solving a problem, name an owner and a time to talk after the call. Everyone else gets their time back.

Start on the minute

About half of meetings start five or more minutes late. On a 15-minute sync, that is a third of the meeting.

Cancel when there is nothing to sync

No blockers and no handoffs means no call. Say so in the channel and move on.

Three Examples

Product and engineering, weekly sync, 10 people: moved updates to a written thread posted Monday morning. The call dropped from 60 to 25 minutes and only covered three or four cross-team blockers.

Sales and customer success, weekly: added "what we need from you next week" to each team's update. Handoff mistakes on new accounts dropped, and the call was cancelled about one week in four.

Design team, daily sync, 6 people: switched from a live round to a written "blocked by" line. They kept a 10-minute call only on days with blockers, about twice a week.

Common Mistakes

Inviting everyone

A sync is for people whose work depends on each other. Others can read the notes.

Solving problems on the call

Surface the problem, name an owner, take it offline.

No written updates

Without them, the call becomes a status round and doubles in length.

Never checking if it is still needed

Projects end and dependencies change. Review each recurring sync once a quarter. See the recurring meeting agenda template.

How Spry Shows Whether Your Syncs Are Worth It

Syncs are short, but they are frequent, and daily meetings add up fast. Spry's calendar analytics show recurring meeting load per person and team, the cost of each recurring meeting, and how much deep work time is left in the week. If your daily syncs have quietly stretched or multiplied, you will see it in the data.

[See your team's meeting load → Request access to Spry]

Moved your sync to written updates? I'd love to hear how it went. DM me on LinkedIn.

Related reading

• Team meeting agenda template

• One-on-one meeting agenda template

• Async status updates: templates and escalation rules

FAQs

What is a sync meeting?

A short, regular meeting between people or teams whose work depends on each other. Its purpose is to surface blockers, handoffs, and changes, not to report status.

What is the difference between a sync and a standup?

A standup coordinates one team's daily work. A sync usually connects people or teams who depend on each other, and focuses on blockers and handoffs between them.

How long should a sync meeting be?

15 minutes for a daily sync and about 30 minutes for a weekly cross-team sync. If it runs longer, updates probably need to move to writing.

What should be on a weekly sync agenda?

Last week's commitments, cross-team blockers, next week's dependencies, and actions with owners and due dates.

Can a sync meeting be async?

Partly. Updates work well in writing. Keep a short live call only for blockers that need people to talk, and cancel it when there are none.