Tickets with deadlines

How it works

Any incident — a leak, noise, air conditioning, a blown light — becomes a ticket with a number, a category, an owner and a deadline. The deadline comes from the bylaws, not from the mood of the day.

The conversation happens inside the ticket. The owner follows it without having to ask, and management does not lose the history when the team changes.

What is close to missing its deadline rises to the top of the queue on its own. What has missed it stays visible to the board.

No more tickets that die in a chat group and nobody knows whether it was resolved.
No more queue-jumping by sympathy — the order is by deadline, and it is public.
A change of trustee does not erase the history of what has already been done in each unit.
The board can measure the management by number, not by perception.

The screen

Ticket queue

Ordered by deadline, not by opening date. What is red is what will blow first.

Tickets · open OpenMineExpiringResolved

Number	Subject	Unit	Owner	Deadline	Status
TK-2291	Air conditioning not cooling	902	Climatiza Services	14h	technician scheduled 9am
TK-2288	Water ingress in the garage	—	Internal maintenance	3h	expires today
TK-2285	Main gate slow	—	Elevadores Sul	-6h	deadline missed
TK-2290	Noise after 10pm	318	Management	2 days	under review
TK-2292	Light in corridor 12	1204	Internal maintenance	36h	open
TK-2287	Leak in the pool	—	Hidro Técnica	22h	parcel on the way

6 open tickets · 1 overdue · 1 due today · average deadline met: 91%Example

What you configure

Deadlines by category
Emergency · water, gas, lift2 hours
Air conditioning24 hours
Building maintenance48 hours
Noise and neighbourliness5 business days
Administrative3 business days
Automatic escalation4h from the deadline
The owner rates it at closingyes
A reopened ticket counts as newno

See this module running in the demo panel.

Try it now Request a proposal