ordenlyour own product · launching

The hotel's faults, finally in order.

The room attendant reports a fault from her phone, maintenance fixes it with a photo and management sees where the time goes. No WhatsApp groups, no paper work orders.

first vertical
Hotels
format
iOS/Android apps + back office
status
launching
9:41
My tasks
3
MineDepartmentAll
#2041High
Leak under the sink
Room 304 · Floor 3
In progressLM
#2038Medium
AC not cooling
Room 212 · Floor 2
AssignedLM
#2036Low
Curtain off its rail
Room 118 · Floor 1
On holdJR
+ Report
// the problem

A fault reported over WhatsApp does not exist.

In most hotels, faults are reported out loud, by phone or in a group chat. That works right up until someone needs to know what is still open, who fixed it, or how long a leak on the third floor usually takes.

01
They get lost. What is said in a corridor, or in a group with forty messages a day, leaves no trace.
02
Nobody knows the status. Not the person who reported it, not the housekeeper, not management. They have to ask.
03
There is no history. Not for the room, not for the unit that breaks down every other month, not for how long each department takes.
// what it does

Report, assign, resolve — and be able to prove it.

QR code per location
A code in every room, common area or plant room. Scan it and the ticket already knows where it is.
Department inbox
Each category — plumbing, HVAC, TV — lands in the department it belongs to. Maintenance sees its own; reception sees its own.
Lifecycle with evidence
From new to assigned, in progress and closed, with a mandatory photo on opening and on closing where configured.
Recurring tasks
The checks due every week or every month generate themselves and show up as one more task.
Immutable history
Every change is recorded with who and when. It cannot be edited after the fact: that is what makes a history worth having.
Reports
What keeps recurring, which department is piling up open work, and how long closing really takes.
// who uses it

Everyone sees their own, without the noise.

Permissions are granted per department, not per person: someone can report in reception and resolve in maintenance. And the housekeeper still has authority over what her attendants report, even when another department is doing the fixing.

// lifecycle of a ticket
NewAssignedIn progressClosedOn hold
1Report

Housekeeping and reception. They open the ticket with a photo from the phone, on the spot, and follow their own.

2Resolve

Maintenance. Sees its inbox and what is assigned, picks up work itself and closes with evidence.

3Supervise

Heads of department and management. They assign, prioritise, reopen and read the reports. Owners and auditors, read-only.

// the back office

Management sees the whole hotel at a glance.

What is open, what is in progress, what was closed today and how long it takes. Without asking anyone for a report: the dashboard feeds itself from what the team does on their phones.

backoffice.ordenly.es
Open
12
In progress
5
Closed today
18
Average time
2:14
TicketLocationDepartmentPriorityStatus
#2041Leak under the sinkRoom 304 · Floor 3MaintenanceHighIn progress
#2040Fire extinguisher checkBasement · Plant roomMaintenanceMediumNew
#2038AC not coolingRoom 212 · Floor 2MaintenanceMediumAssigned
#2036Curtain off its railRoom 118 · Floor 1HousekeepingLowOn hold
#2029Key card will not openRoom 401 · Floor 4ReceptionLowClosed
// under the hood

Built so no hotel can see another's data.

It is a multi-tenant platform: every hotel shares the infrastructure, and none can see a single row belonging to another. That is not solved by being careful while coding, but in the database itself.

  • 01Isolation in the database. Every row carries its tenant and the engine refuses to read it from another, even if a query is written badly.
  • 02Native iOS and Android apps for field staff, with a persistent session on personal phones and PIN entry on shared devices.
  • 03Photos and attachments in European storage, with signed download links that expire.
  • 04Monitored from day one. Errors, metrics and an external check that the API responds, with alerts to on-call.

Do you run a hotel with the faults in your pocket?

We are opening Ordenly with our first hotels. If you want to see it with your own rooms and your own departments, get in touch.

Request a demo