A Kanban Board for Your Moving Company Sales Pipeline
Why working your work requests as cards beats scanning a list, and where the first release stops.
Most moving companies run their sales pipeline as a list. Rows of work requests, a status column, a filter or two, and a sales manager who reconstructs the state of the pipeline in their head every Monday morning. It works, in the sense that the data is all there. It just makes the two questions that matter hardest to answer: where is everything stuck, and what is worth chasing this week.
Movegistics AI shipped a Kanban View for Work Requests on September 3, 2026 — one of the most-requested features on the product updates board. This is the operational explanation: what changes when a pipeline becomes a board, which details actually matter in a moving company specifically, and where the current release stops.
The Problem with Working a Pipeline as a List
A list view answers “what exists.” A pipeline question is almost always “what is the shape of things” — and shape is exactly what a table of rows hides.
Three specific costs show up in moving companies. First, advancing a deal is expensive in clicks: open the record, change the stage, save, go back. Do that thirty times a day and reps quietly stop keeping stages current, which corrupts every report downstream. Second, stage totals are invisible: knowing you have 40 work requests in Estimate Provided tells you far less than knowing those 40 represent $180,000 and a 22% win rate. Third, and most expensive, dead pipeline accumulates silently. Nobody sets out to leave a work request untouched for four months. It just never surfaces, because nothing in a list view makes staleness visible.
What Changes with a Board
Under Sales → Work Requests, a Kanban View toggle switches the same data into stage columns: Survey Scheduled, Lead Qualified, Estimate Provided, and Negotiation in Progress. The same button switches back to List View at any time — this is a second lens on your existing pipeline, not a migration.
Every work request becomes a card carrying its ID, service type, status badges, owner, customer, value, move date, and tags. Dragging a card to another column updates that work request’s stage immediately. Hovering a card exposes a pencil icon that opens the full Edit Work Request page, and an icon row along the bottom gives one-click Unassign, Clone, Download Summary, Add Follow-Up, and Delete. The point is that the board is a workstation rather than a dashboard — you are not looking at the pipeline, you are working it.
Advanced Filters, Quick Filters, and Saved Views all drive the board exactly as they drive the list. Anything you have already built keeps working.
Numbers You Can Trust in Every Column
This is the detail that separates a useful board from a pretty one, and it is worth being precise about.
Each column header shows the count, dollar total, and win percentage for that stage. Critically, those figures are calculated server-side across the entire filtered pipeline — not from the cards currently rendered on screen. Cards themselves load 25 at a time per column with infinite scroll, so the board stays responsive at any data size.
The distinction matters more than it sounds. A board that sums only the loaded cards gives a sales manager a number that changes as they scroll, which is worse than no number at all. Here, the header total for Estimate Provided reflects every matching work request in your date range and filters, whether twelve cards are loaded or four hundred.
The Five-Month Window, and Why It Exists
The board defaults to a five-month window on the move date: the previous month through the next three. That default is a moving-industry decision rather than a generic one. Interstate and military jobs routinely book 60 to 90 days out, so a board defaulting to “this month” would hide the majority of a long-haul pipeline, while a board defaulting to “everything” would bury this week’s work under next spring’s.
The window is adjustable to any custom range through the Date Range picker, or can be set to All to remove the limit entirely for full-history review. Most operations will set it once and leave it.
A 30-minute demo using your stages, your service types, and your actual booking lead times.
Cleaning Up Stale Pipeline in Bulk
The left filter rail gives one-click views for All, Booked (Closed Won), Closed Lost, Tentative, AI Survey, and No Activity — the last meaning work requests with no updates in the past 60 days.
No Activity is where the real housekeeping happens. With that filter applied, checkboxes appear on every card and every stage. You can tick cards individually, select a whole stage at once, or use Select All Cards, then click Mark Selected as Closed Lost to close them out in a single action.
Bulk selection deliberately lives only inside the No Activity filter. That is a sensible guardrail: mass stage changes are exactly the kind of operation you want available for cleanup and unavailable by accident on a live pipeline.
One more visibility touch: work requests with an AI survey attached carry a distinctive colored border and badge, so the leads that historically convert best stand out without needing a filter at all.
What Sales Managers Will Care About
- Stage hygiene improves because advancing a deal costs one drag. The cheaper the update, the more current your pipeline data, and the more trustworthy every report built on top of it.
- Column totals reflect the whole filtered range. Read them in a pipeline review without caveating that the numbers only cover what loaded.
- Win percentage sits at the top of each stage, so the conversation moves from “how many are in Negotiation” to “what does Negotiation actually convert at.”
- Stale pipeline becomes a two-minute weekly task instead of a quarterly cleanup nobody schedules.
- Permissions are simple in this release: anyone with access to the Work Requests module can drag cards between stages.
Where This Release Stops
Worth stating plainly, because it affects how you roll this out. Cards can currently be dragged between any two stages. Stage rules — for example, requiring that an estimate exists before a work request can enter Estimate Provided — are slated for Phase 2 and are not in this release.
For most teams that is fine, and arguably preferable while people are learning the board. But if your process depends on stages being gated rather than conventional, plan on reinforcing that with training for now rather than assuming the board enforces it.
Two smaller conveniences are also queued for Phase 2: a per-user saved date range, so a custom window survives your next login instead of resetting to the five-month default, and a per-user saved view preference, so the Work Requests page can open in Kanban for you every time. Until then, expect to flip the toggle and reset the window each session.
Where This Fits in the Sales Stack
The board is a view over work requests, so it sits directly on top of the pipeline that the CRM already maintains. Leads arriving from web forms, third-party lead sources, and phone calls land as work requests; AI virtual surveys attach to them and mark those cards on the board; estimates and bookings advance them through the stages you are now dragging between.
It also pairs with the Survey Report that shipped in August, which breaks down survey completion rate and work-request-to-booking conversion by owner. The board tells you where the pipeline is stuck right now; the report tells you which rep it is stuck with, and at which step. Both live under Sales.
Frequently Asked Questions About the Kanban Pipeline View
Does switching to the board change my data or my existing views?
No. It is a second view over the same work requests. Advanced Filters, Quick Filters, and Saved Views drive the board identically, and the toggle returns you to List View at any time.
Are the column totals accurate when I have thousands of work requests?
Yes. Count, dollar total, and win percentage are calculated server-side across the full filtered range. Only the cards themselves paginate, 25 at a time per column with infinite scroll.
Can I stop reps from dragging cards into a stage they shouldn’t?
Not in this release. Anyone with Work Requests module access can drag between any stages. Stage rules arrive in Phase 2.
Why does the board default to five months instead of the current month?
Because interstate and military jobs commonly book 60 to 90 days ahead, so a one-month default would hide most of a long-haul pipeline. The window covers the previous month through the next three, and is adjustable or removable.
What counts as “No Activity”?
A work request with no updates in the past 60 days. It is also the only filter in which bulk selection and Mark Selected as Closed Lost are available.
How do I spot leads with an AI survey attached?
Those cards carry a distinctive colored border and badge on the board, and there is a dedicated AI Survey quick filter in the left rail.
Work your pipeline the way you actually think about it
Get a 30-minute walkthrough of the Kanban board on your own stages and service types — including how to set the date window and run a first stale-pipeline cleanup.
Book a Demo
Typical demo: 30 minutes · For movers of every size
