The Complete Copywriting Checklist

At 4:40 in Fablewren's office, Beatrix taps "Read the return conditions" on her phone. The preview opens a delivery page. We'll follow this invented reviewer through a release check for a fictional desk-organizer shop.

The headline has already had several rounds of polish. It still promises "A perfect desk in minutes," although the offer record contains no setup study. Beatrix has two release blockers before she's reached the purchase button.

You can use her review to check your own draft. Keep the current offer beside the preview, and record what would let you close each issue.

Set up the review so problems stay visible

Keep one release record for the review, with the draft, brief and offer versions attached. Add the rendered preview so another editor can reproduce the wrong destination Beatrix found on her phone.

Enter the return-policy link as issue R1. Record its location in preview 12 and its current destination, delivery information. Give each issue a resolution owner and space for the retest result, so a correction can be checked before the row closes.

Keep "blocked" available for issues that prevent release. You can use "needs work" for unfinished edits and record a reason when a check doesn't apply. A request to make the headline warmer shouldn't obscure an unverified claim in the same opening.

The lesson on how to edit copy develops the revision passes. For this Frameworks review, record who can correct the return link and what evidence would settle the headline.

Gate one: is this the right message for this reader?

"Can we keep the headline after all those edits?" a colleague asks. Beatrix points to the brief's product-comparison task: shoppers need to see what fits in the compact tray and how its dividers move. She proposes putting that information first.

Check the brief's basis for that audience. If setup speed is the team's guess, label it and ask where the priority came from. You can make a provisional editorial choice while leaving the missing customer evidence visible.

Questions for the first screen

Reader and evidence

• Can the intended shopper identify this as a desk tray?
• What does the incoming ad lead them to expect?
• Which product detail does the approved brief give priority?

Action and uncertainty

• Does the main button take them to the expected next step?
• Which assumption still needs a customer or business answer?

Compare the traffic source with customer awareness. Someone arriving from a tray comparison may already know the product type. An email about a new divider arrangement can start elsewhere, provided the page answers what the email led them to expect.

Use copywriting research when the audience assumption needs investigation. For this review, record how that uncertainty affects release. You can remove the unsupported speed promise now while the team learns more about which tray details people value.

Gate two: can we stand behind the offer and its claims?

Beatrix puts "in minutes" next to the offer record again. It lists movable dividers and a $38 price, and delivery estimates appear at checkout. Ask the business for setup evidence, or propose wording that describes the product you can demonstrate.

"A desk tray with three dividers you can move" is a workable candidate. The value proposition can explain why that arrangement matters. Keep the demonstration nearby so a shopper can inspect how the compartments change.

The FTC's advertising-substantiation policy calls for a reasonable basis for objective express and implied claims before dissemination. In this US context, leave the evidence attached to the claim. The absence of a customer complaint doesn't supply the missing support.

Offer, evidence and permission

• Match product details, quantities and prices to the current source record.
• Confirm material conditions appear where readers need them.
• Check both the literal claim and its reasonable implication.
• Verify statistics, quotations and customer accounts against their originals.
• Match a customer quote's planned placement to the permission given; record any relationship the reviewer decides must be disclosed.
• Remove invented urgency and any promise the evidence cannot support.

The offer allows returns within 30 days of delivery, subject to the stated condition policy. Beatrix checks whether the page makes the starting date clear, then asks the policy owner for the destination containing the full terms.

If a customer allowed a quote in an email only, leave it off this page until that use is agreed. Record the permitted placement so approval of the sentence doesn't quietly become approval for every channel.

Look at any product images and customer accounts used as support. Compare them with their originals. If a photograph suggests accessories are included, confirm what's actually in the box and adjust the presentation before approving the page.

Gate three: can someone understand the page by looking through it?

Read the first screen and section headings without the body copy. Can you find the dimensions and identify what the main action does? Then read the full page to see whether the explanations answer the questions those labels raise.

Nielsen Norman Group's online-reading research describes persistent scanning behavior, with variation by task and design. Give Fablewren's dimensions a descriptive heading, then check whether you can find it while reading only the headings. Keep the measurements themselves beside the tray image, where a shopper can compare them.

Use landing-page anatomy if the order needs work. Place the divider explanation where the shopper can inspect the product, and make the policy accessible before ordering.

A proposed opening for review

Draft opening

A perfect desk in minutes. Meet your new must-have workspace essential. Get organized.

Revised offer summary

A desk tray with three dividers you can move. Arrange compartments around your small supplies. See dimensions and colors for the $38 tray.

This is a candidate for approval. Attach the working links and the policy version the reviewer should inspect.

Beside the relevant links, add: "Delivery estimates appear at checkout; review the return conditions before ordering."

Read the revised opening in the actual layout. A price that looked adjacent in your document might sit below a large image on a phone. Check what someone can learn before reaching the first purchase button.

For an email review, include the subject and the landing page in this pass. For an ad, compare the destination's opening with the offer in the creative. Keep the same decision in view across the assets you're reviewing.

Gate four: do the words sound clear, specific and appropriate?

With the claims flagged, read the page aloud. If "desk solution" makes you pause, replace it with "tray" and check whether any useful product detail disappears.

Search the preview for the tray's name and its $38 price, then compare each occurrence with the offer record. Include captions in that pass. An old price left below an image needs correcting even if the opening is right.

For the return condition, resist the urge to make every line charming. A shopper needs to understand which condition the tray must be in. Ask the policy owner to settle any ambiguity before replacing formal wording with a friendlier version.

If a playful return-link label hides the policy's purpose, propose "Read the return conditions." Read it with the surrounding sentence. The shopper should be able to find the conditions without working out a joke.

Gate five: does the finished experience work?

Return to the phone preview and follow the main action. Check that the selected tray variant carries into the cart correctly. Use a test environment to inspect form errors and the confirmation without placing a real order.

Preview 13 has the proposed headline and corrected link. When her colleague asks whether the page can ship, Beatrix attaches her phone retest and keeps the headline issue open for approval.

W3C's explanation of link purpose allows the purpose to come from the label or its programmatically determined context, so "Learn more" isn't automatically a failure. Here, "Read the return conditions" gives a clear choice, provided the link goes there. This review covers that link without certifying the whole interface.

Release and handoff

• Inspect the final layout on the relevant screen sizes and formats.
• Follow the main action and verify destination, forms and confirmation copy.
• Check meaningful link labels, image alternatives and visible error messages.
• Confirm the published offer matches the ad, email or other entry point.
• Resolve release blockers and name the final approver.
• Save the approved version, review date and remaining follow-up work.

Decide what still needs investigation after the fixes. You don't need an experiment to establish whether the return link opens the intended policy. Use A/B testing for a defined message question when the setup and traffic support it.

If the team wants to compare the divider explanation with a different supported opening, give that follow-up an owner. Specify what decision the comparison will inform. "We'll test it" won't help the next editor determine whether a page can be released today.

R1 evidence: phone capture of the return policy opened from preview 13.

Beatrix's completed link check

Issue R1: return-policy link. Preview 12 opened delivery information. Beatrix retested preview 13 on her phone: the link opened the policy stating 30 days from delivery and the condition requirements.

Keep the corrected destination beside the preview used to check it.

Send the remaining claim for a decision

With R1 closed, Beatrix asks the offer owner to approve the divider description in preview 13 or provide setup evidence for "in minutes." The headline remains blocked until the owner approves the supported opening or supplies evidence for the speed claim.