How Halden replaced a 40-tab spreadsheet in a weekend
Kwame Asante, Operations Lead at Halden, built an internal rota tool over a weekend. It now runs shift swaps for 120 people across the group's clinics every day.
Lena FischerHead of Community

Halden is a healthcare group that runs a network of outpatient clinics. Each clinic needs the right mix of nurses, receptionists and clinicians on every shift, and for years the schedule for all of them lived in one spreadsheet.
Kwame Asante, Halden’s Operations Lead, inherited that spreadsheet when he joined. This is the story of how he replaced it with an internal tool he built over a single weekend.
The spreadsheet
By the time Kwame took it on, the rota had grown to 40 tabs: one per clinic, plus tabs for leave, cover requests, contact details and a summary that pulled from all of them with formulas nobody wanted to touch.
It mostly worked, until someone needed to swap a shift. Then the process looked like this:
- A nurse messaged a colleague to ask if they could cover.
- If they agreed, one of them messaged the clinic manager.
- The manager edited the spreadsheet, if they remembered and if nobody else had it open.
- Everyone else found out when they next checked, or when someone did not turn up.
“Every Monday started with a phone call about a shift that was on the sheet but not in real life,” Kwame says. “The data was never wrong for long. It was just never right at the moment you needed it.”
A weekend build
Halden had looked at off-the-shelf rota software, but the clinics have rules that the products did not handle well, like minimum skill mixes per shift and clinicians who split their week between two sites. A custom build through the IT team was quoted at several months.
Kwame had used Nest for a small personal project, so one Friday evening he exported the spreadsheet and started a new project. His first prompt described the people, the shifts and the rules, and said what was out of scope: no payroll, no timesheets.
By Saturday afternoon he had a working app with:
- A weekly rota for each clinic, with the old spreadsheet data imported into Postgres.
- A personal view where staff see their own upcoming shifts.
- Shift swaps with manager approval. A staff member offers a shift, a qualified colleague accepts, and the clinic manager approves with one tap.
- A warning when a swap would leave a shift without the required skill mix.
On Sunday he added the two pieces that made it something Halden could actually roll out.
Okta sign-in
Halden uses Okta for every internal system. Kwame asked Nest to add Okta single sign-on and limit access to Halden staff. Roles come from Okta groups, so managers see approval screens and everyone else does not. Nobody has a separate password to forget.
Slack alerts
Most staff already live in Slack. Now, when a swap needs approval, the clinic manager gets a Slack message with a link. When it is approved, both people involved are notified, along with the clinic’s channel.
“I built it over a weekend, but the bit that surprised me was Monday. I showed it to three managers, and by lunchtime they were asking when they could stop using the spreadsheet.”
Kwame Asante, Operations Lead, Halden
Rolling it out
Kwame did not switch everything over at once. He ran the new tool alongside the spreadsheet at two clinics for two weeks, fixed the issues that came up in small follow-up prompts, and then moved the rest of the group over.
Halden’s IT team reviewed the project before the wider launch. Because Nest apps are plain TypeScript with two-way GitHub sync, they could read the code in the repository they already use, check how permissions were enforced and keep a copy in their own systems. The app is published on Halden’s own domain.
Where it is now
The rota tool is used by 120 people every day across Halden’s clinics. Shift swaps that used to take a chain of messages and a spreadsheet edit now take a couple of minutes, and the Monday phone calls have stopped.
The 40-tab spreadsheet is archived, read-only. Kwame has since built a second tool for tracking equipment servicing, and two other teams at Halden have started their own projects.
“I am not a developer and I did not become one,” he says. “I just finally had a way to build the thing I could already describe.”
If your team runs on a spreadsheet that has outgrown itself, see how others use Nest for internal tools, or read more stories on our customers page.

Lena Fischer
Head of Community



