Create a restaurant newsletter in Migma from a single, approved offer brief. Before accepting the design, check that the expiry, eligible location, booking destination, and redemption conditions tell the same story. A clear promise matters more than adding urgency to a promotion that the restaurant cannot honor.
This Migma-published checklist is for restaurant marketers reviewing a time-limited offer. Brevo's restaurant email and newsletter guide provides broad campaign context. The original workflow here concentrates on one practical failure: a newsletter that looks current while its offer or destination is already out of date. Sources were checked on October 15, 2026.
Get the offer brief accepted before the design
Ask the offer owner to approve the applicable dates, service periods, participating location, eligible items, exclusions, and the action the guest must take. If a condition is unresolved, keep it unresolved in the brief rather than letting the designer invent a plausible detail.
Use Migma's brand context for the restaurant's approved identity and voice. Review imported details against the current brief. An old menu page may help explain the visual style while still containing an item that is no longer offered.
Separate the deadline for booking from the date of dining. Those may be different conditions. In a fictional example, guests might need to reserve by Wednesday for a Thursday set menu. A headline saying “Available until Wednesday” would leave the reader unsure whether Wednesday is the booking or dining deadline.
Check one promise across the whole email
Review the subject line, preview text, hero, body, button, and footer together. Do not let the headline imply a broader offer than the conditions support. “Dinner for two” and “a complimentary dessert with two eligible main courses” describe different promises.
Use the checklist below against the approved brief. It is an editorial review aid, not legal advice or a claim that every sending platform validates offer conditions.
| Check | Question to answer before approval |
|---|---|
| Time | Does the copy distinguish booking deadline, service date, and relevant local time? |
| Place | Is the participating restaurant or location explicit? |
| Eligibility | Can a guest tell what they must order, book, or present? |
| Availability | Does any limited-availability statement match an approved fact? |
| Action | Does the button lead to the intended reservation or ordering route? |
| Consistency | Do the subject, image text, body, and destination agree? |
Do not bury the condition that changes the meaning of the offer in a tiny footer. Keep necessary supporting detail readable and close enough to the promise that a scanning guest can understand it.
Write urgency that will still be true when opened
Prefer an approved date and time to an unsupported countdown. “Book by 6 p.m. Wednesday, October 21, restaurant local time” communicates a specific action deadline in the fictional example. “Last chance tonight” depends on when the guest opens the message and which time zone they assume.
Use a countdown only when the team has verified its behavior in the chosen destination and the displayed deadline matches the offer. This workflow does not claim that Migma inserts a live timer or rewrites a received email after expiry.
If the issue might be forwarded or opened later, make the date easy to find. A reader should not need the original send timestamp to work out which “Friday” the email meant. Treat this as a clarity decision and have the offer owner approve the final wording.
Inspect the picture as part of the promise
Review any food photograph, menu graphic, and text embedded in imagery. The hero should not show an excluded item while the body describes a different offer. If the image contains a date or price, it needs the same review as the body copy.
Use real, approved restaurant assets when available. If an illustration is used, avoid presenting it as a photograph of the exact dish the guest will receive. The point of the image is to help the guest understand the offer, not create an unsupported expectation about portions or included extras.
Check the email at a narrow size. Keep the essential date, location, and action in readable text, rather than relying entirely on a detailed menu image. Migma's client-compatibility guidance explains the need for email-safe design and review; it does not promise identical rendering in every client.
Follow the booking path before accepting the creative
Open the primary action from an authorized destination test. Confirm the restaurant location, booking date options, offer explanation, and any applicable code or selection step. A working URL is not enough if it opens the wrong branch of a restaurant group.
Also check the path after the deadline. Ask the destination owner what the guest sees then: an expired-offer explanation, current reservation options, or another approved route. Do not leave the email team to assume that a changed webpage will repair an ambiguous message already received.
If the route requires a code, confirm where that code appears and how the guest uses it. Do not add an invented code just to make the draft feel complete. Preserve the approved reference until the owner supplies a valid destination and instruction.
Hand off the exact reviewed version
Run Email Preflight on the creative and resolve relevant findings. Record the design version and the accepted offer brief together. A passing creative check does not establish audience permission, table availability, or a functioning booking system.
Use Migma's export options when an HTML handoff fits the sending platform. The implementer still needs to adapt the final template and verify links and variables. If the team uses Brevo, review the current supported export workflow and destination result rather than assuming every creative detail transfers unchanged.
Have the sending owner verify the eligible audience, schedule, and any planned reminder. If a reminder could run after the offer expires, that is a workflow problem to resolve before sending. Changing its subject line will not make the expired offer valid.
Keep an expiry decision beside the reusable template
After the promotion, mark the brief as expired in the team's normal content process. Reusing the visual layout should start a fresh review of dates, locations, terms, imagery, and destination. A successful previous campaign does not approve the next offer automatically.
If the offer changes after publication or sending, the authorized owner should decide whether a correction is needed and who should receive it. Keep any correction specific to the changed fact instead of adding a second promotional pitch.
Prepare the restaurant newsletter in Migma with the offer owner involved from the start. The finished email should let the guest answer three questions quickly: what is available, when and where it applies, and what to do next.
Frequently Asked Questions
Should a booking deadline and dining date be stated separately?
Yes, when they are different conditions. Have the offer owner approve wording that tells the guest when to reserve and when the offer can be used.
Can a working booking link still fail the review?
Yes. It may open the wrong restaurant location or show dates and conditions that conflict with the email. Verify the destination journey, not only whether the URL loads.
Does this workflow claim live timers or automatic inbox updates?
No. Use only destination behavior the team has verified. A new creative version does not establish that an earlier received email will change after expiry.
What needs a fresh review when we reuse the layout?
Recheck the dates, participating locations, redemption conditions, imagery, destinations, audience, and schedule against a newly approved offer brief.