
An automation engine inside the edays admin panel. When something happens in the system, workflows can respond automatically — send emails, approve requests, move users between groups. I found out on Thursday that an offshore team was starting Monday with nothing to work on. Four days to design something they could build. Despite the rushed start, it's now described internally as "the brain of edays" — central to how we think about every new feature.
Workflows are built from three components. Triggers kick things off — a user books absence, a timesheet gets submitted. Conditions filter when the workflow applies — maybe only for users in a certain region or department. Actions are what happens — send an email, auto-approve something, move a user between templates.
The clever bit is branching. Workflows can split up to three times, each branch with its own conditions and actions. Gets powerful quickly.

Workflow components
Three-panel layout for building workflows. Component library on the left with everything organised in folders — drag items onto the canvas in the middle. When you drop something, the right panel opens automatically so you can configure it. The real challenge was making this accessible to HR admins who aren't always technically minded. Progressive disclosure keeps things simple until you need complexity. Info chips summarise what's configured at a glance. Tooltips everywhere, written in plain English.

Interface 1

Proud of the quality we delivered under that kind of pressure. Would I have done it differently with more time? Of course — more research, earlier testing. But you work with what you've got, and the work held up.