Claude as a Writing and Drafting Assistant Log in and enroll to track lesson completion. By the end of this lesson, students should be able to: You do not need polished input to get good output. One of the most valuable drafting workflows is providing Claude with rough, unorganized input and asking it to produce structured, professional output. This is not asking Claude to invent content – it is asking it to organize, connect, and write in a professional register from the substance you provide. This works especially well when you have: The transformation prompt structure. The key instruction pattern for transformation tasks: Here is my raw content: [paste your notes/bullets/fragments]. The "do not add new content" instruction is critical. Without it, Claude may embellish, add examples, or fill gaps with plausible-sounding content that was never in your original material – which requires you to re-verify everything before using the output. Expanding an outline into prose. If you have a strong outline but struggle to write the full prose, give Claude the outline and ask it to draft section by section. Work through the outline in turns, reviewing each section before asking Claude to proceed to the next. This is faster than asking for the whole document at once and gives you more control over the output. Reorganizing disorganized content. Sometimes you have the right content but in the wrong order. Give Claude your content and ask it to reorganize it: "Here is the content for this report. Reorganize it so it flows from context -> finding -> recommendation -> next steps. Keep all the content – only change the order and write transition sentences between sections." Condensing and summarizing your own writing. Claude can compress your existing writing without losing key points: "Here is my 800-word draft. Condense it to 300 words without losing any of these key points: [list them]. Keep my voice." This is faster and more precise than condensing it yourself, and having Claude work from your original material means the compression is accurate to your intent. A consultant has rough notes from a client discovery session and needs to produce a written summary. Raw notes input: Client meeting notes – ABC Corp – June 2026 Transformation prompt: Transform these raw discovery meeting notes into a professional client meeting summary for internal use. Output: a clean, organized, professional summary the team can act on – from notes that would have taken significant time to write up manually. When transforming rough notes that include your own commentary alongside facts, label them so Claude knows which is which: "FACT: [specific data point]" vs. "MY INTERPRETATION: [your analysis]." This prevents Claude from treating your interpretation as a fact in the output, which can create problems in documents that will be shared externally or used as a factual record. When transforming notes from client meetings, personnel discussions, patient encounters, or legal matters into documents, review the output carefully for accuracy before distribution. Claude may restructure content in ways that subtly change meaning, emphasize the wrong elements, or drop nuance that was implicit in your shorthand. The transformation should make your content clearer, not interpret it. Take a set of meeting notes, a bulleted brainstorm, or a rough draft from your own work. Give Claude the raw material with the transformation prompt pattern from this lesson. Ask Claude not to add new content. Review the output – did it add anything you did not provide? Did it lose anything important? Note what instructions you would refine for next time. You should be able to submit rough, unorganized content to Claude and get back a structured, professional document – while maintaining control over the content by telling Claude not to add material you did not provide. Log in and enroll to take this lesson quiz.
Lesson 2: Transforming Rough Ideas into Structured Content
Lesson Objectives
Lesson Content
Please transform this into [document type] for [audience].
Keep all the substance I provided. Do not add new content, examples, or claims I have not included.
Organize it as [format].
Tone: [tone].Practical Example
– 3 main pain points: slow invoicing (30+ days), customer service tickets unresolved avg 9 days, sales team lacks visibility into customer history
– Tech stack: Salesforce, QuickBooks, custom internal ticket system, not integrated
– Priority: fix invoicing first, then customer service, then sales visibility
– Timeline: 6 months, budget ~$150k
– Key stakeholder: Jenna (CFO), Marcus (Head of IT), final approval CFO
– Next steps: we send proposal by July 10, they review by July 20
Audience: our consulting firm's project team who will read this before building the proposal.
Keep all the substance I provided. Do not add information I have not included.
Format: three sections – Pain Points, Current State, Next Steps. Include a one-line stakeholder note.
Tone: professional, factual.Lesser-Known Tip
Safety Notes
Practice Task
Completion Check
Lesson Quiz