The real estate brokerage operating guide

Speaking the language of this industry

• MLS (multiple listing service): The regional database of active and sold listings that brokerages contribute to and draw comparable-sales data from — the system of record for listing data itself.
• Listing agreement: The contract between a seller and the brokerage authorizing the brokerage to market and sell the property, including the commission the seller agrees to pay.
• Commission split: How a transaction's gross commission divides between the brokerage and the agent, and between agents when more than one is involved — set by the brokerage's compensation plan.
• Referral fee: A portion of a commission paid to another agent or brokerage for referring the client, agreed before the transaction closes.
• Earnest money / escrow: Funds a buyer deposits to show good faith on an offer, held by a title company, escrow company, or brokerage trust account — not by The Forge.
• Transaction coordinator (TC): The person responsible for tracking a transaction's paperwork, deadlines, and milestones from contract to closing, whether an in-house role or a contracted service.
• Contingency: A condition in a purchase contract — financing, inspection, appraisal — that must be satisfied or waived by a deadline for the transaction to proceed.
• Days on market (DOM): How long a listing has been active without going under contract, tracked per listing and rolled up as an office or brokerage average.
• Errors & omissions (E&O) insurance: Liability coverage most brokerages and agents carry against claims of a mistake or omission in representing a client — a policy tracked on the agent record, not issued by The Forge.
• Dual agency / designated agency: State-specific rules governing how a brokerage or agent may represent both the buyer and seller in the same transaction, including required disclosures.

Signs you're outgrowing your current setup

• A web lead goes two hours without a response because no one was clearly assigned
• Agents compare notes and suspect certain teammates always get the better leads
• A commission figure is not confirmed until the closing statement lands from the title company
• No one can say which ad campaign actually produced last quarter's closed deals
• A listing goes live before the compliance review email chain is ever finished
• A new agent starts calling on leads before their MLS access and license are confirmed
• A client who closed eighteen months ago has not heard from the brokerage since
• The broker-owner's view of a second office comes from a phone call, not a dashboard
• A departing agent's leads, pipeline, and client history leave with them because none of it lived on a shared record
• A missed call from a lead goes unanswered because no one was watching the queue
• A comment or DM on a listing post never makes it onto anyone's follow-up list

Other places brokerages lose time and margin

• Agent licensing and onboarding steps get missed because nothing tracks them on a schedule — Proposed, not yet verified: A new agent's onboarding checklist — license verification, MLS access, e-signature setup, brand and system training — and every agent's license and continuing-education expiration are tracked against a due date, with a reminder task queued before something lapses (it sends once an email or SMS provider is connected).
• A closing happens and the client never hears from the brokerage again until they sell or buy — Proposed, not yet verified: Closed transactions enter a scheduled post-close and anniversary follow-up sequence — a check-in, a home-anniversary touch, a referral ask — so past clients stay a source of repeat and referral business instead of falling out of contact the day after closing.
• A broker-owner with more than one office cannot see production, pipeline, or compliance across all of them — Proposed, not yet verified: Lead volume, pipeline, closed production, and pending compliance approvals roll up across every office and team into one view, so the broker-owner sees the whole operation instead of checking in with each office manager separately.

Information The Forge tracks

• Contact / household: A buyer, seller, or past client, carrying lead source, communication history, saved searches, and the properties and transactions tied to them.
• Property: A physical address tracked across its history with the brokerage — prior listings, prior transactions, and current status.
• Listing: An active or past listing agreement, carrying pricing, disclosures, marketing approval status, and days-on-market.
• Transaction: A deal from accepted offer to closing, carrying its milestones, deadlines, parties, and linked commission.
• Transaction milestone: A required step or deadline within a transaction — inspection, appraisal, financing contingency, title, closing — tracked to completion or escalation.
• Commission: The forecasted and actual commission for a transaction, carrying gross amount, agent and team splits, referral fees, and reconciliation status.
• Lead: An inbound inquiry before it converts to an active buyer or seller relationship, carrying source, routing history, and response time.
• Vendor: A service provider the brokerage or its agents regularly work with — inspectors, lenders, photographers, stagers — tracked by category and relationship.

Who can see and do what

• Broker-Owner / Principal Broker — Required access boundary — not yet verified: Sees production, pipeline, and compliance status across every office and team; Required access boundary — not yet verified: Sees commission forecasts and reconciliation for the full brokerage; Required access boundary — not yet verified: Configures lead-routing rules, approval requirements, and compensation plans; Required access boundary — not yet verified: Reviews license and continuing-education status across all agents
• Team Lead — Required access boundary — not yet verified: Sees pipeline, leads, and production for their own team; Required access boundary — not yet verified: Approves listing and advertising submissions for their team's agents; Required access boundary — not yet verified: Cannot view commission or compliance detail for agents outside their team
• Agent — Required access boundary — not yet verified: Sees their own leads, pipeline, transactions, and past clients by default; Required access boundary — not yet verified: Sees their own commission forecast and history, not other agents' figures; Required access boundary — not yet verified: Cannot access other agents' leads or client records unless explicitly shared
• Transaction Coordinator — Required access boundary — not yet verified: Sees milestone and deadline status for the transactions they are assigned to; Required access boundary — not yet verified: Updates transaction status and flags stalled or at-risk milestones; Required access boundary — not yet verified: Does not see commission splits or agent compensation figures
• Office Admin — Required access boundary — not yet verified: Sees office-wide lead intake, listing approval queue, and onboarding checklists; Required access boundary — not yet verified: Manages agent onboarding tasks and license/CE expiration tracking; Required access boundary — not yet verified: Cannot approve commission disbursement or change compensation plans
• Marketing Coordinator — Required access boundary — not yet verified: Sees campaign spend, lead source attribution, and listing marketing status; Required access boundary — not yet verified: Submits listings and ad creative into the compliance approval queue; Required access boundary — not yet verified: Does not see individual agent commission or transaction financial detail

What this industry has to stay ahead of

• Fair-housing compliance in advertising, lead routing, and client communication — the brokerage's authorized professionals set and apply the standard; The Forge does not make fair-housing determinations itself.
• State real-estate licensing and continuing-education requirements for the brokerage and every agent — tracked on the agent record, issued and renewed outside The Forge.
• Agency-disclosure and dual/designated-agency rules, which vary by state and must be presented to clients at the required point in the relationship.
• Escrow and trust-fund handling — earnest money and commission funds in transit are held by a title company, escrow company, or the brokerage's own trust account, never by The Forge.
• Advertising-review requirements set by state real-estate commissions, which a tracked approval workflow can support but does not certify compliance with.
• Referral-fee and anti-kickback considerations (including RESPA where applicable to a transaction), which the brokerage's compliance process determines — The Forge tracks the agreed fee, it does not evaluate its legality.
• Transaction-file and listing-record retention requirements, which vary by state real-estate commission and remain the brokerage's responsibility to satisfy.

What this looks like in a real week

An independent brokerage with 22 agents across two offices. Proposed, not yet verified: A buyer inquiry comes in through the brokerage website at 6:40pm. It is matched to an existing contact record from a prior search, routed to the on-duty agent under the office's rotation rule, and the agent is notified within two minutes — logged the same way every lead is, so no one on the team can say routing plays favorites. Meanwhile, a listing agent submits a new listing for compliance review before it goes live; the office manager approves the pricing and disclosure language the next morning, and the listing moves to active status on the MLS and the brokerage's marketing channels only after that approval is recorded. Three weeks later, that same buyer goes under contract on a different property — the projected commission (a 6% gross split three ways with a 25% referral fee to the original agent) shows up on the broker-owner's forecast the same day, well before the closing statement exists. As the transaction moves toward closing, the financing contingency deadline is six days out and no update has been logged, so it is flagged to the transaction coordinator instead of surfacing as a surprise the week of closing. On Monday morning, the broker-owner opens one dashboard: 31 active transactions across both offices, $184,000 in forecasted commission for the month, two listings still waiting on compliance approval, and one agent's license renewal due in three weeks.

What a typical launch looks like

• Contact, listing, and transaction data migration (Scope review required): Proposed, not yet verified: Existing contacts, active listings, open transactions, and closed-transaction history are migrated so the team starts with one current record instead of a blank system.
• MLS, transaction platform, and accounting integration configuration (Scope review required): Proposed, not yet verified: Connections to the MLS, transaction-management and e-signature platform, and accounting or payroll system are configured so information flows without duplicate entry.
• Workflow and compensation-plan configuration (Scope review required): Proposed, not yet verified: Lead-routing rules, listing and advertising approval requirements, commission-split and referral structures, and transaction-milestone deadlines are configured to match how the brokerage already operates.
• Agent and staff training, go-live (Scope review required): Proposed, not yet verified: Agents, team leads, transaction coordinators, and office staff are trained on their role-specific views before the brokerage cuts over from prior tools.

Brokerage requirements to review before expanding

• Proposed requirement, not established by a plan or add-on: Add an 'Additional location' for each new office opened, keeping production and approvals separated by office
• Proposed requirement, not established by a plan or add-on: Layer on advanced reporting for deeper commission and marketing-attribution breakdowns as agent count grows
• Proposed requirement, not established by a plan or add-on: Add advanced integrations for specialized back-office commission or accounting systems beyond the standard set
• Proposed requirement, not established by a plan or add-on: Formalize a marketing coordinator permission tier as campaign volume and listing count grow
• Proposed requirement, not established by a plan or add-on: Move to Forge Operations for cross-office and cross-brand executive reporting once the brokerage operates under multiple offices or brands

Frequently asked questions

• Does The Forge replace our MLS? — Keep the MLS for listing data, comparable sales and syndication. An MLS connection has not been verified for this proposed brokerage workflow; confirm supported handoffs before relying on one.
• Does The Forge replace our transaction management and e-signature platform? — Keep closing documents and signatures in your existing transaction platform. Transaction and milestone records require technical setup. A finished brokerage screen, deadline reminders and automatic transfer without re-entry have not been demonstrated.
• Does The Forge make fair-housing or legal compliance decisions? — The brokerage's authorized professionals make fair-housing and legal decisions. Listing and advertising approval tracking remains a proposed requirement to verify, not evidence of a working compliance process.
• Can each agent see only their own leads and pipeline? — Agent, team and office access separation has not been verified. Tenant isolation does not establish private agent records or commission visibility. Review and test the exact permissions before entering confidential information.
• Does The Forge automatically match commission statements to what was expected? — Native commission records exist behind the API, but a user-facing forecast, discrepancy-alert workflow and uploaded-statement matching are not established. Review recorded amounts in your existing commission system until the selected workflow is verified.
• What happens to our existing contact, listing, and transaction history? — Review the source data, supported import format and agreed migration scope before moving records. A complete listing and closed-transaction-history migration is not established by this proposed workflow.