Why do Sales, Delivery and Finance report different figures?
Sales reports the value of the contract. Delivery reports the work completed, including extra visits. Finance reports invoices, revenue and costs. All three may be correct — but management still needs to connect them to understand what happened to the job and who could have acted sooner.
The three reports may all be right
Each report may be correct: signed value, delivered work and recognised revenue measure different things. Link the order, agreed scope, work completed, variations and invoices before treating any difference as an error. The practical issue is whether management can reconstruct a job while there is still time to act.
Sales can see pipeline. Delivery can see work. Finance can see revenue and cost. None of those views alone explains the whole commercial state.
In an earlier property-services example, account revenue and property-maintenance activity existed in different records. The missing link prevented a reliable account-level assessment; it was not evidence by itself that any particular customer was unprofitable.
When does the extra cost become visible?
A service company may invoice at month-end but only review actual labour and uncharged call-outs after a contract has finished. By that point the scope cannot be renegotiated and the same terms may already have been offered to several more customers.
A useful view connects the original price and response conditions to each delivery event and any approved change. It should distinguish extra work allowed by the contract from work triggered by later customer requests or avoidable defects. If the records are sufficiently clear, a simple order-and-cost reconciliation may be enough; a new dashboard is not the default answer.
Even a complete report cannot decide who is authorised to promise an exception or approve additional work. That responsibility belongs in the contracting and operating rules. The joined information makes the consequence visible; management still has to assign authority to act on it.
Which changes does management need to spot early?
What happens before, during and after the deal? Which relationships are expanding, contracting, becoming harder to serve, creating new commitments or changing strategically?
The point is not to show more metrics. It is to represent the changes management needs to recognise and act on.
Which records need to be connected?
The design can then be implemented in CRM, BI, reporting, workflow or a combination.
What needs to be known to manage the whole outcome?
Which commercial changes need to become explicit?
How customer, opportunity, commitment, delivery and finance relate.
Which financial outcomes need to connect back to operating reality.
What management should be able to see without reconstruction.
What should change in process, reporting or systems - if anything.
Agree what the numbers mean before building a dashboard
A dashboard can only display the model underneath it. If the states, events and relationships are wrong, better visualisation makes the wrong model easier to see.
When a joined management view is useful
Some diagnostics end with a process change or a small reporting fix. I use Management View when the evidence shows that the business lacks a coherent management representation.
Decisions a shared view should support
Choose information according to the response management needs, not the number of dashboards.