WorkSpace brings a software team's day into one view. Annual leave balances and holiday calendars, Google Meet standups on a shared calendar, and GitHub or GitLab branches, pull requests and issues inside work tickets. We built it for our own team first; you can host it yourself.
WHY WE BUILT IT
Our engineers work across the UK and India. Before WorkSpace, a simple question such as "can we ship this on Friday?" meant checking a leave spreadsheet, two holiday calendars, a standup document and three GitHub tabs. Each tool was fine on its own; together they cost a little time from everyone, every day, and things still slipped through: a release planned on an Indian public holiday, a pull request waiting for a reviewer who was on annual leave.
WorkSpace puts those pieces in one place. It is not trying to replace your HR system or your whole project management stack. It answers the questions a software team asks every day:
If your team is small, co-located and happy with a spreadsheet, you probably don't need it. It earns its place when a team spans locations, leave policies or Git repositories, and the overhead of keeping everyone in sync starts to show.
LEAVE TRACKING & HOLIDAY CALENDARS
A staff holiday planner that understands mixed-location teams. Each person has the right entitlement and the right public holidays, and managers see clashes before they approve.
STANDUPS & SHARED CALENDAR
Standups work best when the agenda, the actions and the work they refer to are in the same place. WorkSpace keeps them together.
GIT WORK INSIDE TICKETS
Developers lose time switching between the ticket, the repository and the pull request. In WorkSpace they can do the common Git actions without leaving the ticket.
COMMIT SYNC & ACTIVITY
Team leads need to know how work is progressing without asking everyone for status updates. WorkSpace records Git activity automatically.
HOW IT WORKS
Most of the set-up is decisions about your own policies, not configuration. We help with each step.
Create your workspace and project boards, invite your team and give each person a role (super admin, admin, lead or developer) so they see what they need.
Expected window: Step 1
CHOOSING A LEAVE TRACKER
Whichever tool you choose, check these before you commit. They are the things we needed ourselves.
| Question | Why it matters |
|---|---|
| Does it handle different holiday calendars per person? | A UK and India team has different bank and public holidays. One shared calendar leads to wrong balances and missed clashes. |
| Does it prorate entitlements? | Joiners and leavers part-way through the year need the right balance without manual sums. |
| Can managers see clashes before approving? | Approving leave without seeing who else is away is how releases end up short-staffed. |
| Is it close to where the work happens? | If leave lives in one tool and the sprint in another, people have to remember to check both. |
| Where is the data held? | Leave records are personal data under the UK GDPR. Self-hosting or a clear hosting location makes that easier to manage. |
If your team works across the UK and India, our guide to how UK technology companies hire developers in India covers the working-together side too.
FAQ
Straight answers about leave tracking, standups, Git features and hosting.
Request a Demo
Book a live demo. Tell us how your team is spread across locations and how you handle leave today, and we'll show you how WorkSpace would fit.
