Reviewing a mobility partnership: connect service, cost and people's experience

A partnership review should help someone decide what to continue, correct or reconsider. A long presentation of activity can leave those decisions untouched. Start by identifying the commitments under review and the questions that have emerged from the work, then bring the evidence needed to answer them.

For a Sparrow partnership conversation, a useful review structure would connect the agreed scope with the actual operating experience. The format should fit the arrangement rather than assume that every partner needs the same set of measures.

Return to the agreed service requirement

Check the relevant location, working windows, vehicle categories and support responsibilities. Explain any agreed changes during the period. Compare delivered activity with the requirement that applied at the time, rather than with a later version of the plan. Keep unconfirmed additional requests separate from accepted commitments.

Look at exceptions as well as totals. A satisfactory average can conceal a recurring gap in a particular location or time window. Describe where the issue occurred, how long it remained unresolved and what response followed. Avoid using surplus activity elsewhere to make an unmet requirement disappear.

Keep evidence categories distinct

The Magenta Book’s evaluation framework separates implementation evidence from broader outcomes and causal impact. That distinction helps a partnership review stay clear about what its records establish. A completed service action, a satisfied participant and an attributed long-term benefit are different findings.

State the source and completeness of each measure. Identify missing records, changed definitions and estimates. Where two partners report different numbers, reconcile the underlying scope and timing before treating the difference as a performance dispute. The review should improve the common record, not produce competing versions of it.

Connect performance with cost and experience

Review the resources used to achieve the observed service: coordination, maintenance, energy access, replacement arrangements and time spent resolving issues. Distinguish an exceptional recovery effort from a process that can be repeated with the agreed team. A strong result may depend on support that needs to be recognized in the next scope.

Include the people who experienced the arrangement. Captain support can reveal concerns that operating totals miss, such as unclear communication or repeated waiting. Use appropriately shared feedback to understand the work, while keeping personal concerns with the people responsible for resolving them.

Make the next decision explicit

For each material finding, decide whether to correct a record, change a process, clarify a responsibility or reconsider the scope. Assign an owner and a point for checking the result. Keep a proposed change separate from a change that both parties have accepted.

Carry unresolved questions into the next review with their context intact. If an issue depends on information or authority outside the meeting, name that dependency.