If your site manages maintenance, administration tasks, gardening, or general support requests, this is where the work lives.
What the Requests module is for
Requests provide a structured way to:
Capture issues and tasks raised by residents or staff
Assign responsibility to the right internal team or external provider
Track progress from submission through to completion
Communicate updates clearly without losing context
Maintain an audit trail for compliance and reporting
Every request has a clear owner, a visible status, and a history of updates. Nothing falls through the cracks.
Where to find Requests
From the Dashboard, select Requests in the left-hand navigation.
You will see three core areas:
Active Requests – items currently being worked on
Archived Requests – completed or closed items
Request Types – Generally reserved for Super Admins to create or edit existing request Types.
We always advise contact Conpago's Support team when making changes here as they can impact staff and residents immediately.
Most day-to-day work happens in Active Requests.
How Requests are created
Requests can enter the system in several ways:
A resident submits a request via the app
A staff member creates one on behalf of a resident
A request is generated from a form or workflow
Regardless of how it starts, every request follows the same lifecycle and appears in the same table.
Understanding the Requests table
The Requests table is your control panel. It shows all active work at a glance and lets staff prioritise efficiently.
Each row represents a single request and typically includes:
Request type
Resident or unit
Status
Assigned team or provider
Date created and last updated
You can filter, sort, and organise this table to suit how your team works.
How Requests move through their lifecycle
Every request progresses through defined stages, from creation to closure. Statuses are consistent, visible, and timestamped.
Updates added along the way remain attached to the request, creating a complete history that staff, managers, and auditors can rely on.
You do not need to chase emails or ask for verbal updates. The request is the source of truth.
Internal vs external updates
Requests support two types of updates:
Internal updates for staff coordination and notes
External updates that are visible to residents or external providers
This separation allows teams to communicate clearly without oversharing or duplicating information.
What to read next
This article gives you the big picture. Each of the topics below goes deeper into how Requests work in practice:
If you are new to Requests, start with Create a Request Type. That decision shapes everything that follows.