Work
A Media Company — Leave and Company Events
One calendar, fed by the tools you already approve leave in
The Client
A Hong Kong media company. Dozens of staff across shows and desks. Leave was already approved in the company messenger. Outdoor jobs and company events were not. Those still lived on paper, in a group chat, and in someone remembering.
The Brief
Staff needed one place to see who is off, who is out on a job, and what the company is running this week. Re-keying approved leave into a second spreadsheet was the failure — the approval already happened in the messenger. Outdoor work and company events had no home at all. Admin still needed to correct local records without touching the source system. And at 9am the team needed a briefing: who is off today, what is on, stay quiet on a public holiday.
What We Built
One internal HR app. Three kinds of record, one calendar. Leave syncs in from the system that already owns approval. Outdoor work and company events are created in the app. Staff see the week. Admin can correct local rows without writing back to the messenger. A small bot posts a weekday morning briefing to team chat. Hong Kong public holidays come from the government 1823 feed; on a holiday it stays quiet. The first connector was WeCom, because that is where this client already approved leave. The product is the calendar plus the connector: the same shape attaches to Slack, Microsoft Teams, or the HR / ERP stack the office already runs — so leave is not typed twice, wherever it is approved.
Who it is for
Hong Kong offices that already approve leave in Slack, Microsoft Teams, WeCom, or an HR / ERP system, and still run outdoor jobs and company events in a group chat. Media was the first client. It is not a media-only product, and it is not a WeCom-only product.
Outcome
HR and the floor look at the same week. Leave is not re-typed. Events are not a side WhatsApp. The 9am message is the app talking, not someone compiling a list. WeCom was the first wire. Slack, Teams, and the HR or ERP you already pay for are the same job.
What we delivered
- Leave sync from the system of record (no double entry)
- Connectors: WeCom, Slack, Microsoft Teams, HRIS / ERP
- Outdoor work records
- Company events
- Shared calendar for staff and admin
- Local corrections without touching the source system
- Weekday morning briefing to team chat
- Skip Hong Kong public holidays
FAQ
Questions we get
01 Does this only work with WeCom?
No. WeCom was the first connector because that is where this client already approved leave. The same calendar attaches to Slack, Microsoft Teams, or the HR / ERP stack you already run.
02 Will staff have to type leave twice?
No. Leave syncs from the system of record. Outdoor work and company events live in the app. Admin can correct local rows without writing back to the messenger.
03 Can it brief the team in the morning?
Yes. A weekday bot posts who is off and what is on. It stays quiet on Hong Kong public holidays.
Next case study
Newsroom Heatmap