Workspace tasks, approvals and verification
What each task status means, which tasks each approval mode holds back, the plan board and its ⋯ menu, verification badges after a re-crawl, and the weekly report.
Open this screen in the panelEvery task in an active workspace has a status. Each hour the scheduler picks up tasks that are due, passes them through the approval and budget gates, and runs them. This article covers what the statuses mean, the approval inbox, the plan board and the verification badges. To set a workspace up, see Create a workspace.
Task statuses
| Status | Meaning | What you do |
|---|---|---|
| Planned | Scheduled and waiting for its date. | Nothing; or click Run now. |
| Proposed | The weekly re-analysis found something new and suggests a task. | Add to plan or Reject. |
| Awaiting approval | The approval mode needs a human for this task. | Approve (runs right away) or Reject (skipped). |
| Your turn | A manual task that is due. | Do the work, then click I did it. |
| Waiting for budget | The weekly AI budget is used up. | It re-queues itself when the new week starts; Retry also works. |
| Queued / Running | Handed to a background worker. | Wait; see the result in the Log tab. |
| Done / Done manually | Finished. | — |
| Failed | It hit an error; the message shows on the card. | Retry or Skip. |
| Skipped | You skipped or rejected it. | — |
Weekly tasks (marked Weekly on the card) are rescheduled one week ahead after each run.
Which tasks does each approval mode hold back?
- Ask for everything: every task goes to Awaiting approval first.
- Ask only for code and publishing: tasks that change the site or publish (code-fix PRs, Pixel/WordPress/Shopify rules, content generation and publishing, page expansion, schema, AI bot policy, GBP posts, E-E-A-T fixes) wait for approval, as does any task marked Needs approval. Crawls, measurements and syncs run automatically.
- Fully automatic: nothing waits; PRs still never touch the main branch.
Run now skips the schedule but not the approval gate. On a task that needs approval it sends the task to the approval inbox. To make a task that would normally run on its own wait for you, tick Needs approval in its edit dialog.
The plan board
The workspace's Plan tab has two views:
- Calendar: one column per week. Drag a task to another week to change its date. The current week is highlighted.
- Kanban: tasks grouped by work area (Quick wins, Technical, Indexing, Content, Authority, AI visibility, Local).
Hover a card to reveal Run now, Add to plan (for proposals), I did it, Skip, Generate AI prompt, plus edit and delete. AI prompt for all above the board builds one prompt for every open task.
The column ⋯ menu
The ⋯ (Column actions) menu on each column header acts on the open tasks in that column:
- AI prompt for the n tasks in this column
- Run n runnable tasks now: tasks that are not manual and not already queued.
- Mark n tasks as done manually
- Skip n tasks (asks for confirmation)
The approval inbox
The Approvals tab gathers everything waiting on you in five sections: Awaiting approval, Your turn (manual), Re-analysis proposals, Waiting for budget and Failed. Tasks awaiting approval show a preview where possible (for example the issue code and repository, or the number of posts to be written). New approvals and manual tasks raise an in-app notification, and also email or Telegram depending on your notification settings.
Verification badges
When you close a task tied to an audit issue by hand (I did it, or Mark as done in the AI answer review), SEOAsist checks on the next crawl whether the fix really held. The card shows one of these badges:
| Badge | Meaning |
|---|---|
| Awaiting verification · next crawl | No new crawl has finished yet. |
| Verified · gone in the crawl | The new crawl found no URLs with this issue code. |
| Still present · n URLs | The issue still shows on n URLs. It is checked again on later crawls. |
I did it does not start a crawl by itself; the badge updates on the next scheduled or manual crawl. Apply decisions in the AI answer review queues a verification crawl right away.
The weekly cycle and report
Every Monday the weekly cycle runs for active workspaces:
- The site is re-analysed.
- New findings the workspace does not have yet are added as Proposed tasks (up to 8).
- A weekly report is generated: done and pending tasks, metric changes versus the baseline, progress to goal and next week's plan.
Reports are listed in the Reports tab; Open report opens a shareable link. If recipient emails are set on the Reports page, the report is emailed too. To run the cycle without waiting, click Run weekly cycle now in the top right.
The log
The Log tab is the autopilot timeline: what ran, what was approved, what failed. If a task did not behave as expected, look here first.
Related articles
- Create a workspace: goal, pace, channels and approvalSet a goal for a site and build an automatic 30/60/90-day SEO plan, create drafts for every goal at once, then review and start them.
- Generate an AI prompt and review the AI's answerHand tasks to ChatGPT, Claude or your developer with a ready-made prompt, paste the answer back to see what happened to each task, and apply the decisions in one click.
- Technical Audit: crawls, severities and the issue listLearn how to start a crawl on the Technical Audit page, filter issues by severity, and view or export the affected URLs as CSV.
- Workspaces and autopilot: frequently asked questionsShort answers on how a workspace starts, when tasks run, approval modes, budgets, weekly reports and pausing.