Recurring meetings often exist because a team needs visibility, decisions, or a reliable handoff—not because everyone must be in the same room at the same time. This guide shows how to replace a suitable recurring meeting with an asynchronous email workflow, estimate the meeting cost in a spreadsheet, and use reusable templates for status updates, decision requests, agenda-to-action notes, and retrospectives.
Overview
An asynchronous workflow gives people a defined time and place to contribute without requiring simultaneous attendance. Email is usually the simplest coordination layer, but the same workflow can connect to Google Workspace, Microsoft Teams, Slack, or Notion.
The goal is not to move every conversation into email. Live meetings remain useful for urgent issues, sensitive discussions, complex discovery, and decisions that cannot progress without real-time exchange. The better objective is to test whether a recurring meeting is primarily performing routine reporting, review, approval, or follow-up. Those activities are often easier to document asynchronously.
A workable async cycle has five parts:
- A clear owner: one person starts the cycle and closes the loop.
- A fixed deadline: contributors know when to provide updates or objections.
- A structured message: every update uses the same headings and level of detail.
- A visible decision record: the final outcome is easy to find later.
- An escalation rule: unresolved or urgent issues move to a short live discussion.
Start with one recurring meeting rather than changing every team ritual at once. Run the async version for two or three cycles, then compare completion time, decision quality, response burden, and the number of meetings actually avoided.
How to estimate the cost of a recurring meeting
A meeting cost calculator only needs a few repeatable inputs. The basic estimate is:
Meeting cost per occurrence = attendee count × meeting length in hours × blended hourly cost
To estimate the cost over a period:
Period cost = meeting cost per occurrence × number of occurrences
If hourly costs vary significantly, calculate each group separately:
Total cost = (number of people in group A × hours × rate A) + (number of people in group B × hours × rate B)
This is a planning estimate, not an accounting entry. Use the labor cost or internal hourly rate your organization normally uses. If you want to include preparation and follow-up, add those hours as separate inputs rather than quietly inflating the meeting duration.
A spreadsheet layout
Create columns for Meeting name, attendees, duration in minutes, occurrences per period, hourly cost, preparation hours per person, follow-up hours per person, and estimated period cost.
For a single blended hourly cost, convert minutes to hours and use a formula such as:
=Attendees*((DurationMinutes/60)+PreparationHours+FollowUpHours)*HourlyCost*Occurrences
For mixed rates, create one row per attendee group and sum the results. Keep the assumptions visible. A manager reviewing the sheet should be able to change the team size, duration, frequency, or rates without rebuilding the calculation.
This approach complements a broader meeting and email overload cost guide. If the change involves buying a workflow tool, compare the estimated savings with its cost using a software ROI calculator.
Inputs and assumptions
Use the following checklist before deciding whether to replace a recurring meeting.
- Purpose: Is the meeting for status reporting, decision-making, brainstorming, training, problem-solving, or relationship building?
- Frequency: How often does it occur, and how many occurrences are in the period you are measuring?
- Attendance: Who is required, who is optional, and who attends only because the invite is convenient?
- Duration: Use the scheduled length first. Record overruns separately if they are common.
- Preparation and follow-up: Estimate the time spent preparing updates, taking notes, and translating decisions into tasks.
- Hourly cost: Use a reasonable internal planning rate. Do not present it as a precise wage figure unless your accounting method supports that level of precision.
- Response window: Choose a deadline that allows contributors to respond without creating an always-on expectation.
- Decision authority: Name the person who can approve, reject, or escalate the request.
- Record location: Decide whether the source of truth will be an email thread, shared document, project board, or knowledge base.
Do not treat all avoided meeting time as guaranteed savings. The team may spend some of that time reading updates, asking questions, or writing decisions. Track the replacement work separately:
Estimated net time avoided = meeting time removed − async coordination time
For example, if a team removes four hours of combined attendance but spends two combined hours reading and responding, the estimated net time avoided is two hours. The result may still be worthwhile if the written record improves clarity or reduces repeated explanations.
Async meeting email templates
1. Status update template
Subject: [Project] weekly async status update — response by [date]
Progress since the last update:
[Two to five bullets]
Planned next:
[Work expected before the next cycle]
Risks or blockers:
[Issue, owner, and help needed]
Metrics or links:
[Relevant figures, files, or project records]
Please reply with corrections or blockers by [date and time]. No response is needed if your work is on track.
2. Decision request template
Subject: Decision needed: [short question] by [date]
Context:
[What has changed or requires a decision]
Options:
A. [Option and consequence]
B. [Option and consequence]
Recommendation:
[Preferred option and reason]
Decision owner: [name or role]
Reply by: [deadline]
If no response: [state the agreed escalation or default action]
3. Agenda-to-action template
Subject: [Project] actions from this cycle
Completed:
[Decisions or work closed]
Actions:
- [Task] — owner: [name] — due: [date]
- [Task] — owner: [name] — due: [date]
Open questions:
[Question, owner, and deadline]
Next checkpoint:
[Date, purpose, and whether a live meeting is still needed]
4. Retrospective template
Subject: Async retrospective — [project or sprint]
What worked?
[Specific practices to retain]
What created friction?
[Specific examples, not general impressions]
What will we change?
[One to three actions, owners, and dates]
Should the next cycle remain async?
[Yes, no, or conditional—with the reason]
Worked examples
Example 1: A small project team
Assume a six-person team holds a 45-minute weekly meeting. For a simple planning estimate, use a blended hourly cost of $60 and 48 occurrences per year. The attendance-only estimate is:
6 × 0.75 × $60 × 48 = $12,960 per year
If the team spends an additional 15 minutes per person preparing and 10 minutes per person on follow-up, the estimate becomes:
6 × (0.75 + 0.25 + 0.17) × $60 × 48 = approximately $20,160 per year
These are assumptions, not universal benchmarks. Replace them with your own rates and observed preparation time. If the async workflow takes 45 combined minutes each week to produce and review, compare that work with the full meeting estimate rather than claiming the entire meeting cost disappears.
Example 2: Mixed hourly costs
Suppose a 60-minute meeting includes two people planned at $100 per hour and four people planned at $45 per hour, held twice each month. The monthly attendance estimate is:
(2 × 1 × $100) + (4 × 1 × $45) = $380 per meeting
At two meetings per month, the estimate is $760 per month before preparation and follow-up. A spreadsheet with separate rate groups makes this calculation easier to update when the team changes.
If the meeting is replaced, record the async work in the same period: time spent drafting the update, reading responses, resolving questions, and recording the decision. This gives you a more useful comparison than meeting count alone.
When to recalculate and how to run the workflow
Recalculate the meeting estimate whenever the team size, attendee list, meeting frequency, duration, hourly assumptions, or preparation burden changes. Revisit it after a reorganization, a new project phase, a change in recurring meetings, or the introduction of a collaboration tool. Review the workflow at least once per project cycle rather than assuming the original format will remain appropriate.
Before the next scheduled meeting, use this practical sequence:
- Choose one recurring meeting with a clear reporting or coordination purpose.
- Record its current duration, attendance, frequency, preparation time, and follow-up time.
- Build the spreadsheet using the formulas above and label every assumption.
- Send the status update or decision request template with a clear deadline.
- Collect replies in one thread or linked document; avoid scattering decisions across channels.
- Publish an agenda-to-action message that names owners and due dates.
- Escalate only unresolved, urgent, or genuinely interactive issues to a live call.
- After two or three cycles, compare net coordination time, missed deadlines, decision reversals, and meeting hours removed.
Keep the workflow if it improves clarity without creating excessive reading or follow-up. Adjust the deadline, message structure, or audience if contributors are unsure what action is required. If the work repeatedly stalls, restore a short meeting with a narrow purpose rather than abandoning async communication altogether.
For related workflow improvements, see the email workflow template for an overloaded inbox and the guide to email productivity tools for small businesses and freelancers. The same principle applies: make the next action, owner, and deadline visible.