How the Opendoor board counts

Every definition the board uses, in one place. The board itself shows numbers and chips only; this page is linked from its top bar. Back to the board.

Scope: the top-bar filters

Jobs
Every Opendoor job on the platform. "Maintenance" (the default) is the maintenance jobs; "This round" those created since Oct 19; "All Opendoor jobs" adds repairs and projects; "Door hardware only" the SafeHaven knob-swap jobs alone.
Trade
Cleaning, landscaping, pool care or door hardware.
Week
Keeps only the jobs due in the chosen week (this week or next, Mon–Sun; "this week or next" either). Next week is judged the same way a week ahead, and a visit already on the calendar counts for an every-2-weeks cadence.
Came in
The day the job was created on the platform, Eastern Time. The Opendoor sync creates a job when Opendoor assigns the schedule; a prospecting job made by hand before the assignment keeps our own date. Each option shows its count under the current Jobs and Trade filters.
Stage (Map view)
Keeps the ticked sourcing levels, any number at once; reached out and in talks are one chip ("no good price yet"), no outreach has its own. The count on a chip is before the narrowing. It applies to the map and the batch table only.
Show (Map view)
All locations, not on our list only, dropped by Opendoor only, nothing scheduled yet, due this week with nothing scheduled. Applies to the map and the batch table.

Overview and the to-do buckets

Serviced
A visit this week marked done on the platform, or approved / invoiced / in review on Opendoor's portal (the Pulse definition).
Uncovered
Due this week with nothing on the calendar: committed with no date, or no vendor at all.
Batches due
Batches with a visit due in the week, a home outside any batch counting as a batch of one; green has a vendor committed, orange a price in hand at or under 80% of Opendoor's rate, red neither.
Ask the vendor
Claim-list homes whose action starts with asking a vendor: route adds into a route with a committed vendor, and vendor extensions.
Claim
New routes as a group, and route adds into routes still being sourced (strong or fair).
Check on the platform
Homes we claimed that arrived on the platform: owner, supervisors and batch to confirm.
Chase Opendoor
Homes we claimed more than two business days ago that have not arrived.

Sourcing levels

Each job is at exactly one level, its furthest, so the six tiles add up to the Jobs tile and the colours on the map, the bars and the chips mean the same thing everywhere.

No outreach
No vendor identified or messaged yet.
Reached out, no reply
Vendors messaged, none has replied.
In talks
A vendor replied; no price at or under Opendoor's rate yet.
Good price in hand
A vendor price at or under what Opendoor pays, no commitment yet.
Vendor committed
Agreement signed or deposit paid, on the job or on a sibling job in the batch; no visit booked yet.
Visit booked
A visit is on the calendar.
Platform stage
The furthest any vendor has reached on the job: outreach = vendors identified or messaged; in talks = a vendor replied; quoted; contracting; locked in = agreement signed or deposit paid; scheduled = a visit is on the calendar. Shown on the job card.
Via batch
A platform batch is sourced as one unit per trade, so a vendor who committed to, priced or replied on one job in a batch counts for the other jobs of that trade in it, unless that vendor's own thread shows they will not take the home or only named other homes (the job card lists the verdict per vendor under "Thread check"). A booked visit stays per home.
Vendors signed
Distinct companies with an agreement signed or deposit paid on the jobs shown, by the week each first did so.
Vendor prices
From the platform's vendor price fields and quotes, inbound vendor messages with a dollar amount, and internal notes that name the vendor or read like a quote. Amounts next to cap, budget, NTE or "looking for" are skipped, as are amounts under $10. A price under $5 per visit is a placeholder typed on the platform, not a price: it counts as "no vendor cost yet".

Service due this week

Due
Weekly schedules every week; every-2-weeks unless a visit was done the week before (the portal gives no next-visit date); one-offs until done. Pulled-back, finished, stopped and not-yet-started schedules are not due. No cadence in the portal counts as due. A job assigned this week with no start date in Opendoor's note and no visit yet is not counted.
Serviced
A work visit this week marked done on the platform.
Scheduled
A visit on the calendar this week. A visit can be a window ("any day Nov 2 – Nov 8"): it counts for every week it overlaps and is past only once the window has closed.
Committed, no date
Due, a vendor committed, nothing on the calendar.
No vendor yet
Due and no vendor committed.
Start date, frequency, price
From Opendoor's assignment note or the schedule snapshot; "dropped" means Opendoor's portal no longer lists the schedule.

Batches

One row per platform batch. Jobs without a platform batch are folded into the nearest batch within 20 miles or grouped by area, so a row can show the batch owner plus the owners of unbatched jobs nearby. Click a row for its jobs; a job opens in the platform; Map shows it on the map.

Map

Gestures
Scroll to zoom, drag to pan, click a state to zoom in. Shift-drag (or "Select homes by area") draws a box that selects every claim-list home in it for one claim; click a group's dashed route or its label (N1, E1, …) to claim the whole group.
Dots
One per home, coloured by the sourcing level; a home with several jobs shows one wedge per job. Faded with a red cross: Opendoor dropped the schedule. Blue ring: not on the list accepted on Oct 19 (being retired). Pink ring: door-hardware job; dashed pink circles: its proposed batches, numbered.
Vendors
Square: a vendor we have worked with (a job locked in or completed). Diamond: W-9 and COI on file, no job yet.
Pins
Homes on Opendoor's claim list, lettered R (route add), N (new route), E (vendor extension), S (seed). Dashed lines: the road routes of the groups shown. Faint rings: 15 miles around clusters we already serve.

Claim list

Every home Opendoor currently offers for a vendor claim (projects.opendoor.com/home-care-opportunities), classified per service wanted on real road minutes. The board server routes every needed leg once through the public OSRM router (listed home to our same-trade stops within 30 air miles, stops of one cluster and trade, listed home to our vendors' pins within 45, listed homes of one service within 30) and keeps them in road-cache/legs.json; a leg not routed yet is a straight-line estimate (× 1.3, 1.42 min per road mile) and marked "air estimate". Free-flow times are scaled × 1.3 inside the big metros (Atlanta, Washington DC, Dallas–Fort Worth, Denver, Detroit, Boston, North Jersey) and × 1.15 elsewhere unless the Traffic select says otherwise.

Route add
Inserts into a route we already run (same trade; vendor committed, or ours and still being sourced) with a detour of at most 30 minutes and the route's day still fitting at the trade's pace; r = detour ÷ on-site minutes. Action: ask the vendor, then claim. When the route has no vendor yet there is nobody to ask: claim at once when r is strong or fair.
New route
Member of a group of at least 3 listed homes needing the same service within 30 road minutes of a base home (greedy set cover, biggest ball first), toured (nearest neighbour + 2-opt) and cut into days of 8.5 hours, every leg at most 30 minutes; r = driving ÷ on-site over the route. Strong needs r ≤ 0.2, 4+ homes, not fragile (losing any one home keeps it a fair route) and metro or town vendor supply (county density from the Census: metro ≥ 1,000, town ≥ 100 people per square mile). Action: claim as a group.
Vendor extension
One of our vendors (committed on an Opendoor maintenance job) can serve it as a separate trip from their base or their nearest route stop, alone or with the other such homes within 30 minutes, no leg over 45 minutes; r = round trip ÷ (homes × on-site). Action: ask the vendor, then claim.
Seed
A pair within 20 minutes, or a 3+ group that fails the new-route bar only just. Action: watch; promoted when homes list nearby.
Single
None of the above. Action: pass; the nearest vendor on file is only a hint.
Strength
On r: strong ≤ 0.2, fair ≤ 0.4, weak ≤ 0.8 (standard bands; looser 0.25 / 0.5 / 1.0, tighter 0.15 / 0.3 / 0.6).
Pace
On-site minutes per visit are the medians of our own sign-off clock-ins on Opendoor maintenance visits: cleaning 60, landscaping 48, pool 25.
Value
Monthly revenue at Opendoor's pilot card (cleaning 2.17 visits a month, lawn and pool 4.33) and the vendor's implied pay per hour after Tavi's take of 25%, driving included.
Groups
New routes (a base home plus every such home within the territory minutes of it by road, toured and cut into days at the trade's pace), extension groups (what one of our vendors could add as a separate trip from their base or nearest stop) and seeds. Homes already ours or claimed by us are left out.
Claim by rule
A rule names a class and the weakest strength it takes; the Service and State filters apply too. Route adds and extensions need the vendor's yes before the claim, and the confirmation says how many of the selection are such asks. Every claim goes through the same confirmation dialog; nothing is sent before it. Rules are kept per browser.
Vendor said no
A decline recorded on the home card (reason, note) removes that vendor from the home's options; the rating never proposes them for it again.
Was
The retired air-model tiers (A to D, score 0–100), still computed for comparison when "Show the old tiers" is ticked.
Clusters we serve
The platform batches of the active maintenance jobs (one cluster per batch), with unbatched jobs attached to the nearest batch within 20 miles or grouped among themselves.
Nothing claimed without a yes
For route adds and extensions the vendor's answer comes first (decided 2026-11-04).

Revenue

Gross per visit
Opendoor's current rate for the schedule.
Vendor cost per visit
The committed vendor's price: the single-visit payment tranches to them, else the primary quote on the platform divided by the visits it covers. Without a committed vendor the best price in hand is an "indicative" cost.
Net, margin, markup
Net = gross − cost; margin = net ÷ gross; Tavi markup = net ÷ cost. Stated on the schedules with a vendor cost.
Run rate
Per-visit figures × the visits a week of every active schedule (every week = 1, every 2 weeks = 0.5; one-off, finished, stopped and pulled-back schedules carry none); monthly = weekly × 52 ÷ 12.
Booked
The money on the platform's payment tranches, one per visit (what we bill Opendoor and what we pay the vendor), dated by the visit; past visits of pulled-back schedules are included. Periods are listed from the first with a tranche or an active schedule to the last.
Rate card
Opendoor's pilot rates per visit by region (Ben Booi, Oct 21); region by state as read off our assignments. "Short" is the weekly gross missed while a schedule pays under the card.

Team

Teams
From teams.json next to the server (lead and members, edited by hand; seeded from the replica org chart and the cockpit teams). "No team" lists the people the file names without a team; "Others" the people it does not name.
Workload
What each team owns among the jobs shown: platform batches, jobs, homes, trade mix, then the share of its jobs at each sourcing level. A batch counts once per person who owns jobs in it.
Calls and messages
Outbound calls and messages logged on the platform for the jobs shown, by the person who made them. "Last hour" is the 60 minutes before the data was pulled. Messages are SMS and email to vendors. "Other Opendoor" is work on Opendoor jobs not shown right now; "Elsewhere" is calls and messages on other clients' jobs since Oct 19.

Door hardware

Opendoor's SafeHaven knob swap: capital-project jobs whose description mentions SafeHaven and a knob. They are their own category, shown alone under "Door hardware only" (or in the maintenance views while the box in the Doors view is ticked). Their proposed batches are homes within the chosen miles of a hub home, up to the chosen size, never mixed with maintenance batches.

Data

Source
The Tavi platform replica, pulled by the board server at most once a minute; the page refreshes every 5 minutes while open. Without the server the page shows the last snapshot and says so.
Vendors on file
W-9 and COI on the platform, or a job already locked in or completed with Tavi.
Not on our list
Compares each job's address and trade with the 55-address list accepted on Oct 19. Being retired: most jobs since then arrived through claims.