After a meeting, different interpretations of what is to happen may remain. An operational summary should make the next steps clear, keeping distinct from the minutes and forms required by the applicable rules. Its usefulness concerns the execution of the agreed upon work.
I propose to distinguish what has been decided, how much further verification is required and what information needs to be collected. A generic phrase about improving the service may not indicate any concrete activity. Operational responsibility must be consistent with the actual roles of the persons involved.
Let's imagine a discussion about delivery delays. If the outcome is a verification of the most problematic routes, the summary should specify the perimeter and time of return. members can thus understand what to expect and contribute relevant information.
The document should be updated when the path changes, avoiding contradictory copies. The clarity of the outcome occurs in the next work. A good summary reduces the distance between what the participants understood during the meeting and what the structure actually manages to accomplish.