Skip to content
Orbitify
Changelog

Release 2026.11.11

Every change we make that people can see, newest first. Each release is named by the day it went out.

November 11, 2026Release 2026.11.11

New

Time off and on-call in one place

Open Time off and on-call to ask for time off, see your company's holidays and your weekly hours, and see who is on call. A supervisor approves or declines each request, and only approved days count as away on the schedule board. Colleagues see that you are away, never why. On-call schedules hand duty from one person to the next on the days you choose, and someone can cover a turn for a while.

In plans with OperationsLink
New

Record arrival and the client's sign-off

On a work order, press I've arrived when you reach the site. The app records when, how far you are from the work order's location, and photos of how you found it, even with no connection. At the end of the visit the client signs on your phone with their name and whether they are satisfied. A work order type can offer the sign-off or require it before the work order is done: Client signs off the visit, in the type's settings.

In plans with OperationsLink
New

Report extra work found on site

When a technician finds more to do than the work order covers, they press Extra work needed: what it is, the parts and hours they think it needs, and photos. No prices are asked for and nothing goes to the client. The people who plan work see it in the Inbox and turn it into a follow-up work order at the same location, or set it aside with a reason.

In plans with OperationsLink
New

Send after-hours work to on-call

Assignment rules can now send new requests and work orders to the person on call for a team, and can hold only inside or outside your company's working hours, which you set in Settings. Sending work to the team that looks after its asset is now a rule of its own, first in the list, so you can move it. A request given to someone on call is theirs, and they are told at once. A time target can also count the response when the technician arrives on site.

In plans with OperationsLink
New

Work out severity from urgency and impact

In Settings, your company can keep a grid that gives a request's severity from its urgency and how much it affects: one asset, several, or the whole site. Whoever raises a request then says its urgency and impact, and the severity follows the grid. Without a grid, nothing changes: the urgency said is the severity.

In plans with OperationsLink
Changed

O-Agent's abilities are parts of your plan

Knowledge, agents, the apps agents may use, chat apps and websites are now separate parts of your plan, so a company can start with the assistant alone and add the rest as it needs them. Your company keeps what it uses: each new part was added to every plan that already had the parts it needs. Settings has a new AI and agents group, and O-Agent has a Capabilities tab that shows what it can do for your company.

In plans with AssistantLink
Improved

A clearer knowledge graph

The graph on O-Agent's Knowledge tab is easier to read: a location with many things in it folds them until you open it, a Show list picks out pages with lines that disagree, lines not checked yet or the most work orders, and hovering a dot shows its name and links. Dots are sized by how much is known about each one.

How we change Orbitify

New things and fixes go out as soon as they are ready. A change to how you already work, or one that asks something of you, is announced ahead, by this much:

Kind of changeNoticeHow you hear
A new feature, an improvement or a fixNone: announced on the dayWhat's new and this page
A change to how existing work is done: a moved screen, a renamed step, a new required field, a default switched onAt least 14 daysA notice to your administrators, and a coming change in What's new
An administrator must act; a feature is removed; where data is kept, or which AI model or region answers, changesAt least 30 days, with a date to act byA notice to your administrators by email and in the Inbox until one of them acknowledges it, and a reminder 7 days before
A change that breaks what a connected system does through the API or webhooksAt least 6 months, under a new API versionThe API changelog on the developers page, an email to whoever answers for each connection, and Deprecation and Sunset headers
A security fixNone: explained afterwardsThis page

Building on the API? See the developers page for its version and its own changelog. Developers