Sub-Statuses (Tags)

Your own categories of labels that tag a file with finer detail than its status.

Platform Settings → File Substatus (Manager role) holds your sub-statuses, often called tags. They add detail when a file status alone isn't specific enough, and work like labels whatever the file's status is.

How they're organized

Sub-statuses sit in categories you control. The platform ships with several categories and labels you can edit, remove or add to. For example:

  • Lead management: hot lead, cold lead, comparing offers, waiting on counter-offer, unreachable
  • Underwriting: needs manager review, valuation issue, pending legal review, pending inspection, pending conditions
  • Your own categories, such as denial reasons or funding source

A file can carry several sub-statuses at once.

What they drive

  • Pipeline filters and reports: sort, filter and export by any tag.
  • Automation: checking a sub-status can trigger tasks, e-mails, webhooks or a status change. See Automation Rules.
  • Conditional documents and workflow steps: a required document or step can appear only when a sub-status is set.
👍

Tags before statuses

When "Processing" isn't specific enough, add a sub-status rather than another file status. Your pipeline stays readable, and statuses stay reserved for the stages you report on.

🚧

Change carefully once rules depend on them

As with statuses, rules and conditions point at sub-statuses. Renaming or removing one that a rule uses can stop that rule from firing.

Full detail: in LendingWise, open Loan Origination → User Guide → Workflow, File Status & Workflow Actions.


Did this page help you?