Recommendation (short): Use a two-stage pipeline — Claude for long-context extraction and precise source mapping, then ChatGPT for outline-driven drafting, brand-voice polishing, and iterative edits. This splits heavy document parsing from creative/tonal work and reduces hallucination risk.

Task split (high level)
- Claude: ingest full 50–100 page report, chunk if needed, extract fact-level snippets with exact quotes, page numbers, data tables, and create a structured evidence map (claim → source). Produce a concise bulleted summary and 6–8 potential article angles.
- Human reviewer: quick pass to prioritize angles and approve the evidence map.
- ChatGPT: generate outlines, write 1,800–2,200 word draft in brand voice, then perform edits (clarity, transitions, CTA). Use iterative prompts for rounds (draft → refine → final read).

Prompts (copy/paste-ready)
- Claude (ingest & extract): “You will read the attached report (50–100 pages). Produce: 1) a 200–350 word executive summary; 2) a list of all factual claims with exact quote/snippet, page number, and confidence (High/Med/Low); 3) a table of key data points with units and source pages; 4) 6 article angles (1–2 sentences each). Output JSON-like fields.”
- ChatGPT (outline + draft): “Using the approved evidence map, create a 10–12 point outline for a 1,900-word article aimed at [audience]. Include where each claim should cite the report (page numbers). Then write the article in [brand voice descriptors: e.g., authoritative, approachable, 2nd-person sparing], integrate citations inline (e.g., “(Report, p. 23)”), and keep length 1,800–2,200 words.”
- ChatGPT (fact-check pass): “For each paragraph, list the claims and the source page in the evidence map. Flag any claim not traceable to a direct quote/data.”

Verification steps (must-do)
1) Source-to-claim audit: for every factual claim in draft, confirm snippet and page number from Claude’s evidence map.
2) Quote vetting: compare any quoted text against original PDF to ensure fidelity (use exact-match tool or extract in Claude).
3) Numeric/date consistency: verify numbers and units against original table extracts. 4) Editorial pass: one human editor reviews tone and flow.

Decision criteria (when to use which tool)
- Use Claude when reports exceed ~20 pages, contain many tables/appendices, or you need verbatim quotes and a high-fidelity evidence map. Better when you have time to build structured outputs.
- Use ChatGPT for fast drafting, tone control, and rapid iterative edits. Better when you want compact back-and-forth changes.

Best-for / Avoid-if
- Best-for: teams that need reproducible, auditable articles with exact citations and a clear audit trail. Works well for 1–3 writers + 1 editor.
- Avoid-if: you only need quick summaries without citations (skip Claude overhead), or you lack budget/time for two-tool workflow.

Practical checklist (day-of)
1) Upload report to Claude, run extraction prompt. 2) Approve evidence map. 3) Ask Claude for 6 angles; pick one. 4) Send evidence map + angle to ChatGPT with brand-voice prompt and outline request. 5) Produce draft, run ChatGPT fact-check pass. 6) Human audit vs source PDFs (spot-check 10–20 claims). 7) Final edits and publish.

Notes on budget & team: Claude steps cost more compute/time but save downstream verification. If budget is tight, sample-extract key sections rather than full-report parsing.

If you want, I can draft specific prompts tailored to your brand voice and a short evidence-map JSON schema to paste into Claude.

Compare Claude and ChatGPT