Setting community service standards that separate acknowledgement from resolution

A service standard is a promise the team can operate and measure. It should tell members what to expect and help managers decide when capacity or design must change. Do not copy response targets from another organisation without matching its audience, risk and staffing.

What to take away

Define the service window

State when people may participate, when operators are present and how urgent concerns are handled outside ordinary hours. A platform available at all times does not mean expert or moderator cover is continuous.

Publish bank-holiday or planned-closure arrangements in advance. Give members a route outside the community for account-specific or emergency help where the organisation provides one.

Separate acknowledgement from resolution

An acknowledgement confirms receipt and next steps. Resolution means the member has an appropriate answer, action or explanation. Measure both where the distinction matters.

Set priority from consequence and time sensitivity, not the status of the person asking. A routine question from a senior customer should not displace a credible safety report.

Establish answer quality

Define who may provide authoritative product, professional or policy information. Sample responses for relevance, accuracy, evidence, clarity and necessary qualification. Record corrections where the original contribution remains discoverable.

An unanswered question should move to a named owner after a defined point. The service may close it with a transparent statement that the community cannot help, rather than leaving the member waiting indefinitely.

Set moderation and appeal expectations

Tell members how reports are received, which policy applies and whether urgent action can precede a full review. Define the information given after a decision and the route to challenge an error.

Ofcom's illegal content duties guidance describes reporting and complaints obligations for in-scope services. Not every community occupies the same legal position, so obtain a scope assessment and connect statutory duties to the service standard where applicable.

Include access and continuity

Cover joining, authentication, accessibility, account recovery, planned maintenance and supplier outages. The GOV.UK Service Standard is designed for government services and is not a commercial community rule. Its attention to user needs, accessibility, security and reliable operation provides useful questions when writing a private standard.

Test member journeys with relevant assistive technology and support needs. A target that excludes failed login attempts or abandoned forms can hide the people unable to reach the service.

Protect privacy in reporting

Measure workload and quality without circulating unnecessary personal details. Small groups and sensitive cases may be identifiable even after names are removed. Limit access to case-level evidence and use aggregation only when it does not mislead.

Cover failure and recovery

Set expectations for outages, lost access, failed notifications and unavailable experts. Tell members where status information appears and which alternative contact remains usable. Define recovery from the member's perspective, not simply the moment a server starts responding.

Keep supplier targets separate from the organisation's promise. A hosting response time may not restore a broken integration or correct exposed permissions. Map the handoff and identify who communicates during the gap.

Test standards through exercises. Time an urgent report, ordinary question and account-recovery case, then inspect the quality and record. A target that can be achieved only by experienced staff who are rarely available is not an operational standard.

Write measurement rules

For each standard, record the starting event, stopping event, clock, exclusions, data source, quality sample, owner and review period. Avoid quietly pausing a response clock while a case waits for an internal team.

Publish member-facing promises in plain language and keep operational definitions for staff. Review misses by cause and consequence. A service standard improves delivery when failure triggers a staffing, scope or process decision, not when awkward cases are excluded to protect a percentage.

Before you act

Common questions

What is the difference between acknowledgement and resolution?

An acknowledgement only confirms the request has been received and says what happens next. Resolution means the member actually gets a suitable answer, action or explanation, and both should be measured where the gap matters.

How should a community handle an unanswered question?

Move it to a named owner once a set point has passed. If the community cannot help, close it with a clear statement rather than leaving the member waiting.

Why keep supplier targets separate from the organisation's promise?

A supplier's response time may not fix a broken integration or exposed permissions. Keep them apart, map the handoff and name who communicates while the gap remains.