The prompt
Score 10 of 10, Excellent
Use it when A board or committee pack is going out, and members need one page telling them what each paper is and what they are asked to do with it.
- {{meeting}}
- {{board}}
- {{paper_summaries}}
- {{meeting_details}}
- {{carried_over}}
- {{sender}}
- {{house_rules}}
Full prompt and why it works
Prompt
Write the cover memo for the {{meeting}} pack, from the paper summaries below, for {{board}} to read before the meeting. Members often read the cover memo first and some read little else, so it has to tell them what each paper is, what they are being asked to do with it and where to look closely, so that the meeting spends its time on decisions rather than on finding out what is in the pack. The papers in the pack, each with its title, sponsor and a summary or the paper's own executive summary: """ {{paper_summaries}} """ Meeting date, time and place or link: {{meeting_details}} Matters carried over from the last meeting: {{carried_over}} Who the memo is from: {{sender}} House format or governance rules for papers: {{house_rules}} Structure the memo like this: 1. Two or three sentences on the meeting overall: the main decisions it is asked to make and anything time-critical. 2. A table with one row per paper, in agenda order, with the columns: Item, Paper, Sponsor, Action requested (for approval, for decision, for discussion or for noting), The point in one line, Pages. 3. Under the table, for each paper marked for approval or decision only: the resolution or decision sought, worded as the paper words it, and the main risk or trade-off the paper identifies, in two sentences at most. 4. Open questions: points the summaries leave unresolved that members may want to raise, each tied to its paper. 5. Late papers or papers to follow, with the date each is expected. Keep the memo to one page, about 400 words outside the table. The tone should be neutral and exact: the memo describes the papers, it does not argue for them. For example, a row: "4 | Annual budget | Finance director | For approval | Sets next year's budget with a [x]% rise in staff costs | 12 to 19". That example shows the form only; use the real papers. Do not state a paper's recommendation more strongly than the paper does, and do not give your own view on whether the board should approve it. Do not invent page numbers, resolutions or risks. If a summary does not say what action is requested, write "Action: [CHECK WITH SPONSOR]" rather than choosing one. If a paper refers to an appendix or another paper that is not in the list, flag it under open questions.
Variables
- {{meeting}}
- Which meeting, for example "March board meeting" or "audit committee".
- {{board}}
- Who reads the pack, for example "the trustees" or "members of the finance committee".
- {{paper_summaries}}
- Each paper's title, sponsor, page range if known, and its summary or executive summary.
- {{meeting_details}}
- Date, time and place or video link.
- {{carried_over}}
- Actions or matters carried over from the last meeting, or "none".
- {{sender}}
- Who the memo comes from, for example "the company secretary".
- {{house_rules}}
- Any rules for papers, for example "every paper states the action requested", or "none".
Why it works
- Who it's for. Some members read only the cover memo, so it tells each of them what every paper asks of them and where the real decisions are.
- Format. A table of papers with the action requested for each, then the exact resolutions sought, mirrors how a well-run board agenda separates noting from deciding.
- If unsure. A paper with no stated action gets a [CHECK WITH SPONSOR] marker instead of an action chosen by the model.