PHX Money Store Operating SystemBranch ExecutionConditionsTraining Loop

From scattered effort to a clean execution machine.

A role-based operating system that helps PHX Money Store move files from lead to closing while teaching each user what to see, what to do, what to create, and how their data helps the next role act with purpose.

North Star

Every action creates clean data for the next role. Every complex file teaches the branch how to close the next deal better.

Branch Operating Map

The system should show how roles create data, data creates awareness, awareness creates cleaner next steps, and outcomes create reusable training.

Roles

1
Need: Responsibilities blur during pressure.
Solution: Each role has a lane, view, input, output, and escalation trigger.
Outcome: Cleaner handoffs and less duplication.

Conditions

2
Need: Conditions live in email instead of structured rows.
Solution: Each condition gets owner, reviewer, evidence, status, blocker, and clearing logic.
Outcome: No more attached = cleared confusion.

Communication

3
Need: Warmth, accuracy, and escalation collide.
Solution: Separate borrower, agent, escrow, internal, UW, rush, and training lanes.
Outcome: Everyone hears the right thing at the right time.

Timeline

4
Need: Milestones are not tied to blockers.
Solution: Every condition tags ICD, UW, CTC, docs, funding, or post-close impact.
Outcome: Rushes become factual and prioritized.

Foresight

5
Need: The branch reacts after problems appear.
Solution: Predictive checklists fire based on borrower/file complexity.
Outcome: Fewer underwriting surprises.

Training Loop

6
Need: Experience disappears after each file.
Solution: Each exception creates a trigger, template, training note, or checklist.
Outcome: PHX Money Store gets smarter every file.

Jio: Communication Lead

High client exposure

Role View

Need

Needs approved language and task clarity so she can communicate confidently while learning live files.

Solution

Show borrower-facing doc requests, safe talking points, follow-up cadence, and escalation triggers.

Data Created

  • Borrower updates
  • Realtor/escrow updates
  • Doc request history
  • Follow-up timestamps

Data Consumed

  • Kyler's sufficiency notes
  • Nate's strategy language
  • Victoria's milestone status
  • Kathy's context

Outcome

The file feels concierge while the back-end stays controlled.

Guardrails

Owns

  • Communication cadence
  • Doc chasing
  • Receipt confirmation
  • Friday status updates

Avoids

  • Unapproved guideline answers
  • Calling partial docs complete
  • Promising CTC or closing

Lifecycle Timeline

Each phase must pass clean data forward. That is the branch operating spine.

1Kathy / Jio

Lead

Goal: Capture story, source, urgency, and contact speed.

Data: Referral source, lead type, first-touch timestamp, desired timeline.

Risk: Warmth without structure creates later cleanup.

2Nate

Strategy

Goal: Identify product path and likely complexity.

Data: Loan type, flags, product fit, predictive doc checklist.

Risk: Bad assumptions become conditions later.

3Kyler

Setup

Goal: Build file, price, disclose, and verify front-end facts.

Data: Credit, income, assets, property, pricing, disclosure readiness.

Risk: Documents uploaded without sufficiency review.

4Victoria

Processing

Goal: Validate completeness and prepare clean UW submission.

Data: Milestones, title, HOI, appraisal, VOE, processing blockers.

Risk: Processing becomes a rediscovery phase.

5UW / Victoria

Underwriting

Goal: Clear conditions with evidence and logic.

Data: Condition rows, evidence map, reviewer status, clearing notes.

Risk: Email piles replace ownership.

6Closer / Hannah

Closing

Goal: Protect ICD, CD, docs, signing, and funding timeline.

Data: Milestone blockers, rush path, escrow/title status, due dates.

Risk: Rushes are too late or too vague.

7Kathy / Jio / Nate

Closed + Learn

Goal: Thank, nurture, and convert lessons into reusable knowledge.

Data: Close notes, partner feedback, training triggers, template updates.

Risk: PHX Money Store survives the file but learns nothing reusable.

Conditions Command Center

Every condition becomes a structured work item with owner, reviewer, evidence, blocker, status, and clearing logic.

High RiskCTC

Pricing / Product

Non-QM rate-and-term refinance cash back exceeds allowed tolerance.

Entity: Subject refinance

Required Evidence

Correct cash back to program tolerance before CTC.

Ownership

Owner: Kyler

Reviewer: Nate / Processor

Needs Review

Next Action

Rework pricing/cash-to-close and confirm before resubmission.

Lesson

Cash-back tolerance should be validated before UW submission on Non-QM R/T refinances.

High RiskCTC

Mortgage / Servicer

Transferred servicer must be verified with current statement and escrow status.

Entity: 639 E Kino / Selene

Required Evidence

Current statement showing servicer, escrow status, payment, account, and current status.

Ownership

Owner: Jio collects / Kyler reviews

Reviewer: Processor / UW

Partial / Insufficient

Next Action

Do not mark complete with prior servicer summary unless processor accepts substitute.

Lesson

Transferred servicer means current servicer must be verified, not assumed.

High RiskCTC / Docs

Insurance / HOI

Updated blanket HOI policy needed for multiple properties.

Entity: Blanket policy

Required Evidence

Current policy, property schedule, effective dates, mortgagee clauses, and premium status.

Ownership

Owner: Kyler / Insurance Agent

Reviewer: Victoria / Processor

Requested from Third Party

Next Action

Use address-level coverage matrix before calling it complete.

Lesson

Blanket policy requires address-level verification.

Medium RiskUW / CTC

Income / Business

CPA letter needed for ownership percentage and length of ownership.

Entity: Business entities

Required Evidence

CPA letter covering ownership %, length of ownership, and business existence support if needed.

Ownership

Owner: Jio borrower/CPA follow-up

Reviewer: Nate / Kyler / Processor

Requested from Third Party

Next Action

Send CPA template and track each business separately.

Lesson

Entity-heavy files need CPA letter trigger upfront.

High RiskUW / CTC

Assets / Deposits

Large business deposits require source documentation.

Entity: Business account

Required Evidence

Each large deposit needs separate source docs and acceptance status.

Ownership

Owner: Jio collects / Kyler reviews

Reviewer: Processor / UW

Not Started

Next Action

Split into individual deposit rows with source, evidence, and acceptance status.

Lesson

Never use one generic 'large deposits' task for multiple deposits.

High RiskICD

Escrow / Closing Readiness

File not ready for ICD because payoff and updated fees are missing.

Entity: Escrow / subject refinance

Required Evidence

Payoff, updated fees, proposed insured, and chain of title as applicable.

Ownership

Owner: Victoria / Escrow

Reviewer: Processor / Disclosures

Critical Blocker

Next Action

Escalate if not received by deadline. Hannah routes ICD rush to Disclosure Manager when facts are ready.

Lesson

ICD blockers need separate red-lane visibility from general conditions.

Communication Channels

Communication gets its own lanes so client warmth, technical accuracy, and escalation do not collide.

Borrower

Jio

Data: Simple doc asks, receipt confirmation, next steps.

Guardrail: No unapproved guideline or pricing promises.

Realtor / Agent

Jio + Kathy

Data: Milestone status, closing confidence, blockers framed simply.

Guardrail: Do not expose internal chaos.

Escrow / Title

Victoria + Jio

Data: Payoff, fees, title commitment, proposed insured, signing/funding details.

Guardrail: Tie every request to milestone impact.

Internal Strategy

Nate + Kyler

Data: Product path, risk flags, sufficiency decisions, escalation logic.

Guardrail: Do not let strategy live only in chat, memory, or email.

Processing / UW

Victoria + Kyler

Data: Condition packet, evidence map, clearing logic, document location.

Guardrail: Submitted means packaged, not merely uploaded.

Rush

Hannah

Data: Deadline, blocker, requested action, business reason, manager path.

Guardrail: No vague rushes.

Training

Nate

Data: Trigger, mistake, prevention, template update.

Guardrail: Every complex file must teach the next one.

Predictive Doc Triggers

The system should generate likely documentation needs before underwriting asks.

If: Multiple financed properties

  • Current statement for each mortgage
  • 12-month history if not on credit
  • Current servicer verification
  • Escrow status
  • HOI/property tax status

If: Servicer transfer detected

  • Goodbye letter
  • Hello letter
  • Current servicer statement
  • Payment history across transfer
  • Proof payments continued

If: Blanket HOI policy

  • Full current policy
  • Property schedule
  • Effective dates
  • Mortgagee clauses
  • Premium paid status
  • Address-level coverage matrix

If: Self-employed / bank statement / entity file

  • Business narratives
  • CPA letter
  • Ownership percentage
  • Length of ownership
  • Entity docs
  • Large deposit map

If: Private mortgage / VOM

  • Note
  • VOM
  • 12-month canceled checks or bank debit proof
  • Payoff demand
  • Contact information
  • LOX if evidence is nontraditional

Data That Makes the System Smarter

Every field should either move the current file or teach the next file how to move faster.

Contact Speed

Measures how fast new opportunities receive a meaningful first touch.

Jio / KathyImproves: Lead conversion

Condition Aging

Shows how long each condition sits without meaningful movement.

Jio / Kyler / VictoriaImproves: CTC speed

Partial Doc Rate

Tracks docs received but not sufficient to clear conditions.

KylerImproves: Upfront doc quality

Predictive Trigger Hit Rate

Tracks conditions the system predicted before underwriting asked.

NateImproves: Foresight

Rush Quality Score

Measures whether rushes include facts, blocker, deadline, and requested action.

HannahImproves: Escalation success

Training Capture

Tracks whether each complex file created a reusable lesson, template, or checklist.

NateImproves: Team capacity

Minimum Viable Build

Build this in phases so PHX Money Store can use it immediately while it grows capacity.

Phase 1: Visual OS

  • Role views
  • Lifecycle timeline
  • Communication lanes
  • Daily command board

Phase 2: Conditions

  • Condition rows
  • Evidence map
  • Milestone blockers
  • Owner/reviewer/status

Phase 3: Learning

  • Predictive triggers
  • Template library
  • Training notes
  • Performance metrics

Operating Rule

A condition is not complete because a document was attached. It is complete only when the correct reviewer marks it accepted, underwriting cleared, or waived.