Your Weekly Status Meeting Costs More Than You Think

A 30-minute weekly status meeting with eight people uses four hours of paid time every week. Over a 48-week working year, that adds up to 192 person-hours. That is 24 full working days.

Most of that time goes to listening. One person speaks while seven wait their turn. The same updates could fit in a short written note.

This guide shows what your meeting really costs, how to tell if it is worth keeping, and how to replace it with an update your team will actually read.

What your status meeting costs

Move the sliders to match your meeting. The result updates as you go.

01 · Calculator

Price your status meeting

₹ INR $ USD

People in the meeting

8

Length

30 min

Meetings per week

1x

Average yearly salary per person (₹)

Example value, not a market average. Use your team’s real figure.

Adjust assumptions

Working weeks a year

Working hours a week

Prep time per person (min)

Cost multiplier

1 means salary only.

Time to write an update (min)

Time to read it, per person (min)

This meeting costs ₹1,80,000 a year.

That is 192 person-hours, or 24 full workdays. Each meeting costs ₹3,750.

Yearly cost compared

The meeting

₹1,80,000 · 192 h

A written update instead

₹27,000 · 28.8 h

A written update would give back 163.2 person-hours and ₹1,53,000 a year. That is 85% of what the meeting costs.

Why status meetings are so hard to cancel

Status meetings feel like work. Everyone is present, everyone speaks, and the hour looks productive on a calendar.

They also give managers easy visibility. And once a meeting is on the calendar, it stays there because nobody owns the decision to remove it.

None of these reasons is about sharing information faster. That is the one job a written update does better.

Meeting or message? Test yourself

Not every conversation belongs in writing. Pick the better format for each situation.

02 · Quiz

Six situations. Meeting or message?

1. Sharing weekly progress on five projects

MeetingMessage

Message. The information flows one way, so nobody needs to be in the room for it.

2. Picking between two vendors when the team disagrees

MeetingMessage

Meeting. Live debate settles a disagreement faster than a long comment thread.

3. Announcing a reorganisation that changes people’s roles

MeetingMessage

Meeting. Sensitive news needs a human voice and room for questions.

4. Reporting this month’s sign-up numbers

MeetingMessage

Message. Numbers are easier to read in a chart than to hear out loud.

5. A new hire’s first week with the team

MeetingMessage

Meeting. New teams build trust face to face before written updates work well.

6. Getting feedback on a draft product spec

MeetingMessage

Message. Written comments give people time to think before they react.

When a status meeting is worth keeping

Some meetings earn their place. Tick what is true for your meeting in most weeks.

03 · Checklist

Keep it or cancel it?

• A decision gets made in the room
• People need to debate or disagree live
• Someone is usually blocked and needs help right away
• The news is sensitive, such as feedback, conflict or layoffs
• The team is new and still building trust

Nothing ticked: send it as a written update.

A rule of thumb, not a formula.

How to switch to written updates in four weeks

Cancelling a meeting overnight can make a team feel cut off. A gradual switch works better.

1. Week 1: Keep the meeting, but ask everyone to post their update in writing first. Use the meeting only for questions.
2. Week 2: Cut the meeting to 15 minutes. Discuss only blockers and decisions.
3. Week 3: Cancel the meeting. Keep a 15-minute slot for blockers, and skip it on weeks with none.
4. Week 4: Ask the team what they miss. Add back only what they ask for.

Write your first update

A good update is short, follows the same order every week, and puts blockers where people will see them. Fill in the fields below and copy the result.

04 · Update builder

Build your weekly update

Team

Week of

Shipped

In progress

Blocked

Decision needed

Numbers

Preview

Status update · [Team] · week of [date]

Copy my update

Post it at the same time every week, so people know when to look. Link to documents instead of pasting them in, and keep the whole update short enough to read in under three minutes.

If you keep the meeting, keep it short

• Send the agenda a day ahead, and cancel the meeting if the agenda is empty.
• Cap it at 15 to 20 minutes.
• Invite only people who need to speak or decide.
• End with decisions and owners, written down where everyone can see them.

Teams split across India and the US

For teams split between India and the US, a live status meeting has an extra cost: someone always joins outside working hours.

A 9am to 6pm day in Bengaluru ends at 7:30am in New York in winter and 8:30am in summer. San Francisco is three more hours behind. A written update lets each side read it during their own working day.

How the calculator works

1. Hourly cost = annual salary ÷ (working weeks × hours per week) × cost multiplier
2. Person-hours per meeting = people × (length + prep time) ÷ 60
3. Yearly cost = person-hours per meeting × meetings per week × working weeks × hourly cost
4. Written update = writing time + reading time × (people − 1), at the same hourly cost

Everything runs in your browser. Nothing you type is stored or sent anywhere.

Worked example: 8 people, 30 minutes, once a week

Say the average salary is ₹18 lakh a year, with 48 working weeks of 40 hours each.

• Hourly cost: ₹18,00,000 ÷ (48 × 40) = ₹937.50
• Each meeting: 8 people × 30 minutes = 4 person-hours = ₹3,750
• Each year: 48 meetings = 192 person-hours = ₹1,80,000
• Written update: 15 minutes to write plus 3 minutes × 7 readers = 36 minutes, or ₹27,000 a year

The switch saves ₹1,53,000 and 163.2 person-hours a year, about 85% of the meeting’s cost.

Meeting cost calculator FAQ