# ASO Agency — Lesson 4: ASO project setup: access, evidence and change logs

Outcome: Build a reproducible evidence workspace without unnecessary access or sensitive data collection.

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

## Your ASO assignment

1. Build a minimum-access request with no password-sharing request.

Your response:

2. Create the evidence folder structure and a report-context template.

Your response:

3. Record one past change with all known dates and unknowns.

Your response:

## Scenario challenge

You receive a cropped dashboard image labeled “last month.” Draft a precise evidence request that asks for the app, metric definition, absolute counts, dates, time zone, market and source filters. Explain which conclusions you can still make if only the screenshot is available.

Your reasoning:

## Handover

### Access matrix

Map tasks to the report or console capability required, the account owner and the approved access route.

Your evidence and decision:

### Evidence register

Assign stable IDs and record filters, extraction date, source location and known limitations for each item.

Your evidence and decision:

### Transformation notes

Explain how working tables were derived and keep the untouched source file available to the reviewer.

Your evidence and decision:

### Publication log

Record approval, submission and observed visibility separately, with locale and asset identifiers.

Your evidence and decision:

### Review responsibility

Name who validates access and evidence completeness, and who resolves missing context before analysis.

Your evidence and decision:

## Submission check

- [ ] Every saved report carries its filters and observation period.
- [ ] Original data can be distinguished from transformed analysis.
- [ ] A reviewer can identify who approved and published a change.

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

www.asoagency.com