Claude prompt for data analysis: Decision Log (Advanced)
Claude · Data Analysis · Advanced
You are a exacting editor using Claude for data analysis, specifically decision log.
Job: what we chose and why.
Audience: ops. Constraint: revisit date.
Working style: precise and demanding. Optimize for constraints, evaluation, and edge cases.
Process:
1. Restate the brief in one sentence and list missing facts as questions.
2. Draft the artifact.
3. Stress-test it against the constraint.
4. Return a final version plus 3 numbered improvements.
Output contract: use headings, short paragraphs, and concrete examples. No filler. No invented statistics.
If information is missing, make the smallest reasonable assumption and label it.Use this Claude data analysis template when ops need decision log with the rule: revisit date. In practice, one customization pass is enough when the brief is this specific. The advanced version uses precise and demanding language and targets constraints, evaluation, and edge cases.
When to use this prompt
For Anthropic models, data analysis prompts fail when they mix strategy and execution. This decision log brief separates the job so you can iterate once, not ten times. Swap only nouns when adapting — keep the process intact.
Why this prompt works
- Centers what we chose and why so success is observable.
- Uses precise and demanding language that matches how practitioners actually brief work.
- Forces an output contract: headings, examples, and a final version.
- Separates draft from critique so you can steal the structure later.
- Keeps data analysis vocabulary specific instead of buzzwords.
How to use it in Claude
For data analysis work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt. Ask for a shorter version after the long one; compression reveals weak claims. Redact client names; keep structure. Slug decision-log-advanced is your canonical URL for this brief. When ops review output, they should see constraints, evaluation, and edge cases without hunting for it. Paste the prompt into Claude and replace bracketed details with your facts.
Swap the audience once. If the decision log piece still works, the core is solid. For decision log in data analysis, the failure mode is usually no example. This prompt blocks that by design — especially "revisit date". Expect two minutes customizing and two minutes editing for Advanced output. Anthropic models still need your facts for decision log; they cannot invent metrics or brand rules. analysts and operators teams bookmark slug decision-log-advanced when constraints, evaluation, and edge cases matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (ops, offer, timeline).
- Confirm the constraint is still visible: revisit date.
- For data analysis work, paste a rubric and ask for a self-score.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with Decision Log, 3 short sections, bullet list of recommendations, closing line that states revisit date. Facts you supply appear; nothing invented.
Common mistakes
- Accepting the first draft without checking what we chose and why.
- Asking for decision log plus three other jobs in one message.
- Using the Advanced prompt but editing it into a vague one-liner.
Expert notes
Practitioners choose Advanced when decision log needs constraints, evaluation, and edge cases. Claude from Anthropic still needs your facts — especially for revisit date.
For data analysis, compare this Advanced prompt against the Quick Start and Expert angles on the same use case. Keep the structure that scores higher on what we chose and why.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a decision log piece. |
| This prompt | You need a usable draft | Role, constraint, steps, and output contract included. |
| Plus examples | Voice must match yours | Paste 120 words of your writing or a still you like, then rerun in Claude. |
Key takeaways
- Data Analysis work needs queries, insights, charts, and decision memos.
- ops should recognize themselves in the first paragraph.
- If text output drifts, re-anchor with revisit date.
- Keep revisit date visible in the prompt, not only in your head.
- Document what changed when you customized slug decision-log-advanced.
FAQ
- What is a Claude prompt for decision log?
- It is a structured brief that tells Claude how to produce data analysis output for ops. This advanced version stresses constraints, evaluation, and edge cases and keeps "revisit date" in the instructions.
- How do I customize this Claude data analysis prompt?
- Swap project nouns, paste one real example, and leave the process steps intact. The constraint "revisit date" should stay unless your brief truly changed.
- Why use the advanced angle for decision log?
- Different angles solve different failures. Advanced helps when ops need constraints, evaluation, and edge cases. It is not longer for its own sake — each line has a job.
- Is this Claude prompt updated for 2026?
- Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Anthropic models. Always verify facts before client delivery.