What TDM software actually measures, vendor by vendor.

The four questions that separate these products

Feature grids make these platforms look interchangeable. These four questions do not.

• Where does a trip record come from? A survey, a self-reported log, a GPS recording, a parking badge read, a transit card tap, and a third-party app import are six different levels of evidence. Most platforms accept several. Ask which one the number in the report was built from.
• Who is the end user? An employee administering a benefit, a commuter logging a challenge, or a group of friends deciding where to go. The product's whole shape follows from this, and so does whether anyone opens it when no program is running.
• What does the money do? Administering a pre-tax deduction, allocating a parking space, and releasing an incentive after an outcome are three different financial jobs with three different control requirements.
• What happens when a claim fails? This is the question that gets skipped. Ask whether a rejected trip is recorded with a reason, whether you can read the denial list before you buy, and whether a campaign can overspend its funded capacity.

What each platform's own site says, checked 25 and 28 September, 2 November and 5 November 2026

Descriptions below are each company's own public positioning, not our assessment of it. Where a site does not state something, this page says that rather than guessing.

Where Hytch differs, stated narrowly

GPS is not the difference. CommuteHub's own site describes GPS-verified carpool trips, so any vendor claiming phone-based trip capture as a unique property is overstating it, and that includes us. Three things are actually different, and all three are checkable before you talk to anyone here.

• The denial list is published. The reasons a claim gets rejected are written down in public: outside the program time window, insufficient dwell, low-confidence location, duplicate submission, failed geofence containment, suspicious speed, incomplete trip, and campaign capacity exhausted. Every denial is recorded with its reason. Read them on the rewards page before a sales conversation, not after.
• Funded capacity pauses itself. A sponsor buys a fixed reward capacity, and an issuance that would exceed the remaining balance is rejected rather than approved. A campaign stops when its capacity is gone instead of overspending and reconciling later. The supported issuance path uses idempotency controls. Confirm the program's payout path, reconciliation and exception handling separately.
• The reporting policy sets a numerical floor. MobileFlow’s adopted reporting policy requires withholding nonzero counts based on fewer than 10 distinct people, including sensitive categories. The minimum may be raised, never lowered. Confirm the effective threshold, complementary suppression and permissions in the selected reporting environment before external disclosure. Confirm configured location precision, retention and deletion for the selected data flow before sharing a report. The full list, including what Hytch does not hold, is on the trust page.

The unit of record differs too. These other platforms record a commute belonging to one employee. Hytch records a plan belonging to a group, which is why its reporting describes coordinated movement rather than individual commute compliance, and why the same product is useful on a Friday night with no employer involved.

Where Hytch is not the answer

A comparison page that only lists reasons to pick the author is an advertisement. These are real gaps, and for some requirements they are disqualifying.

• No parking management. No parking inventory, reservations, permits, waitlists or cash-out administration. Both CommuteHub and Luum treat parking as a first-class product surface. Hytch does not have one.
• No pre-tax benefits administration. No transit card issuance, no payroll or HCM integration, no IRS qualified-transportation-fringe handling. If the requirement is administering the monthly pre-tax limit, that is a benefits platform purchase.
• No published roster of contracted TDM customers. CommuteHub names large employers, universities, health systems and state DOTs on its site. Hytch does not publish an equivalent list, and its institutional history is sponsor-funded reward programs rather than enterprise TDM contracts. Treat that difference as real when you score references.
• No security certification. Hytch holds no SOC 2 report, no ISO certificate and no third-party security audit, and does not claim one. If your procurement gate requires one, Hytch does not clear it today.
• Message content is not end-to-end encrypted. Encryption in transit and at rest is a different guarantee. MobileFlow and the providers that operate the platform retain the technical ability to access message content.

Ask for scoped program evidence

A historical payout or event-volume claim needs a dated, reconciled accounting record with a defined scope. This page does not provide that evidence. Program reporting should distinguish capacity, authorized rewards, issued benefits, redemptions, and confirmed settlement; none predicts what a new member will earn.

A buyer should request the period, participating cohort, evidence policy, missingness, funding and settlement states, and method behind any outcome or savings claim. This preparation is not a claim of contracted enterprise TDM deployments. Review the program evidence requirements before treating a historical figure as proof.

Common questions