What you will achieve
Create a 90-day working plan that connects a campaign's discovery questions with evidence review, useful content, publication and later observations. The completed plan will have owners, dependencies, a manageable release sequence and decision points.
Ninety days is a planning window, not a promise of ranking or citation results. Keep the plan in an ordinary working document and use current AdCyte campaign and review capabilities where they fit. This guide does not assume a native 90-day planner.
Before you start
Choose one campaign and gather its relevant ads, current product references and existing public destinations. Name a coordinator, a factual reviewer and a publisher. Agree the effort and any paid activity through the team's normal process before scheduling it.
Use the video-discovery article for the opening check and the GEO brief guide for a detailed writing assignment. This guide organises the wider programme; it does not replace the product steps in those resources.
1. Record the starting position
List the campaign assets, product identities and public pages that matter to the first project. Record known gaps and current owners. Use real URLs and current source references where available, with unknown items clearly marked.
If visibility observations are part of the project, retain a small set of actual branded and unbranded answers with the questions, providers, dates and relevant collection context. If none are available, mark the baseline as missing and plan an authorised check rather than inventing a starting score.
Check: the plan begins with an inspectable account of what exists and what has actually been observed.
2. Define the customer outcome and the work outcome
Write what the customer should be able to understand. For a compact appliance campaign, this might be the storage requirements and differences between the demonstrated configurations.
Then define what the team will complete: reviewed explanations on appropriate pages, working links and a maintained source record. Keep external observations as a separate learning objective. Publishing an answer is within the programme's scope; obtaining a particular recommendation is not something the team can promise.
Check: the plan has a concrete delivery objective and a separate method for learning about discovery.
3. Choose a small set of questions and destinations
Collect questions from available search data, enquiries and the campaign brief. Record their origins. Select the questions with a clear customer purpose and enough evidence to make useful progress within the planning window.
Map each question to an existing or justified new destination. Do not automatically commission a fresh article for every gap. Updating a product section, correcting a link or clarifying a current FAQ can be an important part of the plan.
Check: every planned content task names the question, intended reader and destination it serves.
4. Review the campaign evidence and dependencies
Inspect the relevant ads and edits in AdCyte, opening useful findings at their source moments. Match product statements with authorised references and identify missing decisions. Keep different variants and market conditions separate.
Record dependencies as actions with owners. “Confirm dimensions with the product owner” is useful. “Await stakeholder alignment” has the advantage of sounding important while remaining almost impossible to finish.
Where a task depends on a current product capability or publishing route, verify that dependency before placing it on the critical path. A manual handover may be sufficient; an unconfirmed integration should not become the plan's hidden foundation.
Check: essential facts, permissions and implementation requirements have owners and realistic resolution points.
5. Build the three-stage plan
Use the following as an illustrative planning pattern. Adjust dates and workload to actual capacity rather than treating the ranges as a required schedule.
| Period | Main work | Evidence of completion | Typical owner |
|---|---|---|---|
| Days 1–30 | Establish questions, inspect campaign evidence, resolve key facts and brief priority outputs | Agreed scope, source record, owned dependencies and reviewed briefs | Campaign coordinator with product and search colleagues |
| Days 31–60 | Draft, review and publish the first useful outputs; connect existing pages | Approved versions, working public destinations and publication checks | Content and publishing owners |
| Days 61–90 | Review the live information, inspect available observations and decide what to improve next | Dated findings, corrected issues and an evidence-based continuation decision | Coordinator with measurement and product owners |
Some work will overlap. A ready correction need not wait until day 31, and a delayed product decision should not be disguised as a complete task because the month has changed. The schedule should describe the work, not negotiate with reality on its behalf.
Check: the stages connect to each other and allow ready work to move forward without an artificial publication cap.
6. Add a usable task record
For each priority task, record its purpose, source, owner, dependency, target window and completion evidence. Keep the record small enough to use in an ordinary review meeting.
| Task | Dependency | Completion evidence | Follow-up trigger |
|---|---|---|---|
| Explain the demonstrated storage arrangement | Confirm current model and dimensions | Approved section on the intended product page | Product configuration changes |
| Clarify included accessories | Product owner confirms the market pack | Reviewed wording with conditions intact | Pack contents change |
| Connect the launch film to the explanation | Public destination exists | Tested link from the campaign destination | Page or video is replaced |
| Review the question samples | Authorised collection method agreed | Preserved answers with context and findings | Scheduled review or a material source change |
These examples are planning records, not completed tasks or sample results. Replace them with your actual campaign information before assigning work.
Check: another team member can tell what each task needs and what will count as finished.
7. Agree approval and publication responsibilities
Identify who confirms facts, who approves the written use and who publishes. Record the approved revision and intended destination so the wrong draft does not become the public version.
After publication, inspect the actual page and its important links, conditions and media. Keep that check separate from the approval record. Use the existing publishing guide for the detailed workflow.
Check: every public output has a named route from draft to approval to a checked destination.
8. Define the review decisions now
Choose the questions the end-of-period review should answer. Did the team publish useful explanations? Which dependencies took longer than expected? Did the live information remain accurate? What do the available discovery observations show, and what remains unknown?
Record effort and outcomes without assigning invented financial value. If the team wants to compare efficiency, define the method and gather the relevant time or workload information. A shorter meeting is welcome, but it is not automatically evidence of a transformed marketing operation.
Use the review to continue, adjust or stop particular tasks. A campaign that has expired or a question that is already answered well may no longer justify more content.
Check: the review can lead to a different decision, rather than automatically approving another batch.
Troubleshooting
| Problem | Response |
|---|---|
| Product approval delays one output | Separate independent work and keep the unresolved dependency visible |
| No baseline observations exist | Start an honest record and avoid unsupported before-and-after claims |
| Too many pages are proposed | Prioritise distinct customer questions and useful existing-page improvements |
| A required publishing route is unavailable | Agree a feasible manual handover or revise the task |
| External answers vary | Retain context and inspect the actual responses rather than forcing a single conclusion |
Completion checklist
- The campaign scope and starting sources are recorded.
- Customer questions and delivery outcomes are explicit.
- Evidence gaps and dependencies have owners.
- Tasks have destinations and completion criteria.
- Publication and observation records remain separate.
- The 90-day review has defined questions and decision options.
Put the plan into practice
Explore AdCyte's campaign content workflow to connect reviewed video evidence with written outputs. For a programme involving several teams, book a campaign planning demo.
FAQs
Must the plan last exactly 90 days?
No. Use a period that fits the campaign and team capacity. The example provides a manageable planning structure without implying a fixed timetable for external search results.
Is this the same as approving a content-generation plan?
No. It covers the wider work across sources, writing, publication and observations. Any product-level plan approval is one possible part of that programme, with its own current controls.
Can the plan begin before the campaign is public?
Yes. Prepare evidence and briefs using authorised material, while keeping unreleased assets and information private. Public discovery checks and publication follow the appropriate release decisions.

