A Word file can open in Google Docs without automatically becoming a Google Docs copy. Before editing, decide which file your team intends to use, then check that working version against the Word original. Opening the document confirms access—not that it is approved or ready to move toward a CMS.
This guide covers the upload-and-open steps, how to choose between the Word file and a Docs copy, and what to record before handing the document to another editor.
Choose the working version before opening the file
First, confirm that you have the intended Word document. Note its filename and where the original will remain stored. If there are several versions, ask the sender or document owner which one is authoritative; do not decide based on a filename alone.
Then agree on which version the team will edit:
| Team decision | Working version | What to retain or share |
|---|---|---|
| The Word file remains the agreed source | The uploaded Word file opened in Google Docs | Retain the original in its agreed location and share the link to that file. |
| The team will collaborate in Google Docs | A separate Google Docs copy | Retain the Word original, name the copy clearly, and share the copy as the working version. |
You can open a Word document in Google Docs without first creating a Google Docs copy. Opening and making a copy are distinct choices; neither establishes that the content has been approved. If the task is to add the contents of a Word file to an existing Google Doc, that is a different operation from opening the Word file. Confirm that this is what the team needs before proceeding.
Upload and open the Word document in Google Docs
If the .docx file is on your computer, use Google Drive to put it in the folder agreed for the project:
- Open Google Drive and navigate to the intended folder.
- Choose New and then File upload. Select the
.docxfile from your computer. - After the upload completes, locate the file in that folder. Check its name against the version you expected to receive.
- Open the file with Google Docs. Depending on the available file actions, this may be under an Open with option.
- Check the document title and file type before editing. Confirm that you opened the uploaded Word file, not a similarly named document or an existing copy.
If the file is already in the right Drive folder, start at step three. Interface wording can vary, so verify the file that opens rather than relying only on the menu choice. If the name, folder, or contents do not match the expected source, pause and ask the sender which file to use.
Create a Google Docs copy only if that is the agreed workflow
If the team chose to collaborate in a Google Docs version, create that copy as a separate step after opening the Word file. Use the available copy or conversion option in the document, then verify that a second document exists. Menu labels may vary, so check the result rather than assuming the command produced the file you intended.
Give the copy a name that distinguishes it from the original—for example, Spring Guide — editorial review—and keep the Word file in its agreed location. Record which one is the working version, then share that link with collaborators. Avoid sending both links without explaining their roles: a recipient should not have to guess which file to edit.
If the team agreed to keep editing the Word file, do not create a second version just because the file is open in Google Docs. Keep the original as the working source and make any separate-copy decision explicit with the document owner.
Compare the opened document with the Word original
Before treating the opened file as the working draft, compare it with the Word source. This is an editorial check, not a guarantee that every element transferred unchanged. Review the beginning, middle, and end of the document so that you are not relying on a single opening-page check.
Check elements that could affect the next editor or the eventual publishing source:
- Headings: Compare wording, order, and hierarchy. A heading that looks prominent may not have the same structural level.
- Links: Check that important linked text is present and that each link still points to the intended destination.
- Lists and tables: Compare item order, numbering, rows, columns, and whether the information remains readable.
- Images: Confirm that expected images are present and placed near the relevant text.
- Review notes: If comments or other notes are part of the approval process, confirm they are accounted for before treating review as complete.
For each discrepancy, record what differs and who will resolve it. For example: “The middle-section table has all rows, but its heading is missing; the source owner will confirm the heading before editorial acceptance.” The source owner should resolve questions about intended content or approval. The editor assigned to the working file can handle agreed editorial corrections. Do not silently choose between conflicting versions.
Record the handoff decision and next owner
A document passes this handoff check only when the intended working link and the person responsible for acceptance are recorded, and discrepancies are either resolved or explicitly assigned. If the team cannot identify the authoritative source, or an unresolved difference has no owner, hold the handoff.
A short handoff note can include:
- Original Word file: filename and Drive folder or other agreed location.
- Working version: link and whether it is the Word file or a Google Docs copy.
- Comparison result: what was checked and whether it passed.
- Open issues: each discrepancy, its owner, and the next action—or “none.”
- Acceptance owner: the editor who confirms the document can move to the next stage.
For instance: “Original: Spring-Guide.docx in the client folder. Working version: Spring Guide — editorial review in Drive. Headings, links, lists, tables, and images checked; one table heading is with the source owner. Editorial acceptance is on hold until that heading is confirmed.” This tells the next editor which file to use and what must happen before the handoff is accepted.
A passed document is still a source document, not a WordPress draft or a published page. Once the working version is accepted, continue with the relevant Google Docs publishing handoff guidance for the separate CMS workflow.