Non-drive-alone journeys
Define qualifying shared or transit-connected trips for an employer, campus, or agency program. Retain the evidence and rule that establish eligibility.
TRANSPORTATION DEMAND MANAGEMENT
Fund better travel.
Verify the outcome.
Arcus connects transportation demand management to a Verified Outcomes Engine (VOE), accountable rewards, and privacy-preserving program data. Define the mobility choices you want to encourage, establish which journeys qualify, and connect program funding to outcomes you can explain.
Discuss a TDM programTHE PROGRAM MODEL
01 / PARTICIPATIONA qualifying mobility choice
Transit, a shared trip, or an eligible arrival
02 / VERIFIED OUTCOMES ENGINEEvidence meets program policy
Decision, reasons, and confidence retained
03 / AUTHORIZED EFFECTAn accountable reward
Eligibility and campaign capacity govern issuance
04 / PROGRAM INSIGHTA measurable result
Aggregate participation and cost per outcome
Illustrative workflow · Scope defined for each program
THE INFRASTRUCTURE FOR DEMAND CHANGE
A common engine for the behavior your program values.
Transportation demand management encourages people to use transportation capacity more effectively. Arcus focuses on the mechanism connecting an eligible action to a decision, a reward, and a defensible program record.
Time and place that matter
Focus a program on an eligible corridor, location, or arrival window. Connect off-peak or first-mile/last-mile goals to explicit qualifying conditions.
Repeatable program learning
Understand qualifying participation, repeat behavior, reward cost, and progress toward fewer single-occupancy vehicle journeys.
FROM EVIDENCE TO REWARD
The policy decides what earns the reward.
- 01
Define the qualifying journey
Set eligible participants, modes, places, time windows, evidence requirements, and reward terms under a named policy.
- 02
Evaluate authorized evidence
Retain source, freshness, consent scope, and confidence. Route insufficient or conflicting evidence through the agreed review path.
- 03
Authorize the reward
Connect eligibility to funded campaign reward capacity. Bound issuance to program limits and retain the decision behind it.
- 04
Preserve an accountable record
Connect each result to its rule and any reward. Idempotent processing is intended to prevent a retry from issuing the same reward twice.
MAKE THE IMPACT TRACEABLE
Measure the action. Substantiate the change.
Verified journeys document the behavior a program encouraged. Connect that evidence to the intervention, an appropriate baseline, and a stated method to demonstrate progress and evaluate the change your program creates.
What qualified?
Qualifying trips by program and mode, evidence confidence, and review outcomes.
What did funding enable?
Authorized capacity, rewards issued or denied, remaining capacity, and cost per verified outcome.
What changed over time?
Repeat participation and measured progress toward fewer drive-alone trips. Label modeled vehicle miles and emissions with their factors and uncertainty.
PRIVACY-PRESERVING PROGRAM DATA
Useful evidence without unrestricted trip histories.
Program reporting should disclose the information needed to evaluate outcomes while limiting exposure of individual activity.
The design starts with purpose-bound consent, authorized evidence, and minimum necessary disclosure. Coarse geography, aggregate reporting, limited retention, and small-group suppression reduce exposure. Reporting controls and privacy thresholds are established for each deployment.
A consumer application handles the participant experience. Arcus focuses on the shared program machinery: verification, policy, reward controls, and outcome reporting. See how Hytch brings the consumer coordination side to life.
PRACTICAL ANSWERS
Define the program. Understand the result.
What does Arcus add to a TDM program?
Arcus brings a common verification and rewards model to transportation demand management. A program owner defines qualifying behavior, authorized evidence, and campaign rules. The Verified Outcomes Engine connects the decision to an outcome record and any permitted reward, creating a basis for cost per outcome, repeat participation, and measured progress toward program goals.
How are rewards tied to qualifying trips?
The intended mechanism releases a sponsor-funded reward only after the applicable policy establishes eligibility. Campaign reward capacity bounds authorized issuance; each reward retains its connection to the qualifying outcome. Duplicate requests should not create duplicate rewards, and incomplete or conflicting evidence follows the program's denial or review path.
How can the program demonstrate fewer single-occupancy trips?
Connect the intervention to verified qualifying journeys, then compare program results with an appropriate baseline. Report observed actions, repeat behavior, and cost per outcome. A stated method and assumptions support claims about reduced single-occupancy vehicle trips; any modeled vehicle miles or emissions should include their factors and uncertainty.
Can a TDM program use its own consumer application?
Arcus is being developed as independently licensable infrastructure. A partner application can be the participant experience while Arcus provides the shared verification, policy, reward-control, and reporting model. Evidence access, integration readiness, operating controls, and fulfillment are established for each proposed deployment.
LET'S DEFINE THE OUTCOME
Which travel behavior should your funding encourage?
Bring your target behavior, permitted evidence sources, program constraints, and measurement question. Start with a bounded pilot and a clear definition of a qualifying result.
Arcus is a platform initiative in development. Pilot scope, integrations, controls, and readiness are agreed for each deployment.