What we are
building

Write something now and have it publish on a date you choose. Put a review or expiry date on a document, so a policy that has gone stale says so itself rather than quietly sitting there. And mark an item as required reading, so members acknowledge it and an admin can see at a glance who still has not.

Stop two people from holding the same thing at the same time. Add an optional approval step for resources that are not simply first come first served. And add a view of who is in today, which is the screen whoever is on reception would leave open all day.

A weekly club night currently has to be created by hand every single week, so recurring series. A calendar subscription, so what is on appears in the calendar you already live in rather than one more app to check. And checking people in by scanning a code, which would finally give attendance reporting something real to report.

At the moment a fault can only be raised by an authorised person during a checkout or a return, so anyone else who notices has to find someone to tell. This would feed the same maintenance queue that already exists.

Knowing when it was last serviced is not, and we would like to close that gap.

The idea is a service interval on each item, a work order raised automatically when something comes back damaged or missing, a view of everything overdue, and cost and damage history across an item's working life.

We would like to add an opt in route that sends an idea to us as well, with your say so and without carrying any of your organisation's data along with it. It would land on the same board this page is published from.

We would like to add one and do a full accessibility review at the same time, because the two touch the same styling, and because your organisation's own brand colours are exactly what makes readable contrast hard to guarantee.

We would like to support signing in with a Microsoft 365 or Google Workspace account, and to add and remove members automatically as your own directory changes. Anything touching how people prove who they are needs a careful security design before a line of it gets built, so this is a design question first.

The expiry is the whole point. A certificate that quietly runs out is the difference between a library of training content and something you can actually show an auditor, and it is what makes the same feature work for trade qualifications, health and safety, and bringing new starters up to speed. Not scheduled yet.

It is also the thing we get asked for most often.

The shape would be: members submit when they can work, an admin publishes a rota from that, and members clock in and out against it. Saying it is on the list is not the same as saying it is coming, and this one is far enough out that we would rather be honest about that.

The thinking is to keep the last version of each screen you are entitled to and show it behind a clear notice that it may be out of date, then hold on to the things that matter most, form submissions and equipment check ins, and send them once you are back in range. Orbit gets used on boats, in warehouses, in plant rooms and in basements, so this matters more here than it might elsewhere.

Today if you miss the banner, clear it, or turned notifications off when you installed the app, there is no way back to the message, and whoever sent it cannot tell that happened.