Work Order and Request Workflow: Best Practice Guide
This guide details how to establish full request management and operational control within Dwellant, structuring the core Request Triad (Informal Requests, Works Orders, and Quotations) alongside audience routing, contractor compliance, resident communication, and automated completion trails.
1. Request Intake Process & Framework
Establishing a disciplined intake baseline ensures that all reactive building maintenance and resident enquiries are captured systematically rather than managed informally through personal email inboxes.
Inbox vs. Dashboard Philosophy: Transition away from working reactively out of personal email inboxes by managing daily priorities directly through the Dwellant dashboard queues.
Why: Personal inboxes trap task progress within individual accounts, creating operational blind spots and single-point-of-failure risks if a team member is absent; the dashboard provides shared, portfolio-wide visibility so tasks progress without interruption.
Important Totals Monitoring: Track the "Important Totals" bar daily, focusing on Unacknowledged Requests, Late Requests, and New End-User Requests.
Why: Ensures rapid initial acknowledgement so delayed communication does not escalate tenant frustration beyond the underlying maintenance issue.
Building List & Estate Context: Access individual property dashboards to view building-specific actions, active contractors, and estate news bulletins.
Why: Isolates operational priorities to the physical block, preventing multi-site managers from conflating tasks across different developments.
Audience Accountability Roles: Assign the core request roles (Creator, Property Manager, and Assignee) at inception.
Why: Establishes transparent operational responsibility, ensuring every ticket has a clear owner responsible for pushing it to resolution
2. Resident Intake & Informal Request Setup
Informal requests log internal operational tasks, resident reports, and general site enquiries before or instead of dispatching financial instructions.
Creating on Behalf of an Occupant: Use the spacebar unit search shortcut to locate the resident, tag the source channel (phone, email, letter, or portal), and select the exact flat or communal location.
Why: Enables property staff to log phone or email issues instantly while tying the ticket directly to the resident's account as if raised by them.
Notification Safeguards: Check the "Email notifications" tickbox on the ticket and confirm the resident's profile notification settings are enabled.
Why: Requires alignment between ticket settings and account preferences to ensure automated updates reach the resident without silent delivery failures.
Review Group Routing: Flag high-risk, statutory, or specialist issues to dedicated review groups (e.g., Health & Safety) before actioning.
Why: Ensures specialist technical oversight on critical issues (such as lift defects or fire door faults) prior to contractor dispatch.
Task vs. Private Attachments: Attach documentation clearly marked as either public/task-visible or restricted private files.
Why: Prevents internal notes, sensitive costings, or personal resident data from leaking to end-user feeds.
3. Works Order Generation & Contractor Compliance Gates
Works orders act as legally binding operational and financial commitments instructing approved contractors to carry out defined tasks.
Approved Contractor Verification: Check contractor status before instruction; contractors with expired public liability insurance or unapproved RAMS display red compliance warnings.
Why: Acts as a mandatory safety gate, preventing the instruction of uninsured, unaccredited, or non-compliant suppliers.
Advanced Contractor Search: Use the Advanced Search tool to filter approved suppliers by specific trade (e.g., Lift Services – Maintenance), compliance status, and proximity to site.
Why: Speeds up contractor selection during urgent incidents and ensures only fully compliant, trade-appropriate vendors are dispatched.
Expenditure Caps & Financial Realism: Define a realistic maximum authorised expenditure cap (e.g., £1,200 call-out estimate) and target completion date; never enter £0.
Why: Entering £0 placeholders breaks automated financial accruals and prevents the system from reserving committed spend against the building ledger.
Single vs. Multiple Cost Schedule Allocation: Allocate the works order across single or split service charge schedules (e.g., Block Operating Schedule vs. Reserve Fund).
Why: Automates downstream accounting and invoice matching, removing the need for manual recoding when contractor invoices arrive.
4. Quotations & Blind Tendering Workflow
Dwellant manages competitive tendering and major expenditure through a relational tendering triad:
Request/ Specification > Blind Quote Submissions > Authorised Work Ordewr
Triad Linkage Hierarchy: Always link quotation requests to the underlying specification, and convert approved tenders directly into works orders.
Why: Preserves commercial integrity by ensuring the instructed order matches the exact scope, pricing, and contractor terms agreed during the tender.
Blind Multi-Contractor Selection: Add multiple contractors to the Quotation tab and issue tender invitations simultaneously.
Why: Guarantees fair commercial bidding; contractors only see the baseline scope and their own portal submission, keeping rival quotes and commentary strictly confidential.
Tender Rate Adjustments & PM Overrides: Review contractor portal submissions and enter negotiated property manager revisions directly where required.
Why: Accommodates scope adjustments and post-tender commercial negotiations within the platform's auditable record.
Acceptance, Rejection & Direct Order Conversion: Accept the winning contractor's quote with a single click, which automatically declines unsuccessful bidders and converts the approved quote into an active works order.
Why: Streamlines procurement, notifies suppliers instantly, and eliminates the manual re-entry of agreed scopes into new works orders.
5. Advanced Communication, Linking & Task Consolidation
Centralising communication prevents task duplication and keeps all estate stakeholders informed throughout an incident's lifecycle.
Combine & Link Requests: Merge duplicate tickets raised by multiple residents regarding the same communal issue (e.g., three reports for the same broken access gate) into a single master request.
Why: Eliminates administrative clutter and allows property managers to update or close multiple related resident tickets in one action.
Add Posting (Broadcast Bulletins): Generate estate or stairwell-specific notices directly from an active request, with optional push notifications and urgent flags.
Why: Delivers proactive, targeted communication to all affected occupants at once, drastically reducing repetitive inbound call volumes.
Contractor Portal Interaction: Contractors submit operational commentary, request variations, confirm completion, and upload job sheets or invoices directly inside the ticket portal.
Why: Keeps operational dialogue and supporting completion evidence centralised on the task record rather than scattered across external emails.
Batch Completion & Sign-Off: Complete combined requests simultaneously, issuing a standardised resolution message to all linked residents.
Why: Closes the loop with every reporting occupant while maintaining a clean, auditable closure history.
6. Verification, Monitoring & The Operational Audit Trail
Real-time operational dashboards track active requests across estates and portfolios to maintain full service accountability.
Request Status Key:
🟢 Green (Completed / Closed): Work verified, resolved, and signed off with complete documentation.
🟠 Amber / Orange (In Progress / Within SLA): Active request or works order within valid operational target dates.
🔴 Red (Late / Overdue / Escalated): Target action date exceeded, resident update overdue, or contractor deadline missed.
❓ Question Mark (Unassigned / Unacknowledged): Ticket logged but unassigned to an owner or lacking initial triage.
Why: Provides an instant visual snapshot across portfolios, enabling teams to spot stalled jobs and communication bottlenecks before leaseholders escalate complaints.
Contractor Performance Tracking: Monitor contractor response times, completion rates against target dates, and invoice accuracy per works order.
Why: Supplies verifiable performance data for supplier reviews, retendering exercises, and client reporting.
The Operational Golden Thread: Every completed request permanently archives the full conversation history, status updates, contractor job sheets, and resident communications.
Why: Provides an irrefutable historical record to defend service charge challenges, support insurance claims, and demonstrate proactive management during regulatory audits.