Help new starters practise an important workplace task.

Task and audience

Turn a vague client request into an actionable brief before delivery starts. New project coordinators in a fictional IT service team.

Observable objective

Prepare a handover that names scope, acceptance criteria, owner, approver, confirmed deadline, checkpoint, and an action for unresolved information.

Sequence

1. Clarify the request: choose how to resolve missing audience, scope, approver, and deadline; inspect the consequence of the choice.
2. Resolve the trade-off: align scope and delivery capacity with the client; separate portal work from the Friday checklist.
3. Make the handover usable: record owner, approval, explicit deadline, and checkpoint; review the decisions made.
4. Apply it: use the confirmed source notes to write a delivery brief that also handles the outstanding policy-link check.
5. Review the work: compare with the four-criterion guide, inspect an illustrative response and human review, and revise the handling of uncertainty.

Feedback plan

Each decision reveals its consequence and reasoning. The written task receives criterion-based review by a subject expert.

Use the source notes and written brief above as the work sample. Rate each criterion as missing, partly demonstrated, or clearly demonstrated, and cite the response that supports the rating.

Scope

Names the deliverable, audience, acceptance criteria, and excluded work.

• Missing: Does not identify the deliverable or its acceptance criteria.
• Partly demonstrated: Identifies the deliverable but leaves the audience, acceptance criteria, or exclusions unclear.
• Clearly demonstrated: Records the agreed deliverable, audience, acceptance criteria, and excluded work.

Owner

Names the accountable delivery owner, client approver, and next checkpoint.

• Missing: Names no accountable owner or approver.
• Partly demonstrated: Names an owner or approver but leaves responsibility or the checkpoint unclear.
• Clearly demonstrated: Names the delivery owner and approver and records the agreed checkpoint.

Deadline

Records an explicit deadline that the delivery owner has confirmed for the agreed scope.

• Missing: Gives no explicit deadline.
• Partly demonstrated: Gives a deadline but does not record confirmation of capacity for the agreed scope.
• Clearly demonstrated: Records the agreed day and time and the delivery owner’s confirmation of capacity.

Uncertainty

Identifies an unresolved issue, its owner, its check date, and a next action if it remains unresolved.

• Missing: Treats unresolved information as confirmed or omits it.
• Partly demonstrated: Acknowledges some uncertainty but omits an issue, its owner, its check date, or the action if unresolved.
• Clearly demonstrated: Records the outstanding issue, who will resolve it, when it will be checked, and the action if it remains unresolved.

The worked review above demonstrates how to use this guide. Completion of the choices alone does not demonstrate workplace readiness.

• Subject expert checks the process, fictional facts, expected response, and assessment criteria before final sign-off.
• Client reviews the agreed scope and supplies consolidated feedback for the two review rounds.
• Final checks cover the agreed browser and device journey, keyboard use, visible labels, and readable feedback.
• Handover notes identify the final module version, agreed launch steps, known limitations, and how future changes are requested.

• Agree what an acceptable handover contains with the client’s subject expert before development.
• Collect responses to different, comparable requests before and after practice, using the same criteria.
• Record who took part, how review was conducted, and any other training or support that could affect the result.
• Review transfer to work with the client. Publish a case study only with permission and describe the limits of the evidence.

Proposed plan only. No client outcome data exists for this fictional example.