- Keep your rate card and inventory calendar as data, and generate every quote, IO and invoice from them.
- Book placements when the IO is signed, not on a verbal yes. Holds expire.
- Put deliverables, deadlines, labels, reporting, makegoods and payment terms in the IO, so nothing is decided after the send.
- Let sponsors build and approve their creative in a live preview of your real template.
- Label every placement clearly as an ad, in the template, above the copy.
- Send proof of placement and a short report the morning after, then invoice from the same record.
- Close the month by matching IOs, sends, invoices and payments line by line.
What ad operations actually covers
Ad ops is everything between a sponsor saying yes and the money landing: contracts, scheduling, creative, the sponsored issue, proof of delivery, invoicing and the month-end check that it all adds up.
At most newsletters it lives across a spreadsheet, a calendar, an inbox and a payment tool, held together by one person's memory.
The fix is one record per deal that every step reads from and writes to.
| Stage | The record it produces | Where it usually breaks |
|---|---|---|
| Quote | Placements and prices pulled from the rate card | Prices typed by hand drift from the rate card |
| Booking | Dates reserved on the inventory calendar | Verbal holds that never expire, double-sold slots |
| IO | Signed terms with an audit trail | Terms agreed in email threads, not in the IO |
| Creative | Approved copy, links and logo, locked | Late copy, edits after approval, broken links |
| Trafficking | The sponsor slot filled in the scheduled issue | Copy pasted into the wrong issue or the wrong slot |
| Proof and report | Send confirmation, screenshot, delivery and click data | Reports assembled days later, inflated by bot clicks |
| Invoice and collect | Invoice tied to the IO number, tracked to paid | Invoices sent late, to the wrong person, without a PO |
1. Treat your rate card and calendar as data
Store placements, prices and rules in one place your tools can read. Every quote, IO and invoice should be generated from it, so prices never drift between documents.
The rate card says what you sell. The inventory calendar says what is left: every send date and slot, marked open, held, booked or delivered.
Build it from your real publishing schedule, including skipped holidays and special editions, or you will sell a date you are not sending.
How to check it: pick any date next month and ask how many slots are open. If the answer takes more than ten seconds, or needs someone to check their inbox, the calendar is not the source of truth yet. For setting the prices themselves, see the guide on building a media kit and rate card.
2. Book on signature, hold with an expiry
A sponsor asks for the first two Tuesdays in November. You want to hold them. Fine, but give every hold an expiry date, and release it automatically if the IO is not signed by then.
Only a signed IO turns a hold into a booking, and the signature should update the calendar on its own.
When two sponsors want the same date, the first signature wins. Say so in your proposal.
3. What goes in the insertion order
Anything you might argue about later belongs in the IO now.
- Parties and contacts: advertiser, agency if any, the person approving creative and the person who pays invoices. They are rarely the same person.
- Deliverables: placement type and issue dates.
- Price: rate per placement, total, and any discount, all pulled from the rate card.
- Creative terms: deadline, length limits, logo specs, revision rounds, and your right to decline copy.
- Disclosure: the label the placement will carry.
- Reporting: what you report, when, and whether automated clicks are filtered out.
- Makegoods: what happens if a placement is missed, broken or late.
- Cancellation: notice period and what is owed if they cancel late.
- Payment: when you invoice, when payment is due, and any PO number finance needs.
Agency buyers may point you to the 4A's/IAB Standard Terms and Conditions for Internet Advertising, Version 3.0, published in 2010. It was written for agency media buys, says it is not meant for direct buys between advertiser and publisher, and notes it may not fully cover sponsorships. It is still a useful reference for how buyers expect cancellation, makegoods and invoicing to work.
4. E-signatures that hold up
- IO viewed by sponsorViewed
- Signed with audit trailSigned
- Dates booked, invoice sent via StripeSynced
Illustrative example. Names and figures are fictional.
Send the IO as a link the sponsor signs online, and make the signature easy to defend.
Here is what US law actually says. The federal ESIGN Act states that a signature, contract or other record relating to a transaction "may not be denied legal effect, validity, or enforceability solely because it is in electronic form." It does not force anyone to accept electronic signatures. Its consent and disclosure rules apply when a law requires information to be given to a consumer in writing.
The state version is the Uniform Electronic Transactions Act. It has been enacted in 49 states, plus DC, Puerto Rico and the US Virgin Islands. New York is the exception and uses its own Electronic Signatures and Records Act. UETA applies only when each party has agreed to do the transaction electronically, and that agreement can be read from context and conduct.
In practice:
- Ask the signer to agree to sign electronically, and store that agreement.
- Verify the signer, for example with a one-time code sent to their work email.
- Keep an audit trail of who opened and signed, and when.
- Store the signed version unchanged. ESIGN's retention rule asks for an accurate record that stays accessible and reproducible.
This is not legal advice. Have a lawyer review your IO template once.
5. Creative intake with the limits up front
It is Thursday at 4 p.m. Monday's sponsor copy is 40 words over, the logo is a screenshot, and the link 404s. Each problem is cheaper to catch at intake than at send.
Give each sponsor one secure page for their placement, with the limits and deadline shown before they start typing. Validate links on submission, not at build time.
Add tracking parameters for them. Google Analytics documents utm_source, utm_medium and utm_campaign for this, and utm_content to tell apart two links in the same email. Use one naming pattern for every sponsor, so their analytics team can find you.
Set a deadline with a fallback, written into the IO: if copy is not approved in time, their last approved copy runs.
6. Sponsor previews in the real template
The old loop is a PDF proof, edits by email, another proof, and a final change at 11 p.m. the night before.
Replace it with a live preview. As the sponsor types, they see their placement rendered inside your actual template, with your fonts, your label and your width. They approve it on the same page. Approval locks the copy and records who approved it and when.
Preview in the real template, not a mockup. Copy that fits a design file can wrap badly on a phone.
7. Traffic it into the issue, labeled
Your production pipeline should pull the approved placement for each send date and fill the slot. Nobody should paste sponsor copy by hand.
Build the disclosure label into the slot itself, so it cannot be left off. The FTC's guide on native advertising is the reference here. It names labels consumers are likely to understand: "Ad," "Advertisement," "Paid Advertisement" and "Sponsored Advertising Content."
The same guide is specific about the rest:
- Put the label in front of or above the headline, in the ad itself.
- A company logo or name on its own is unlikely to be enough.
- "Promoted" is at best ambiguous.
- "Sponsored by" or "Presented by" can suggest the sponsor paid for content without writing it. For copy the sponsor wrote, use a plain ad label.
- Make the label legible: text that contrasts strongly with its background.
How to check it: send yourself a test of every sponsored issue. Confirm the sponsor, the date, the label above the copy, and that every link resolves with its tracking parameters.
8. Proof of placement and reporting
Sponsors renew when they can see what they got. Send proof the morning after.
Proof of placement is simple: send date and time, recipient count, and a screenshot or web link of the placement as it ran.
Then a short, honest report:
- Delivered, as a count, not just a rate.
- Unique clicks on their links, after filtering automated clicks, with the raw number alongside.
- Click-through rate on delivered, using the filtered number.
- A note on anything unusual.
Be careful with opens: privacy features in some mail apps load images automatically, recording opens that never happened. Label them as an estimate, if you report them at all. The guide on measuring newsletter engagement covers how to filter bot clicks.
9. Makegoods: decide the rules before you need them
Eventually a send fails, a link breaks or a placement runs on the wrong day. The IO should already say what you owe.
The 4A's/IAB terms are a useful model. If deliverables fall short or an ad is omitted, the parties try to agree a makegood flight. If they cannot, the buyer can take a credit for the under-delivered value. A buyer who prepaid can, under conditions, take a refund. And no makegood may run beyond the IO dates without the buyer's written consent.
For a newsletter, in plain rules:
- Missed or broken placement: rerun in the next comparable slot the sponsor accepts, or credit it.
- Your error in the copy or link: makegood.
- Their late or broken creative: no makegood. Say so in the IO.
- Delivered as booked, but fewer clicks than hoped: no makegood, unless your IO guaranteed clicks.
10. Invoice and collect
Put your invoice timing in the IO: on signature, before the first send, or after it runs. One sensible split is prepayment for new sponsors and terms for repeat ones.
If an agency buys on the 4A's/IAB terms, payment is due 30 days from receipt of invoice unless the IO sets another schedule. Those terms also expect invoices to carry the references the agency asks for, such as the IO number and the advertiser or campaign name, and let the agency ask for proof of performance.
Send the invoice from the deal record. Invoices get paid late for boring reasons: a missing PO number, the wrong billing contact, an amount that does not match the IO.
Use a payment tool that chases for you. Stripe's invoicing, for example, can send reminders for unpaid invoices, copy additional billing contacts on invoice emails, and notify your system with an event when an invoice is paid, so the deal record updates itself.
How to check it: list every invoice past due today. For each one, you should know why without opening an email thread.
11. Reconcile every month
Once a month, match four lists line by line: signed IOs, placements actually sent, invoices issued, and payments received.
- A placement sent but not invoiced is lost revenue.
- An invoice with no matching send is a dispute waiting to happen.
- A booking with no signed IO is a risk to the calendar.
If every step writes to the same record, this takes minutes.
A worked example
A fictional weekly B2B newsletter sells one primary sponsor slot per issue. Here is one deal, end to end.
- Monday: a software company asks for two November dates. The operator places a hold that expires Friday.
- Wednesday: the sponsor signs the IO. The hold becomes a booking and the intake link goes out.
- Next week: the sponsor writes, trims and approves the copy in the preview. Copy locks.
- Send day: the pipeline fills the labeled slot. A test send confirms the links.
- Next morning: proof and a short report go out, with filtered and raw clicks.
- Second send: a link breaks after the sponsor's site migration. Their error, so no makegood, but the operator flags it within the hour.
- Month end: two sends, one invoice, one payment. All match.
Nobody opened a spreadsheet. That is the point.
Metrics worth tracking
| Metric | What it tells you | How to read it |
|---|---|---|
| Sell-through | Share of available slots booked, by month | Low months show where outreach should focus |
| Hold-to-signature rate | How many holds become signed IOs | A low rate means holds are blocking real buyers |
| Creative on time | Share of placements approved by deadline | Falling numbers mean intake is too hard |
| Days to paid | Time from invoice to payment | Watch by sponsor, not just on average |
| Renewal rate | Sponsors who book again | The best single test of your reporting |
What most guides miss
Lessons from systems we have built and run, not the usual checklist.
Book on signature, not on a handshake
Verbal yeses get double-booked and forgotten. Make the signed IO the only thing that reserves a date, and have the signature book it automatically.
The approver and the payer are different people
The marketer who loves the placement never sees the invoice. Capture a billing contact and any PO requirement in the IO, or your invoice lands in an inbox nobody reads.
Lock copy at approval
Late edits after approval are where typos and broken links come from. Allow changes, but route them back through the preview and a new approval, with the deadline still enforced.
Filter clicks before you report them
Corporate security tools click links before a person does. Raw clicks look great once and then fail to repeat. Report filtered clicks, with the raw number beside them.
How we do it
For a B2B trade newsletter publishing three times a week with one operator, we built this flow end to end: sponsor outreach, booking, e-signed IOs, live sponsor previews in the real template and invoicing, wired into an AI-assisted production pipeline with editor approval and bot-click filtering on the engagement data. See our monetization systems, how we build on Resend, or start upstream with building a sponsor outreach system.
Not sure where your own process leaks? A process audit maps it step by step and shows what to automate first.
Sources
- IAB and 4A's: Standard Terms and Conditions for Internet Advertising, Version 3.0 (PDF)
- GovInfo: 15 U.S.C. 7001, Electronic Signatures in Global and National Commerce Act
- Uniform Law Commission: Electronic Transactions Act
- Google Analytics Help: Collect campaign data with custom URLs
- FTC: Native advertising, a guide for businesses
- Stripe Documentation: Send customer emails
- Stripe API Reference: Types of events
Facts checked against these sources in October 2026.