A client can finish a twenty-page questionnaire without giving an agency enough information to launch one responsible ad. Brand adjectives are complete, but the service area is ambiguous, the offer expires next week, and nobody knows whether reported revenue includes canceled orders.
An AI advertising onboarding brief should resolve the decisions that block useful work. Start with a small operating document, attach evidence, and leave unknowns visible. The following structure is an editorial workflow you can adapt to your agency, not a platform requirement or a promise about any software's capabilities.
Identify the engagement before connecting accounts
Record the legal or trading business name, client contact, agency owner, ad platforms, exact account IDs, currency, and account timezone. List included brands, territories, and destinations. Separate the client's existing accounts from accounts the agency proposes to create.
The account list is also an exclusion list: access to a parent organization does not make every subsidiary part of the engagement. Ask the client to confirm the actual operating scope, then compare it with the connected account readback.
Google's manager ownership documentation distinguishes linking an existing account from receiving ownership privileges. Determine the access needed for the work instead of treating the strongest available permission as a standard onboarding checkbox.
Translate the commercial objective into a decision
Replace “grow profitably” with an operating question. For an ecommerce client, that might be whether to increase acquisition spend while preserving first-order contribution. For a service business, it might be whether another campaign can fill qualified appointments without exceeding dispatch capacity.
Capture the result, unit, acceptable cost, time horizon, and constraint. If allowable acquisition cost is not established, assign its calculation to an owner. Do not let the AI infer a margin from the selling price or convert an aspirational revenue target into an approved budget.
Document temporary priorities separately. Clearing discontinued stock can justify a different objective from acquiring customers for a new subscription. The brief should say when that exception ends and who can renew it.
Establish the measurement agreement
Use a short table the client and buyer can both understand.
| Question | Evidence to attach |
|---|---|
| What counts as a conversion? | Event or CRM stage definition and an example record |
| Which system determines revenue? | Order or finance report with inclusion rules |
| When does data become usable? | Typical import delay and reporting cutoff |
| How are returns and cancellations handled? | Adjustment process and responsible owner |
| What remains unreliable? | Known outage, missing source, or unresolved discrepancy |
Keep business outcomes distinct from the signals used in bidding. A submitted lead may be a practical early signal while the actual objective is a completed, profitable job. Link the signal to the later outcome rather than calling both a “conversion” without explanation.
Use the metric dictionary worksheet when several systems use the same label for different numbers. This agreement often prevents more reporting conflict than another dashboard.
Ask for proof behind the offer
Collect current pricing, terms, product details, approved assets, customer permissions where relevant, and the evidence supporting specific claims. Mark draft offers as drafts. Attach the destination where a buyer will verify the promise.
An example entry might read: “Free installation applies to orders above the stated threshold within these postal codes through this date. Operations owner confirms capacity weekly.” This is actionable. “We offer unbeatable service” is neither a precise promise nor supporting evidence.
Use an ad claims review before production. Distinguish the client's preferred tone from facts that must remain accurate in every variation. A generator should not turn “designed to reduce setup time” into an unsupported quantified guarantee.
Define the work the agency can actually perform
For each task family, record whether the agency may inspect, draft, recommend, or execute. Include budgets, creative launches, audience changes, conversion settings, destination edits, and pauses. Name the client approver and agency operator where approval is required.
The NIST AI Risk Management Framework provides voluntary guidance for managing AI risks. It does not certify a campaign workflow. Here, the practical application is to make responsibility and limits explicit before automation begins.
The service agreement and the software configuration should agree. If the contract promises client approval before launches, verify that the operational process actually holds launches for approval. A sentence in a brief is not evidence that a technical control exists.
Run a first-decision rehearsal
Give the operator a realistic question: “Product A has stronger reported ROAS than Product B. What information is needed before moving budget?” A useful response should identify contribution, inventory, conversion maturity, campaign role, and current authority where relevant.
If the response confidently recommends a transfer despite unknown stock or ambiguous account scope, repair the brief or the workflow before execution. Record the misunderstanding so the team can see what changed.
The rehearsal is not a benchmark of the vendor's general intelligence. It tests whether this client packet supports this decision. Follow with a bounded handoff checklist and account-state verification.
Keep the brief current without rewriting it weekly
Assign an owner to the active brief and record the last substantive update. Separate current operating rules from historical campaign lessons. A promotion that ended should remain in history without appearing as a live instruction.
Use event triggers for updates: a price change, a new market, a measurement release, a new client approver, or a change in service capacity. Routine reporting can link to the brief rather than duplicating all its contents.
Onboarding is ready when the team can identify the account, explain the business objective, interpret the data, substantiate the offer, and state who may authorize the first change. Completed form fields alone do not establish that readiness.