Letter of Support Request for NALC Review

A carrier-protective visibility pilot forsafer, fairer postal operations.

Letter carriers are operating under increasing workload, safety, staffing, parcel, and service pressure. Momentum Labs respectfully asks NALC to help shape and conditionally support a limited USPS pilot that makes those pressures visible and documented before carriers are blamed for them.

No discipline use
No route cuts
Jointly governed

Letter for NALC Review

Request for review and conditional support of a carrier-protective USPS visibility pilot.

Dear NALC Review Team,

Letter carriers are operating under increasing workload, safety, staffing, parcel, and service pressure. Momentum Labs respectfully submits this request for your review, guidance, and potential conditional endorsement of a limited USPS pilot using MovementAI and Quotron visual operations displays. Our goal is simple: make those pressures visible and documented before carriers are blamed for them, while creating shared evidence that improves safety, staffing, route fairness, contractual accountability, and service reliability.

Momentum Labs builds MovementAI, a shared operating-visibility layer for high-motion facilities. The system analyzes approved operating signals — such as route readiness, parcel volume, processing and station-arrival timing, dispatch pressure, aggregate manpower capacity, and safety conditions — and converts them into plain-language workload and safety visibility. Quotron adds a physical visibility layer: zone-specific ticker displays that can show approved, non-sensitive alerts where action happens, rather than limiting operating conditions to a one-sided dashboard.

We are not asking NALC to endorse AI management technology or surveillance. We are asking NALC to help shape a pilot that does the opposite: makes facility conditions visible so carriers are not blamed for volume spikes, upstream processing delays, station-arrival drift, unsafe weather, manpower shortfalls, unrealistic route expectations, or dispatch pressure created by the system around them. The pilot should not track, rank, score, discipline, compare, or pressure individual letter carriers.

If USPS accepts a pilot, NALC’s support would be essential. Your endorsement, with written guardrails, would help ensure this technology is tested as a carrier-protective tool: non-disciplinary, transparent, jointly reviewed, and focused on safety, workload visibility, route protection, and fair staffing evidence. The pilot should not be used to eliminate routes, reduce staffing, increase forced overtime, impose new performance standards, or weaken the National Agreement, local agreements, route adjustment procedures, grievance rights, or existing safety obligations.

We believe this pilot can give NALC and USPS a shared way to see what carriers experience every day — before it becomes overtime conflict, missed assistance, unsafe conditions, grievance disputes, or service failure. We respectfully request a meeting with NALC reviewers to review the proposed pilot, discuss labor safeguards, and determine whether NALC would consider a conditional letter of support subject to written non-disciplinary, non-surveillance, and contract-protection terms.

What This Pilot Is Not

The clearest trust point is what the pilot cannot be used for.

NALC support should be based on written limits that prevent the pilot from becoming a surveillance, discipline, route-cutting, or speedup tool.

Not individual carrier surveillance

Not scanner or GPS discipline

Not street-time scoring

Not route-cut justification

Not staffing reduction support

Not a one-sided administrative dashboard

What NALC Would Gain

Labor should not be outside the system looking in.

If USPS modernizes operating visibility, NALC should help shape the rules early so the system becomes shared protection infrastructure, not one-sided administrative visibility.

Shared access to approved workload and safety evidence

Better documentation of route overload and staffing mismatch

Stronger basis for heat, fatigue, and safety conversations

Clearer context for steward conversations and grievance review

Visibility into facility causes of carrier delay

A seat at the table before technology is deployed

Who We Are

Momentum Labs builds MovementAI.

MovementAI is an operating-visibility layer for complex facilities. For postal operations, it can help document route overload, package pressure, dock delays, dispatch risk, manpower mismatch, safety exposure, and workload causes before those pressures fall onto carriers without context or become one-sided data visibility.

What Quotron Adds

The building can show what is happening.

Quotron displays can translate approved MovementAI outputs into shared visual operations: route assistance needed, heat safety alerts, dispatch countdowns, dock pressure, package surges, and customer-safe service notices visible to the people affected by those conditions.

Why NALC Should Care

This should help prove what carriers already know.

The strongest case for NALC support is not automation. It is shared operational evidence: making route pressure, staffing need, safety risk, dispatch conditions, and facility causes visible before carriers are blamed for system conditions.

Route protection evidence

Show recurring route overload, parcel spikes, departure risk, and assistance needs with shared operational proof.

Overtime transparency

Document when overtime pressure comes from volume, upstream processing delays, station-arrival drift, aggregate manpower gaps, dispatch timing, or unrealistic expectations.

Safety visibility

Surface heat, fatigue, late-day risk, weather exposure, and workload stress before they become injuries or emergencies.

Fair staffing signals

Make staffing mismatch visible early so supervisors can request help, rebalance work, and reduce forced crisis decisions.

Facility-flow context

Connect dock, staging, package, and dispatch conditions so carrier delays are understood in full branch context.

Shared accountability

Give carriers, stewards, and management a common view of workload pressure, safety context, staffing needs, and grievance-relevant operating conditions instead of hidden dashboards or incomplete assumptions.

NALC should support the pilot only if it is explicitly non-disciplinary, non-surveillance-based, jointly reviewed, and designed to protect letter carriers from unsafe, unfair, or hidden operating pressure.

NALC-Specific Visuals

What NALC would be able to see.

The visual layer should not sell “cool tech.” It should show carrier-protective evidence: route pressure, safety risk, aggregate manpower mismatch, station-arrival ripple effects, and facility causes without person-level tracking.

Shared Protection Board

Approved route-level and facility-level visibility

Route 22 parcel load 38% above baselineLate inbound truck affecting 9 routesHeat index safety alert active 1–4 PMDispatch risk caused by dock delay, not carrier delay

Route pressure

Route 14 flagged for assistance review

Safety condition

Heat exposure risk visible before departure

Facility cause

Dock delay documented as source of route impact

Allowed: route-level, zone-level, facility-level pressure and safety conditions.

Not allowed: individual ranking, speed scoring, discipline flags, or route-cut justification.

What We Are Asking

We are requesting NALC’s review, guidance, and conditional endorsement.

If USPS accepts the pilot, we would like NALC reviewers to consider supporting it only as a limited, carrier-protective modernization effort — provided written labor guardrails are built into the pilot from the beginning.

NALC’s conditional endorsement would help ensure the Building Brain is shaped with labor trust, contractual respect, and shared visibility — not deployed as a one-sided administrative tool.

Recommended Conditions for NALC Support

Support should be conditional, written, and enforceable.

Written non-disciplinary agreement before pilot launch
No individual carrier tracking, ranking, speed scoring, discipline, or harassment
No use of pilot outputs to eliminate routes, reduce staffing, increase forced overtime, or impose new performance standards
No replacement for the National Agreement, local agreements, route adjustment procedures, grievance rights, or safety obligations
NALC branch and steward access to the same approved operational visibility shown to management
Joint NALC/USPS review of metrics, data definitions, displayed content, and pilot findings before any expansion

Recommended endorsement language

NALC should support a limited USPS pilot of MovementAI and Quotron only as a transparent, jointly governed, non-disciplinary workload, safety, manpower, route-pressure, and service-visibility tool that protects letter carriers, respects contractual rights, prevents one-sided data visibility, and improves service reliability for the communities they serve.

Final Position

NALC should support the pilot if it protects carriers first.

This proposal makes sense because it asks NALC for exactly the right thing: not blind approval of technology, but careful review, written guardrails, and conditional endorsement of a pilot that could make carrier workload, safety, manpower, and route conditions more visible.

With NALC involved from the beginning, the pilot can be framed as a shared protection layer rather than a management surveillance system, route-cutting tool, or one-sided operational dashboard.

Our request: help shape and conditionally endorse a limited, transparent, jointly governed USPS pilot that proves whether MovementAI and Quotron can improve safety, fairness, staffing evidence, route protection, contractual accountability, and service reliability.

NALC support request URL

/nalc-support-letter

Owner pilot

Turn friction into a clear decision.

Start with your messiest movement problem. We'll map the signals, deploy intervention cards, and capture the proof.

Build the memory

Start with one asset, workflow, or zone and define the rules the Building Brain needs.

Flow the decision

Turn one live movement problem into a clear intervention card or dashboard event.

Sync the proof

Create a simple record of what happened, what action was taken, and what improved.

Building Brain Delivery

Deliver the brain as Flow cards, a central dashboard, or both.

Action cards

Route the brain’s next move directly to the people or teams who need to act.

Central dashboard

Collect every movement decision and evidence thread in one owner/operator view.