MX Checked
List with us

MX Checked previews — walk the whole site

This page is a preview tool. It links the rehearsal pages together so you can walk the whole site and see each page in the state you pick. The real site is built later. Nothing here is the real site.

Now showing: Nothing yet

Open this page on its own
Pick any story, page, or state below, and it opens here.

If a page does not appear in the frame, open it on its own — that link always works.

The conversations

Each conversation is one exchange between the chairs, walked in order: one chair sends, the next chair sees it and answers, and the first chair sees the answer. Every step names its chair first. You tap a step, and the page opens in the viewer above in the state the conversation needs. A step that needs a switch on the page says so in the words of the switch. A step that has no page in the set says so plainly, in a dashed box. Nothing is dressed up as a page that does not stand.

1. A project is approved — Selva Escondida

  1. Developer — submits the projectMy Projects: Selva Escondida stands in review, sent in on October 19, 2026.
  2. Admin — reviews the project and approves itOpen MX Checks in the left-hand list, then the Selva Escondida project review. The reviewer reads the facts, marks the two documents read in the document box, sets the three marks, and commits in the final box. The button in the box reads “MX Check it.”
  3. Developer — reads the approval emailThe email the developer receives: its subject reads “Selva Escondida is approved.”
  4. Developer — sees the approval at homeDeveloper Home: turn on the switch that reads “Demo: a project is approved, not yet live.” The approval stands as a line on the home screen until the project goes live.
  5. Developer — sees the project standing approvedMy Projects: on the row for Selva Escondida, set the pill row labelled “Demo only” to Approved.
  6. Developer — publishes the projectTake Your Project Live: the publish page for Selva Escondida. The card is entered on the page of Stripe itself; this page only hands the developer over to Stripe.
  7. Buyer — sees the project page, liveThe public project page stands live for buyers, with its Checked panel.

2. A change is asked for, and it comes back

  1. Admin — sends the changes requestOpen MX Checks, then the Palma Real change waiting for a check. The reviewer sends the request from the item; the admin states that MX Checked emails the business the note.
  2. Developer — reads the changes emailThe email names the two facts to fix — the delivery date and the street address — and it promises that MX Checked writes again with the result when the change comes back.
  3. Developer — sees the work waiting at homeDeveloper Home: turn on the switch that reads “Demo: a project needs a change.”
  4. Developer — opens the project in its changes stateMy Projects: set the pill row labelled “Demo only” to Changes requested. In the previews, this state stands on the row for Selva Escondida, with the note the reviewer sent.
  5. Developer — fixes the facts and sends them backAdd a Project: Palma Real in edit mode, with the two facts shown as submitted — the live words on the left, the submitted words on the right. The developer corrects them and sends the change back.
  6. Developer — Casa Verde Norte stands in My Projects with the reviewer’s noteMy Projects: the row for Casa Verde Norte stands in its Changes requested state, and it carries the note the reviewer sent: “One document needs another look — our note is on the submission.”
  7. Developer — the submission record stands in Add a ProjectAdd a Project: Casa Verde Norte in edit mode. The submission record stands in its Changes requested state, with the reviewer’s note on the submission and the facts as the developer sent them.
  8. Admin — checks the returned change and approves itMX Checks: the Palma Real change stands in the queue again as a change waiting for a check. The reviewer checks the two facts and commits in the final box.
  9. Developer — the standing work clearsDeveloper Home: turn on the switch that reads “Demo: all clear.” Nothing needs the attention of the developer.
  10. Developer — the project stands with its new factsMy Projects: Palma Real stands live, and its row carries the corrected delivery date.

3. A registration number is corrected

  1. Admin — the number does not match the official listOpen MX Checks, then the registration check for Selva & Mar Developments. The number the business gave is not confirmed against the official list, and the reviewer sends the changes request.
  2. Developer — reads what the email asks forThe registration lines of the changes email name the number that could not be confirmed, and they read: “Correct the number in Profile Settings and send it again.” Its button reads “Go to Profile Settings.”
  3. Developer — corrects the number and sends it againProfile Settings: the field labelled “SEDETUS registration number (matrícula).” The business corrects its own number here; no one at MX Checked types it for them.
  4. Admin — confirms the corrected numberMX Checks: the corrected number comes back as a registration check. The reviewer checks the official list, compares the names, and confirms the number. The machine never confirms a number on its own.
  5. Developer — reads the resultApproval Email: set the case selector at the top of the page to “Registration confirmed.” The email’s subject reads “Your SEDETUS registration is confirmed,” and it carries the line “The number we confirmed is the corrected number you gave us.”
  6. Admin — the record stands confirmedOpen Businesses and people, then the record for Selva & Mar Developments. Its Registration part now stands confirmed, with the number of record.

4. The About text is sent back

  1. Broker — writes the About textProfile Settings: the About text the brokerage writes about itself. The text Runaway Realty sent calls the brokerage “verified” and “MX Checked approved” — words that only the marks of MX Checked may say.
  2. Admin — checks the wordsOpen MX Checks, then the profile text check for Runaway Realty. The words this check is about stand marked in brown on the preview of the profile, and the reviewer sends the text back from the final box.
  3. Broker — reads the changes emailThe profile text lines of the email name what must change, and its button reads “Go to Profile Settings,” landing on the About text.
  4. Broker — sees the line that stands at homeProfile Settings: turn on the switch that reads “Demo: MX Checked sent the About text back.” The line tells the brokerage that its text is waiting on its own correction.
  5. Broker — corrects the text and sends it againThe brokerage rewrites the About text in its own words, without the claim words, and sends it back.
  6. Admin — checks the new textMX Checks: the corrected text comes back as a profile text check, and the reviewer passes it.
  7. Buyer — reads the profile with its new textThe public brokerage profile carries the About text exactly as the brokerage wrote it.

5. A listing becomes Checked — the boleta conversation

  1. Broker — the listing is live, and it is not Checked yetMy Listings, the Not checked yet tab: Casa Orquídea stands here. It is live in search, and only its Checked mark waits, because its boleta header has not been read yet.
  2. Broker — the header waits in the listing’s document boxThe broker added a photo of the top of the Boleta de Registro to the document box of the listing. This page shows the document box: what the person who added a document sees, and what the reviewer sees.
  3. Admin — reads the header and checks the listingOpen MX Checks, then the Casa Orquídea boleta header check at the bottom of the list. The reviewer opens the header in the document box, marks it read, marks “The numbers match,” and commits in the final box. The button reads “MX Check it.”
  4. Broker — reads the resultApproval Email: set the case selector at the top of the page to “Boleta passed.” The email’s subject reads “Casa Orquídea is Checked now,” its Checked date reads November 4, 2026, and the boleta header photo will be deleted on December 4, 2026.
  5. Broker — sees the listing standing CheckedMy Listings: turn on the switch that reads “Demo: the listing is Checked.” Casa Orquídea carries the Checked mark, and the count of homes not checked yet moves.
  6. Broker — the other path: the header cannot be readIf the header cannot be read, the reviewer asks for a change instead. The boleta line of the changes email reads: “Your listing stays in search while you make this change.” The listing never leaves search while the broker fixes it.

6. The documents are read — the document box

  1. Developer — adds the two documentsAdd a Project: the two documents of the project — the land-use approval and the construction license — go into the document box of the submission. These are the only seller documents MX Checked ever holds.
  2. Admin — opens the box and reads the documentsThe Document Box, in the part headed “What the reviewer sees — the same box.” Every opening of the box is a dated line in its access record, naming the person who opened it.
  3. Developer — sees who opened the box, and whenThe Document Box, in the part headed “What the developer sees — during the review.” The access record stands where the developer can read it.
  4. Developer — after the approval, the deletion clock standsThe Document Box, in the part headed “What the developer sees — after the approval.” The files of Selva Escondida will be deleted on December 4, 2026, one month after the review ended, and the developer may delete them sooner.
  5. Developer — reads the deletion reminderNotification Emails, number 12: the document deletion reminder, sent 7 days before the files are deleted.
  6. Developer — the box after the files are goneThe Document Box, in the part headed “The box after the files are gone.” The record of the deletion stands; the files do not.

7. Publishing, and the payment that does not go through

  1. Developer — is ready to publishTake Your Project Live: Aldea Serena, ready to publish. The page states the amount due and hands the developer to the secure page of Stripe for the card.
  2. Developer — the payment does not go throughThe developer lands back on the publish page with the notice. Nothing is charged, and the project stays ready to publish.
  3. Developer — the payment is cancelledThe cancelled landing on the same page. The project still waits, ready to publish, and the developer may try again.
  4. Developer — updates the cardThe developer Account page: a card was updated on the page of Stripe, and this is the success return that lands back in Billing.
  5. Admin — watches the moneyOpen Billing. MX Checked watches every subscription here and charges nothing from the admin. The subscription of Marina Village stands paused, because its renewal payment failed.
  6. Developer — sees the project standing pausedMy Projects, the Paused tab: Marina Village stands here while its page is paused.
  7. No page in the set — Marina Village has no fix-payment page of its own in the previews. The card door that stands in the set is the developer Account door in step 4. In the real build, the paused row itself carries the way back.

8. A Preferred spot is offered

  1. Admin — sends the offerOpen Preferred. The offer to Puerto Morelos Properties stands sent on November 1, 2026, and the business has 72 hours to answer, until November 4, 2026.
  2. Broker — reads the offer emailNotification Emails, number 1: its subject reads “A Preferred spot in Puerto Morelos is open to you until November 4, 2026.”
  3. Broker — sees the offer waiting at homeBroker Home: turn on the switch that reads “Demo: a Preferred offer is waiting.”
  4. Broker — answers the offerBecome Preferred: set the scenario switch to “Spot offered to you (72 hours)” and accept. To accept, the business adds its card on the page of Stripe, and Preferred starts right away.
  5. Admin — the board flipsOpen Preferred again. The brokerage spot for Puerto Morelos now stands taken by the business that accepted, and the count of offers waiting for an answer moves.
  6. Broker — the other ending: Preferred endsIf a brokerage loses its Checked standing, its Preferred spot ends at the end of the month it has paid for. Notification Emails, number 2, is that email; the case drawn there reads “Preferred ends for Selva & Mar Properties on December 31, 2026.”

9. The weekly availability check

  1. Broker — receives the weekly checkThe Weekly Availability Check page opens with the email as the broker meets it. The “Portfolio size” buttons at the top — 1 listing, 2 listings, 69 listings — show the check at each size.
  2. Broker — answers the checkThe broker confirms which homes are still available, marks any home that sold, and sends the answer. The page ends with the words “Done — thank you, Kim.”
  3. Admin — sees the answer standOpen Confirmations. The answer of the brokerage stands here, and the count on the section names what still waits for an answer.
  4. Broker — the silence path: two weeks with no answerIf two weekly checks pass with no answer, the listings pause on their own. Notification Emails, number 3, is the email that tells the broker; its subject reads “Your listings are paused.”
  5. Broker — sees the pause the silence causedMy Listings: turn on the switch that reads “Demo: a listing is paused — two missed weekly checks.” A paused home leaves search and the collections until the broker confirms it again.

10. The monthly numbers check

  1. Developer — sees the check waiting at homeDeveloper Home: turn on the switch that reads “Demo: the monthly numbers check is waiting.”
  2. Developer — reads the monthly emailNotification Emails, number 6: its subject reads “Your monthly numbers check.” The counts of homes left, for each type the project sells, stand already filled in.
  3. Developer — answers the checkMy Projects: the monthly numbers check card stands on the page. The developer answers “Still right,” or updates the numbers. On the page, the pill row for the check reads “No check waiting” and “Check waiting.”
  4. Admin — sees the numbers stand confirmedOpen Confirmations. The numbers of the developer stand confirmed for the month, and silence never pauses a page that is paid for.
  5. Developer — a zero answer opens the sold-out checkIf the developer updates every count to zero, the project is sold out. That answer opens conversation 13, the sold-out check.

11. A home is sold

  1. Broker — the homes stand soldMy Listings, the Sold tab: Casa Brisa del Mar and Condo Vista Marina stand here, sold in October 2026. Marking a home sold on its row is the only act that sets this state.
  2. Buyer — sees the sold look in searchSearch homes: both cards carry the navy Sold pill and the greyed photo, and each price reads “Listed at,” because the home is not for sale any more.
  3. Buyer — sees the sold look on a listing pageA listing page: the sold look stands in the similar homes row at the bottom of the page.
  4. Buyer — sees them under Recently soldThe brokerage profile: both homes stand in the Recently sold part of the page, beside the Checked homes the brokerage holds now.
  5. Admin — the record standsOpen Businesses and people, then the record for Runaway Realty. Its Holdings part carries both sold homes, and the folio and the agreement dates stand in the record.

12. An agreement ends, and a home is paused

  1. Admin — the warning stands 30 days aheadOpen Confirmations. A card stands here for each agreement that ends soon: the agreement for Condo Aldea Zama ends on November 28, 2026.
  2. Broker — reads the warning emailNotification Emails, number 4: its subject reads “The listing agreement for Condo Aldea Zama ends on November 28, 2026.” The same warning stands as a line on the home screen of the broker.
  3. Broker — when the date passes with no new agreementNotification Emails, number 5: its subject reads “Condo Manglar Bay is paused.” The listing pauses on the day its agreement ends.
  4. Broker — sees the home standing paused, with its reasonMy Listings, the Paused tab: Condo Manglar Bay stands here. Its reason reads in plain words that the listing agreement ended on October 28, 2026, and that the home is out of search until the brokerage records a new agreement end date.
  5. Buyer — the home is simply not hereSearch homes: Condo Manglar Bay does not appear. A paused home is hidden from buyers, and no reason for a pause is ever shown to a buyer.
  6. Broker — the way backOn the same row in My Listings, the brokerage records a new agreement end date, and the pause lifts. The home returns to search.

13. The sold-out check — Gran Selva, Unit 12

  1. Developer — reports zero homes left, and signsMy Projects: on the row for Gran Selva, set the pill row for the sold-out statement to Signed. The statement stands signed by Marco Torres on October 27, 2026. Signing it is the only act that marks a project sold out.
  2. Admin — two items stand in the queueOpen MX Checks. The sold-out statement of Gran Selva stands here, and beside the project sits the listing held — the sold-out check for Unit 12, a listing in the project that Runaway Realty holds.
  3. Admin — makes the closing call and closes the checkIn the sold-out check, the reviewer writes the note of the call and sets the mark that reads “I checked with the developer.” Only then does the button that reads “Close it” open. A person closes this check; it never closes on its own.
  4. Broker — reads the resultNotification Emails, number 8: its subject reads “The sold-out check for Gran Selva, Unit 12 is closed.” The email goes to the brokerage that holds the listing.
  5. Broker — sees the outcome standing at homeBroker Home: turn on the switch that reads “Demo: the sold-out check is closed.” The line stands on the home screen of the broker, and the held listing is released.
  6. Buyer — the developer's profile stands, with Gran Selva as past workThe Developer Profile in its six-month gate state: no project of Terra Verde Developments is live in this state, and the profile stays public because Gran Selva sold out on October 27, 2026 — inside the past six months. Gran Selva stands on the profile as past work, and its counts stand at zero.
  7. No page in the set — Gran Selva's own project page is not drawn in the previews. In the real build, the sold-out project's page stays public while the six-month gate holds, its counts standing at the signed zero, and when the gate lapses with no project live it leaves search, the city guides, and the New developments browse together with the sleeping profile.
  8. Buyer — when the gate lapses, the profile is simply not thereThe Developer Profile in its not-published state: the address returns a plain page that reads 'This page is not here.' Nothing on the page says that a profile is hidden.

14. An agent joins a team

  1. Broker — sends the inviteBroker Home: the Team button in the right-hand rail opens the team popover. “Invite an agent” sends the invite from there.
  2. Agent — reads the invite emailNotification Emails, number 9: its subject reads “Kim Smith invited you to join Runaway Realty on MX Checked.” The link in the email works for 7 days.
  3. Agent — follows the link and joinsCreate Your Account: the account-type picker at the top of the form shows the fields for an agent. The agent joins under the registration of the brokerage; an agent is never confirmed on their own.
  4. Agent — lands in the chair of the agentAccount: set the persona bar at the top to “Agent — Lacy O’Loughlin.” This is the seat as the agent meets it: her own account, her collections, and the brokerage she sits under.
  5. Broker — sees the seat standing filledBroker Home: the team popover now carries the agent on the team. An invite that still waits for its answer reads “Invite pending” in the same popover.

15. A seat ends, and the collections come home

  1. Broker — ends the seatBroker Home: in the team popover, the broker ends the seat of the agent. The collections of the agent park with the brokerage in the same act; nothing is deleted.
  2. Agent — reads the emailNotification Emails, number 10: the seat ended. The email tells the agent what happens to the collections.
  3. Agent — sees the standing noticeAccount: set the persona bar at the top to “Agent — Lacy O’Loughlin,” then use the button that reads “Seat ended by the brokerage.” The notice stands on the account: the seat ended on November 4, 2026.
  4. Agent — the collections wait with the brokerageThe Collection Builder: the collections the agent built stand parked, waiting with the brokerage, under their own links.
  5. Agent — reads the reclaim emailNotification Emails, number 11: the collections are reclaimed when the agent sits at a new brokerage, or opens a brokerage of their own.
  6. Agent — the collections come back to the account of the agentThe Collection Builder: the reclaimed collections stand with the agent again, under the same links the clients already hold.
  7. Client — the collection still opensThe page the client opens from the link of the agent: the same collection, with the same homes. A collection hangs on the account of the agent, never on the name of a brokerage.

16. A business is removed

  1. Admin — removes the business from its recordOpen Businesses and people, then the record for Casa Caribe Realty. Removal happens here, never from a queue row: the final box assembles the reason on its own, and its button reads “Remove from MX Checked.”
  2. Business — reads the emailNotification Emails, number 7: its subject reads “Casa Caribe Realty was removed from MX Checked.” The reason stands in the email, assembled from the record.
  3. No answer exists — by design. The removal email carries the fact and the reason, and it carries no door back. A removed business does not reply its way back in.

17. A development is flagged

  1. Admin — a candidate waits for a person to decideOpen Flagged developments. Residencial Brisa del Puerto stands here as a candidate, found by the weekly sweep of the registry of irregular developments. A person checks the registry entry and decides; the machine never applies a flag.
  2. Admin — the flag that already standsCosta Azul Residences, a project of Brisa Homes, stands flagged: the registry entry is dated September 8, 2026. The developer was told on the day the flag was verified, before anything went public.
  3. No page in the set — two steps of this conversation are not drawn. The telling of the developer has no email and no page in the previews, and no public page in the set carries the red flag band. In the real build, the page of a flagged project carries the band with the registry date, carries no Checked marks, and sorts last in its city.

18. A password is reset

  1. Admin — sends the reset from the record of the personOpen Businesses and people, then the record of the person who cannot sign in. The reset is sent from the record, and it is written in the activity of the platform. No one here ever sees, sets, or chooses the password of another person.
  2. No page in the set — the reset email itself is not drawn as a page. The person meets this conversation at the page the email lands on, in the next step.
  3. Broker — lands on the page the email points toSet a New Password: the page reads that the link can be used only one time, and that the link stops working after 1 hour. If the person did not ask for the email, the password does not change.
  4. Broker — signs in with the new passwordSign In: the same page serves the sellers and the staff of MX Checked.

19. A resale inside a sold-out project

  1. Broker — the blocked card names whose unit it isBroker Home: turn on the switch that reads “Demo: the sold-out check is closed.” The blocked card for Gran Selva, Unit 12 stands here: the sold-out check is closed, and the listing stays blocked. The card now carries the fact “Whose unit: the developer’s unit.” and the door “This unit is an owner’s resale — tell us.”
  2. Broker — tells us the unit is an owner’s resaleBroker Home: turn on the switch that reads “Demo: the broker told us this unit is an owner’s resale.” The broker uses the door, and the card reads that the claim was told, the check is open again, and the listing stays blocked while the check is open.
  3. Admin — the check stands reopenedOpen MX Checks, and turn on the demo state that reads “Demo state — the sold-out check has reopened.” The sold-out check for Gran Selva, Unit 12 stands reopened. Its facts carry the broker’s answer — “Runaway Realty told us this unit is an owner’s resale.” — and the agreement-holder line: the listing agreement on the record is with the owner of the home, and the agreement record agrees with the broker’s answer. The reviewer makes the mark that reads “The broker’s answer closes this check.”
  4. Admin — closes the check as a resaleIn the same demo state, the reviewer closes the item as “Released — an owner’s resale” through the final-confirmation box. The box states “MX Checked emails Runaway Realty the outcome.”
  5. Broker — reads the outcome emailNotification Emails, number 13, “Sold-out check released”: its subject reads “Gran Selva, Unit 12 is live again.” The email tells the broker that the check confirmed the unit is an owner’s resale and the listing is live again, and its door reads “Go to My Listings.”
  6. The standing record — in the standing canon, Gran Selva, Unit 12 is the developer’s unit and stays blocked. This conversation walks the labelled demo states built for the resale path.

20. A unit comes back: the statement is amended

  1. Developer — reports a unit available againMy Projects: on the row for Gran Selva, the signed record of the sold-out statement carries the door “We have a unit available again.”
  2. Developer — the report stands sentMy Projects: on the same row, set the pill row labelled “Demo only” to Report sent. The developer’s report stands sent, and the statement stands until MX Checked ends it.
  3. Admin — the statement is recorded as endedOpen MX Checks, and turn on the demo state that reads “Demo state — a unit is available again.” The reviewer confirms the report with the developer, and the sold-out statement of Gran Selva is recorded as ended. Both dates stand in the history — signed October 27, 2026; ended November 4, 2026 — the blocked listings of the developer’s units are released, and the six-month clock stops.

Every page

Every page in the set stands here, grouped by the chair of the person who uses it. You tap a page, and the page opens in the viewer above.

Public

The states

Every state stands here, grouped by its page. A state that sits behind an address parameter is its own link, so you never type an address. A state that a switch on the page shows stands as the page link with the words of the switch beside it.

Become Preferred

My Listings

My Projects

Broker Home

  • Broker Home — the switches on the page

    On the page, switches each labelled “Demo”: “a listing needs a change” · “a listing is paused” · “an agreement ends soon” · “the weekly availability check is waiting” · “a Preferred offer is waiting” · “the sold-out check is closed” · “all clear” · “no listings”. The Team button in the right-hand rail opens the team popover.

Developer Home

  • Developer Home — the switches on the page

    On the page, switches each labelled “Demo”: “a project needs a change” · “a project is approved, not yet live” · “documents in their deletion window” · “the monthly numbers check is waiting” · “a Preferred offer is waiting” · “all clear”.

The admin

Account

  • Account — the persona bar on the page

    On the page: the persona bar at the top — “Broker admin — Kim Smith” · “Agent — Lacy O’Loughlin”. In the chair of the agent, the button that reads “Seat ended by the brokerage” stands up the seat-ended notice.

Profile Settings — brokerage

Weekly Availability Check

How Preferred Works

Create Your Account