Can this IO be signed electronically?

Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states, provided intent, consent, attribution, and retention requirements are met.

Do IOs need notarization or witnesses?

Generally no for commercial IOs. Notarization or witnesses are only required if local law or contract language makes the IO a notarized instrument; verify with state rules or legal counsel.

What if the payer requests a different legal name?

Use the payer's exact legal entity name on the IO. Mismatched names can delay payment and require an amended IO or reissued invoice.

How should I correct errors after signing?

Create an amended IO or addendum that references the original IO number and is signed by the same authorized parties; avoid handwritten changes on the executed document.

What authentication level should I require?

Require simple email authentication for low-value IOs and stronger methods (SMS, 2FA, or advanced signer authentication) for high-value or sensitive campaigns.

How long should signed IOs be retained?

Retain for at least 3 years after the campaign, extend retention for tax, HIPAA, or litigation holds; follow IRS rules (IRC §6501(a)) and HIPAA retention (45 CFR §164.530(j)) as applicable.

Electronic Signature
Templates
Marketing
Marketing PreLaunch IO Template

Marketing PreLaunch IO Template

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

MARKETING PRELAUNCH IO TEMPLATE

Parties

This Insertion Order (IO) is entered into between Brand/Client: and Agency/Creator: .

Brand/Client Primary Contact Brand/Client Address Agency/Creator Primary Contact Agency/Creator Address

Effective Date & Campaign Overview

Effective Date:

Campaign Name Objectives Target Audience Channels (select all that apply)

Social Media Display Ads Search Marketing Influencer Content Email

Campaign Start Date: End Date:

Deliverables

The Agency/Creator shall deliver the content items described below in accordance with specifications and deadlines. Each deliverable is subject to Brand approval as set forth in the Approval & Revisions section.

Deliverable 1 — Description

Format: Quantity: Deadline:

Deliverable 2 — Description

Format: Quantity: Deadline:

Deliverable 3 — Description

Format: Quantity: Deadline:

Compensation & Invoicing

Total Fee: $ Currency:

Payment Schedule / Milestones

Invoicing Terms: Net days from invoice receipt. Late payments accrue interest at .

Payment Remittance Instructions

Usage Rights & Intellectual Property

License Grant: Upon full payment, the Agency/Creator grants Brand a license to use the Deliverables for the Territory: for a Duration: .

Ownership: Select applicable allocation:
Brand owns Deliverables outright after payment. Creator retains underlying rights and grants Brand the license above. Joint ownership as separately agreed in writing.

License Scope / Restrictions

Exclusivity

Exclusivity Required: If checked, Exclusivity Period Start: End:

FTC Disclosure Compliance

The Agency/Creator represents and warrants that all paid or sponsored content will include clear, conspicuous disclosures in the manner required by applicable advertising and consumer protection laws and agree to comply with applicable endorsement and advertising disclosure practices.

Creator will include FTC-compliant disclosure on each social post/ad: Acknowledged

Approval, Revisions & Change Orders

Brand Approval Turnaround Time: days. Included revisions per deliverable: . Additional change orders will be billed at rates set forth in Payment Schedule.

Reporting & Metrics

Reporting Frequency KPIs & Deliverables Measurement

Termination

Termination for Convenience: Either party may terminate upon giving days' prior written notice. Kill Fee: Upon termination by Brand without cause, Brand will pay a kill fee of $ , plus fees for work performed through termination date.

Termination for Cause: Either party may terminate immediately for material breach if breach remains uncured for days after written notice.

Confidentiality & Indemnity

Confidential Information exchanged in connection with this IO shall be held in confidence for a period of from disclosure. Recipient shall not use Confidential Information except to perform obligations under this IO.

Indemnity: Each party shall indemnify, defend and hold harmless the other party from third-party claims arising from its breach of representations, willful misconduct, or negligence in connection with this IO, subject to any limitations set forth in a master agreement between the parties.

Miscellaneous

Force Majeure: Neither party will be liable for delays caused by events beyond its reasonable control. Governing Law: This IO shall be governed by the laws of the state of .

Brand Approval Contact Agency/Creator Contact for Delivery

Representations & Signatures

Each party represents that it has the full right, power, and authority to enter into this IO and to grant the rights and perform the obligations set forth herein. This IO is subject to the terms of any underlying master services agreement between the parties; in the absence of such agreement, this IO constitutes the complete agreement between the parties with respect to the subject matter herein.

Brand/Client - Printed Name:

By:

Date:

Agency/Creator - Printed Name:

By:

Date:

What the Marketing PreLaunch IO Template Is

The Marketing PreLaunch IO Template is a standardized insertion order used to record agreed campaign terms before launch, including media placement, creative deliverables, rates, and timing. It creates a single reference that aligns the agency, client, and vendors on scope, payment triggers, and acceptance criteria so execution teams can move from approval to live deployment with fewer misunderstandings.

Why a Consistent PreLaunch IO Matters

A clear IO reduces disputes, shortens approval cycles, and documents commercial terms in one place. Consistency helps budgeting, reporting, and legal review without replacing formal contracts.

Who Typically Completes and Signs This Template

Final signatures usually come from an authorized budget holder and an agency representative; internal routing and countersignature rules vary by organization.

Marketing managers and campaign owners who control budgets and delivery dates.
Agency account leads and media planners who specify placements, CPMs, and creative specs.
Procurement or legal approvers responsible for commercial terms and billing conditions.

Step-by-Step: Completing the PreLaunch IO

Follow these sequential steps to ensure the IO is complete, validated, and authorized before campaign activation.

01

Collect Requirements: Confirm campaign objectives, target audiences, and measurement KPIs with stakeholders.
02

Populate Template: Fill all required fields, including IDs, budget items, and creative deliverables.
03

Validate Numbers: Cross-check CPMs, impressions, and totals against media buy sheets.
04

Obtain Approvals: Route to budget owner and legal for signatures and version control.

Where the Completed IO Goes and How It Flows

Routing depends on your organization, but a typical flow moves from creator to approver to operations and finally to finance for invoicing.

Agency to Client: Agency sends completed IO to client contact for review and signature.
Client Approval: Authorized approver signs, confirms budgets, and returns the IO to operations.
Operations Handoff: Operations use the IO to configure ad servers and trafficking settings.
Finance Archive: Finance stores the signed IO for billing and audit purposes.

How to Configure an Online IO Workflow

Set up a reusable workflow in your document system to standardize fields, routing, and authentication for every prelaunch IO.

Field	Configuration
Template	Lock required fields and add conditional sections for media type.
Authentication	Use email or SMS codes; require stronger auth for high-value buys.
Routing Order	Set sequential approval: creator → manager → legal → finance.
Bulk Send	Enable bulk distribution for large, repeatable campaigns.

Delivery Options and Technical Integrations

Ensure the chosen platform supports audit trails, secure storage, and export to accounting systems for invoicing.

File Formats: PDF and DOCX preferred for archival and field mapping.
Integrations: Connectors for Salesforce, NetSuite, or Google Workspace simplify handoffs.
Authentication: Use 2FA or SMS codes for higher-value IOs.

Essential Elements of a Professional PreLaunch IO

A complete IO reduces ambiguity. The components below should be present, clearly worded, and aligned with invoicing and trafficking systems.

Campaign Identification

Unique campaign and purchase order identifiers that map to ad servers and finance systems, enabling reconciliation and preventing duplicate buys or misattributed spend.

Scope of Work

Detailed deliverable descriptions, creative specs, targeting parameters, and frequency caps so operations can implement trafficking without follow-up clarification.

Pricing and Payment

Clear unit economics (CPM, CPC), total budget, payment terms, and invoice schedule to prevent billing disputes and accelerate collections.

Timing and Milestones

Precise start and end dates, flight schedules, and creative delivery deadlines so activation and reporting timelines are enforceable and measurable.

Acceptance Criteria

Pass/fail conditions for creative, reporting format, and post-campaign reconciliation processes that define when services are considered delivered.

Legal Terms

Basic contractual clauses including indemnity boundaries, termination conditions, data sharing limits, and governing law to reduce downstream legal risk.

Required Information and Key Data Fields

Advertiser: Legal entity name

Agency: Authorized agency name

Campaign ID: Standardized campaign code

Budget: Total and unit rates

Dates: Start and end MM/DD/YYYY

Signatures: Authorized signers and dates

Practical Tips for Accurate, Efficient IO Completion

Follow these practices to reduce approval time, simplify trafficking, and lower the risk of billing disputes.

Standardize Templates

Use a single, version-controlled IO template across teams. Standardization reduces interpretation errors and speeds legal review. Maintain a change log and require approval for template changes.

Preflight Numbers

Validate budgets, CPMs, and impression forecasts against media vendor confirmations. Automated checks reduce manual math errors and prevent underfunded flights.

Lock Critical Fields

Make IDs, budget totals, and signature blocks non-editable after approval. Locked fields prevent accidental changes and preserve an auditable record of agreed terms.

Archive Signed Copies

Store executed IOs with a searchable index and link to billing entries. Retention supports audits and reconciliations, and eases dispute resolution.

Common Mistakes to Avoid

Leaving key fields blank, which causes delays and rework while approvals are clarified.
Using inconsistent campaign IDs that prevent reconciliation with ad servers and invoices.
Failing to specify acceptance criteria, creating disputes over whether deliverables were met.
Routing to the wrong approver or skipping legal review for nonstandard commercial terms.

Risks and Consequences of Incorrect or Missing IO Details

Delayed Invoicing: Missing or mismatched names can delay payment and reconciliation.

Billing Disputes: Vague rates or scope may lead to chargebacks or withheld payments.

Contract Exposure: Unapproved terms can create liability for indemnity or termination costs.

Operational Failures: Incomplete specs risk incorrect trafficking and measurement.

Regulatory Risk: Noncompliant data sharing may trigger privacy enforcement actions.

Audit Problems: Poor records increase difficulty proving deliverables during audits.

Key Dates to Track for Each PreLaunch IO

Track these dates in your project plan to align creative delivery, approvals, trafficking, and billing.

Creative Submission Deadline:

Date when final assets must be delivered to operations to meet launch.

Client Approval Deadline:

Last date for client sign-off to avoid launch delay.

Campaign Start Date:

First date impressions are allowed to run.

Billing Cutoff:

Date that determines the invoiced period and invoice generation timing.

Post-Campaign Reconciliation:

Deadline for final reporting and resolve of discrepancies.

Milestone Sequence from IO Draft to Live Campaign

These numbered stages show the typical path and responsibilities from draft to launch.

01

Draft IO

Create IO with all fields populated and attach media specs for review.

02

Internal Review

Campaign owner and finance validate numbers and budget availability.

03

Client Approval

Authorized signatory approves IO and returns signed copy to agency.

04

Activate Campaign

Operations configure ad servers and start delivery according to schedule.

How the PreLaunch IO Differs from a Statement of Work

Compare an IO to a SOW to determine which document best fits your project governance and contractual needs.

Criteria	Insertion Order	Statement of Work
Primary purpose	purchase details	detailed deliverables
Level of detail	transaction-level	project-level
Typical signers	budget owner	legal and program owner
Billing trigger	media delivery	milestone completion

eSignature Vendor Pricing Comparison for IO Workflows

A high-level comparison of common eSignature vendors and plan entry pricing. Confirm vendor plan details before purchase.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	Varies by vendor	Varies by vendor	Varies by vendor	Varies by vendor
Bulk Send	Yes (Business Premium)	Yes (plan dependent)	Yes (plan dependent)	Yes (plan dependent)	No or limited
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes (BAA)	Yes (BAA)	Yes (BAA)	Varies	Varies

Real-World Examples of Streamlined IO Workflows

Customer examples show how standardized IOs and eSignature reduced turnaround and improved compliance in practice.

Brian Fitzgibbons, COO

Optica Ventures standardized IOs across campaigns to reduce ambiguity and accelerate launches.

The interface simplified internal approvals.
The result was fewer corrections, faster client sign-off, and clearer audit trails for finance during reconciliation.

Tim Martin, Founder

Martin Properties used online IOs to process documents remotely and maintain compliance when teams were distributed.

Mobile signing enabled field approvals.
This reduced in-person meetings, kept campaign timelines intact, and preserved consistent records for later audits.

Who Signs and Who Can Authorize an IO

CMO

The Chief Marketing Officer or delegated budget holder typically has authority to approve campaign spend and sign IOs above delegated thresholds. Organizations should publish a signature authority matrix to avoid invalid approvals.

Agency Lead

An agency account lead or authorized procurement representative signs on behalf of the agency. Ensure the agency signer has documented authority and that their corporate name matches invoice records.

Frequently Asked Questions About the Marketing PreLaunch IO Template

Answers to common questions about completing, signing, and storing the prelaunch IO to prevent delays and disputes.

Need help? Contact support

Can this IO be signed electronically?
Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states, provided intent, consent, attribution, and retention requirements are met.
Do IOs need notarization or witnesses?
Generally no for commercial IOs. Notarization or witnesses are only required if local law or contract language makes the IO a notarized instrument; verify with state rules or legal counsel.
What if the payer requests a different legal name?
Use the payer's exact legal entity name on the IO. Mismatched names can delay payment and require an amended IO or reissued invoice.
How should I correct errors after signing?
Create an amended IO or addendum that references the original IO number and is signed by the same authorized parties; avoid handwritten changes on the executed document.
What authentication level should I require?
Require simple email authentication for low-value IOs and stronger methods (SMS, 2FA, or advanced signer authentication) for high-value or sensitive campaigns.
How long should signed IOs be retained?
Retain for at least 3 years after the campaign, extend retention for tax, HIPAA, or litigation holds; follow IRS rules (IRC §6501(a)) and HIPAA retention (45 CFR §164.530(j)) as applicable.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now