Home/Blog/How to Write a Weekly Exec Flash from a Closed Metrics Pack
Blog

How to Write a Weekly Exec Flash from a Closed Metrics Pack

P
promptstudio
How to Write a Weekly Exec Flash from a Closed Metrics Pack

Weekly flashes fail when they borrow quarterly targets from a board pack that was not attached. The model writes on track. The CEO asks for the cell. There is no cell.

The matching generator is the Weekly Exec Flash from a Closed Metrics Pack (No Invented KPIs) (Weekly Exec Flash From A Closed Metrics Pack No Invented Kpis) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).

Close the ledger before the headline

Turn a closed metrics pack into a one-page weekly exec flash. No invented KPIs, targets, or quotes. Not a board deck. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.

Paste these fields before you hit run:

Week ending date and audience: [Week]
Closed metrics table (name, value, unit, period): [Metrics]
Targets I may cite (or NONE): [Targets]
Owners for each metric: [Owners]
Wins I can prove: [Wins]
Misses I can prove: [Misses]
Decisions I need this week: [Decisions]
Quotes I may use (or NONE): [Quotes]
Words I must not use: [Banned]
Max words: [Budget or 400]

That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.

Scoreboard with NOT IN INPUTS for missing targets

Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.

Walk the Generate list in order:

  1. Honesty ledger: every metric name, value, unit, owner, and quote. Forbidden: KPIs not in Metrics, targets not in Targets.
  2. Headline (20 words max) that uses only Metrics and Week. No on-track claim unless Targets exist and math supports it.
  3. Scoreboard table: metric, value, unit, vs target or NOT IN INPUTS, owner.
  4. Wins and misses: only Wins and Misses. One sentence each.
  5. Decisions needed: only Decisions. If empty, write none this week.
  6. Quote block: only Quotes. If NONE, omit.
  7. Risks implied by Misses. Do not add a new metric to soothe them.
  8. Compliance pass: quote Banned words, invented KPIs, and board-deck padding. Cut them. Print word count vs Budget.

If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.

Wins, misses, and the one decision

Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.

Honor the constraints as hard stops, not vibes:

  • Weekly exec flash, not a board book and not an investor update.
  • Never invent a KPI, target, or customer quote.
  • Stay under Budget words.
  • If Targets is NONE, do not write percent-of-goal.
  • No emojis.

When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.

Stay under the word budget and off the board book

Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.

Tags on the card (weekly exec flash metrics, closed metrics pack memo, no invented kpis) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.

Fill the card, then run

Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.