DSP Software and the Problem of Proving Invisible Work
Summary answer: destination service providers sell prevention, and prevention is hard to evidence because its successes are things that did not happen. FIDI's April 2026 whitepaper identifies this directly and argues that technology's role is not to create value but to make existing value visible and communicable. In system terms that means a DSP platform's most important function is not the task list. It is whether it can produce, on demand, a complete record of what was delivered, when, by whom, and with what outcome.
Disclosure: Moovi builds DSP capability into its platform and competes in this market. The FIDI whitepaper is FIDI's work, not ours.
What the FIDI paper says
FIDI Global Alliance published "Proving the value of Destination Services in a cost-driven world" in April 2026.
Its central observation is that destination services operate in what it calls the prevention zone. The assignment that never failed, the lease dispute that never happened, the family that settled without incident. Real outcomes, genuinely difficult to represent in a procurement spreadsheet.
Several changes made this harder. Procurement now controls decisions it did not previously own. Institutional knowledge inside corporate HR and RMC teams has thinned, so the people buying and selling DSP services often lack direct experience of what those services prevent. And pricing shifted from being fixed on scope to being fixed on time, which changes the client's first question from what will this achieve to how many hours does this cost.
The paper is candid that the industry participated in its own commoditisation rather than simply suffering it.
On technology it is precise, and worth quoting exactly once. It states that technology "does not create DSP value per se; it makes that value visible and communicable".
That is the most useful description of what DSP software is for that this industry has produced.
What that means for a system
If technology's job is to make delivered value visible, the design priority is the evidence record, not the task list.
Every service delivered, timestamped and attributed. Not a status field showing a stage complete, but who did it, when it completed, what the outcome was, which supplier performed it, what documents exist, and whether the client signed.
Documents held against the engagement. Signed tenancy agreements, registration confirmations, school acceptance letters, immigration documents. Retrievable later by the client without asking the provider.
An output procurement can use. The whitepaper's argument is that the case must be made to buyers who respond to evidence rather than assurance. That means a programme level record, across every assignee for one corporate client, produced on request rather than assembled over a fortnight.
Three parties, three views. The corporate client holds the rate card, receives the invoice and needs programme level rollup. The assignee needs a scoped view of their own services and nothing else. The supplier is assigned per task with their cost attached to the line they performed.
What an evidence layer looks like in practice
The capability worth asking any vendor about is this: can you answer the question "what did your consultant actually do for this assignee in March" without anyone assembling anything.
In Moovi that is an engagement record with every service, every task, every timestamp, every sign off, signature certificates attached and SHA-256 hashes printed, exported as a single pack. The same export runs at programme level across every assignee for one corporate client. Two clicks.
A DSP engagement is treated as a first class work unit, a peer of a job rather than a variant of one. A pure DSP operator with no vehicles, no warehouse and no crews holds zero job records and nothing degrades. There is no move date to invent and no removals scaffolding to work around. Where a DSP engagement sits alongside a move, the two are siblings on one thread, each independently quoted, delivered and billed, and closing one does not close the other.
Service lines are a per tenant catalogue, so an operator adds a service and its task checklist from settings without waiting for a release. Orientation, home search, school search, settling in and departure ship as defaults; repatriation, tenancy management and anything else a firm sells are rows they type.
Money runs through the same engine as a move rather than a parallel one. Each service line carries a sell price from the rate card and a supplier cost, so margin is live at engagement level and rolls up by service type. Fixed fee, hourly and bundles. Multi currency with a stamped FX rate. A corporate client's rate card applies to their engagements automatically.
And one deliberate absence, because of how this category is currently marketed: no AI touches DSP delivery. The prompt engine is a date engine and is described as one. Milestone emails reach the assignee, document requests go out, overdue work nudges the consultant. Warn, never block.
The tension the paper is honest about
It would be easy to read the whitepaper as an argument for technology replacing consultants. It says the opposite.
Local expertise, human judgement and relational trust are what destination services actually sell. The paper reports that clients who moved towards virtual or technology led DSP found it less successful than expected and have moved back towards people on the ground.
What technology does well is capture and communicate what happened, and handle administrative layers such as lease review, compliance checklists and document preparation, freeing consultant time for work that requires a person.
That is a narrower and more honest claim than most software marketing in this sector makes, and it is the right one.
The certification context
FIDI launched a standalone FIDI-DSP Quality Certification in 2025, open to pure DSP companies for the first time, alongside FIDI-FAIM for household goods movers.
That matters commercially. A standalone certification creates a defined quality standard for a category that previously had none, giving procurement something to specify other than price. Any DSP system should be able to produce the records an audit would ask for.
The smaller provider problem
The paper makes a point worth emphasising: smaller DSPs cannot fund bespoke systems, and the realistic path for them is shared frameworks and collective tools.
This is the same structural problem the moving industry has. Capability a large provider builds in house is unaffordable individually for a small one and entirely affordable shared across many. For software vendors the implication is simple. Building evidence capability only enterprise providers can afford solves the problem for the part of the market that already had options.
What to ask of any DSP system
Can it produce, for a single assignment, a complete record of what was delivered, when and by whom, without manual assembly. Can it do the same at programme level across a client. Can the assignee access their own documents without going through the consultant. Does it hold the documents themselves or only references. Can a pure DSP operator use it without configuring around removals features they will never use.
Most systems answer well on the first and poorly on the rest.
Frequently asked questions
What is a DSP in relocation?
A destination service provider. DSPs deliver the services an assignee needs on arrival: home finding, lease negotiation, school search, settling in orientation, temporary accommodation, and partner and family support.
Why is DSP value hard to prove?
Because destination services largely prevent problems rather than produce deliverables. The successes are the lease dispute that did not happen and the assignment that did not fail, which are difficult to evidence in a procurement process.
What does FIDI's 2026 DSP whitepaper say about technology?
That technology does not create DSP value but makes it visible and communicable. It reports that clients who moved towards technology led DSP found it less successful than expected and have moved back towards local consultants.
What is the FIDI-DSP Quality Certification?
A certification launched by FIDI Global Alliance in 2025, open for the first time to pure destination service providers as a standalone certification, alongside FIDI-FAIM which certifies household goods moving companies.
What is a DSP evidence pack?
A single export covering an engagement or a whole programme: every service, every task, every timestamp, every sign off, with signature certificates attached and hashes printed. It exists so a corporate client asking what was delivered in a given month gets a document rather than an assurance.
Can DSP software work for a provider with no moving operation?
It should. In Moovi a DSP engagement is a first class work unit rather than a variant of a move, so an operator with no vehicles, no warehouse and no crews holds no job records and nothing degrades. Many platforms in this space are removals systems with DSP fields added, which shows.
Sources
- FIDI Global Alliance, "Proving the value of Destination Services in a cost-driven world", April 2026
- FIDI Global Alliance published material on FIDI-DSP and FIDI-FAIM certification
A note on this piece. We write properly elsewhere. This one is written to be found, which means headings, structure and the answer near the top. If you want the version with an argument in it, that is what the Moovi Dispatch is for.
About the author. Sam Clark is the founder of Moovi. He started in the removals industry as a porter at Pickfords at fifteen, spent sixteen years in enterprise technology and regulated markets working with the NHS and Crown Commercial Service, and returned to the vans in 2025 before building anything. He is the author of the Moovi Regulatory Review, published free twice a year.