Download your lesson workbook · Open the assignment tool →
Your ASO learning objective
Export a complete listing review pack that another person can implement and review without guessing.
- Step 1Name the approved version and scope
- Step 2Attach assets, evidence and decisions
- Step 3Verify exports and assign remaining work
A handover preserves the decisions
The final pack should let a designer, product owner or marketer understand what was approved and why. Begin with app, store, locale, audience and the communication objective. Include the original proposal and the selected version. Keep a short decision record for important changes so an implementer does not accidentally restore wording that the team deliberately rejected.
For each screenshot, include its position, message, supporting product evidence, visual direction and image description. Name the location of the original submission asset. The workspace's smaller review copies help collaborators inspect the proposal, but they do not replace the source files or final technical checks. Missing assets should have an owner and status, not an empty field that looks like an omission.
Make approval and open questions distinct
Record who reviewed product accuracy, language and creative execution, and when they reviewed the actual files. Keep unresolved evidence gaps separate from approved decisions. If the product version changes after review, identify which screenshots need another pass. Approval of an earlier draft should not silently carry over to a different final asset.
Include the metadata comparison when relevant, the chosen screenshot sequence and the proposed experiment. State whether the work is a full launch package or a treatment intended to isolate one change. An implementer should not need to infer the experiment scope from the visual difference between two mockups.
Test the handover before calling it finished
Download the review pack, storyboard CSV, metadata report and editable project backup. Open them and check that the images, order and notes match the approved proposal. The HTML review pack can be printed to PDF from a browser. Ask someone else to identify the approved locale, first screenshot and remaining blocker using only these files.
Use that independent read as the final quality check. If they cannot distinguish approved work from alternatives, revise the version notes. Your capstone is complete when the team can execute the next action and understands what still needs verification. Self-recorded course completion reflects finishing the assignment; it is not an external certification.
Worked example: Trail Notes
This fictional hiking-journal app is the teaching project. Treat the example as a reasoning exercise you can adapt to your own evidence.
- Original draftA folder of numbered images and a message saying ‘use the newest ones’.
- Revised proposalA dated pack naming the approved store and locale, ordered assets, metadata decisions, evidence references, pending approvals and the next experiment owner.
- Why it changesThe completed pack removes ambiguity about versions and responsibilities. It preserves the reasoning so later edits can be reviewed against the original objective.
Your ASO assignment
- Fill gaps in both versions and state clearly which is approved, which is an alternative and why.
- Export all four outputs. Open the review HTML and print it to PDF if your team needs that format; import the JSON backup to verify editability.
- Have a colleague identify the approved first screenshot, target locale, evidence gap and next owner from the pack. Revise anything they cannot locate.
Your handover and assessment criteria
Your work is ready for review when each deliverable below can be understood without a verbal explanation. Include the source or product reference, the decision owner and any unresolved evidence gap. If a reviewer cannot verify a claim, record the missing evidence before treating the proposal as approved.
- Deliverable 1Review pack and original asset references
- Deliverable 2Storyboard CSV, metadata report and editable backup
- Deliverable 3Approval record, open gaps and next experiment
Check your understanding
The review pack contains images but does not say which version is approved. Is the project complete?
Read the interpretation
No. Add an explicit approval decision with store, locale, version, date and owner. Preserve alternatives as alternatives, and separate unresolved work from approved instructions.
Record your progress
Mark this lesson complete after checking your assignment against the handover criteria. Progress stays in this browser, separately from your tool project.
Sources and further reading
Platform references checked 30 September 2026.