# ASO Agency — Lesson 57: ASO handover: research, metadata and experiments

Outcome: Deliver an ASO pack that another person can implement, verify and maintain without guessing.

App / store / market / locale:
Prepared by / date:
Product or listing version:

## Your ASO assignment

1. Build a release-pack index for one locale.

Your response:

2. Include one exclusion rationale and one unresolved dependency.

Your response:

3. Ask another person to identify what they would publish and how they would verify it.

Your response:

## Scenario challenge

Write a one-page index for the keyword-field example that includes the original list, approved name and subtitle, exact field, inclusion/exclusion reasons, locale, review date and remaining gaps. Explain each item's purpose to the recipient.

Your reasoning:

## Handover

### Research archive

Preserve candidates, evidence and exclusion decisions with dates and locale context.

Your evidence and decision:

### Approved release

Provide exact strings, file IDs, counts and approvals for each destination.

Your evidence and decision:

### Open decisions

Name gaps, next actions and whether they block release.

Your evidence and decision:

### Verification

Specify console, live-store and measurement checks with owners.

Your evidence and decision:

### Ownership transfer

Record the walkthrough, resolved ambiguities and ongoing maintenance responsibility.

Your evidence and decision:

## Submission check

- [ ] The recipient can identify exact approved assets without asking.
- [ ] Open questions have owners and release implications.
- [ ] The previous live state and validation steps are preserved.

## Next action
Owner:
Required evidence:
Due date:
Review decision:

www.asoagency.com