The task
Choose one of the Apple, Google Play, Adobe or Netflix teaching cases. Write for a person trying to leave that service. Establish the relevant purchase channel and plan before describing the route.
Your guide must include the customer’s goal, applicability, official sources with a checked date, the main route, one meaningful exception and the evidence that would confirm the outcome. Where fees or refunds enter the discussion, state which terms and region your explanation uses.
Hand in
One PDF of up to six pages, named field-guide.pdf. Include a 150-word note explaining how a classmate’s reading changed the guide. Submit to the teaching team in the workshop as a local file or printed copy.
What matters
Specificity beats the number of screenshots. A polished sequence that sends a partner-billed customer to the wrong organisation is not successful. A clear exception branch and a justified verification step are stronger than a promise that cancellation always works the same way.
A strong guide can be followed without your spoken explanation and makes its limits easy to see. Use the source register and course policies. The skills are taught in weeks 2–8; the deadline is 23:59 Canberra time.
How it is marked
| Criterion | Weight |
|---|---|
| Correct route and scope | 40% |
| Clarity and important branches | 30% |
| Verification and source handling | 30% |
Submission checklist
- The requested document and evidence are present and readable.
- Every external instruction names its source and scope.
- The conclusion follows from the supplied records, with uncertainty stated.