Draft and analyze business content by using AI
Draft, Transform, Summarize, and Move Business Content
CoreChoose the correct content workflow for a new draft, a source-based transformation, a management summary, or a cross-app handoff.
Aligned to the AB-730 skills measured as of July 22, 2026; product behavior verified August 23, 2026.
Why this matters
Business content tasks can sound similar while requiring different evidence and destinations. AB-730 tests whether the user starts from requirements or an existing source, preserves meaning, tailors the output, and reviews the result in the right Microsoft 365 app.
Must Know
- For a new document with no source to transform, prompt with purpose, audience, required content, tone, structure, and desired outcome.
- To generate a document from an existing document, reference the current approved source, specify the new audience and form, preserve decisive facts and caveats, and verify the result against the source.
- A management summary distills the decisions, risks, metrics, assumptions, and next actions leaders need from a source. It is not merely a shorter copy.
- Summary brevity does not excuse unsupported figures or removed caveats. Trace decisive claims to the report and keep material uncertainty visible.
- Move data and insights to the app that supports the next step: analyzed workbook insights to a presentation, structured actions to Excel for tracking, or a reviewed Copilot Page to Word or PowerPoint for a formal deliverable.
- Cross-app movement does not remove the need to verify meaning, owners, dates, calculations, narrative, and formatting after the handoff.
- Use Researcher for a complex sourced report across information; use Analyst for quantitative exploration of data, trends, statistics, outliers, and visual insights.
Compare and Distinguish
- New draft vs source-based document vs management summary: create from requirements vs transform selected source material vs distill the source for decision-makers.
- Transformation vs copying: change audience, structure, or form while preserving meaning vs reproduce content without purposeful adaptation.
- Summary vs proposal: report the source’s essential implications vs invent or recommend a new course of action beyond the source.
- Excel vs PowerPoint vs Word destination: structured analysis and tracking vs presentation narrative vs editable prose document.
- Researcher vs Analyst: multi-source evidence synthesis vs data-heavy analysis.
Scenario examples
- Scenario: Communications needs a first draft of an employee announcement with no source document. Think: prompt for a new Word document with audience, tone, sections, and next actions.
- Scenario: An approved technical plan must become plain-language customer guidance. Think: generate from that plan, preserve commitments and caveats, and verify the transformation.
- Scenario: Executives need decisions, risks, metrics, and owners from a long report. Think: create a management summary grounded in the report and check decisive claims.
- Scenario: A meeting action table must be sorted and tracked. Think: move it to Excel and verify owners, dates, and actions.
Exam traps
- Copilot does not need an existing document to create a new draft, but an existing-source task does need deliberate grounding.
- The newest file is not necessarily the approved file.
- Changing tone or readability must not change commitments, figures, or caveats.
- A management summary is audience- and decision-focused, not just shorter text.
- Cross-app handoff is not permission to paste unverified raw data or recreate content from memory.
Key takeaways
- Identify whether the task starts from requirements, a source document, or a need for decision distillation.
- Preserve grounding and verify every source-based transformation or summary.
- Choose the destination app by the next business action and verify the handoff.
How it works
- The user chooses a source or requirements-only starting point, specifies audience and output constraints, generates a draft, and iterates without losing the governing evidence.
- For a handoff, the reviewed content moves to the destination app and is checked again because formatting, structure, or interpretation can change.
Objects and administrative surfaces
- Copilot in Word — start a draft, draft from referenced content, summarize, and continue editing in the document workflow.
- Copilot in Excel and Analyst — analyze structured data and produce insights that may feed other deliverables.
- Copilot in PowerPoint — turn reviewed content or insights into a presentation workflow.
- Copilot Pages — refine collaborative content before conversion to Word or PowerPoint where supported.
When to use it
- Use requirements-only drafting for net-new content, source-based generation for transformation, and management summary for decision distillation.
- Use Excel for structured data/tracking, PowerPoint for presentation, Word for formal prose, and Pages for collaborative refinement.
Security and governance implications
- Use only authorized source documents and review the sharing permissions of the destination artifact.
- Do not remove material sensitivity, caveats, or attribution while simplifying content.
How to reason about this
- If a draft omits a source requirement, keep the approved source referenced and refine the explicit constraints.
- If a summary contains a questionable figure, trace it to the report rather than asking Copilot to certify its own output.
More detail
- Word can draft from a prompt or referenced content and leaves the output editable. The user remains responsible for checking accuracy, completeness, tone, and fidelity.
- Management-focused summaries should surface decision-relevant evidence without inventing implications. Figures and recommendations must be checked against the actual report.
- Current Copilot Pages documentation supports converting a Page into a Word document or PowerPoint presentation, enabling a collaborative draft to continue in a formal app workflow.
Ready for the quiz?
- What makes a management summary different from a general rewrite?
- How should the user choose among conflicting source versions?
- Which destination fits structured action tracking?
- Why should caveats remain in a short executive brief?
Related objectives
- D3.1.a — Create a new document from a prompt
- D3.1.b — Generate a document from an existing document
- D3.1.c — Generate a management summary based on a document
- D3.1.d — Move data and insights between Microsoft 365 apps