Prepare the pack

Show the volume, the quality sample, the exceptions, the aging, and the open decisions. Keep it to one page. A long pack will not be read. Record the next action, the owner, and the date for ['A service review should show the work, the quality, the exceptions, and the decisions. It should not be a status meeting.', 'The coordinator can prepare the pack, but the operations owner and the client decide the changes.']. A case without a next action will sit in the queue. Keep the evidence for ['A service review should show the work, the quality, the exceptions, and the decisions. It should not be a status meeting.', 'The coordinator can prepare the pack, but the operations owner and the client decide the changes.'] in the approved system. Do not copy customer, worker, or contract data into a chat.

Review the exceptions

Group the exceptions by cause and owner. Choose one fix for the next month. Record the owner and the date. A review without an action is a ritual. Record the next action, the owner, and the date for ['A service review should show the work, the quality, the exceptions, and the decisions. It should not be a status meeting.', 'The coordinator can prepare the pack, but the operations owner and the client decide the changes.']. A case without a next action will sit in the queue. Keep the evidence for ['A service review should show the work, the quality, the exceptions, and the decisions. It should not be a status meeting.', 'The coordinator can prepare the pack, but the operations owner and the client decide the changes.'] in the approved system. Do not copy customer, worker, or contract data into a chat.

Close the loop

Send the summary and start the next review with the prior actions. Review the cadence quarterly. A monthly review may become unnecessary when the lane is stable. Record the next action, the owner, and the date for ['A service review should show the work, the quality, the exceptions, and the decisions. It should not be a status meeting.', 'The coordinator can prepare the pack, but the operations owner and the client decide the changes.']. A case without a next action will sit in the queue. Keep the evidence for ['A service review should show the work, the quality, the exceptions, and the decisions. It should not be a status meeting.', 'The coordinator can prepare the pack, but the operations owner and the client decide the changes.'] in the approved system. Do not copy customer, worker, or contract data into a chat.

Authority and evidence

For ['A service review should show the work, the quality, the exceptions, and the decisions. It should not be a status meeting.', 'The coordinator can prepare the pack, but the operations owner and the client decide the changes.'], name the accountable owner before the coordinator acts. A request from a client or a manager is context, not authority. Record the source, version, and date for each material field in ['A service review should show the work, the quality, the exceptions, and the decisions. It should not be a status meeting.', 'The coordinator can prepare the pack, but the operations owner and the client decide the changes.']. A value without a source is an assertion. Separate preparation from decision. A complete packet or a drafted message is not approval.

Adverse cases

Test ['A service review should show the work, the quality, the exceptions, and the decisions. It should not be a status meeting.', 'The coordinator can prepare the pack, but the operations owner and the client decide the changes.'] with a missing source, a conflicting record, an unavailable owner, and a request outside the lane. Preserve the original request and the correction. Do not overwrite the earlier value. If the case affects money, access, safety, or a customer commitment, stop and route it to the owner.

Verification and close

Close ['A service review should show the work, the quality, the exceptions, and the decisions. It should not be a status meeting.', 'The coordinator can prepare the pack, but the operations owner and the client decide the changes.'] only when the destination system shows the approved change. A sent message is not proof. Tell the affected person what changed and when it will appear. Give a contact for a correction. Review a sample of ['A service review should show the work, the quality, the exceptions, and the decisions. It should not be a status meeting.', 'The coordinator can prepare the pack, but the operations owner and the client decide the changes.'] cases monthly. A repeated gap should change the procedure, not only the coaching.