BCMS scope and specialist role

Review questions

Scope and authority

Start with the beneficiary-visible service result, then define its start, end, channels and dependencies. An app or server is a resource, not the output. Record each stakeholder need and its source; separate verified contract text from an untested interview expectation. During disruption, the specialist proposes action and shows impact while the authorized owner approves activation and messaging. A name in a role matrix does not prove after-hours reachability. When a supplier or channel changes, revisit fallback capacity and linked records, and distribute the current version to the workers who will use it. A short deputy-reachability exercise can reveal a decision gap before it becomes a real delay.

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

  1. Question 1A pharmacy plan says “scope is the order server.” Which revision defines a testable service?
  2. Question 2The center does not operate its carrier but promises delivery. How should the carrier appear in scope analysis?
  3. Question 3A worker recalls a one-hour notice deadline, but contract text is unavailable. What belongs in the requirements register?
  4. Question 4During an outage, staff need safe intake instructions and customers need an update time. Which response serves both?
  5. Question 5The specialist can calculate impact, but the plan assigns activation to the service owner. What should the specialist do?
  6. Question 6The activation owner is absent after hours and no deputy is named. What gap does a role exercise expose?
  7. Question 7A contact register is past its review date, but its number has not been shown wrong. How should it be described?
  8. Question 8A call-routing supplier with capacity 70 is replaced by one with 40. What review is needed before updating the plan?