Claude prompt for data analysis: Decision Log (Workflow)
Claude · Data Analysis · Workflow
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: operational. Optimize for step order, checkpoints, and handoffs.
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.Looking for a Claude prompt for decision log? Start here — the workflow angle focuses on step order, checkpoints, and handoffs. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The workflow version uses operational language and targets step order, checkpoints, and handoffs.
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
- Separates draft from critique so you can steal the structure later.
- Asks for a self-check pass, which cuts hallucinated details.
- Forces an output contract: headings, examples, and a final version.
- Centers what we chose and why so success is observable.
- Uses operational language that matches how practitioners actually brief work.
How to use it in Claude
Name the success metric aloud: what we chose and why. If the draft cannot pass it, do not polish prose yet. Ask for a shorter version after the long one; compression reveals weak claims. Queries, insights, charts, and decision memos. Keep that context in the thread when you iterate. Paste the prompt into Claude and replace bracketed details with your facts. When ops review output, they should see step order, checkpoints, and handoffs without hunting for it.
Have Claude list assumptions about data analysis before drafting. Delete any you cannot defend. 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 Workflow 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-workflow when step order, checkpoints, and handoffs 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.
- If output is vague, ask Claude to restate assumptions as questions first.
- 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 Workflow prompt but editing it into a vague one-liner.
Expert notes
Anthropic users working on decision log in data analysis should treat "revisit date" as non-negotiable. Queries, insights, charts, and decision memos. When ops run the Workflow variant, they usually care about step order, checkpoints, and handoffs more than length.
If text output feels generic, re-paste revisit date as the first follow-up message — do not rewrite the whole prompt.
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
- The Workflow variant is for step order, checkpoints, and handoffs.
- If text output drifts, re-anchor with revisit date.
- Claude improves when you paste a real snippet or reference still.
- Keep revisit date visible in the prompt, not only in your head.
- Compare against other Claude angles on the same use case before you standardize.
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 workflow version stresses step order, checkpoints, and handoffs 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 workflow angle for decision log?
- Different angles solve different failures. Workflow helps when ops need step order, checkpoints, and handoffs. 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.