Claude prompt for data analysis: Decision Log (Starter)
Claude · Data Analysis · Starter
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: plain and encouraging. Optimize for first successful run with safe defaults.
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.This Claude data analysis decision log prompt helps you what we chose and why without rewriting instructions from scratch each time. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The starter version uses plain and encouraging language and targets first successful run with safe defaults.
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
- Forces an output contract: headings, examples, and a final version.
- Separates draft from critique so you can steal the structure later.
- Asks for a self-check pass, which cuts hallucinated details.
- The starter angle adds first successful run with safe defaults without extra fluff.
- Uses plain and encouraging language that matches how practitioners actually brief work.
How to use it in Claude
This Starter path is for ops who care about what we chose and why. If the first answer is vague, reply with the constraint again: revisit date. Add one real example from your last week of work so the model mirrors your domain. When ops review output, they should see first successful run with safe defaults without hunting for it. For data analysis work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt.
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 Starter 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-starter when first successful run with safe defaults 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 Starter prompt but editing it into a vague one-liner.
Expert notes
Slug decision-log-starter: a analysts and operators-oriented data analysis brief. Queries, insights, charts, and decision memos. Pair it with one real asset from your portfolio before the second run.
Refresh quarterly: Claude models change. Keep constraints; update examples. Mark the page stale if revisit date no longer matches policy.
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
- Ship a draft, then tighten. Do not chase a perfect first token.
- The Starter variant is for first successful run with safe defaults.
- ops should recognize themselves in the first paragraph.
- Document what changed when you customized slug decision-log-starter.
- 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 starter version stresses first successful run with safe defaults 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 starter angle for decision log?
- Different angles solve different failures. Starter helps when ops need first successful run with safe defaults. 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.