Changelog
What has shipped, and when
Written by hand, dated, and describing only what is in the product today. Nothing here is a plan. For whether Rotaaa is up right now, service status carries the availability we have measured.
Swaps and drops, two reports, spreadsheet and PDF output, and the account controls that go with them.
- Shift swaps and drops
- Somebody can offer one of their own published shifts to a named colleague, or give it up for a manager to reassign. A swap goes to the colleague first and only reaches an approver once they have agreed. Nobody decides their own request, including a manager who raised one — it goes to another approver.
- Clear a week
- A planner can empty a week in one action rather than deleting shifts one at a time. A week containing published shifts is refused outright rather than partly cleared, and clearing those as well is a separate, explicit request that costs the permission to publish. Everything a clear removes lands in the deleted-shifts log and can be restored.
- Hours and rostered cost
- A report over any date range, by person, by department and by site, with unpaid breaks already deducted and each shift priced at the rate in force when it was written. Every column says rostered, because these are planned hours rather than clocked ones.
- Leave, absence and lateness
- A second report over the same range: leave counted by day, absence counted by spell, lateness counted by shift. A day of leave is priced against each person’s own contracted pattern, so a part-timer’s day is their day rather than a full-timer’s. A business that does not clock in sees no lateness table at all, instead of a table of zeros.
- Spreadsheets
- The people list, a week of the rota, one person’s timesheet week and the leave register all download as CSV. The people list and the leave register refuse above ten thousand rows rather than handing back a file cut off at the bottom.
- Print, or save as PDF
- The people list and a timesheet week print properly — the sidebar and the controls drop away, the business’s name and the range go on the page, and tables break across pages at a row rather than mid-line. Saving as a PDF is the browser’s own print dialog, so there is nothing to install.
- Signed-in devices
- Your account now lists everywhere you are signed in, with the device, the browser and roughly where it was last used, and lets you end any session or all the others at once. The one you are reading on is marked so you cannot sign yourself out by accident.
- Delete your own sign-in
- A control under Your account removes your sign-in and your membership of every business here, and leaves your employment record with your employer. The sole owner of a business cannot use it until somebody else is an owner, because it would leave that business with nobody able to run or close it.
- The activity log records who joined and who exported
- Accepting an invitation now leaves a row naming the person and the role they joined as. So does every download of the people list, the leave register or a full copy of the account, with the number of rows and whether pay columns were included. The log still publishes what it does not record, on the page.
- A home page that is about today
- The dashboard warns when next week still has no published rota, and the Needs action queue collects what is actually waiting on you — leave to decide, swaps and drops, open-shift claims, timesheets to approve, clock-out notes and overrunning breaks. A headline figure that compared a part-finished week against a whole one, and so read wrong six days out of seven, is fixed.
- Finding things
- Cmd-K, or Ctrl-K, opens a palette that finds a person or a page from anywhere in the product. The rota grid gained keyboard shortcuts, a filter you can link a colleague to, and duplicate and restore.
- Notice when the legal documents change
- Each of the four governing documents carries a version and an effective date, and the product tells an owner when the documents have moved since they last agreed to them rather than quietly treating silence as agreement.
Organisations came in-house, email started sending, and the public site got the documents and the status page it was missing.
- Organisations, memberships and roles are ours
- Businesses, the people in them, their roles and their invitations moved out of our authentication provider and into our own database. Clerk holds the sign-in and nothing about your business. It is why an invitation can now be listed, withdrawn and resent, and why the waiting-to-join list exists.
- Take a copy of everything
- Organisation settings hand back the whole account — people, rotas, leave, allowances and timesheet entries — as one readable file, straight away, rather than as a request that takes a month.
- Rotaaa sends email
- The email switch on a notification stopped being a preference nothing read. Notifications past their grace window are sent on a timer, one message per person per pass, so publishing a fortnight to somebody costs them one email rather than fourteen. Addresses that bounce or complain are dropped from future sends instead of being tried again.
- A status page with real figures
- Availability is measured and recorded rather than asserted, component by component, with any open incident and a record of the closed ones. Outages the application is too broken to record itself are recorded from outside it.
- Support threads
- Owners and administrators can open a support thread from inside Rotaaa, tied to their business, and a reply arrives where the thread is rather than only in an inbox.
- Terms, privacy, cookies and a service level agreement
- Four governing documents, each with a version, an effective date and a summary of what changed, and an accessibility statement beside them. The service level agreement is the one that says plainly what Rotaaa does not promise.
- A strict Content-Security-Policy
- Every page is served with a one-time token and only scripts carrying it will run. Violations report back to us, so the policy is tightened on evidence rather than on hope.
- Clock-out notes and timesheet corrections
- Somebody can leave a note when they finish a shift, and it reaches the people who can act on it. A manager can override the paid minutes on a timesheet line with a reason, and the punch behind it is never edited — the correction sits beside the original.
The first public build: the rota grid, the people it schedules, and the name.
- Rotaaa, at rotaaa.app
- The product took its name and its address, made by ImKyleJK Studios.
- The rota grid
- One row per person, one column per day. Add a shift, drag it to move it, drop it onto somebody else to reassign it, copy a week forward or save it as a template. A genuine double-booking is refused; the softer clashes are warnings a planner can override with their eyes open.
- People, sites, teams and job roles
- The records the rota is built from: staff with their contracted hours and the roles they hold, the places they work, the teams they work in, and the job roles that price a shift.
- Leave
- Requests, approvals and balances, with approved leave checked against the rota — approving leave that clashes with a rostered shift asks what to do with the shift rather than leaving two records that disagree.
Something here not working as described?
That is a defect in the product or in this page, and both are worth telling us about. The routes are on support, and pricing covers what all of this costs, which is nothing.