For Learning & Development Managers ·
What you'll accomplish
Your designer sends an outline on Friday afternoon and you have twenty minutes before your next meeting. You want to know which business outcomes have no matching content, and you want to know it before you write a word of feedback. A Claude Project holds the original brief, the business goal and your review checklist, so each new draft gets the same first pass. You still give the feedback. Claude only does the reading.
What you'll need
Check before you paste: Briefs and drafts often name a business unit, a reorganization or a product launch that has not been announced. Replace those with neutral labels ("Business Unit A", "the Q3 launch") and remove employee names. Your company's AI policy and approved tool list decide whether Claude may see this material at all. On a personal free or paid account, check whether chat data may be used to improve the model and whether you can turn that off in your privacy settings.
Put the brief, the business goal and your checklist in separate files or clearly labelled sections. Claude reads them better when each has a plain title.
What you should see: Three short documents on your desktop, none longer than a few pages. Troubleshooting: If your checklist lives only in your head, use the checklist builder prompt below to have Claude draft one from the brief. Then edit it.
What you should see: An empty project page with a knowledge area on the right side. Troubleshooting: The Claude help center notes that Claude does not have access to the name and description you type here. Put anything Claude needs to know into the instructions or the knowledge, not the description.
What you should see: The three files listed under project knowledge. Troubleshooting: Context is not shared between chats in a project unless it sits in the project knowledge. If a fact matters for every review, add it as a file. Do not rely on having said it in an earlier chat.
You are a review assistant for a Learning and Development manager.
Your job is to compare a designer's draft against the project brief and the business goal in the project knowledge.
Always report in this order: (1) business outcomes in the brief with no matching content in the draft, (2) content in the draft that no outcome asks for, (3) items on my review checklist that the draft fails, (4) questions I should ask the designer.
For every finding, quote the exact line from the draft or the brief that supports it.
If the brief does not say something, say "the brief is silent" rather than guessing.
Do not rewrite the draft and do not suggest new course content. I give the feedback to the designer myself.
What you should see: The instructions appear on the project page. Troubleshooting: If Claude starts rewriting the draft, add a line to the instructions repeating that you only want gaps and questions.
What you should see: A four-part answer in the order you set, with quoted lines. Troubleshooting: If the quotes do not match your files, see the verification step below before you send any feedback.
Second-round review:
Here is the revised draft. Compare it with my earlier feedback below.
For each point of feedback, say whether the revision addresses it, partly addresses it or ignores it, and quote the evidence.
[PASTE YOUR EARLIER FEEDBACK]
Checklist builder:
Read the brief in the project knowledge. Draft a review checklist of eight to ten questions that a manager should ask of any draft for this program.
Keep each question answerable with yes, no or a quote.
Feedback conversation prep:
Based on the gaps you found, list the three questions I should ask the designer in our review meeting, ordered by how much they affect the business goal.
Phrase them as questions, not instructions.
Scope-creep check:
List everything in this draft that goes beyond the brief. Do not judge whether it is good. I only want to know what was added.