Monday CRM Setup for Mortgage Brokers

A monday CRM implementation for a brokerage turns monday’s flexible boards into one file workflow, where each borrower has one record and each loan file has one owner. Most of the work is design. You decide which boards hold clients and files and how they connect. You also decide who can see each board and which automations move a file along. Test that design on sample files before launch, because a board that looks right can still leak access or drop an assignment.

Set the Monday CRM Implementation Scope

Start by writing down the client and deal tasks monday CRM will own. For most brokerages that means borrower and referrer contact details and one deal per loan file. It also covers file stages, tasks, reminders and each client’s email history. Lodgement, lender assessment and commission reconciliation stay in their own systems. Track My Trail reads the aggregator’s commission reports beside the CRM, and its Commission Verification matches each upfront payment to the trail that should follow within two months.

Confirm three prerequisites before you build anything:

Product entitlement. monday CRM is sold separately from monday’s work management product, on the Basic, Standard, Pro and Ultimate plans. The monday CRM pricing page bills per seat from three users, and Ultimate is the new name for the Enterprise tier. Pick the plan after you know which permission and automation features the brokerage needs, because several start at Pro or Ultimate.
Administrator access. Name one account admin and a backup. The admin creates boards, sets board owners and manages users and guests.
Sample data. Prepare invented borrower files that cover a purchase, a refinance, a joint application, a company borrower and a declined file. Real client data enters only after the acceptance tests pass.

Define the launch outcome in testable terms. For example, every new enquiry creates one contact and one deal, and the deal has an owner. Each stage change runs its automation, and every lodged file carries a confirmed aggregator reference. If an implementation partner is doing the build, put the same outcome in the CRM implementation agreement as the acceptance terms.

Keep CRM boards separate from general task and project boards. Office tasks, marketing calendars and team projects belong in work management boards that never hold client details. A client name typed into a project board becomes a second, unmanaged client record.

Build Boards Around Borrowers and Files

Use one board for each kind of record and connect them with the Connect Boards column. That column links an item to items on another board, and the Mirror column then shows the linked item’s details, such as a borrower’s phone number on the deal.

Board	One item is	Columns to include	Connects to
Contacts	One person	Item ID, name, email, phone, owner, consent status	Deals, Consents
Companies	One company or trust that borrows	Item ID, entity name, ABN, directors or trustees	Contacts, Deals
Deals	One loan file	Item ID, stage, lender, loan amount, settlement date, owner, aggregator reference	Contacts, Companies, Consents
Consents	One consent event	Consent type, notice version, how it was given, recorded by	Contacts, Deals

Here is a hypothetical file. Ana and Luis Moreno are buying their first home together. Each has an item on the Contacts board.

The Moreno purchase is one item on the Deals board, connected to both contacts. Mirror columns on the deal show their email addresses and phone numbers. A Consents item records their privacy consent and links to both contacts and the deal.

Identifiers, Required Details and Ownership

Give every record a unique identifier with the Item ID column. monday generates the number automatically. Its custom key setting adds a prefix, so client items can read CL and deal items DL. Put the client’s Item ID in each deal’s name, so staff can match a file to its borrower without relying on a name.

Make the required details hard to skip. Use a monday form with required questions for new enquiries, so every enquiry arrives with a name, email, phone and consent answer. On the Deals board, add a File complete status that the processor sets only after checking the lender, loan amount, purpose and borrower links.

Set ownership with a People column on each board. The broker who owns the client relationship is the owner of the contact and of every deal for that client. Add a separate Stage owner column on the Deals board for the person responsible for the current stage.

Stop Multiple Boards Becoming Conflicting Records

Duplicates usually come from a second board holding client details. Apply these checks:

Keep one Contacts board. Every other board links to it with a Connect Boards column and never stores its own copy of a client’s email or phone.
Search the Contacts board by email before creating a client by hand.
Remember the import rule. When you import from Excel into monday CRM, you can choose the Phone column to match existing items. An item whose phone number matches is then replaced with the imported details, so check phone numbers before importing.
Review the Contacts board each week for two items with the same email, and merge them before either one gains a new deal.

Control Permissions and Automations

Set access at the board first, then narrow it with item and column permissions. monday’s permissions guide and board articles set out these controls:

A main board is visible to every team member in the account. Use it only for boards with no client details, such as a lender list.
A private board is visible only to the members invited to it, and guests cannot join a private board. Use private boards for Contacts, Companies, Deals and Consents.
A shareable board can include guests from outside the account. Use it for an external participant, such as a referrer or solicitor, and copy across only the items that person needs.
On Pro and above, a board can let non-owners view the board but edit only the items assigned to them. Use it so brokers edit only their own files.
On Ultimate, item view permissions can limit a user to the items they created or are assigned to. Use it when brokers must not see each other’s clients at all.
A column can restrict who views it or who edits it, but not both on the same column.

Apply them by role. Brokers edit only the deals assigned to them, and on Ultimate they see only those deals. Processors edit every deal at their stages and see the Files column. External participants never join the Contacts or Deals boards.

Automations With Triggers and Owners

Write down each automation’s trigger and condition with the result you expect. Then name the person who fixes it when it fails. Plan limits apply. The pricing page lists 250 automation actions a month on Standard and 25,000 on Pro, and each run of an automation uses actions.

Automation	Trigger and condition	Expected result	Owner when it fails
Assign new enquiries	A form creates a deal and the referral source is Website	The deal’s owner is set to the broker on the website roster	Administrator
Lodgement check	Stage changes to Lodged and File complete is not Done	The stage owner receives a notification and the stage returns to Fact find	Processor
Conditional approval reminder	Stage changes to Conditional approval	The broker receives a task to collect the outstanding conditions	Broker who owns the deal
Settlement reminder	The settlement date arrives	The owner and processor are notified to confirm settlement	Processor

Check failures in Run history. It shows when each automation ran and whether it is in progress, failed or succeeded. It keeps only the past 10 days. The automation’s owner checks it each week, so a failure is found before the record disappears.

Follow one file through the connected boards to check that consent, access and responsibility stay with it. The Moreno file shows the path.

Enquiry consent. The Morenos complete the enquiry form, which creates their contacts, a deal and a Consents item. The Consents item records the version of the privacy collection notice they saw and how they agreed.
Document access. Identity documents and payslips go into the Files column on the Moreno deal. Only the board’s members can open them, and on Ultimate the Files column can be restricted to the broker and processor.
File-stage responsibility. Each stage names a Stage owner. When the file moves from Fact find to Lodged, the stage owner changes from the broker to the processor.
Lodgement handoff. The broker lodges the application in the aggregator CRM and enters the aggregator’s lodgement reference on the deal. The deal’s Handoff status changes to Sent.

Confirm Receipt and Reconcile the Result

The handoff is a staff step that the deal records. Treat it as complete only when the aggregator’s system confirms receipt. The processor opens the application in the aggregator CRM, checks that the lodgement reference, lender and loan amount match the deal, and changes Handoff status from Sent to Confirmed.

The processor is also the person who reconciles. Each week they filter the Deals board for files at Lodged with Handoff status still at Sent. A file with no matching application in the aggregator CRM goes back to its broker, who lodges or corrects it and updates the reference. When Handoff status reads Confirmed on every lodged file, the two systems agree.

Accept and Launch the Broker Workflow

Run the acceptance checks in this order on sample files, then go live in stages.

Sample import. Import the invented borrower list from Excel into monday CRM. Confirm the item count matches the spreadsheet and the import summary reports no unexpected replacements.
Restricted-user checks. Sign in as a test broker, a test processor and a test guest. Each sees and edits only what the role allows, and the guest cannot find the Contacts or Deals boards.
Duplicate-file handling. Create a second contact with an existing client’s email and a second deal for the same file. Confirm the weekly review finds both and the merge keeps every connected deal and consent item.
Automation failure checks. Break one automation on purpose, such as by removing the roster broker. Confirm Run history shows the failure and the named owner fixes it.
Export reconciliation. Export the Contacts, Deals and Consents boards to Excel. Each board export covers up to 10,000 items and includes table views only. Confirm every deal and consent row carries the Item ID of the right borrower.
Controlled go-live. Start with one broker’s new enquiries for the first few files, then add the other brokers once those files have moved through each stage without a fix.

If you are moving existing clients from another system, finish these checks before the real import, then use a CRM migration plan for the cutover.

Fix Common Faults

Symptom	Diagnostic check	Corrective action	Recovery confirmed when
A Mirror column on a deal is blank	Open the deal’s Connect Boards column and check the linked contact still exists on the Contacts board	Relink the deal to the correct contact, or restore the deleted contact	The Mirror column shows the borrower’s details again
A new enquiry has no owner	Open Run history for the assignment automation and read the failed run	Correct the condition or roster, check the monthly action limit, then assign the owner by hand	A test enquiry is assigned to the right broker
A broker can see another broker’s clients	Check the board type and item view permissions, then list the board’s members and guests	Make the board private, remove the extra members and apply item view permissions on Ultimate	Signed in as the test broker, only their own deals appear

First-File Support and Staff Practice

Name one person, usually the administrator, to sit with each broker while they create their first live file. That person fixes anything the acceptance checks missed and records each fix. Before go-live, every broker and processor works one invented file through the real boards and automations, from enquiry form to Confirmed handoff. Use CRM training for later refreshers, built on the same implemented workflow and the faults staff actually meet.