A campaign launch status check is not a general request for everyone to say that they are busy. It is a focused test of whether the work required for launch is ready, which dependencies remain and who can make the outstanding decisions. A campaign can have every task labelled “in progress” and still be unable to launch because one tracking check, creative approval or audience decision is missing.
Before the go-live meeting, ask the people who own the launch-critical tasks seven questions. Capture the answers against the right work items, and keep the final go/no-go decision with the accountable launch lead. Scheduled calls can help collect the answers, especially from collaborators who are not constantly checking the project board.
First map the chain of launch dependencies
A campaign launch usually moves through brief approval, creative production, landing-page readiness, analytics setup, media configuration, QA and final authorisation. Some steps happen together; others cannot finish until an upstream decision is complete.
Give every task one accountable owner, a required completion state, its dependency and a last meaningful checkpoint. In monday.com, maintain an authoritative project board rather than stitching together a different status list from email threads. The platform’s marketing management guidance outlines work tracking, approvals and campaign timelines that can support this structure.
The goal is not to ask everybody the same generic question. Adapt the questions to each workstream while preserving a consistent definition of “ready”.
Seven questions for a campaign launch readiness check
1. What exactly is complete, and where is the evidence?
Ask the owner to name the deliverable and point to its current file, URL, board item or test record. For creative, that may be an approved asset version. For analytics, it may be a QA log. “It’s done” without a way to review the result is only a reported status.
2. What still needs to happen before your work is launch-ready?
Distinguish finishing touches from launch blockers. A designer may have completed production but be waiting for accessibility review. A paid media specialist may have drafted campaigns but lack the approved budget. Record the remaining action precisely.
3. Who is waiting on your work, and whom are you waiting on?
Dependency questions expose gaps between teams. The landing page may be technically ready but waiting for approved legal copy. The ad team may depend on the final destination URL. Name both sides of the handoff so the project lead can act.
4. Has the authorised reviewer approved the final version?
A team member saying “the client liked it” is not the same as an approval in the agreed system. Capture whether formal sign-off exists and who can provide it. Keep the final asset approval and campaign authorisation with the designated human decision-makers.
5. Have the required quality and tracking checks passed?
For a digital campaign, the owner may need to confirm that links resolve correctly, forms work, conversion events appear in test conditions, creative renders appropriately and budget controls reflect the plan. The precise checklist depends on the channels and the project. AI can ask whether checks were completed; qualified people must perform and review them.
6. What could stop the launch in the next 24 hours?
Ask for a forward-looking risk, not a reassurance. An unconfirmed spokesperson, a pending legal decision or a delayed feed approval may threaten the schedule even if production appears finished. Have the owner describe the risk, likelihood in plain language and next action without inventing a numerical risk score.
7. If the launch cannot proceed, what decision is needed and who owns it?
The useful outcome of a readiness check is a decision path. Someone may need to defer a channel, replace a creative asset, contact a vendor or change the launch time. Record who can approve that decision and when the team will review it. Do not allow an AI caller to decide to publish, pause paid media or override an approval gate.
Turn the answers into a monday.com status view
A proposed launch-readiness board could group work into Creative, Landing page, Tracking, Media setup, Approvals and Communications. For each item, distinguish Reported progress, Evidence link, Open blocker, Decision owner and Human-verified readiness.
Imagine a hypothetical product launch where the ads are built and the landing page is published, but a conversion form has not passed the final test. A call to the tracking owner reports: “The event fires in our staging test; production form confirmation is still pending.” The board should capture Tracking reported: testing incomplete, Blocker: live form verification and Next action: analytics owner to verify production. It should not mark the campaign ready because most tasks are green.
The Autoza AI for monday.com product describes scheduled status calls, board write-back, retries and call summaries. For launch work, these are information-gathering tools. The exact field mappings and restrictions should be confirmed during setup, particularly for approval and go-live statuses.
Set the call schedule around a real decision point
A staged review is usually more useful than one frantic round of calls. For example, a team might check significant dependencies several working days ahead, run a focused owner update one day before launch and hold a final readiness review shortly before activation. The timing is illustrative and should reflect the campaign’s actual approval process.
Call only the owners whose updates are outstanding or time-sensitive. Do not interrupt everyone simply because a campaign exists. If a task owner is unavailable, preserve the unanswered status and escalate to the project manager. If an answer conflicts with a QA record, prioritise human verification over convenience.
Inform recipients when automated calls are used, respect their contact preferences and obtain any required consent for AI calling or recording. The AI Workflow Design privacy policy provides product-level information; the organisation remains responsible for a lawful and appropriate calling process.
Give the final launch decision to a person
The launch lead should review the evidence, approval status, unresolved risks and any agreed contingency plan. A call summary can help gather that information, but it cannot test a website, verify an ad account, approve a legal claim or accept the business risk of going live.
Define explicit gates: Ready for review means the owner has submitted the required evidence. Approved to launch means the responsible authority has confirmed it. This distinction protects the team from treating a positive-sounding update as permission to activate a campaign.
Measure the quality of your next launch review
Track unresolved launch-critical items at the final review, time from blocker report to owner action, late changes introduced after sign-off and the number of status requests made manually. Check whether the seven questions produce specific, verifiable responses. A campaign that slips for a sound business reason is not evidence that follow-up failed; discovering the reason early may be exactly what the process was meant to achieve.
Frequently asked questions
Who should be contacted before a campaign launch?
Focus on accountable owners of launch-critical tasks such as creative, site experience, tracking, paid media, compliance and final authorisation. Adapt the list to the campaign rather than treating every contributor as a launch gate.
What happens when a status answer is unclear?
Record that the answer needs verification, request the supporting evidence and refer the item to its human owner. Do not mark a critical task as ready based on inference.
Can an AI check-in approve or activate the campaign?
No. It can collect the owner’s reported status. Final approval, budget changes and activation should remain with the people and systems authorised to make those decisions.
How early should launch-readiness check-ins begin?
Begin early enough to resolve dependencies. More consequential or externally controlled tasks may need an earlier checkpoint. Use an agreed project schedule rather than a universal call frequency.
Start your next campaign with fewer unknowns
Use the seven questions to identify the information your launch lead needs before signing off. If your team manages campaigns in monday.com, review Autoza’s scheduled follow-up workflow or discuss a controlled setup that collects answers without treating AI calls as the final approval authority.