Play Console handover
The app is not handed over until Play Console can be maintained without the agency.
A proper Play Console handover gives the founder control over account ownership, users, app signing, releases, store assets, policy declarations, support contacts, and future updates.
Many app launches end with "the app is live" but not with a real handover. The founder may not know who controls Play Console, which Google account owns the app, where app signing records are stored, how to submit an update, or what to do if a policy issue appears.
This checklist is for founders, agencies, and internal teams closing an Android app launch.
Official source note: Google Play Console Help documents adding developer account users and managing permissions. Use current permissions in the live account and document the final access model: Add developer account users and manage permissions.
Handover standard
New Android app launch
Start with account ownership, app record, AAB readiness, store listing, app content declarations, testing track, and production release notes.
App stuck in review
Recheck policy status, Data safety, app access, privacy links, account deletion, permissions, broken login paths, and reviewer instructions.
Agency or founder handover
Document owner account, app signing, release tracks, users, permissions, policy declarations, store assets, and support contacts before transfer.
Quick answer
A Play Console handover should make the founder operationally independent.
Include:
- Account owner and recovery details.
- User and permission matrix.
- Agency access review.
- App package name and app records.
- App signing and upload key notes.
- Release tracks and rollout process.
- Store listing assets and source files.
- Data safety, app access, privacy, account deletion, and content rating notes.
- Support contacts and escalation plan.
- Future update checklist.
Play Console handover checklist
Handover worksheet
| Area | Handover item | Why it matters |
|---|---|---|
| Ownership | Account owner, recovery, contact email | Prevents account lockout. |
| Users | Permission matrix and agency access | Controls who can publish or edit. |
| Signing | Upload key and app signing notes | Protects future updates. |
| Releases | Tracks, release notes, rollout process | Makes next update predictable. |
| Listing | Copy, screenshots, icon, feature graphic | Keeps store assets maintainable. |
| Policy | Data safety, app access, privacy, deletion | Reduces future review confusion. |
Users and permissions
Review every user before handover:
Permission review checklist
- Remove users who no longer need access.
- Reduce agency permissions after launch if ongoing support is limited.
- Confirm at least two business-side admins where appropriate.
- Avoid shared Google accounts.
- Document who can create releases.
- Document who can edit store listing.
- Document who can manage policy declarations.
- Document who can add or remove users.
Release and signing records
The technical handover should include:
- Package name.
- Current version code and version name.
- Last release track used.
- Build source or repository reference.
- App signing status.
- Upload key ownership and recovery note.
- Release notes history.
- Known issues and next release plan.
This prevents the next update from becoming a rediscovery project.
Policy and store assets
Store and policy assets should be in a folder the business controls:
Keep editable source assets
Store screenshots, icon files, feature graphic, descriptions, and translations should be stored outside one designer's machine.
Keep declaration notes
Data safety answers should be linked to the app and SDK inventory so future changes are reviewed.
Keep reviewer credentials controlled
Test accounts should be documented, rotated where needed, and never mixed with customer records.
Know who responds to Google
The business should know which email receives policy, review, payment, or account verification notices.
FAQ
When should Play Console handover happen?
Handover should happen before final launch if possible, then be updated after production release with final track, status, and known issues.
Should agencies keep admin access forever?
Only when there is a clear ongoing role. Otherwise, reduce or remove access after launch and keep support access scoped.
What is the most important handover item?
Account ownership and recovery. Without it, every future release, policy response, or update can become dependent on the wrong person.
Can Shinka create the handover runbook?
Yes. Shinka can prepare a Play Console handover runbook with owners, permissions, release process, signing notes, listing assets, and policy records.
