diff --git a/docs/android.md b/docs/android.md
index fa984e01f..7f1a8a526 100644
--- a/docs/android.md
+++ b/docs/android.md
@@ -67,9 +67,8 @@ npx eas build:list --limit 10 --non-interactive --json | jq '.[] | {platform, st
 
 # Inspect a build
 npx eas build:view <build-id>
-
-# Recent store submissions
-npx eas submit:list --limit 8 --non-interactive --json
 ```
 
+`eas submit:list` is not a real command — submission state is only on the Expo dashboard.
+
 See [docs/release.md](release.md) for the full mobile-build babysitting flow.
diff --git a/docs/release.md b/docs/release.md
index dfc41d0fc..f2eb76e52 100644
--- a/docs/release.md
+++ b/docs/release.md
@@ -176,12 +176,11 @@ npx eas build:view <build-id>
 
 # Stream logs for a build.
 npx eas build:view <build-id> --json | jq '.logFiles[]'
-
-# Recent submissions (auto-submit / Fastlane lanes).
-npx eas submit:list --limit 8 --non-interactive --json
 ```
 
-A build's `gitCommitHash` must match the release tag commit. `status` walks through `NEW` → `IN_QUEUE` → `IN_PROGRESS` → `FINISHED` (or `ERRORED`/`CANCELED`). When `FINISHED`, the submission step takes over and shows up under `eas submit:list`.
+A build's `gitCommitHash` must match the release tag commit. `status` walks through `NEW` → `IN_QUEUE` → `IN_PROGRESS` → `FINISHED` (or `ERRORED`/`CANCELED`).
+
+There is no `eas submit:list` command in `eas-cli` (it errors with "command submit:list not found"). EAS submits to the stores automatically after a FINISHED build — Android via `eas submit`'s submit config and iOS via the Fastlane lane — and the submission state lives on the Expo dashboard, not the CLI. Heartbeat checks should look only at `eas build:list` for build state; if you need to confirm store-side submission, open the Expo dashboard or the Play Console / App Store Connect directly.
 
 ### Babysitting mobile after a release