Working with maintenance requests

Create a maintenance request from the dashboard, follow it on the list and profile, assign a service provider, and update status.

Written for Account operators User guide last reviewed on 2026-09-03

A maintenance request is the work record in Nabeeh: a reported fault, a scheduled visit, or a job opened from a plan. You run it from the list and the request profile — not from a separate screen for every field.

Create a request from the account

Open a new request from the dashboard or from the maintenance-request list.

Choose the property or asset the work belongs to. The request is filed under that place’s branch, even if the header shows another branch.
Choose the service if your role allows it.
Complete the customer name and mobile if they are not already filled.
Write clear notes: what is happening, and where on the unit or asset.
Attach photos or video when that shows the fault.
Set the visit date and time if those fields are visible on your account.
Submit. The request number appears on the list and on the profile.

If confirm send rejects the selection, the message names the provider or group and the reason — for example not assigned to this property, a group chosen as an individual, or an inactive provider. Correct the selection and confirm again.

Some accounts show request type or priority. Leave a field empty if it is not on the form; do not invent values the screen does not offer.

The list: search, then filter

Open Maintenance Requests from the sidebar (the screen title is Maintenance Requests Management). That list is the place to see all requests your account and branch allow. Cards on the dashboard summarize the same work; they are not the full list.

Filter with the labels on the screen:

Registration Date — when the request was created (a date range).
Schedule — the visit window (a date range).
Status cards (All Requests or a status) or the Status filter.
Request number, Customer, Service, Service Provider, property, or asset when you need a narrower set.

The calendar is a week view of visits. Use it after the list when you are planning the week — not as the place to review every request. Dashboard cards such as Needs attention, Upcoming requests, and Requests by property & asset open this same list with a preset filter.

Open a row to go to the request profile. From the list you can also update status for selected rows, or delete the selection, when your role allows — that bulk action is for account operators only.

Note: The request number is the shared reference with the customer and the service provider. Copy it as shown; do not rely on a name alone.

Tip: To check every request for a date, start on this list, then use Registration Date or Schedule. Do not stop at the dashboard cards.

The profile: where you follow the job

The profile keeps follow-up in one place:

Request information: service, schedule, status, assignment type.
Contact details: customer, mobile, WhatsApp, follow-up owner.
Property or asset data: name, address, location.
Status log, notes, attachments.
Custom fields your account defined for maintenance requests, when they appear on the profile.
The assigned service provider, which you can change until the status blocks it.

From the profile you can change the visit time, send a reminder, add an attachment, or cancel the request with a reason. If your role allows, you can also edit an existing note on the profile — you do not need a second note to correct the first. Do not cancel a request that is already completed or that the current status will not allow.

If the request is on the wrong branch, use Move to branch on the profile. Only this request moves. If the destination is not the property or asset branch, the screen warns you. Staff assigned to only one branch do not see this action.

Assign a service provider and update status

While assignment is still open:

Open the request profile.
Choose a service provider from your account, or the path your account uses to hand off work.
Save the assignment. The request appears for the provider under latest assigned orders.
Add a status in the status log when the field reality changes: waiting, in progress, then complete after the account’s payment rules are met.

If price approval appears, handle it on the profile before you ask to complete the request. Requests with unpaid dues stay open until the required payments are collected. See invoices when the customer should see an amount.

Other ways a request arrives

Not every request starts on the dashboard form. A request can also arrive from a QR code on a property or asset, or from the customer app. The list shows the source of the request so you can tell team-created work from a resident submission. Handle both from the same profile.