The HR system of record: leave requests, personal records, org chart, and company policies. If it's about you as an employee, it starts here. Log in with your GovTech account.

Shared HR documents (handbooks, forms, onboarding checklists) live in Google Docs, access-controlled per document. TODO: confirm with HR which docs to signpost here, then list each with its own blurb.

Collaborative whiteboards for project planning, workshops, and service mapping. Reach for it when a conversation needs a shared canvas rather than a document.

Who is working on what, by team and initiative. Check here before asking in Slack who owns a service or workstream.

The delivery roadmap: what we are building and roughly when. TODO: confirm whether this or the Notion public roadmap is canonical, then mark the other as a mirror.

Design files, prototypes, and the component library. Where every screen is designed and reviewed before it is built.

All source code, issues, and pull requests for GovTech services live in the govtech-bb organisation. Project 7 is the shared work backlog.

The coded component library behind our services — use these components before building anything new, so services look and behave like one government.

The public standards every GovTech service is measured against. Read before starting a new service; cite during service assessments.

The operations playbook: how we run ceremonies, make decisions, and collaborate day to day. The first stop for "how do we do X here?".

Team documentation workspace: meeting notes, drafts, and longer-form internal docs that have not (yet) earned a more permanent home.

Metrics, logs, and traces for alpha services. Your first stop when something looks slow or broken and you want data instead of guesses.

Status overview of GovTech services: what is live, in which environments, and its current health at a glance.

How we classify severity, who to escalate to, and the steps to run when something breaks. Read it before you need it. TODO: link the playbook. If none exists yet, this entry is the prompt to write one — owner: engineering.

Live alerts route to the #alpha-gov-alerts Slack channel (SNS → Chatbot). Pair with the Observability and Service dashboards above to see what is actually happening.

Blameless write-ups of what broke and what we changed. TODO: link the postmortem log location. If none exists yet, name an owner rather than pretending — owner: engineering.

Where the team talks. Key channels: #alpha-gov-alerts (live service alerts — during incidents, watch here first). TODO: add our workspace URL.

Public-facing communications and announcements from GovTech Barbados. What citizens and press see; link it, don't duplicate it.

The externally shareable roadmap view. TODO: confirm canonical roadmap (see Delivery & Planning) and cross-reference accordingly.