Lucknow, India

Service Planning

Build a service governance meeting people can use

Turn reporting into decisions with a clear agenda, accountable actions and an agreed escalation route.

IGS Editorial · 3 min read · Updated 17 November 2026

Build a service governance meeting people can use — editorial artwork
Illustrative service planning image

A service review meeting should help the parties understand performance and decide what to change. Reading a dashboard aloud rarely achieves that. The meeting needs a purpose, the right participants and a reliable way to track decisions.

Separate operational review from broader commercial governance when the subjects and decision-makers differ. A daily queue discussion should not become the only place where scope or strategic issues are raised.

Send a decision-focused pack

Provide agreed measures, relevant context and a short list of issues requiring action. Make definitions and refresh times visible. Highlight material changes instead of expecting participants to discover them in a large spreadsheet.

Include previous actions and their status. An action marked complete should have evidence of the intended result where appropriate. Finishing a task is not always the same as solving the original problem.

Discuss causes before remedies

When a measure changes, examine volume, work mix, system conditions and process changes. Avoid immediately attributing the result to individual effort. A rise in handling time may reflect more complex cases rather than reduced productivity.

Use representative examples to test the explanation. Keep personal information out of broadly shared packs unless it is necessary and appropriately protected. Aggregated patterns and controlled case references are often sufficient.

Assign actions clearly

Each action needs an owner, expected output and review date. “Improve quality” is not specific enough. “Revise the duplicate-check instruction and validate it on a defined sample” can be reviewed.

Distinguish actions within the service team's authority from decisions required from the client. If approval is the blocker, record the decision owner and information needed. Repeating a reminder is not a substitute for resolving an unclear authority route.

Control changes through the right route

A review may identify a useful new task, but discussing it does not automatically add it to scope. Assess impact on capacity, risk, systems and commercial terms. Use the agreed change process before implementation.

Keep a record of decisions and assumptions. People absent from the meeting should be able to understand what changed and when. Avoid relying on informal memory for material instructions.

Review the meeting itself

Periodically ask whether the cadence, attendance and information support decisions. Remove reporting that consumes effort without influencing action. Add focused reviews when a new risk or transition requires closer attention.

Escalate unresolved issues through a known route rather than carrying them indefinitely in the same minutes. Good governance creates a shared operating picture and a way to act on it. Its value is visible in clearer ownership, resolved blockers and improvements that can be checked against the evidence.

Rescue an action that keeps returning

A recurring meeting lists clarify approval policy as open for several weeks. Ask who has authority to make the policy decision and what information they lack. The assigned operational coordinator may be able to arrange discussion but not resolve the underlying question.

Rewrite the action so it identifies the decision owner, specific question and evidence needed. If that owner is outside the regular meeting, use the agreed escalation route. Keep the operational consequence visible while the decision remains pending.

At the next review, check whether the action produced a decision and whether instructions changed accordingly. Do not mark it complete merely because an email was sent. Governance improves when actions describe outcomes that can be verified. Repeatedly carrying an item forward is a signal to examine authority, dependencies or the wording of the task, rather than a reason to make the action log longer.