Direct answer
Maintenance tracking needs one record per request, showing who raised it, where, how urgent it is, who has it and whether the work was confirmed done. Most failures come from requests handled in chats and calls, where an item is assigned and never seen again. We build this as a scoped internal tool around your own sites and rules. It is not property-management software: it does not cover leases, rent, accounting or tenant billing. For the wider family of tools, see internal business tools, and for a sector example internal tools for property management companies.
Intake
Give people one place to raise a request, with a short form: location, what is wrong, how it affects use, and a photo if helpful. The form should be usable from a phone. Requests that arrive by phone or email are entered by a person into the same list, so there is a single source. The general pattern is described in internal request portal.
Priority as a client rule
We do not decide what is urgent. You do. Write the categories in plain language, such as safety issue, service stopped, inconvenience, and say what each means for response. The tool can suggest a priority from the answers, but a person can change it. Keep the list short so it gets used.
Assignment
Each request gets one owner, either your own staff member or a contractor. Set the rule: by site, by type of fault, or by a coordinator who assigns. Show unassigned requests prominently, because the first delay in most systems is the gap between raising and assigning.
Contractor updates
If outside contractors do the work, they need a simple way to accept the job, give a visit date and report progress, without a long training. Their view should show only their own jobs. Where a contractor cannot log in, a coordinator can enter the update on their behalf, marked as such.
Photos and notes
Photos before and after are useful evidence of what was found and what was done. Notes should stay with the request, so the next person sees the history. Decide who may add and who may delete, since a clean history is only useful if it is not editable by anyone.
Repeat issues
One leaking tap is a job; the same tap leaking four times is a different problem. Let requests be tagged by location and item, so repeats show up in a view. That leads to a decision about replacement instead of another visit. We do not attach any figure to how often repeats occur; your own records will show it.
Closure
Define what closed means: work done, and confirmed by the requester or a coordinator. A contractor saying done moves the request to "awaiting confirmation", not straight to closed. If the requester says the problem persists, it reopens with the history intact.
Reporting
Useful reports are plain: open requests by age, by site and by owner; requests awaiting confirmation; repeats. A list that shows what is stuck is worth more than a chart. Reports read from the same records, so there is no second spreadsheet to keep up to date. LATYNEX is a remote English-language vendor with no discovery fee; we agree one scope and one price in writing.
Questions
Is this property-management software?+
No. It tracks maintenance requests only. Leases, rent, tenant accounts and accounting are outside its scope and stay in whatever you use now.
Can contractors use it?+
Yes, with limited access to their own jobs, or a coordinator can enter updates for them. Access is scoped to what you decide.
Who sets the priority levels?+
You do. We build your categories and response expectations into the tool, and we do not set them for you.
Does it work for something other than buildings?+
The pattern of request, owner, work and confirmation fits equipment, vehicles and shared facilities too. We scope the fields to whatever you maintain.