What this actually is, in plain words
Most of this site is written for people who already know what they are looking at. This page is not. If somebody has sent you here and you are not sure what the product does, read this one first and the rest will make sense.
Somebody needs help, and nobody knows where they are
A nurse is assaulted in a ward at two in the morning. A maintenance fitter goes into a switch room alone and does not come out. A resident with dementia walks out of a door nobody was watching. An officer needs backup and cannot reach a radio.
In every one of those, the same three things decide how it ends. Whether anybody finds out quickly. Whether the people who could help know where to go. And whether, afterwards, there is an honest record of what happened rather than an argument about it.
Most organisations answer this with a pull cord on a wall, a personal alarm nobody can locate, a phone tree, and a spreadsheet. Each part works. The gaps between them are where people get hurt.
What a "real-time location system" is
You will see the letters RTLS everywhere in this industry, including on this site. It is a simpler idea than it sounds.
A tag
A small radio, worn on a lanyard, clipped to a pump, or built into a phone or a handset. It does one thing: it announces itself, over and over.
Locators
Fixed devices on the ceiling that hear the tag. Each one works out its own answer to "how far away is that, and in what direction?"
A fix
Where those answers agree is where the tag is. That agreement is a fix: a position, with a note on how much to trust it.
That is the whole of it. A real-time location system answers one question continuously: where is this person or this thing, right now. Outdoors, satellite positioning does the same job with a different set of ears.
Here is the part worth understanding, because it is the part most products stop at. A dot on a map is not safety. Knowing that a tag is in Ward 4B does not tell you whether the person wearing it is in trouble, who is closest, whether that position is still current, or what should happen in the next thirty seconds. That gap is the reason this platform exists.
It watches, it decides, and it will not go quiet
WillowCreek takes the position and does something with it. Four things, really.
- It notices. Somebody presses a button, or falls, or fails to check back in when they said they would. Each of those becomes an alarm with a name and a place attached.
- It decides who to tell, and keeps deciding. The alarm goes to the people who should get it. If nobody acknowledges, it climbs to the next tier, and the next. Silence is never treated as "handled".
- It says what it does not know. If a position is old, it says so rather than showing you a confidently wrong dot. If a message was queued rather than delivered, it says that too. That sounds like a small thing. It is the difference between a system you can act on and one you learn to second-guess.
- It keeps the record. What happened, when, who was told, who acknowledged, who stood it down. Written as it happens, not reconstructed six months later for a coroner or an inspector.
What it looks like on an ordinary day
Nothing happens. That is most days. A control room screen shows the floor, who is on it, and a quiet list. Handsets sit in pockets. The platform is checking that it can still hear every tag and every locator, and it says so on screen, because a safety system that has quietly stopped working looks exactly like one where nothing is wrong.
Somebody goes somewhere alone. A community nurse heading to a home visit, or a fitter going into a plant room, tells the app where they are going and how long they expect to be. If they do not come back out and check in, the platform raises the alarm for them. That is the lone worker side of it, and it is the half most organisations end up buying separately.
Somebody presses the button. The alarm is priority one from the moment it is created, and nothing in the product can quietly downgrade it. It goes to the nearest responders with the person's position attached, it keeps climbing until a human acknowledges it, and the person who pressed sees on their own screen that it landed. That is the duress side.
Afterwards. Somebody stands the alarm down, and that is a deliberate act rather than a side effect of acknowledging it. The record closes with the whole sequence attached.
Everything the platform does, by name
Pick whichever is closest to the problem you came here with. Each of these is a page, not a paragraph.
Duress & life safety
Somebody presses a button, or falls. How the alarm is raised, who it reaches, and what the platform refuses to do with it.
The safety runtime →Lone worker
Somebody works alone. Scheduled check-ins, a deadline the server owns rather than the phone, and an alarm raised on their behalf when the check-in does not come.
Check-in and escalation →Location intelligence
Where people and equipment are, indoors and out, from whatever positioning hardware you already own.
The location engine →Rules & automation
What the platform does automatically when something happens, and why the escalation ladder is deliberately not something a customer can misconfigure into silence.
Rules and the lab →Operator surfaces
The screens people actually use: the control room, the Command Centre, the handset and the kiosk.
The four surfaces →Every capability, listed
The full index of what runs, written as the mechanism behind each one rather than as an adjective.
The capability index →Architecture & deployment
Where it runs, what it runs on, and what happens when something breaks mid-alarm.
The architecture →Your industry
The same platform, configured for the way your sector actually works. Healthcare, aged care and corrections are the ones running today.
Fifteen industry packs →How we evidence it
The claims on this site are meant to be checkable. This is what we can show you, and how.
Proof and evidence →Still not sure whether this fits?
Describe the problem in your own words and we will tell you plainly whether the platform solves it, partly solves it, or does not.