Skip to content

Getting Started

Submitting and Tracking Your Own Requests

For anyone who reports problems rather than fixes them: how to raise a maintenance request, what each status means, and how to follow what happened to it.

Updated September 15, 2026

Raising a request

Not everyone who uses Rivolq fixes things. Office managers, shift leads, teachers, and front-desk staff report problems and want to know someone picked them up. My requests is built for them. Open My requests and fill in four things: Facility (where the problem is), Title (what is wrong, in a few words), Description (what you saw and anything that helps whoever turns up), and Priority (low, medium, high, or emergency).

A specific description saves a wasted visit. "Third-floor east men's room, second sink from the door, dripping steadily since Monday" gets fixed on the first trip. "Sink broken" gets a phone call first. Be honest about priority: emergency exists for a genuine safety risk or a hard stoppage. If everything is an emergency, nothing is, and the label stops routing work faster.

What the statuses mean

Your requests appear newest first with a status.

  • Pending: submitted and waiting to be triaged.
  • Approved: accepted by the maintenance team.
  • Rejected: not going ahead. There will normally be a reason.
  • Converted: a work order has been created from it. The job is now scheduled, tracked, and assigned.

Converted is where your request stops being a request and starts being work.

What you can and cannot see

If your account is a requester, the list shows your own submissions only, not the whole organization's. You get your queue, not everyone's. Supervisors, admins, and other roles with wider permission see all requests and triage them from a different screen.

Reporting without an account

Contractors, tenants, and visitors who do not use Rivolq can still report problems through your organization's maintenance request portal, a public link that needs no login. Requests raised there land in the same triage queue. That is usually the better route for one-off reporters; accounts are for people who come back.

Common mistakes

  • Raising the same request twice because the first one did not change status within an hour. Triage is not instant, and a duplicate just adds work.
  • Putting the detail in the title. The title is for scanning a list; the description is where the detail belongs.
  • Emergency by default.
  • Reporting by corridor conversation instead of the app. If it is not a request, it is not tracked, and nobody can prove it was ever reported.

To see what happens once a request becomes a work order, read create and close work orders well.

Still need help?

Reach out for broken behavior, account-specific help, or billing questions.

Contact support
Rivolq
Book a demo