Onboarding
Part of Community roles and operating routines
Planning coverage across time zones
Plan staffed community windows, shift overlap and response expectations across Australian and overseas time zones.
Plan coverage around when members need a human decision. Track when questions and reports arrive, set a response promise, and give each staffed window an owner and backup. An alert can notify someone; it cannot make a reviewer available.
Separate posting from staffed hours
Members may be able to post whenever the space is open. Decide what can wait until the next staffed period and what needs a faster reporting route. Tell members when routine questions are normally reviewed and how to raise an urgent concern. Promise only what the roster can support.
If the community has a history, group questions, reports and approvals by hour and day, then read the cases behind busy periods. For a new community, set an initial window that available staff can cover and revise it as demand becomes visible. A temporary launch peak need not determine the permanent roster.
Record each coverage window
| Field | What to record |
|---|---|
| Window | Start and end dates and times with a named time zone. |
| Primary | Person watching incoming work who is authorised to act. |
| Backup | Person contacted when the primary is unavailable. |
| Overlap | Time to pass unresolved cases to the next shift. |
| Escalation | Route for work outside the shift’s authority. |
| Member promise | Expected response during and outside staffed hours. |
A person who receives notifications may still lack the permissions, context or time to review an item. Check each before counting the window as covered. Pass on unresolved cases with their current owner and next action so the incoming person does not duplicate or miss work.
Steps to Establish and Maintain Effective Coverage Across Time Zones
- Define staffed windows with time zone clarityUse named zones (e.g., Sydney/AEST, London/GMT) not abbreviations like 'EST'.
- Assign primary and backup staffEnsure both have access, context, and authority to act.
- Set overlap and escalation pathsDefine handover times and routes for unresolved or complex items.
- Monitor and adjust based on real dataReview delayed items post-trial; refine shift timing or promises as needed.
Check clock changes
Daylight saving time can make fixed offset maths unreliable. Some regions switch clocks and others do not, and clock changes may occur on different dates.
Whenever a clock change is approaching, compare each shift in the working person’s time zone and the zone used in member notices. Use a dated calendar entry with a named zone rather than an ambiguous abbreviation such as “EST”. Recheck recurring meetings, automated notices and shift overlap. Verify overseas colleagues’ clock changes for their particular locations; they may occur on different dates.
Key Dates for Daylight Saving Time Adjustments in Australia and Key International Zones
- Australia (AEST, AEDT)
- First Sunday in October (start), first Sunday in April (end)
- United States (EST/EDT)
- Second Sunday in March (start), first Sunday in November (end)
- United Kingdom (GMT/BST)
- Last Sunday in March (start), last Sunday in October (end)
Review the gaps
After a trial period, inspect items that arrived outside staffed hours. Record when each first received human review, whether specialist help was needed and whether the stated response expectation was accurate. One delayed complex case and a recurring overnight backlog call for different decisions.
Extend or move a shift, train a backup, narrow the promise or improve the urgent reporting route as the evidence warrants. Revisit the decision after a clock change or material change in participation.
