> ## Documentation Index > Fetch the complete documentation index at: https://docs.gradial.com/llms.txt > Use this file to discover all available pages before exploring further. # Make & Edit Office Documents > Use Gradial to create and edit Word, Excel and PowerPoint files — campaign briefs, copy docs, trackers, QA analyses and readout decks — directly from your content workflows. ## Why This Matters A surprising share of marketing work isn't content in a CMS — it's the documents around it. The brief that kicks off a campaign. The copy doc legal marks up. The spreadsheet tracking 200 pages through review. The QA summary someone assembles by hand before a launch readout. The deck that goes to the leadership meeting. These artifacts get built manually, usually by the person with the least time, and they go stale the moment the underlying work moves on. Worse, they're the interface to everyone outside the content team — legal, brand, leadership — so when they're out of date, decisions get made on old information. Gradial produces these documents as part of the work itself, populated from what actually happened rather than from someone's notes. *** Gradial can create and edit Microsoft Office files as part of your content workflows — **Word** documents, **Excel** workbooks and **PowerPoint** decks. Ask Grady to build a campaign brief, produce a copy document from a live page, generate a formatted QA analysis, assemble a tracker, or turn a set of findings into a readout deck. Gradial can also **read** these files. Attach a brief, a copy deck, a spreadsheet of changes or an existing presentation, and Grady works from its contents — which is usually the fastest way to start a piece of work. *** ## What You Can Create Generate a structured brief from a prompt, a set of pages, or an existing strategy document. Includes audiences, messaging pillars, channel breakdown, and timelines. Pull copy from live CMS pages into a formatted Word document — useful for legal review, translation handoff, or stakeholder sign-off. Produce a custom QA report as a formatted document, summarizing findings, issues, and recommended fixes for sharing outside the platform. Turn campaign results, a QA or accessibility summary, a CX Optimizer report or GEO findings into a PowerPoint deck — built from your own template so it arrives on-brand, with speaker notes where they help. Any tabular or structured content — status trackers, campaign matrices, approval checklists, per-page change lists — assembled into an Excel workbook, ready to filter and sort. Anything else you'd otherwise put together by hand, in whichever of the three formats suits the audience. ### Working from your own template For decks and documents that represent the company, point Gradial at an existing file — your standard deck template, a previous quarter's readout, a brief in your house format. Gradial builds the new one to match it, so layouts, fonts and brand treatment carry over rather than being approximated. *** ## How It Works Office document creation works through Gradial Chat or as part of a larger workflow. Describe what you need and Gradial produces the document: ``` "Create a campaign brief for our Q3 product launch targeting enterprise buyers. Include messaging pillars, audience segments, and a channel breakdown." ``` ``` "Pull the copy from [page URL] into a Word document formatted for legal review." ``` ``` "Build an Excel tracker for this batch of content updates with columns for page URL, status, assignee, and go-live date." ``` ``` "Turn the accessibility report for this launch into a deck for Monday's review. Use the attached template. One slide per severity level, and a summary slide up front with the counts." ``` ``` "Read the attached Q2 readout deck and build the Q3 version using the same structure, with this quarter's numbers." ``` Gradial returns the completed file attached to the task, ready to download. Decks and documents can also be previewed in Gradial before anyone downloads them. *** ## Common Use Cases **Translation handoff.** Extract copy from live pages into a clean Word document formatted for your translation vendor — no manual copy-paste from the CMS. **Legal and compliance review.** Generate a Word document containing all regulated copy across a set of pages for legal sign-off before a campaign launches. **Campaign matrix trackers.** Produce an Excel file tracking every asset, page, and deliverable across a campaign — auto-populated from the task data Gradial already has. **Stakeholder briefings.** Assemble a structured brief or summary document from a strategy doc, a set of Gradial findings, or a CX Optimizer report. **Leadership readouts and QBRs.** Turn a quarter's activity, a launch retrospective, or a set of QA, accessibility and GEO findings into a deck on your own template — so the slide build stops being the reason the readout is late. **Working from an inbound deck.** A stakeholder sends a deck with the campaign concept in it. Attach it and ask Grady to work from it directly, rather than retyping the relevant slides into a brief. *** *Files created by Gradial can be attached to tasks, shared externally, or fed back into Gradial as source material for future work.* *** ## Who this is for | Role | What Gradial handles | | :- | :- | | **Campaign Manager** | Briefs and status trackers generated from the work itself, not maintained by hand | | **Content Strategist / Copywriter** | Copy docs produced from live pages, so review happens on what's actually published | | **Legal / Compliance Reviewer** | A document to mark up, in the format you already review in | | **Marketing Leadership** | Readout decks and summaries assembled from real activity rather than from someone's recollection | | **Marketing Ops** | Per-page and per-asset trackers as spreadsheets, ready to filter and sort | | **Enablement / Comms** | Briefing and training decks built on the house template, from what actually shipped | ### How this maps to your function Reviewers outside the content team don't want CMS access — they want a document. Gradial produces a copy doc from the live page, so what legal marks up is what's published, and the changes come back into the same workflow instead of into an email thread. See [Regulated Industries & Compliance Workflows](/docs/governance/regulatory-compliance). Quarterly readouts and launch retrospectives get assembled by hand from several systems, which is why they're late and approximate. When the underlying record is the work itself, the document — or the deck — is a byproduct rather than a project. Point Gradial at last quarter's version and it will build this one to match. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.