# Craft ASO audit worksheet

Use alongside https://www.asoagency.com/briefs/craft. Published copy proposals are hypotheses, not tested outcomes.

## Define your scope

- App and listing URL:
- Store, territory, language and device:
- Observation date and reviewer:
- Visitor intent and source:

## Your ASO assignment

1. Verify one document-to-task flow and capture the saved destination without invented UI.
2. Document offline content access, reconnect sync and network-dependent features separately.
3. Test only the third frame using the same sample document and accurate access context.

## Keep evidence separate from judgment

For each of your first three screenshots record: source URL, capture date, visible content, interpretation and proposed action. Identify the material that must remain unchanged.

## Review the proposed copy

Name: Craft: Notes & Documents
Subtitle: Write, organise, plan your day

Reasoning: Keep the writing category clear and express the planning job in ordinary language rather than another collection of AI and reminder nouns.

Tradeoff: This removes AI from the name and scheduling terms from the subtitle. Research whether those queries bring qualified users before adopting the proposal; hold metadata fixed in the workflow test.

Your alternative name:
Your alternative subtitle:
Character counts:
Important inclusions and exclusions:
Feature and entitlement checks:

## Plan one test

Example question: Does a saved task from the same document explain Craft’s note-to-action workflow better than an open composer?

Your audience:
Control:
Treatment:
Randomization or other comparison method:
Primary metric and definition:
Real baseline and available traffic:
Minimum practical effect and sample requirement:
Guardrails:
Decision rule and review date:
Confounding changes:
What would make the result inconclusive:

## Handover

Include the original listing snapshot, source links, dated review sample and selection method, competitor observations, copy decisions, approved creative, test brief and remaining evidence gaps.

## Evidence still needed in this audit

- Current offline scope across writing, AI, integrations and sync conflict handling.
- Task source context, persistence and plan entitlements on iPhone.
- Baseline workflow comprehension and document/task activation by acquisition channel.