Roadmap
Open branches: what we are building, testing and only exploring.
What we are building next
Every open branch off the main line. A solid lane is being built, a dashed lane is still an idea we are testing with teams. Dates are aims, not promises.
Branch offline-clock-in, being built
offline-clock-in
Building
Clock in without Wi-Fi
For basements, warehouses and sites with a weak signal. Aimed at v2.4.
Branch break-rules, being built
break-rules
Building
Break reminders by local rules
The rota warns when a shift is too long without a break, using the rule you choose.
Branch multi-site, being tested
multi-site
Testing with 9 teams (sample)
Several locations, one rota
Move people between sites and see cover for each one.
Branch labour-cost, being explored
labour-cost
Exploring
Labour cost against takings
We are talking to teams before we build anything here.
Branch open-shifts, being explored
open-shifts
Exploring
Open shifts for a pool of casual staff
A shift anyone on a list can claim, first come first served.
Released on main Branch being built Being explored
Tell us what is missing
Most branches started as a sentence from a manager on a demo call. We count requests by team, and every branch is tested with real teams before it merges.
How a feature gets on the roadmap
We read every request. What gets built depends on three questions.
How many teams ask?
Requests are counted by team, not by message, so one loud thread does not decide.
Does it fit shift work?
Ferrow stays a rota, swap and timesheet app. HR and payroll stay with the tools you have.
Can we test it with real teams?
Every branch is tried by a group of customers before it reaches everyone.
See your own rota in Ferrow
Twenty minutes on a video call with someone who builds the product. Bring last week’s rota and we set it up with you, or start on the free plan and ask us later.