Requests are how maintenance work gets reported into FacilityLane by people outside your maintenance team — tenants, occupants, staff, and visitors. A request describes a problem; your team reviews it and, if approved, converts it into a work order that gets scheduled and executed.
Requests grid view with request cards showing title, status badge, priority, and submission date

The Requests page showing incoming requests in grid view with status badges

How intake works

Requests arrive through a public intake form that you share as a URL or a printed QR code. Submitters do not need a FacilityLane account — anyone who scans the code or opens the link can report an issue with a title, description, priority, category, location, and photos. See Public Request Form.
Printed poster with a QR code linking to the public maintenance request form

A QR code poster that occupants scan to submit a maintenance request

Request lifecycle

The typical flow is: Pending → Under Review → Approved → Converted to Work Order, with Rejected as the alternative outcome at review. See Managing Requests for the review workflow.
Request detail page with status shown as Under Review and Approve and Reject buttons

A request detail page showing its status progression and review actions

Requests vs work orders

Converting a request creates a work order carrying over the request’s details and photos, so nothing reported by the submitter is lost. The original request keeps the Converted to Work Order status as its record.

Learn more

Public Request Form

Set up the intake form and share it via QR code or URL.

Managing Requests

Review, comment, approve or reject, and convert to work orders.

Work Orders Overview

Where approved requests go — the full work execution lifecycle.

Creating Work Orders

All the ways work orders are created, including request conversion.