IRM365
Approvals & Audit

Approval workflow software for real estate teams.

Approval workflow software for real estate teams: IRM365 routes lead disqualification and MOU activation through approval queues, then records business-data changes with searchable before-and-after audit history.

Feature Workflow

What this module helps your team do

A quick map before the detailed product proof. Jump to the area that matters most.

01Approval Queue

Route consequential actions through a second reviewer.

Approvals keep a second pair of eyes on consequential actions through four focused queues: Needs My Decision, Team Queue, My Requests, and History. Today, lead disqualification (Lost, Unqualified, Junk) and MOU activation go through approval, and the record stays unchanged until someone decides.

  • Each row shows the decision asked for, the record, who raised it, how long it has waited, and when it is due
  • Due dates follow the requester's priority — same day, next day, three days, or a week — and turn red once overdue
  • Approve runs the deferred action immediately and notifies the requester
  • Reject needs a written reason; the record stays unchanged
Approval RequestsOldest first
Needs My DecisionTeam QueueMy RequestsHistory
  • Mark as UnqualifiedLEAD-IM-13550 · raised by Kyle PaulanDue in 1 day
  • MOU activationMOU-IM-0318 · raised by Waleed AshrafDue today
  • Mark as JunkLEAD-IM-13552 · raised by Farzana SiddiqOverdue
02Decision Flow

Approve, reject, or cancel with a reason.

Reviewers see the requested action, the requester's notes, and evidence captured when the request was raised. Lead disqualification reviews show lifecycle gaps, budget and preferences, activity outcomes, contradictions, and anything changed since; MOU activation reviews show parties, property, dates, amount, and commission gaps. Whoever raised a request can cancel it while it is still waiting.

  • The requester can cancel a waiting request with a required reason, from the request page or the lead's Pending flag; nothing on the record changes
  • MOU activation separates draft preparation from financial commitment
  • A request sitting with the wrong reviewer can be reassigned by an administrator
  • Approval request pages are available in English and Arabic
Mark as JunkLEAD-IM-13552
Reviewer
Approve DisqualificationKeep Lead Active

Rejecting needs a written reason; the requester can raise a corrected request.

Requester
Cancel requestReason required · record unchanged
Customer called back this morning
Request pages in English and Arabic
03Audit Log

See who changed what, when, and from where.

IRM365 audit logs record business-data changes across records and settings. Each row names its record — "Samina Fazal · Lead" with its reference, such as LEAD-IM-13550 — and opens into a before → after view with the record's own history beside it, so you can see what else happened without returning to the list.

  • Search a reference such as LEAD-IM-13550 to find every change to that record
  • Linked records show real names instead of ids; where you lack permission, they read Restricted record
  • Updates show both sides, such as Draft → Approved; creates and deletes list the values as they stood
  • Request and database details sit in a Technical context panel; filter by date, actor, record type, event, or record
  • Lead, opportunity, contract, and MOU pages have a History button with a timeline of every change, for people with the View record history permission
Audit LogsSearch a reference
LEAD-IM-13550
  • Samina Fazal · LeadLEAD-IM-13550Updated
What changed
Status Qualified → Nurturing
Owner Kyle Paulan, not an id
Record history
This entry
Earlier update
Created
Capabilities

Control and traceability

Approvals prevent unilateral high-impact actions; audit logs reconstruct what changed after the action is complete.

Approval decisions

Reviewers approve or reject according to permission and routing rules; the requester can cancel a waiting request with a reason.

Sensitive actions

Lead disqualification (Lost, Unqualified, Junk) and MOU activation are approved by a second person before they take effect.

Before/after diffs

Audit entries show each update as before → after, with linked records by name.

Permission scoped

Approval queues and audit logs respect role, permission, and hierarchy scope.

Notifications

Requesters are notified when their request is decided, whether it is approved or rejected.

Record history

Lead, opportunity, contract, and MOU pages have a History button with a timeline of every change.

FAQ

Frequently asked questions

Two actions go through approval today: lead disqualification (Lost, Unqualified, or Junk) and MOU activation. The record stays unchanged until a reviewer approves or rejects the request, so a second person checks the decision before it takes effect.

Continue the workflow

IRM365 modules are connected. Explore the next capabilities that usually sit beside this feature in a real brokerage workflow.

Get started

Ready to close more deals with less effort?

Join UAE real estate teams who run their entire business — leads, deals, contracts, and finance — from one platform. No annual contract.

Personalized walkthrough
30-minute live demo
No annual contract — cancel anytime
GDPR-ready
TLS 1.2
AES-256
Audit trail