What to Include in a First-Draft Submission Email

A first-draft submission email should tell the reviewer exactly what is ready, where each file lives, which brief version you followed, and what decision you need by when. It should also disclose open questions and known deviations. The goal is not to persuade the brand that the work is perfect; it is to make an accurate review possible.

Use a subject line that identifies the decision

Avoid a subject line such as “Draft” or “Files attached.” Include the campaign, creator, deliverable, version, and action. A reviewer managing several campaigns should understand the request without opening the message.

Examples:

• Review requested: Spring launch / Jordan / Reel 1 / v1
• First drafts ready: Trail campaign / Videos 1–3 / due Sept. 4
• Decision needed: Product demo v1 / one open claim question

If the brand has supplied asset IDs or a naming convention, use them. Do not rename the same deliverable differently in email, storage, and the brief.

Inventory every submitted file

Put a numbered manifest in the message. For each item, list the deliverable name, exact filename, version, format, duration, and review link. If several exports come from one concept, list them separately.

For example:

1. Reel 1, CB_Spring_Reel01_v1_9x16.mp4, 00:31, first draft
2. Story 1, CB_Spring_Story01_v1_9x16.mp4, 00:14, first draft
3. Cover, CB_Spring_Reel01_Cover_v1.jpg, 1080×1920

State whether links require an account and when access expires. Test them in a private browser window before sending. If uploads are still processing, do not call the package ready.

The milestone structure in the sponsored content production timeline helps keep submission day from becoming an improvised file hunt.

State the source requirements you followed

Identify the dated brief, approved concept or script, claims list, and any later written changes. This lets the reviewer compare the cut with the same source you used.

A useful summary might say:

Produced against Brief v3 dated August 21, the approved “morning routine” concept, and the offer update sent August 25. The attached cuts use code MORNING20 and the September 1–10 offer dates.

Do not attach five versions of the brief without identifying the controlling one. If the brand has not resolved a conflict, name it plainly rather than choosing silently.

Before submission, use the first-try approval guide to check disclosures, claims, required shots, offer details, and technical exports on every cut.

Disclose open questions and known deviations

If something differs from the approved plan, say so before the reviewer finds it. Separate blockers from decisions that can be made during review.

Examples:

• “The approved package color was unavailable; this cut shows the current blue package. Please confirm acceptance.”
• “The spoken product name matches the pronunciation file, but the brief uses a different spelling. Please confirm the caption spelling.”
• “The final tracking link has not arrived, so the caption includes a marked placeholder and is not ready to publish.”
• “Music is temporary for review and is not cleared for final commercial use.”

Do not describe a known missing requirement as a harmless creative choice. Give the reviewer enough information to approve an exception, request a change, or hold the asset.

Ask for one consolidated decision

Name the requested response and deadline. “Thoughts?” invites scattered reactions. Ask for approval, approval with specified changes, or one consolidated revision list from the designated owner.

Use language such as:

Please return one consolidated decision by 3:00 p.m. ET on August 28 so the agreed revision window remains available. If feedback arrives later, I will confirm the effect on the publication date before proceeding.

This is not a threat; it makes the schedule visible. Do not claim that silence equals approval unless the agreement clearly says so and that treatment is valid under applicable law.

When feedback arrives through several channels, point everyone back to the agreed review location. The consolidated feedback guide explains how one decision owner can resolve conflicts before notes reach the creator.

Use this complete email template

Subject: Review requested: [Campaign] / [Deliverable] / v1

Hi [Name],

The first drafts below are ready for review against [brief/version/date] and [approved concept or script].

Files

1. [Deliverable: filename, version, duration, link]
2. [Deliverable: filename, version, duration, link]

Included in this version

• [Required disclosure, claims, shots, offer, CTA]

Questions or deviations

• [State each issue and requested decision]

Please send one consolidated [approval/revision] decision through [location] by [date, time, time zone]. The planned next milestone is [date].

Thanks, [Creator]

Adapt the fields to the campaign. Keep the manifest even when there is only one file; it becomes valuable when v2 arrives.

Preserve the delivery record

Keep the sent message, upload confirmation, manifest, submitted files, and returned decision together. A record helps both sides identify what was reviewed, but it does not by itself determine ownership, payment, or acceptance in a dispute. Those questions depend on the agreement and applicable law.

After approval, record the exact final asset and publication instructions rather than relying on the first-draft thread. That prevents an old export from becoming the live post.