Changelog

The browser extension is in the Chrome Web Store

Added

• DispaLoadIQ — Honest Rate Check for Chrome (version 0.1.5), in the Chrome Web Store. Select a load’s text on any page and right-click, or paste it into the extension: the rate verdict where the lane is measured, and the broker’s FMCSA record, including other registrations that share its phone or email. It works only when you start it, reads no pages on its own, and needs no account. What it sends is in the privacy policy.
• A link to it on the home page, under the three tools.

Fixed

On the site and in the web app. Where the iPhone app or the browser extension has the same feature, the fix ships in its next version.

• Choosing a company after a search by name did not start the check. When a load posting shows only a company name, the broker check lists the registered companies with that name. Tapping one showed the same list again instead of checking it. It now checks the company you pick.
• The rate check opened with a sample lane already filled in (California to Illinois, reefer). If you typed your rate without changing it, the answer was about someone else’s lane. The origin, destination and trailer now start empty.
• PDF rate confirmations lost their line breaks, and some words split in two (“fi ne”). As a result, payment terms such as “Net 30” and some fines were missed, and the payment terms were listed as not in the document. PDFs are now read line by line, and a sentence that wraps onto the next line is joined back together.
• The rate con reader recognises more of the wording real contracts use: “chargebacks”, “after the first 3 hours”, “Truck Order Not Used”, amounts with cents in the middle of a sentence, and table rows such as “Detention … free. Max $225”.
• A per-mile rate read from pasted text could be the wrong one. A deadhead, out-of-route or fuel-surcharge rate (“Deadhead $1.00 per mile”) was taken as the load’s rate. These are now skipped.
• The payment check flagged a short payer name as a different company. Checks often show “TQL” or “CHR PAYABLES”. These are now matched against the broker’s initials, and a different company is still flagged.
• The broker check now shows the legal name when it differs from the name shown. On phones, the broker number field is no longer squeezed by the button next to it.

Signs of a re-brokered load you can check yourself — and none of them accuse anyone

This entry covers the site and the web app. The iPhone app gets the same in its next update; the browser extension in its next version.

Added

• Compare the BOL with your rate-con. After you check the MC on a rate confirmation, paste the bill of lading (or open its PDF). It is read on your device and not sent anywhere. It tells you whether the BOL carries your broker’s MC, only its name, other MC numbers — or none of these, in which case it asks you to read the company names yourself rather than telling you all is well.
• Who paid you. Payment Check now has a field for the name on the check or ACH line, and a box for “my factoring company paid me”. If the payer’s name shares no word with the broker’s, it says so, lists the harmless reasons first, and what to ask. We keep only which of these it was — not the payer’s name.
• “The load was re-brokered” reports can name the MC of the company that actually had the load (from the BOL or the shipper). It is kept with the report and shown to no one, never displayed next to either company, and used only in totals without names, published only from 20 or more reports. Reports can be filed from the iPhone app (in its next update); the broker check — and the extension, in its next version — link to the form (a report needs a free account).
• Broker check: other registrations with the same phone or e-mail. How many other FMCSA registrations list the same phone number or email address, and how many of them are active — counts only, never names. A contact shared by a very large number of registrations is shown as saying little about the company.
• Alerts for brokers you saved: when the phone or email domain in the FMCSA record changes, when a cancellation of a bond, trust fund or liability insurance is on file, and when authority becomes active again.

Changed

• The public dataset now measures what the rate-con check finds: whether the MC on a rate confirmation is a carrier, whether the FMCSA phone appears in the document, whether the email domain matches — never the numbers, domains or names. A metric named “double-broker flag” counted every lookup that returned a carrier, including carriers checking their own MC, so it is now named “lookup returned a carrier”. Nothing had been published under the old name.
• How a broker pays, and reports about a broker, now appear only once at least 10 different carriers stand behind them (it was 3), so a handful of accounts cannot shape what everyone sees about a named company. A lane’s measured rate and a broker’s median rate still need 3.
• The app’s privacy policy describes the above and what the browser extension sends (updated October 2); this site’s own policy now points to it for the extension (October 3).

Removed

• From suspension-notice alerts: “such notices are often resolved” — we have no count behind it. It now says a notice can still be resolved before its date. From the rate-con check: “one MC is usually yours” — now “one of them may be yours”.

A pricing page that matches reality, and text you can read on a small phone

This entry covers the site and the web app. The same readability fixes are in the iPhone app’s next update and in the browser extension’s next version.

Fixed

• The pricing page offered a “Pro” plan at $29 a month, with an email to switch it on — while no paid plan exists. It now says what is true: everything is free today; if a paid plan ever appears, its price will be on that page and announced in advance.
• Colored text that was hard to read. The rate verdict (above / at / below market) and status labels read at 3.1–3.9 to 1 against their backgrounds, under the 4.5 to 1 readability guideline (WCAG); they are now 4.7–5.4. Section labels and links on this site went from 3.7 to 5.8.
• On phones, the section title in the app header broke over two or three lines and was cut off at the top, and on 320-pixel screens it ended in “…”. Checkmarks and bullet icons sat alone on a line above their text on ten screens.
• When the broker check failed for any reason, the message blamed FMCSA — including when our own server did not answer. It now says the check could not be completed.
• In the dark theme (opt-in, in Settings), text disappeared on eighteen screens — dark text on a dark background, or light text on a light card.
• Cards, tiles and notifications that could be clicked but not reached with the Tab key now work from the keyboard.

Changed

• The cost-per-mile calculator’s default wear reserve and its “pay yourself a driver’s wage” target now cite the source line by line: ATRI, An Analysis of the Operational Costs of Trucking — 2026 Update (2025 data) — repair and maintenance $0.215 a mile, tires not included; average driver wages $0.818 a mile, benefits not included.

Removed

• “Many brokers won’t touch an MC under 1–2 years” and “a dedicated lane that asks for a deposit is a scam — every time”: neither had a count behind it. The advice stays — ask each broker what their minimum is, and don’t pay a deposit until you have verified who you are dealing with.

A first visit, walked through on a phone: a sign-up form you could not fill in, and sentences we could not back up

We went through the site and the web app the way a new visitor does. This entry covers the site and the web app; the iPhone app gets its share in its next update.

Fixed

• The sign-up questions after creating an account were unusable on a phone — a side panel left the form a strip about 90 pixels wide. It now uses the full width.
• A dispatcher who signed up with email never got a directory listing. They now go through the short setup that creates it.
• On a shared computer, the next account could see the previous one’s numbers — cost per mile, invoices, tax and maintenance entries kept in the browser. They are now cleared when a different account signs in; what you entered before creating your own account stays yours.
• A figure on our home page was off by a tenth: carriers with ten or fewer trucks are 90.2% of FMCSA-regulated carriers, not 90.3% (FMCSA Pocket Guide 2024, table 1-11, 2023 data).
• “What to say to the broker” counted a wear reserve you had not entered. Without your own figure it is now left out, and the line says so.
• Password-reset emails arrive in the language you use the site in.

Removed

• Sentences that stated more than we can show: that one phone call “stops most” double-brokering, that a carrier number “usually means” double-brokering, that “most people” leave the wear reserve out, that you can dictate a message. None had a count behind it.

The broker check called a trust fund a bond, and one of its warnings could never fire

We compared what the broker check shows with the FMCSA records behind it. This entry covers the site and our server; the Chrome extension and the iPhone app get the same in their next updates.

Fixed

• Every broker with financial security was shown as “Bond on file (BMC-84)”. A broker can file either a BMC-84 surety bond or a BMC-85 trust fund, and FMCSA records show some brokers with a BMC-85. The check now names the form FMCSA has on record and who provides it, and says “bond or trust fund” when the form is not known.
• The “bond below required” warning could never fire. FMCSA’s interface gives the bond amount in thousands of dollars and the requirement as a yes/no flag, and we compared the two as numbers. The check now shows the amount in dollars and warns when it is below the $75,000 federal minimum for brokers (49 CFR 387.307).
• The date the authority was first granted was never shown. A line for it was on the page, but our server never sent the date. It now comes from FMCSA’s authority history, and it is not shown when that history could not be loaded in full.
• Phone numbers are shown as (312) 555-0100 instead of 3125550100.
• Unsubscribe and confirmation links in our emails acted on the click itself. Email security scanners open links on their own, so a scanner could unsubscribe someone — or, through an old confirmation email, subscribe them again — without them knowing. The links now open a page with a button, and nothing changes until the button is pressed.

Added

• Authority history. When FMCSA first granted the authority and how long ago; revocations, with the warning counting only the kind of authority being checked; a revocation that was started and then discontinued is shown as exactly that; involuntary suspension notices with the effective date written on the notice, and whether FMCSA later recorded a reinstatement; and, when FMCSA’s records already show one, a cancellation of an insurance policy or bond that has been scheduled. Source: FMCSA licensing & insurance records on data.transportation.gov.
• The full registered address, the date the USDOT number was issued, when the MCS-150 was last updated, and whether a broker also holds carrier authority.
• An alert for companies on your list when FMCSA serves a suspension notice — saying whose authority it concerns, broker or carrier. Until now the list only alerted you once the authority was already inactive. The alert is not sent if FMCSA later recorded a reinstatement, or if part of the record could not be loaded.
• An unsubscribe link in the weekly summary email. Until now it could only be turned off in settings.

The rate-con reader read some clauses backwards, and “what you keep” came from someone else’s cost

We read real rate confirmations through the reader line by line, went through the public pages with a keyboard and checked what a screen reader is told, and checked the sentences on this site against what the code does. This entry covers the site and our server; the iPhone app gets the same fixes in its next update.

Fixed

• The rate-con reader said the opposite of the document. “Fuel surcharge: included” was read as fuel paid separately. “No TONU” and “TONU: N/A” were read as TONU paid when the broker cancels. “Payment: 30 days” came back as “no payment terms”. A late-delivery fine on a page that mentions a tracking app became a tracking fine, and “Fines for late delivery: $250” was not found at all. Each now reads as written, and every case has a test.
• The lane came from the wrong words. “Columbus OH to Nashville TN” gave Tennessee as the origin; “Laredo TX to Denver CO” lost the destination; “deadhead 45 mi, loaded 925 mi” divided the rate by 45 miles.
• “An average truck would keep” is gone. Before you entered your own cost, the rate check and the load P&L showed what a truck at the US average would keep, using $1.85 a mile. That is ATRI’s figure excluding fuel, so it overstated what is left. Until you enter your own cost there is now no take-home figure, only a request to enter it.
• “Not in this rate-con” meant “the reader did not find it”. The reader goes by wording, and a clause phrased in an unusual way can slip past it. The list is now titled “Not found in this rate-con” and says to check those lines yourself.
• Sign-up and sign-in errors were raw system text, such as “Firebase: Error (auth/email-already-in-use).” They now say what happened, in English, Spanish or Russian.
• Cost per mile swallowed commas. “2,85” typed on a Spanish or Russian keyboard vanished from the field. A comma is now read as a decimal separator there and in the other number fields.
• Failed saves looked like saves. In settings, invoices and cost per mile, a save the browser or the server refused still showed as saved. It now says it did not save. A second click no longer creates a second invoice, and a detention claim whose saved times failed to load no longer overwrites them with empty ones.
• Sample brokers in the demo carried the names and MC numbers of real companies, two of them under “blacklisted”. All were replaced with invented names and numbers, checked against the FMCSA registry.

Added

• Terms and Privacy in Spanish and Russian. The English text remains the binding one, one tap away.
• Emails and notifications in your language. Our server did not know which language you had chosen and wrote to everyone in English, including the alert that a carrier’s operating authority is no longer active.
• dispaloadiq.com/ru/ and dispaloadiq.com/es/ — this site in Russian and Spanish, with link previews in the same language when the link is shared in a messenger.
• Keyboard and screen readers. Form fields have names a screen reader can say; error messages are announced; keyboard focus is visible; menus and dialogs close with Escape; there is a “skip to content” link. Grey text is darker, to at least the 4.5:1 contrast that WCAG asks for.

Old numbers under new labels, and failures that read like facts about a broker

We changed inputs after a result was on screen, switched tabs mid-load, and cut the connection to each data source in turn.

Fixed

• Load P&L relabelled old numbers. After Calculate, typing a new cost per mile turned the result computed from the US average into “your cost” with a green “take it” — without recalculating. The result now keeps the inputs it was computed from. The default wear reserve is marked as a US average until you enter your own.
• Rate check kept an old verdict. If a second check failed, the first verdict stayed on screen next to the new rate, and the negotiation line used whatever lane was selected at the moment rather than the lane that was checked. Both fixed.
• Lane rates could show reefer medians on the Van tab. Switching trailer type while rows were loading let the previous type’s answers land in the new tab, including the “top market rate” line. Late answers are now dropped.
• “Not enough data” when the rate server was down. The load check now says the market comparison did not run.
• Broker checks turned failures into findings. A failed read of our payment history showed as “no payment history”; a failed phone lookup showed as “FMCSA has no phone for this number”; an unexpected registry reply could show as “no record”. Each now says the lookup did not complete. Average days to pay is shown only from three or more reports that include a date, with that count.
• A photographed rate confirmation with an unknown MC passed silently. It now warns that FMCSA has no record for that number.
• The notification bell was always empty. For signed-in accounts it never read the alerts the server writes (broker authority, FMCSA changes). It does now.
• Settings could overwrite your profile. If the profile had not loaded, Save wrote empty name and phone fields over the real ones and said “saved”. It now refuses and says why. Lanes chosen during setup are no longer replaced by an empty list on a new device.
• Invoice amounts that could not be read printed as $0.00. The field is flagged and printing is off until it is fixed.
• IFTA dropped a state where you bought fuel but drove no miles — and its fuel credit with it. It stays in the table and the CSV.
• The updates form said “Recorded” after a network error. It now says the request did not go out.
• Brokers were checked against the wrong registry. An MC number read from a rate confirmation arrives as bare digits and was looked up as a USDOT number first. Another company almost always holds that USDOT number, so a real broker was marked “does not match” and the load dropped out of that broker’s rate median and the dispatcher’s score. Both registries are now checked, and rate confirmations marked this way are checked again.
• Sign-in and invitations. Signing in with email no longer drops you into the owner-operator app before your own profile has loaded. An invitation without a role no longer promises one. A failed sign-out now says so instead of looking signed out.
• Company accounts had two buttons to nowhere. “Add a truck” and “Create an order” led to pages that do not exist. The page now says fleet tools are not built and points to the checks that work.
• Detention times carried over between documents. Rate confirmations without a readable load number shared one saved set of arrival and departure times. Each document now keeps its own.
• A typo in miles became a rate. A load pasted as “$3,100, 45 mi” showed as $68.89 per mile in batch triage, rate-con capture and the load check; the last two also compared it with the market. A rate outside $0.30–$20 per mile is no longer shown; the line asks you to check both numbers. “$1,015/mi” is no longer read as $15, and “$2.40 / mi” with spaces is now read.
• The roadmap page carried figures without a source (“$940B+ market”, “500K+ carriers”, “135+ operators”) and a price we have not announced. Removed; the sign-up count is dated, as on the home page.

Changed

• Scheduled checks finish. Background jobs — FMCSA re-checks, the saved-broker watch, the weekly emails — had one minute to run and skipped whoever was left. The FMCSA re-checks now work through the whole list in batches; the others have nine minutes; and a repeated run does not send the same broker alert twice.
• The published dataset file. Row-level events now carry the same bands as the aggregate table (not exact hours, days or percentages), and no rows are published for a set smaller than twenty.
• Limits against automated abuse. The rate-alert form and the verdict-or-range vote accept requests only from this site; AI features have a daily limit of 200 requests per account.

Screens that stayed silent when something failed, and a reader that took the broker’s address for the pickup

We ran every screen with its data deliberately unavailable, and read real rate confirmations through the checker line by line.

Fixed

• The load check read the wrong lane. When it had to find the states in the text itself, it took the first and the last “City, ST” in the document — on a real rate confirmation that is the broker’s letterhead and the remit-to address, not the pickup and the delivery. It now looks for the pickup and delivery lines first and falls back to the order of mention only when they are missing.
• A normal rate confirmation had “no miles”. “Total: $2,150.00” followed by “Miles: 925” on the next line was read as zero miles, so no rate per mile was worked out. Fixed, with tests.
• “Added to the broker’s pay record” when it was not. One account counts at most five payment outcomes per broker per 30 days. Past that, the server stored the report but left it out of the signal, and every screen still said it had been added. They now say it was saved to your log and not counted, and why.
• A failed read looked like an empty page. The notification centre showed no alerts, the rate-con capture page showed no market comparison, and the weekly-email switch in settings showed its default position — all when the data simply had not loaded. Each now says it could not load, which is a different thing from having nothing.
• An FMCSA outage marked brokers as not matching. When the registry did not answer, a rate confirmation from a real broker was stamped “does not match” and dropped out of that broker’s median for good. It is now “not checked” and is checked again later.
• IFTA route miles went missing. Route segments that could not be placed in a state (border crossings, coastline) were silently left out of the per-state table. Their total is now shown so you can assign them yourself before you file.
• One carrier could raise a dispatcher’s score alone. A score needs outcomes from three different carriers, but one of them could report the same dispatcher any number of times. The cap is now five per carrier per 30 days, the same as for broker payments.
• “Send Invites” did nothing. The button in setup had no action behind it. It now sends the invitations and reports on each address.
• Words we could not stand behind. “Verified carriers”, “vetted dispatchers” and “your report protects thousands of dispatchers” are gone: we do not verify carriers or dispatchers, and we have no such numbers. Star ratings are no longer shown as a score out of 100.

The roadmap said three things were done that are not built

We checked every “Done” on the roadmap against what a real account actually sees, and checked the demo for numbers that were not marked as samples.

Fixed

• Route optimization, live cargo tracking and the US freight map were marked “Done”. A real account sees “not built yet” or “no tracking data” on all three; only the demo has screens, with sample numbers. They are now marked “Not built”, and the phase is “Partly built”.
• Features that do not exist were described. “AI Optimize”, “demand heat zones” and “rate forecasts” are gone from the roadmap. Rate analytics is described as it works: rate confirmations shared by carriers, shown for a lane only when at least three carriers contributed, plus public USDA benchmarks.
• The mobile app was listed as a future plan. It exists and is in internal test builds; it is not in the App Store or Google Play yet. The roadmap now says that.
• Demo numbers without a sample label. The demo home screen in the app showed an invented profit per mile with a “Measured” badge; the demo map was badged “Live”. Both now say “Sample”. Demo earnings, dispatcher hub, finance, workspace, notifications and the booking window now carry the sample banner, and sample loads and profiles are tagged where they sit next to real ones.
• Real companies next to invented numbers in the demo. A few real broker and shipper names had survived earlier anonymisation, attached to made-up rates and revenue. They are replaced with invented names. The demo settings also showed three integrations as “Connected” with sync counts; no integrations are built, so the demo now says so, like a real account.

Nine places where a button said something had happened, and nothing had

We went looking for screens that confirm an action the product never performs. We found them, including in tools a carrier could switch on for themselves. Most carried a yellow “preview” label, and that label was not enough: it said the numbers were samples, not that the buttons did nothing.

Fixed

• Quick Pay promised money that does not exist. The page described us as a factoring company: 90% of the load advanced within 24 hours, collection from the broker handled for you. It accepted a Bill of Lading and a rate confirmation and answered “you will receive $X in your account within 24 hours”. Nothing was filed and no money was ever coming. DispaLoadIQ does not advance money and is not a factoring company; the page now says exactly that. If you need cash before the broker pays, the Factoring page works out what a real factor’s rate costs you, on your own numbers.
• DVIR claimed your inspection was filed under 49 CFR 396.11. It showed a report number that was invented and identical for everyone. Nothing was stored — the page had no network and no storage at all. The walk-around checklist is real and stays, now with a summary of the defects you noted so you can copy it into whatever you actually file. The screen states plainly that it is not a filed DVIR. Three counting faults went with it: a clean truck could never finish the inspection, the “items checked” counter always read full, and a hint asked for 24 items when there are 26.
• Identity verification asked for a passport it could not check. It requested a government ID and a selfie holding it, waited 2.2 seconds, and announced that the document matched the photo. No comparison happened; the file was never even read. Beside it stood a privacy note naming an identity provider we have never connected. Asking for a passport under a check that does not exist is not something a preview label excuses. The upload is gone.
• ePOD pretended to send your documents to the broker. A 1.4-second spinner, then “documents sent successfully” and a delivery marked as sent. Proof of delivery is what gets you paid. The screen now shows what such a send would contain and says nothing left the device.
• Onboarding threw away what it asked for. The step titled “where and what you run — so we can show honest rates” asked for your lanes, the states you avoid and your minimum rate per mile, then saved none of it. It saves them now. The minimum rate goes somewhere only you can read: your profile is readable by any signed-in user, and a broker who knows your floor will offer exactly that.
• The module list offered tools that invent their data. An owner-operator could switch on 40 modules, 22 of which were built on sample data. The catalogue now offers only pages whose data is real — 18 of them — and a page returns to the list the day it stops inventing.
• Sample data used real companies’ addresses. Broker names in the demo were already anonymised, but the email addresses behind them were not, so invented payment disputes sat next to live addresses at real brokerages. Real receivers had invented failures attributed to them. All of it now uses a domain reserved for documentation, which cannot belong to anyone.
• Industry figures with no source. “$455M lost annually to freight fraud”, “68% of owner-operators ghosted by a dispatcher”, “4.2 hours before they notice”, “dispatchers with full profiles get 4× more responses”. None had a source and several were invented outright. Removed. A figure returns when it has a published source next to it.
• The trailer guide named platforms that do not exist. An anonymisation pass meant for demo data also renamed the real power-only platforms, so the guide pointed at companies you could not find. It now names Amazon Relay, Uber Freight Powerloop, RXO Flex Fleet and J.B. Hunt 360box — each checked.

Changed

• The three free tools now lead to each other. The rate check was a dead end: the reader and the calculator linked to it, and it linked to neither. Work out your cost per mile once and the rate-con reader tells you when a load pays less detention than your floor, while the rate check shows what a run leaves you.
• Lane watch says what it will actually do. It now names the lane you just checked and the real rule: every Monday we look at the median, you get an email only if it moved 4% or more, and nothing otherwise.
• The calculator is usable with a thumb. On a phone its 27 cost fields were 25–30 pixels tall. They are 44 now — the size both iOS and Android are built for.

The rate confirmation reader and cost per mile work without an account; cost per mile no longer starts from our numbers

Two of the three tools on the home page led to a login screen, and one of them did not do what the home page said it does.

Changed

• Rate confirmation reader, no account. It opens at app.dispaloadiq.com/ratecon, and the home page buttons go straight there. It never needed an account: the reading is a set of text rules that run in your browser.
• Cost per mile, no account. It opens at app.dispaloadiq.com/cpm. Every number is calculated in your browser from your own inputs. Without an account, saving keeps your break-even on this device, and the rate confirmation reader then compares a detention rate with the floor you entered. Templates that follow you across devices still need a free account.
• Less leaves the browser. Each finding carries a short quote from your document so you can check it against the page. Those quotes were sent along with the observation, although they were never stored. Now only which clauses were found and their numbers are sent.

Fixed

• Cost per mile started from an example truck. The home page said nothing is pre-filled. The calculator opened with fuel at $3.89, 6.5 MPG, a $2,200 truck payment, a $2.45 rate, $75/hr detention and a 25% tax rate, and drew a break-even and a trip profit from them. Every field now starts empty.
• Profit shown from incomplete costs. With only fuel entered, the calculator labelled a $0.54 cost per mile “Efficient — below average” and projected $168,942 a year. Margin, trip profit, the monthly projection, rate scenarios and the target rate now appear only when every cost line is filled in (0 where there is none). The “below average” label had no source and is gone.
• The sample rate confirmation could enter the dataset. Running the reader’s built-in sample reported it like a real document — at most once, because documents are deduplicated. It is now never reported. Whether such a record exists has not been checked yet.

The About page was removed

It described more than the product does, and it contradicted the home page.

• What it claimed. “Proprietary AI load scoring, FMCSA HOS compliance, full TMS”, “DAT ONE API (planned)”, “Real-Time Driver Communication Hub”, a “500K+” figure and “$48K/mo Revenue Visibility”. Hours-of-service compliance, a TMS and a load-board integration are on the home page’s own list of what the product does not do. The two figures had no stated source.
• What replaced it. /about now redirects to the home page, which carries what works today, what does not, and who built it.
• What was kept. The removed page is preserved as it stood, in the Wayback Machine (September 5 and September 8) and in the project’s version history. Nothing was rewritten after the fact.
• What comes next. A separate About page may return once the rate confirmation reader and cost per mile work without an account. Until then it would mostly repeat the home page.

The website was rebuilt around the free broker check

The old page collected email addresses and never linked to the product. It had sixteen links to a waitlist form and none to the app.

Fixed

• Zero links to the product. The page described a platform without offering a way in. There are now direct links to the free broker check in the top bar, the navigation, the hero, the tool cards and the footer.
• Seven links that went nowhere. Every href="#" is gone. Every link on the page now resolves to a real page.
• A second, stale copy of the product. The site carried its own /check page that called the same production endpoints as the app but had not received the fixes made on September 2. It is deleted; /check now redirects to the app. One tool, one place, one codebase.
• Two sign-up forms producing two rows per person. One form now, at the foot of the page, carrying hidden source fields so a registration can be traced to where it came from.
• Claims the product does not support. "AI-Powered Dispatch" (five times), "Limited Spots Available", "Cancel anytime", "Early access pricing locked in for life", "AI Finds Best Loads", "real support, real people", and the truck-type requirements — which are brokers' requirements, not ours — have been removed. What is not built is on the Roadmap or on the page below the fold, not in the headline.

First-launch audit: five defects found and fixed

All five were found by running the product, not by reading the code.

Web

• The detention claim inserted a rate that was not yours. The letter drafted to the broker carried a $50/hour detention figure taken from nowhere in particular. It no longer fills in a rate the carrier did not enter.
• The dispatcher catalogue reported an offer that had not been sent. A button confirmed success for an action that never happened. A false confirmation costs more than a dead button: the person relies on it and waits for a result that is not coming.
• Cost per mile never reached existing users. The module was added to the defaults, which only affects new accounts; everyone already registered kept the old list. Rolled out to existing users.
• Broker Trust was English-only in a product that is otherwise trilingual. Translated.
• The header carried items that led nowhere. Cleaned.

Mobile

• The ELD screen asked for a real API key for an integration that does not exist.
• Load Check showed "you keep $X" computed from someone else's cost per mile.
• Cash Plan, TCO, Batch, the tax reserve and factoring were pre-filled with our figures instead of being left empty.
• A minimum rate-per-mile threshold silently filtered the board with no indication that it had.
• Five default tabs were untranslated.

The "Transport Company" role was removed from the website, not softened

• The role had been switched off in the product since July 3: it existed in the code but was filtered out of the sign-up screen, so anyone who clicked through reached a registration form with no role for them. Four of its five advertised features were also unbuilt. A feature can be marked "in development"; a locked door cannot be advertised as an entrance.