Where is the underlying information stored?
Microsoft explains that a linked object retains its data in the source file, with the Word document storing a location and representation. An embedded Excel object becomes part of the Word file and does not automatically reflect later changes to the original workbook.
Returnables Agency is independent and is not affiliated with Microsoft. Confirm the actual software, recipient environment and submission instructions. This guide does not recommend enabling external content, bypassing a security warning or sending additional attachments that the tender does not permit.
Sources: Microsoft: Microsoft Support: Linked objects and embedded objects, checked 20 October 2026
Which evidence should the issue register retain?
Identify each object and its intended role. A calculation preview, a complete required workbook and a source-linked chart are different deliverables even when they look similar on a page.
| Review field | Evidence | Issue decision |
|---|---|---|
| Object location | Word section and object reference | What must the reader receive? |
| Storage type | Linked, embedded or ordinary content | Where is the underlying information? |
| Source revision | Approved workbook reference | Is the displayed value current? |
| Update state | Actual reviewed representation | Was a later change incorporated? |
| Recipient test | Permitted environment and opening check | Can the required evidence be read? |
| Release approval | Accepted package and exceptions | Are file and format rules met? |
How can two identical previews behave differently?
Illustrative example. Two fictional tender documents display the same reviewed equipment summary. File A links to a workbook on the author's local drive; File B contains an embedded copy. The recipient can see a representation in each, but that appearance alone does not establish access to the linked source or prove that the embedded copy is the approved current revision.
The reviewer records the storage type, source revision and required recipient action. An embedded copy may still need inspection for unintended confidential content. A linked object may contain an unsuitable file path. Resolve the actual issue package without assuming that embedding is always safer or linking always wrong.
What should the final recipient check cover?
Test the final permitted files through the agreed review process, including the visible output and any required underlying evidence. Do not change trust settings to make a failing file appear acceptable. Record inaccessible or stale content as an open action for the response owner.
Keep a controlled source and the exact approved issue package. If the buyer requires a PDF rather than an editable object, inspect that final PDF against the response requirement; do not assume that the native object or every workbook tab travels with it.
Common questions
What else should the bid team know?
Does a visible preview prove that a linked workbook is included?
No. Check where the source is stored and what the recipient can access.
Does an embedded copy update when the original workbook changes?
Microsoft explains that it does not automatically reflect those changes.
Should security warnings be bypassed for the test?
No. Use the approved document-handling process.