Agent's daily playbook
on the Rebato platform.

Your dashboard is the home base. It is intentionally calm — four key numbers, a handful of quick-action links, and a sidebar that lets you jump to deeper screens. The header carries a small badge showing your sponsoring broker so you never lose track of which brokerage you are operating under (especially relevant if you ever hold sponsorships in multiple states).

Layout. Sidebar on the left (Dashboard / My listings / New listing / Clients / Offers / Inbox / Back to public site), main content on the right, header pinned with your sponsoring broker badge. The same shell wraps every /agent/* page so navigation stays predictable.

/agent/clients lists every active Buyer Broker Agreement on which you are the agent of record. Each row shows the buyer’s name, email, BBA status (signed / pending / expired), term-end date, and the timestamp when the BBA was signed. The list is sorted by term-end so the agreements closest to expiring float to the top.

When a buyer wants to tour a home, the system enforces the BBA Hard Gate — the buyer must have a signed, in-term BBA before any showing request goes through. If they do not, you (or the buyer) trigger a DocuSign BBA flow from the listing detail page; once the envelope returns signed, the showing endpoint becomes callable. Pre-NAR-settlement workarounds like “just show it once and we’ll sign later” are blocked at the database level — there is no path to bypass the gate.

Click a client row to drill down (v2 — for now the list view is read-only). The drill-down will show the BBA itself, every audit event tied to the buyer, every search query they ran, every showing they attended, and every offer you authored on their behalf. It becomes the single pane of glass for an agent-buyer relationship.

Term-end approaching? Renewal flow is a v2 feature. Today, the buyer signs a fresh BBA with a new envelope. The old BBA stays in the immutable audit log forever — you can always look back and prove what was in force on a given date, which is exactly what state regulators ask for in a complaint investigation.

/agent/offers shows every offer you authored — drafts, pending, countered, accepted, rejected, withdrawn. Each row shows the listing, the buyer (if you have BBA), the price, the contingencies, and the state machine transition log so you can see at a glance how negotiation is moving.

To draft a new offer, start from a listing detail page and click “Make an offer.” The form captures price, contingencies (financing / inspection / appraisal / sale-of-current), financing details, escalation clause if any, and expiration. The buyer must already have a signed BBA — without it, the “Make an offer” button is hidden.

Submitting the offer triggers the same compliance stack: Gate 8 (license recheck), Gate 7 (state policy resolver — picks up the offer-submission rules for the listing’s state), and Gate 9 (audit log row OFFER_SUBMITTED). If the listing is in a state with required disclosure forms attached to offers, the form blocks submission until those are also signed.

Counter-offer, accept, reject, and withdraw are all logged with state-machine transitions in offer_status_history. Invalid transitions (e.g., trying to accept a withdrawn offer) return a 422 with code INVALID_TRANSITION — there is no way to skip a step.

Once an offer is accepted, the closing saga auto-tracks: inspection → appraisal → title search → walk-through → close. Each milestone is its own event, its own audit log entry, and its own compliance check (e.g., title clearance, state-specific anti-flipping windows for resale).

Every sensitive action you take is logged. The log is hash-chained, append-only, and exported nightly to S3 Object Lock — a worm bucket that cannot be modified by even the most privileged DBA. This is what makes the platform legally defensible. If a regulator opens an investigation five years from now, we can reproduce exactly what happened on any given day.

For your own actions, every entry has actor_user_id = your_id. Compliance officers query this through /admin/compliance (most agents do not have access to the admin console — that is intentional). They see the full chain of BBA signings, agency disclosures, search queries, offer submissions, rebate calculations, and license verifications you triggered.

License expiry mid-transaction? The system pauses the transaction at the next sensitive action and notifies you and your sponsoring broker. You can still view your dashboard and read old data; you just cannot transact until the broker re-verifies and re-activates your sponsorship. The audit chain ensures the freeze itself is recorded, so we can prove that no unlicensed activity slipped through.