Two different milestones
It's easy to blur these together, but they answer different questions:
Approved — "Is this plan good?" A person reviewed the agent's work and signed off. The card moves to the Approved column, with the approver and time recorded. At this point nothing has changed in the ad platforms yet.
Implemented — "Did we actually do it?" The recommendation was applied in the ad platform or channel — budgets moved, creative swapped, settings changed. Marking a card Implemented is your confirmation that the plan left Omega and went live in the real world.
Keeping the two separate means the board always tells the truth: an Approved column full of cards is a to-do list, not a victory lap.
Reports stop at Approved
Some cards aren't a plan waiting to be applied — they are the deliverable. Weekly reports, monthly reports, exec memos and any report an agent files in Omega on a schedule finish at Approved, and that's the end of the ladder for them.
For a report, approving is the decision: you're signing off that it's right and can be published or filed. Nothing is waiting to be changed in an ad platform, so there's nothing to confirm went live — and there's no go-live date to record, because a report describes what a metric did rather than moving it. That's why report cards carry no Mark implemented button: the step doesn't exist for them, so an approved report is finished, not a to-do you forgot to close out.
Note: The column is named Approved — if you or your team say "accepted," that's this same column. And if you've already marked a report Implemented, nothing is broken: open the card, choose Back to Approved, and it sits where it belongs.
How to mark work implemented
Find the card in the Approved column. Approved cards for platform changes carry a Mark implemented button right on the card (it's also available inside the card's detail view) — report cards don't, for the reason above.
Click Mark implemented.
You'll be asked: When did this go live in the platforms? Enter the actual go-live date — not today's date, unless they happen to match.
Confirm. The card moves to the Implemented column, showing the go-live date and who marked it.
Why the go-live date matters
Omega measures a recommendation's impact by comparing the metric before and after the change took effect. That comparison is anchored to the go-live date you enter.
If a plan was approved on Monday but the media team applied it Thursday, and you record Monday, three days of "before" performance get counted as "after" — and the impact read is wrong. The date prompt exists so before/after analysis starts on the right day.
Tip: Mark cards implemented as soon as the change goes live, while the date is fresh. Backfilling from memory a week later is where dates drift.
Made a mistake?
If you marked a card Implemented too early or with the wrong date, open the card and choose Back to Approved. The card returns to the Approved column, and you can mark it implemented again with the correct date when the time comes.
Note: Implemented is the end of the pipeline. Once a card is there with an accurate date, the Monitoring page can track what the related metric did from the moment the change went live — that's how you show the work paid off.
