OperationsListed · screen comingQueue & board

UnitRunner

The hour a nurse spends hunting things, given back.

Notify meJoin the early-access listHow pricing works →

What it is

Real-time location for tagged equipment — pumps, vitals machines, wheelchairs — so a nurse asks the floor plan instead of walking it. The other two halves of this idea have already shipped inside apps that exist: one-tap requests to other departments with response clocks are PorterPing, which now carries the unit a job serves and filters its board to it, and closes only when somebody other than the porter confirms the thing arrived; supply levels before the shelf is empty are ward stores and par levels in StoreStock. What is left here is the tags, and tags are hardware.

Who uses it: Built for: Every specialty
Reads: Asset tags
Writes: Equipment locations
Never: It does not exist yet, and it will not until a hospital has bought and hung the tags: everything on this page that could be built without them was built into PorterPing and StoreStock instead of into a second board beside them.
Access: Only people whose role includes it — the clinic owner decides who
Your data: No PHI. Hosted in Boston, United States. On uninstall: Every record stays; only the workflow leaves.

How it works

The usual shape of a queue & board app. UnitRunner’s own steps are written from its screen when it ships.

It arrivesA new item lands on the board — from a booking, a referral or a colleague.
Work itAssign it, move it along, see who is waiting and for how long.
Close itDone items leave the board and stay in the record.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It does not exist yet, and it will not until a hospital has bought and hung the tags: everything on this page that could be built without them was built into PorterPing and StoreStock instead of into a second board beside them.

AI in UnitRunner

AskQuestions about what is on screen — “What needs attention in UnitRunner today?” — answered with the records it read.

DraftSummaries and notes for the team, marked as drafts until a person signs.

Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

Questions clinics ask

What does UnitRunner do?

The hour a nurse spends hunting things, given back. Real-time location for tagged equipment — pumps, vitals machines, wheelchairs — so a nurse asks the floor plan instead of walking it. The other two halves of this idea have already shipped inside apps that exist: one-tap requests to other departments with response clocks are PorterPing, which now carries the unit a job serves and filters its board to it, and closes only when somebody other than the porter confirms the thing arrived; supply levels before the shelf is empty are ward stores and par levels in StoreStock. What is left here is the tags, and tags are hardware.

What data does UnitRunner read and write?

UnitRunner reads asset tags and writes equipment locations. Its data class is No PHI. Every app works on the same patient record — nothing is copied into a silo.

What does UnitRunner deliberately not do?

What happens to our data if we uninstall UnitRunner?

Every record stays; only the workflow leaves.

Is UnitRunner available today?

UnitRunner is in design: the surface exists and the platform underneath is ready. Join the waitlist and it moves up the build order.

Want to see UnitRunner running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

More in Operations

All 145 →