Your Bengali cultural association has 80 families. Forty are in the New York area. Twenty are in Texas. Ten are in California. The rest are scattered across four other states. You schedule the monthly meeting for 7 PM Eastern. That’s 6 PM Central (fine), but 4 PM Pacific. Half your California members are still at work. They miss the meeting. They miss the next one. After three months, they stop checking the group chat. By renewal time, they don’t bother.
You didn’t lose those members because they stopped caring. You lost them because 7 PM in New York is an impossible time in Los Angeles.
This is the time zone problem, and it hits nearly every diaspora community, professional network, and alumni group that’s grown beyond a single city. The AmeriCorps research on volunteering found over 75.7 million Americans formally volunteered between 2022 and 2023. A growing number of them participate in organizations where the membership is spread across the map. When the organization was local, meeting times were simple. Now that it’s national, they’re a puzzle nobody’s solved.
The Meeting Problem (And Why Rotating Fixes It)
There’s no perfect meeting time for a group that spans three time zones. 7 PM Eastern is too early for Pacific. 7 PM Pacific is 10 PM Eastern, which is absurd. The “compromise” of 8 PM Eastern / 5 PM Pacific still catches West Coast members during commute time.
Stop looking for the perfect time. Rotate instead.
January meeting: 7 PM Eastern (convenient for East Coast, manageable for Central, tough for Pacific)
February meeting: 6 PM Central (convenient for Central and Pacific, a bit early for Eastern)
March meeting: 6 PM Pacific / 9 PM Eastern (convenient for West Coast, late but doable for East Coast)
Each time zone gets a convenient meeting once every three months and an inconvenient one once every three months. Nobody’s always excluded. Nobody’s always prioritized. That’s fair.
Will some people miss the late meetings? Sure. Record them. A 20-minute recording that someone can watch on Saturday morning costs nothing to produce and makes a West Coast member feel included even if they couldn’t attend at 10 PM their time.
A few practical tactics:
- Publish the rotation a year out. Members plan around a known schedule.
- Use calendar invites that display multiple time zones (Google Calendar and Outlook both support this). Show ET, CT, MT, PT side by side.
- Watch the DST trap. Indian and Bangladesh Standard Time don’t observe DST. If you have members in Dhaka or Mumbai, the gap from US Eastern shifts twice a year.
- Make it normal to RSVP “watching the recording later.” 60-percent live plus 30-percent recording-watch beats 70-percent live where the West Coast never shows.
Async Is Your Real Meeting
Most multi-time-zone organizations get this backwards. The monthly Zoom call is the secondary gathering. The group chat is the primary one.
Think about it. The WhatsApp group or Slack channel is active every day. People post at all hours, on their own schedule. The person in Seattle reads the morning messages with their coffee. The person in Miami responds during lunch. The person in Houston chimes in after dinner. Nobody needs to be online at the same time.
That group chat is where community actually lives for a distributed organization. The monthly call is where decisions get formalized. But the relationships, the banter, the recipe sharing, the “anyone know a good dentist in Dallas?” questions: those happen asynchronously.
If your organization treats the monthly meeting as the only touchpoint and the group chat as informal noise, you’ve got it backwards. The group chat is where your distributed members feel connected, and where year-round connection actually happens. The meeting is the least important thing you do.
Tools that make async actually work
- Threaded chat. Slack threads or WhatsApp reply-to-message keep parallel conversations from drowning each other. The West Coast member opening 200 messages can scan threads, jump into two, skip the rest.
- Short async video. Loom or a one-take phone video beats typing. The treasurer records a three-minute walkthrough of the quarterly finances.
- A shared workspace. Notion, Google Docs, or a pinned Drive folder for content that doesn’t belong in chat: bylaws, minutes, vendor lists.
- Polls. WhatsApp and Slack both have built-in polls. “Picnic, June 7 or June 14?” Twelve replies in two days. Done.
- Transcription. Otter.ai or Zoom’s built-in transcription turns a recording into a searchable transcript.
The pattern: lower the cost of catching up. The member who missed the meeting should be fully informed in 10 minutes, not 90.
Regional Clusters: Let Them Be Local
If you’ve got 20 families in the Dallas area and 40 in the tri-state area, let those clusters do their own thing.
A DFW sub-group that meets locally for Eid dinner or a summer barbecue doesn’t need permission from the national board. They just need encouragement. “Hey, if there are enough of you in one area to meet up, do it. Post photos in the main group. We’ll promote it.”
Regional gatherings solve the time zone problem by making it irrelevant. Nobody’s on Zoom. Everyone’s in someone’s living room eating biryani. The community identity stays national. The community experience becomes local.
This works especially well for cultural associations, where the social events (dinners, religious celebrations, cultural programs) are the whole point. A national Zoom meeting can handle elections and dues announcements. But you can’t eat together over Zoom. Regional clusters can.
Async Event Ideas That Build Connection
The hardest part of distributed community isn’t logistics. It’s the feeling. A Zoom members can’t attend doesn’t make them feel like they belong. Async events can, with a little care:
The story chain. Pick a prompt. “Share a photo of your kitchen on a Friday night.” Members post over a week. The Houston member’s biryani photo gets a comment from Seattle. Conversations start without anyone being online together.
Async book or film discussion. Pick a title. Give three weeks. Open a thread. Depth is often better than a live discussion because people have time to think.
Recorded talks with comment threads. A speaker records a 20-minute talk. Post it Sunday. Comments stay open a week. Good for networks where speakers prefer recording once over a live event at an awkward hour.
Photo challenges. Monthly theme: “best home-cooked meal,” “what’s on your desk.” Submissions over a week. Light voting. Builds connection without synchronous attendance.
The “follow the sun” event. A live event runs 12 to 18 hours with members in different zones taking shifts. Sydney to London to New York to Los Angeles. For a once-a-year event the energy is real.
Don’t Punish the Wrong Time Zone
Watch for accidental exclusion patterns. If every decision happens at the monthly meeting and the monthly meeting is always at 7 PM Eastern, then East Coast members are making all the decisions. West Coast members find out what was decided after the fact. That’s not a time zone problem. That’s a governance problem wearing a time zone costume.
Fix it by separating decisions from meetings. Share the proposal in the group chat: “We’re considering raising dues from $75 to $100. Discussion is open until Friday. We’ll vote at the meeting on Saturday.” The discussion happens async, on everyone’s schedule. The vote can happen at the meeting or by online poll.
Any decision made at a meeting that half the membership can’t attend isn’t a representative decision. It’s a decision by whoever happened to be free at that hour. That’s how you end up with a California chapter that feels like an afterthought.
The Newsletter as the Great Equalizer
Time zones don’t affect email. A monthly newsletter lands in every inbox at the same local time (if you schedule it right), and everyone reads it on their own schedule.
For distributed organizations, the newsletter is essential: the one communication channel that’s completely time-zone-neutral. Everyone gets the same information at the same time. Nobody misses it because they were at work during the meeting.
Keep it short. What happened this month. What’s coming next month. One member spotlight. One reminder about dues or events. Done. Five minutes to read. That five minutes does more for connection than a 90-minute Zoom call that half the members missed.
Events That Cross Time Zones
Your annual cultural program or gala is probably in-person, in one city. That means out-of-state members either travel for it or miss it. Both options cost them something.
For the signature event, pick a weekend and give notice early. Three months minimum. Out-of-state members who want to attend need time to book flights and arrange childcare. A two-week notice excludes everyone who doesn’t live locally.
For everything else, consider hybrid. The town hall meeting, the election, the cultural quiz night: these can have an in-person component in one city and a Zoom link for everyone else. It’s not perfect. The hybrid meeting problem is real, and Zoom participants will feel like second-class attendees if you’re not careful. But it’s better than missing entirely.
Small things that help remote participants feel included: call on them by name during the Zoom. “Raj, I see you joined from California. Any thoughts on this?” Acknowledge their presence. It costs nothing and it signals that they’re not just watching a live stream. They’re in the room.
The Two-Meeting Solution
Sometimes rotating isn’t enough. Board has five members: two in New York, two in Houston, one in San Francisco. Agenda needs 90 minutes of real discussion. No single time works.
Run the meeting twice. Once at 7 PM Eastern, once at 7 PM Pacific. Same agenda, same prep doc. The chair attends both. Decisions get ratified after both, with everything documented in between.
More work, yes. But for a board losing its West Coast member because she can never attend, it’s the difference between her staying engaged and quietly disappearing.
Milder version: one live meeting plus an async followup. The meeting gets recorded with a transcript. Members who couldn’t attend have 48 hours to comment in a thread. The chair holds the vote open until the window closes.
Neither is elegant. Both beat pretending one meeting time serves everyone.
What Happens When You Get Distribution Right
The organizations that handle time zones well share a few traits. They don’t privilege one city’s schedule. They use async communication as the backbone, not the afterthought. They let regional groups form organically. And they make major decisions in ways that don’t require synchronous attendance.
The result? Members in Phoenix feel as connected as members in Philadelphia. Renewal rates don’t drop off by geography. The California chapter doesn’t drift away because they feel forgotten.
Your community isn’t defined by a zip code anymore. It hasn’t been for years. The organizations that thrive are the ones that build for the community they actually have, spread across three time zones and six area codes, instead of the one they used to have, all within driving distance of the same temple.
Winning back lapsed members starts with making sure they didn’t lapse because the meeting time excluded them. Fix the structural problem before you blame the member.
FAQ
How do we run a board meeting when members are in three time zones?
Rotate the time on a published quarterly schedule, send the agenda 72 hours in advance, and let members weigh in async before the meeting. If rotation still leaves one member chronically excluded, run two sessions in the same week or hold the vote open for 48 hours after the discussion. The goal isn’t getting everyone in the same room. It’s making sure every board member’s input shapes the decision.
Should we just record everything?
Recording helps, but isn’t a substitute for participation. A member who only watches recordings drifts away because they’re receiving the conversation, not part of it. If a member is consistently watching instead of attending, rotate the meeting time toward their zone.
How do we keep social connection when nobody can be at the same event?
Lean on async formats that build connection over time rather than one-shot live events. Story chains, photo challenges, book discussions. Houston sees Seattle’s photo, comments, gets a reply two days later. Different from “we were all in the same Zoom on Tuesday,” but often more durable.
What if our members are spread across continents?
For a community with members in India and the US, no rotation avoids putting someone at 2 AM. Async becomes the only realistic primary channel. Live meetings happen at whatever works for the largest cluster, and international members participate through chat. Set that expectation when they join.
A scattered membership still needs one source of truth. Somiti gives every member the same access to records, events, and payments, regardless of which time zone they’re in.