Published: October 13, 2026 / Last updated: November 2, 2026
Shiftto is a shift scheduling tool I built and run on my own while studying in an engineering laboratory at the University of Tokyo and working as a freelance web developer. Why I built it, what I changed after people actually used it, what got easier and what is still missing. I'll cover not only what went well but also what falls short.
The main reason is that existing tools didn't fit shifts for one-off events. Many scheduling services ask which days are free, and aren't made to ask for fine availability by the hour, like “free 10:00 to 12:00 but not in the afternoon.” Tools that do handle hours were either paid or required everyone to register, and for an event over in a few days the effort wasn't worth it.
Another reason is that I wanted a friend's group to actually be able to use it. I had a small group close by to try it with, so rather than stop at building it, I decided to see it through to real use.
I also took an optimization course at university and wanted to try applying what I learned to a real problem. Shift assignment is about placing people into slots under fixed conditions, so the ideas from the course seemed directly usable.
Before, I asked for availability with a Google Form, put the answers into a spreadsheet and built the shifts by hand. For a small group, that works fine. But as the group grew, these three things got heavy.
None of them is a one-time job; you redo them every time someone's answer changes. Handing these three to a machine was the starting point.
The first group to use it was a staff team for on-campus and community events. It had roughly 10 to 30 people, and the shifts rotated the staff's duties by time slot.
Since launch, it has been used in practice by many groups, well beyond people I know. What I write here is what actually happened in that use.
Once people used it, several things came up that I hadn't noticed. Here are the ones I actually fixed.
None of these occurred to me at the design stage. It reminded me that you only find out when people actually use it.
I counted how much it is used from the production data, looking at events that gathered a fair number of respondents. Names and participant details were not used in the count.
| Item | Range | Median / total |
|---|---|---|
| Respondents per event | About 10 to 30 | Median about 10 |
| Number of time slots | 5 to the 30s | Median about 10 |
| Number of roles | 1 to 6 | Median 3 |
| Events with saved assignments | About 70% | Automatic and manual roughly half and half |
| Times a person edited their own answer | In a few events only | Under 10% per respondent |
Of the assignments, those placed automatically and those placed by hand by the organizer were roughly half and half by count. The numbers are rounded so that individual events cannot be identified. The definitions and every item are in the article on usage data.
Compared with the spreadsheet and Google Form approach, these are the three things that I feel got easier.
I haven't measured how much time was saved well enough to give a number. It is only the impression of me and the people who helped.
I'll be honest about what falls short too.
The first two remain by the nature of the approach. The last two are features that are simply missing.
Within the scope of how it has actually been used, what I can say is that it suits one-off or short-term events of roughly 10 to 30 people. It saves the most effort for shifts where headcount differs by role and busyness changes through the day.
On the other hand, fixed-member shifts that continue every week, and management that includes attendance and payroll, are outside what this tool is for. A dedicated service is better suited to that.
A detailed explanation of how it works is in the article on automatic scheduling, and you can see what the resulting table looks like on the demo page. Comments and requests are welcome on the contact page.