An action arrives already validated, so approval is a decision about intent rather than a proofreading pass. What follows is what is worth checking anyway.
Where the review happens
Each group Concord prepares is a card in the conversation. Open Review platform actions on the card for the full review screen: every field with its before and after, the submit and cancel controls, and a box to ask for an edit without leaving the screen. Asking for a change sends it as a normal message, so the corrected group arrives in the same thread.
A group you already submitted or cancelled stays reviewable from its card, as a record of what was decided.
What to check
Does the diff match what you asked for? The most useful check by far. The action shows every field, before and after — read the fields you care about rather than the summary.
Is the scope what you expected? Which campaigns, ad sets, line items, and creatives are touched. An action group that reaches further than your request did is the signal to stop and ask.
Are the budget and dates right? Amount, currency, and flight dates. Currency is the one that quietly produces a figure off by orders of magnitude.
Is the timing right? Seasonality, other campaigns in flight, and anything your client has agreed elsewhere. Concord does not know about a commitment that lives in an email.
Do you understand the dependencies? Actions execute in order — a parent object before its children. The group shows what executes together.
Approving
Approve and Concord submits. Each action gets its own status, so if one fails you can see which and why rather than guessing at the group.
Anything newly created lands in a non-active state. Approving a build does not start delivery — see Testing without going live.
Rejecting
Rejecting is clean. Nothing half-applies, and nothing is left in a partial state on the platform: the action group is simply not submitted.
Common reasons to reject:
- The action does not match what you asked for
- The budget change is larger than you are comfortable with
- The timing conflicts with something Concord cannot see
- You want a smaller version first
Say why in the conversation. “Too big, do the same thing with half the budget” gets you a corrected action immediately, and a reason that recurs is worth turning into a rule.
Turning a correction into a rule
If you find yourself rejecting for the same reason twice, the fix is not a third rejection.
Ask Concord to remember it as a Skill and it writes it, so the next action arrives already respecting it.
After approval
Concord confirms what landed, with a status per action. To review submissions later — yours or a teammate’s — use Action history, which is filterable by user, platform, and date range and exports to CSV.
Review carefully, and then approve without hesitating when the diff matches your intent. The value of the approval step is that it is cheap: the diff is explicit, so most approvals take seconds.
