Give mortgage brokers a clear lender submission portal

Design around the broker's next action

Canadian broker research identifies paperwork help, technology, turnaround, and service as parts of the lender experience, but it does not prescribe one portal design. Ask brokers to complete a submission, answer a condition, and check status in a prototype. For each screen, label the action the broker can take and the person who will respond. Do not make brokers hunt through a dashboard for a simple acknowledgement or a clear request.

Keep one file ID and an item-level needs list

Create one lender file identifier at intake and retain the broker's own reference beside it. Track each requested item as not requested, requested, received, under review, accepted, or replaced, with a date and owner. A document upload is not the same as an accepted condition. Let the lender define its submission checklist by product and channel; do not imply there is a universal broker package or make a portal checklist decide credit eligibility.

Show status without exposing internal notes

Define a small set of broker-visible states such as received, incomplete, assigned, review in progress, decision communicated, conditions outstanding, closing coordination, and funded. Give every state an update source and accountable owner. Test access with separate broker firms and users, including assistants and reassigned files. Keep pricing deliberations, underwriting discussion, other borrowers, and private staff notes outside the broker view unless an approved policy explicitly makes an item shareable.

Pilot exceptions before inviting every broker

Test incomplete submissions, a duplicate file, a changed broker contact, a document uploaded to the wrong condition, and a portal outage. Confirm that each exception reaches a named lender employee and that the broker can see what to do while it is being resolved. Keep an alternate support route for urgent files. Record portal access, uploads, condition changes, and status messages so the lender can reconstruct the file's communication history.

WORKED EXAMPLE / ILLUSTRATIVE

A fictional broker submission journey

The example shows visible progress and ownership without exposing a borrower's confidential underwriting notes to the broker portal.

Before you put it to work

• Interview brokers about three tasks they repeat on live files.
• Confirm each displayed status has a reliable source and owner.
• Test access across two firms and reassigned broker users.
• Test incomplete, duplicate, and misfiled submissions.
• Review privacy, retention, and support requirements with compliance staff.

Portal design must follow the lender's privacy, security, retention, and access policies. Canadian federal privacy principles and provincial rules can apply; Quebec requires a separate Law 25 review. This is general information, not legal advice. Confirm requirements with your compliance counsel.