7.2. Transforming Existing Documents
💡 First Principle: Transforming an existing document is fundamentally different from creating a new one. You are giving Copilot a source to work from — which means the output should be anchored to that source, not generated from general training. This distinction changes the review standard you should apply. When creating from scratch, fabrication risk is obvious — you know Copilot had nothing to ground from. When transforming an existing document, users often lower their guard because a source was provided. That is the more dangerous scenario: Copilot can omit critical details, misrepresent quantitative data, or reframe conclusions during transformation. The source provides grounding; it does not guarantee accuracy. Human review is non-negotiable either way.
Document transformation covers a family of related operations: rewriting, reformatting, restructuring, converting, and adapting existing content for a new purpose or audience.
Common document transformation operations:
| Operation | What Copilot Does | Example Use Case |
|---|---|---|
| Rewrite for tone | Adjusts language style while preserving meaning | Convert a technical specification into plain language for stakeholders |
| Reformat structure | Reorganizes content into a different layout | Convert a narrative report into a bullet-point executive brief |
| Expand content | Adds depth, examples, or supporting detail to existing text | Flesh out a bulleted outline into full paragraphs |
| Condense content | Reduces a long document to its essential points | Compress a 20-page report to a 2-page summary |
| Convert format | Adapts content for a different document type | Turn a Word document into a PowerPoint presentation |
| Translate tone for audience | Adapts the same content for a different reader | Make a technical document accessible to a non-technical audience |
Generating a document from an existing document is a specific and important transformation: you provide an existing document as the source, and ask Copilot to produce a different document based on it. A key example is the PowerPoint use case — you can point Copilot to a Word document (a report, a proposal, a research summary) and ask it to create a presentation from it.
How this works in PowerPoint:
- Open PowerPoint and start a new presentation
- Select "Create from file" in the Copilot panel
- Reference your source Word document
- Copilot generates slides that reflect the structure and content of the source document
- Review, edit, and add visual elements as needed
⚠️ Exam Trap: When Copilot "generates a document from an existing document," it is not copying and reformatting the source — it is using AI to produce new content grounded in that source. The output will be different from the input: restructured, summarized, or rewritten. Do not assume the transformation preserves every detail of the original; always review for completeness and accuracy.
Reflection Question: A consultant has a 40-page technical research report and needs to present key findings to a client in 10 slides. Describe the Copilot workflow that would accomplish this most efficiently.
