impact.com Programme Management Cadence

Quick Answer A management cadence is your fixed schedule of impact.com tasks — daily checks, weekly approvals and recruitment, monthly reporting and action review, quarterly strategy. impact.com adds two rhythms to bake in: reviewing locked/unlocked actions before payout, and watching Event Risk flags.

What it is

Cadence is the operating rhythm of your programme: recurring tasks on a fixed schedule rather than ad hoc. In impact.com that rhythm wraps around Contracts, the action ledger (where sales lock as payable), Event Risk monitoring, and the Discover marketplace for recruitment. The platform automates a lot, which is exactly why a human review rhythm matters — automation pays out whether or not you checked.

Picture it like running payroll plus quality control on a schedule: the system will run regardless, so your job is to review before it does, not after.

Why it matters

impact.com programmes drift the same way any do — tracking breaks, applicants pile up, creative goes stale — but automated payouts raise the stakes on inattention. If you don't review actions before they lock, returns and risky orders get paid. Event Risk flags are only useful if someone actually looks at them. A written cadence turns these from 'when I remember' into scheduled work, which is what keeps margin and quality intact.

How it works

Daily (5 minutes): scan actions and clicks for anything obviously wrong — a drop usually means a tracking issue, a spike can mean risk.
Weekly: approve or decline partner applications, reply to messages, and check top partners for unusual movement.
Weekly: review Event Risk flags and any actions the platform has marked for attention.
Monthly: run the performance review by partner type, review actions before they lock, and refresh expired creative and offers.
Monthly: recruit through Discover and follow up with partners who joined but haven't driven sales.
Quarterly: review Contracts and locking windows against margin, prune inactive partners, and plan seasonal promotions.
Quarterly: run a compliance sweep — brand bidding, traffic quality and risk patterns — on your top earners.

! Common mistakes to avoid

Ignoring the action ledger until after payouts lock, so returns and risky orders get paid anyway.
Treating Event Risk flags as noise and never reviewing them.
Only logging in to fight fires, so recruitment and creative refreshes never happen.
Skipping the tracking re-test after a site change, the classic cause of silent sales loss.

💡 Reporting tips

Maintain a weekly pulse (actions, clicks, top-partner movement) and a monthly deep dive (revenue and new-customer share by partner type, locking status, AOV). Treat your Event Risk queue and unlocked-action backlog as standing numbers — they represent money and quality at risk if left unreviewed. Looking at the same views each period is what lets you separate a genuine trend from a one-week wobble.

In practice: a worked example

A partner's conversions start tripping Event Risk flags. Because you review the risk queue every week, you catch the cluster early, investigate, and find a sub-source sending bot-like traffic. You pause that partner before the actions lock — no payout leaves the building. The manager who treats Event Risk as background noise sees the same flags, ignores them, and the automated payout cycle pays the fraud in full a few days later. impact.com automates so much that the only thing standing between you and paying for junk is a scheduled human look at the flags and the action ledger. The cadence is what guarantees that look actually happens.

When to lean in — and when to hold back

A fixed cadence helps when	You can go lighter when
You manage impact.com alongside other work	Affiliate is your full-time focus already
You have volume locking and Event Risk flags to review	Volume is tiny and review takes seconds
Tracking and site changes happen often	Your setup is completely stable
Recruitment keeps slipping	Pipeline-building is already habitual

Related guides

Frequently asked questions

It's when a recorded sale becomes payable after a set window. Reviewing actions before they lock lets you reverse returns and risky orders before commission is paid.

Weekly is a good default so flags get reviewed while they're still actionable. High-volume programmes may want to check more often.

Re-testing tracking after a site change. A broken tag can cost weeks of untracked sales before anyone notices.