Status lane
Open requests
Client needs that have been captured but still require review, routing, or additional context.
Status visibility
Clients should never wonder what happened after intake.
The status layer is designed to show what is open, what is moving, what is blocked, who owns the next action, and what evidence confirms progress.
Status model
Every request needs a visible posture.
Status lane
Active work
Requests with an assigned owner, a clear next action, and an execution path underway.
Status lane
Waiting on decision
Items that cannot move responsibly until a client, operator, or executive decision is made.
Status lane
Blocked work
Requests slowed by missing access, unclear authority, dependency risk, or incomplete information.
Status lane
Completed outcomes
Closed work with a visible result, responsible owner, and enough evidence to support review.
Status lane
Follow-up required
Completed or paused work that created a new decision, opportunity, or support need.
Dashboard preview
Status becomes useful when it tells the client what happens next.
Next action
A status view should create confidence and accountability.
The Business Portal status model keeps the request, owner, next action, and progress evidence in the same operating path.