From Form to Loan Officer: What Should Happen

The sequence of events we want, from a member submitting a form to a loan officer picking up the phone.

From
Jon Dmytro, BEVEL
Date
August 24, 2026
Purpose
Agree on the target sequence first. Gaps between this and what happens today are a separate conversation.

The sequence

1

Member completes a form Member

Where
Their employer's BEVEL benefit website
Which form
Purchase, Refinance or Selling — or the dependent version of any of those
Data captured
Name, email, phone, current address, and the answers for their program: timeline, income, credit, down payment, price range, occupancy, and either the subject property or the area they want to buy in
2

Submission is recorded on their employer's board Automatic

Data carried
Everything the member answered
Sorted into
Employee submission, dependent submission, or referral
3

A deal is created in Deal Triage Automatic

Data carried
Everything from step 2, plus program type (purchase, refinance or selling) and whether they are the employee or a dependent
Not included
Referrals. Those stay on the employer's board and do not become deals
4

A member record is created in Member Workflow Automatic

Data carried
Everything from step 3 — contact details, program, and every financial and property answer
Status
New
5

Member gets a welcome email from BEVEL

To
The member
From
support@gobevel.com
Content
Branded welcome, wording matched to their program. Confirms we have their request and tells them what happens next
6

BEVEL support is notified a new member has arrived

To
support@gobevel.com
Content
Member name, employer, program type, employee or dependent, contact details and their key answers — enough to review without opening the board
7

Support reviews the member and selects the lender Manual

Who
Whoever is manning support@gobevel.com
Action
Reviews the submission and sets the lender — today, Nations Lending — on the Member Workflow board
Why manual
We want this to stay a deliberate human decision
8

Support receives the lender notification, with an Assign MLO button

To
support@gobevel.com
Content
A short summary of the member — enough to sanity-check the file, not the full record
Action in email
An "Assign MLO" button
9

Support assigns the loan officer Manual

Action
Clicks the button, which opens a form, and enters which MLO is being assigned — name and contact details, for example Justin Hominsky
Result
Submitting that form is what advances the member
10

The loan officer receives the member's full file

To
The assigned MLO
From / CC
support@gobevel.com, copied to support@gobevel.com
Content
Everything the member submitted — contact details, program, timeline, financial answers, and the property or target area — so the MLO can open the conversation already informed
11

The member is told who their loan officer is

To
The member
From
support@gobevel.com
Content
Branded template: you have been matched with your BEVEL-approved mortgage professional. Names the MLO and gives their contact details, so the member recognises the name when the phone rings
Timing
Same moment as step 10
12

Member status advances Automatic

Changes
New → Request for Pre-Approval
13

The loan officer contacts the member Lender

Note
The handoff is complete. Everything past this point is a separate phase

Two things that sit outside this sequence

Referrals. When an employee refers a family member, that submission stays on the employer's board. It does not create a deal and does not enter this sequence. The only thing it triggers is a thank-you back to the employee who made the referral.

Dependents. A dependent follows this exact same sequence. The only difference is that their record is flagged as a dependent rather than the employee, and we keep the name of the employee they belong to.

Summary of emails

Two manual steps: selecting the lender (step 7) and assigning the MLO (step 9). Everything else runs on its own.