Template for writing West End show reviews for spotlight.tsufeden.com. Use this skill when Tsuf wants to write a review of a specific show she has seen. Works in combination with tsuf-writing-style (for voice) and seo-brief (for keyword target). Triggers when user says "write a review of", "I saw [show]", "review for [show]", or provides notes/bullet points about a show they attended. Produces a full draft structured as: TL;DR, rating, who it's for, what to know beforehand, the main review, optional depth section, and CTA.
Before running this template, confirm:
If no raw input is provided, ask Tsuf: "What did you think? Give me your honest take — what worked, what didn't, who would love it, and would you recommend it?"
A complete blog post draft of approximately 800–1,200 words, structured in the exact format Tsuf uses across her existing reviews. The draft uses Tsuf's voice throughout and requires only light editing before publishing.
Collect these before drafting. If any are missing, ask.
| Input | Why it's needed |
|---|---|
| Show name |
| Title and SEO |
| Theatre name + street address | Practical info for tourists |
| Nearest tube station(s) | How to get there section |
| Runtime + interval? | Essential for trip planning |
| Tsuf's rating (X/5) | Stated at the top — not inferred |
| Tsuf's overall verdict | One sentence: is it worth it? |
| What worked | Specific: performances, music, staging, story |
| What didn't work | Specific: same categories |
| English difficulty | Fast/slow, accent, how much matters |
| Who it's for | Comparable shows, audience types, age range |
| Any personal stake | Did Tsuf know the source? See it multiple times? |
| Price range (cheap / mid / premium) | Budget framing for tourists |
| Seating notes | Best areas, what to avoid, any restricted views |
| Ticket link | For the affiliate CTA at the end |
Build the post in this exact order. Do not reorder sections.
Purpose: Give the skimmer everything they need in one paragraph. This is above the fold — the most important real estate on the page.
Rules:
Tone: Direct and warm. This is a friend texting you before you buy tickets.
Example pattern: "[Show name] is [what it is — one specific description, not a genre label]. If you're [specific audience], this is [verdict]. [One more thing a tourist genuinely needs to know before deciding]."
Format: Star rating + number, e.g. 5/5
State the rating plainly. No explanation here — the review earns it.
Purpose: Help the reader self-select. This is one of the most useful sections for tourists who don't know where to start.
Format: Bulleted list of "if you..." statements. Each bullet is one sentence.
Always include:
Optional to include:
Tone: Practical and kind. The reader should finish this section knowing whether this show is right for them.
Purpose: Give the reader the context that will help them enjoy the show more. Not a plot summary — orientation.
Include if relevant:
Exclude: Full plot summary. If the post includes a spoiler section, flag it clearly and put it later.
Length: 100–200 words maximum. If it runs longer, cut.
Purpose: Tsuf's honest, personal, specific take. This is the heart of the post.
Length: 400–600 words. The longest section.
Structure within the section:
Opening image or verdict — Start with a vivid description of the experience, or a strong opinion statement. Not a summary. Make the reader feel something in the first two sentences.
What genuinely worked — Specific. Name performances by actor name and character. Name songs if they stood out. Describe staging, design, or moments — not categories. "The muses stole every scene they were in" not "the ensemble was strong."
What didn't work — At least one thing. Specific. Explain why, briefly. Note what would have made it work. Move on without dwelling.
The thing that surprised her — One observation that wasn't in any other review. What did Tsuf notice that no one else is talking about? This is the section that earns trust.
The emotional core — What does this show actually do to you? Not what it's about — what it makes you feel. "You leave with your cheeks aching from smiling" is more useful than "it's a comedy."
Voice reminders for this section:
Purpose: Give the tourist everything they need to actually get there and buy a ticket. This section exists because tourists land on this post from search and often don't know London at all. It converts readers into ticket buyers.
Format: Four sub-sections, each short and scannable. No prose paragraphs — use short lines, bold labels, and bullet points.
Format:
The theatre
[Theatre Name]
[Street address], London [postcode]
Then 1-2 sentences of context if the venue itself is worth mentioning — historic building, unusual layout, famous for something. Skip this if there's nothing genuinely interesting to say.
Example:
The theatre
The Fortune Theatre
Russell Street, London WC2B 5HH
One of the most intimate stages in the West End, built in 1924. Wherever you sit, you are close to the action.
Purpose: Tourists in London default to the Tube. Give them exactly what they need.
Format:
Getting there
Nearest Tube: [Station name] ([line colour]) -- [X minute walk]
Also convenient: [Second station if relevant] ([line]) -- [X minute walk]
[One sentence on any useful extra: night tube, nearby bus, walking from another show, etc.]
Rules:
Purpose: Help the reader pick the right seat for their budget and preference. This is one of the most-searched questions about any West End show and almost nobody answers it well.
Format: Three tiers, each with a 1-2 sentence honest take:
Where to sit
Stalls (ground floor)
Best for: [what experience this gives]
Watch out for: [any specific issues]
Dress Circle (first balcony)
Best for: [what experience this gives]
Watch out for: [any issues]
Upper Circle / Grand Circle (upper balcony)
Best for: [what experience this gives]
Watch out for: [height, steep rake, restricted views at sides]
Always include:
Tone: Practical and honest. If the upper circle is genuinely not worth it for this show, say so. If the dress circle is the sweet spot, say so confidently.
Purpose: Set expectations for tourists who don't know West End pricing. No one else on the internet gives honest budget framing — this is a competitive advantage.
Format:
Ticket prices
Budget seats: from ~£[X] (upper circle, sides, or day seats)
Mid-range: ~£[X]-£[X] (dress circle, back stalls)
Premium: £[X]+ (front stalls, centre dress circle)
[1-2 sentences on value: is this show good value at full price? Are there ways to get cheaper tickets?]
Rules:
Purpose: Reward the engaged reader. This section is for people who want more after the review.
When to include: When there's genuinely interesting context — historical accuracy (like Operation Mincemeat), comparison to the source material (like Hercules vs. the 1997 film), or behind-the-scenes insight.
When to skip: When there's nothing genuinely interesting to add. Don't pad.
Format: One or two sub-sections with headers. 150–250 words each maximum.
Examples from Tsuf's existing posts:
Purpose: Send the reader somewhere — to tickets, to Instagram, to think.
Always include:
Affiliate disclosure (always include when a ticket link is present): "Disclosure: the ticket link above is an affiliate link — if you book through it, I earn a small commission at no extra cost to you. It helps me keep writing."
Tone: Warm, never pushy. The recommendation feels like a friend's, not a sales pitch.
Before outputting the draft, confirm:
For a show Tsuf loved: "[Show] is the kind of night out that makes you annoyed at yourself for waiting this long to book. [Specific thing that makes it stand out]. If you're trying to decide, here's my honest take."
For a show Tsuf has mixed feelings about: "[Show] calls itself [its own marketing claim]. It mostly earns it — with one or two caveats worth knowing before you spend [price range] on tickets."
For a hidden gem: "Nobody is talking about [Show] the way they should be. It's been running quietly at [theatre] while the big names get all the attention — and that's a mistake."
For a show that disappointed: "I wanted to love [Show]. I really did. [Reason for high expectations]. Here's what actually happened."
If Tsuf wants to include a full plot summary or act-by-act breakdown, put it at the very end of the post, after the CTA, under a clear header:
"Full Plot Summary (Spoilers Below)"
This preserves the review for undecided readers and rewards those who have already seen it or explicitly want spoilers. It also adds significant word count that helps SEO without cluttering the main review.
Once the draft is complete, flag the following for Tsuf's review: