Skip to content
Interface language: English
Audit / Signal

An AI-generated Office document can contain more than its visible pages

How to review an AI-generated Office document for macros, links and external content.

Article language: English

Illustration: part of a stone column, with a thin line marking a crack.
In this article

“If a warning appears, enable content” should not accompany an AI-generated report as an instruction. The recipient was meant to read a summary; instead, they have been asked to approve an unknown file action. Rather than ask for blind consent, the author should explain what the file contains and why a particular action is needed.

Consider Nuta, a fictional studio preparing an inventory of room equipment. An assistant creates a Word document and an Excel workbook. The pages look ordinary: room names, chair counts and a short comment. Yet the workbook might depend on another workbook, and an image of the room plan might reference an external resource. Looking at visible cells alone does not resolve those dependencies.

We do not assume a file is harmful because AI helped create it. Nor do we treat it as checked because an assistant called it ready. The acceptance question is specific: what material may be handed over, in which application will it be used, and which behaviours belong to the assignment? This is an operational document review. Examining suspicious content or security requires a separate scope and appropriate expertise.

First choose what is being handed over

Nuta needs a one-off summary to read. The recipient must decide which room should receive eight chairs. An automatically refreshed equipment database is unnecessary. A reference to the author's working workbook is a dependency to explain, not an automatic benefit. The author's convenience must be separated from the recipient's needs.

A workbook used by a team each week is a different assignment. Data updates may then be justified, but need an identified source, access rules and an owner for maintenance. “Current numbers” does not say whether they were recorded on Monday or fetched on the next opening. The two files may look identical until the source changes.

For each delivered version, record the full name, format, purpose and intended way to open it. Include an editable document supplied beside an export. “PDF for the manager and the source just in case” means two materials to accept. Reading the first does not automatically approve the second. The guide to accepting a presentation and its source (in Polish) describes a similar separation.

Format narrows some questions. Microsoft says Open XML formats ending in x, such as docx, xlsx and pptx, do not store VBA or XLM macros. Macro-enabled formats are another category. This distinction concerns a properly saved file, not arbitrary content someone has renamed.

Do not reduce the decision to its last letter. The person or tool performing the check should establish the actual format. Renaming document.docm to document.docx is not a macro-removal procedure. Nor is the label “safe” a technical property. If the name and identified format disagree, return the material for clarification before further circulation.

Nuta can request a document without macros, but must still ask about external dependencies and attached content. A no-macro requirement settles one part of the assignment. It must not become “the file has no active features at all” in the report. Such a broad claim would require different evidence.

A clickable link to instructions differs from an image fetched during display. A connection that refreshes data has another role. At acceptance, record not only an address but how it is used: to display content, update a result or support a recipient's deliberate navigation. A list of addresses beginning with https does not explain those differences.

Microsoft's external-content documentation lists images, linked media and data connections in workbooks and presentations. It also describes separate settings for connections and workbook links in Excel. Organisational settings can differ from defaults; knowing a warning's appearance on the author's personal computer is not enough.

In our example, the room list may link to an internal instruction the recipient cannot open. That is an access problem for needed information. If the document tries to fetch a working plan from the author's private folder, it creates an environmental dependency. If the source contains the entire register, the scope of shared data becomes a question. One generic “link does not work” comment blurs these cases.

Nuta's acceptance card states: the room plan is attached as approved material; figures correspond to the register on a specified date; the workbook must not fetch new values after delivery. This is a decision for the example, not a universal Office configuration. Another workflow can allow updates, provided responsibility for the source and recognition of the result are clear.

For the room plan, the author specifies whether the image is inside the delivered file. An external reference instead needs justification. For a one-off summary, a stable approved plan will usually be easier to maintain than a dependency on a working folder. The recipient compares it with the correct room, rather than merely checking that some illustration exists.

For the chair count, ask what remains if the source is unavailable. A blank cell is a visible gap. An unlabelled old number may look current and escape notice. If the workbook is updated, acceptance should cover both cases and show the data date. The trial should reveal whether the recipient can recognise the result's state, not merely confirm the file opens.

Aeneia conceptual photography

If a reference requires access to an internal register, define the minimum information needed. Do not share the author's password or grant access to an entire directory to run one chart. The data owner may prepare an approved extract or appropriate source for that workflow. Accepting a document does not grant permission to connect further resources.

A conversation with Aeneia Audit can start with the input, generated file and actual path to the recipient. Content review, dependency checks and permission to hand over can then be assigned to the appropriate owners. Discuss the possible scope; missing evidence from one check should have a clear owner.

Do not send working files merely to make a document open identically elsewhere. If the attached register contains more than the summary needs, prepare an appropriate extract first. Hidden columns or data invisible in a preview do not settle what is handed over. The article on false confidence in AI anonymisation (in Polish) shares the same underlying question: what actually leaves the company?

A preview is not a trial of every opening method

A document may look correct in a browser and behave differently in a desktop application. Microsoft says Word for the web opens docm documents but does not run their macros. That observation does not mean the file has no macros. It applies to a particular way of using it.

“We checked the preview” therefore needs detail. Which program and version? Was display alone checked, or editing too? Will the recipient download and open the file locally? At Nuta, the manager may only read the summary, while a coordinator later changes the chair count in a desktop application. The first path does not replace acceptance of the second.

The article on opening AI-generated HTML and SVG (in Polish) illustrates the same boundary: “preview” does not describe every environmental restriction. But do not transfer browser recommendations directly to Office. The person responsible for the actual application environment should identify the approved route and limits of the trial.

Microsoft describes default blocking of Internet macros in certain Office applications on Windows. It also distinguishes opening routes, trusted locations and organisational settings. This is not a universal promise of identical behaviour for every application, platform and file copy. Interpret a warning in its actual environment.

Acceptance instructions should not require bypassing a warning. If the document cannot meet its agreed use without additional consent, return the task to the author and application owner. They clarify what was blocked and whether the feature is needed. Changing global settings for one report changes working conditions for other files too.

Finish with a decision about a specific version

A trial should use fictional data and an approved environment. Do not open a suspicious file on company material just to see what happens. In an agreed routine acceptance, collect content-check results, observed behaviour and unchecked elements separately. They must not be merged into one green “OK” field.

Keep the kind of evidence for each result. Format identification can come from an approved tool's report. A figure's accuracy requires comparison with the agreed register. Behaviour observations should identify the application and actions performed. An assistant's “I removed the connections” is a claim of a fix until an appropriate check confirms the new version.

No visible fetching during one opening does not settle every dependency. A resource may not have been needed on that path or may already have been available in the environment. A technical owner should therefore combine a structural check with a suitably prepared observation. The business recipient records the trial's limits and result; they need not improvise network-traffic investigation.

Suppose Nuta receives a corrected workbook with stored values, an attached plan and no automatic fetching of new data. Acceptance includes comparing the numbers, labels and layout again. Removing a dependency might leave an old value or remove a needed description. A changed file behaviour does not automatically confirm agreement with the approved register.

If materials arrive together, checking ZIP contents and extraction (in Polish) answers a different question from accepting a document. Correctly transferred bytes do not approve Office functions. Likewise, the article on CSV text that a spreadsheet may interpret as a formula (in Polish) shows why interpretation must be considered in the recipient's application.

Nuta's final record could say: we deliver the specified document and workbook with a fixed data state; display and agreed editing were accepted in the stated program; an outstanding technical check and its owner were identified. If its result is required for use, the material remains on hold. We do not add approval for every other way of opening it.

The recipient finally has a simple instruction: use this version, by this route, for this task. If an unexpected request to run additional content appears, stop the handover for clarification. A report about eight chairs can do without unexpected permissions.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear