Freeze an Approved Google Doc and Keep an Editable Copy

To freeze an approved Google Doc while keeping a working copy, name the approved version, remove other people’s edit access to the original, and make a separate copy for revisions. Keep the approval message tied to the original document, not the copy.

An approved document needs a separate working file

An approved Google Doc is easiest to protect when the approved text stays in one file and future work happens in another. Google Docs version history can preserve a named point in a file’s history, but naming a version does not stop someone with edit access from changing the current document. A separate copy gives editors a clear place to continue without changing what people were asked to approve.

Use this approach when a proposal, policy, agreement draft, or other document needs a clear handoff. The approved original is the reference. The copy is a draft, even if its text initially matches the original. Choose file names that make those roles obvious, and tell colleagues which file was approved. Do not describe the copy as approved just because it came from approved text.

For a document that only you edit and rarely share, a named version may be enough to help you recover earlier wording. When other people will keep revising or circulating the document, the separate-file approach is safer because its purpose does not depend on everyone interpreting version history correctly.

A named version records the text that received approval

Save a final version of a Google Doc by naming its current version immediately after the approved wording is in place. First, resolve any proposed changes that are part of the approval. Check the title and the content, then ask the approver to confirm which document they approved. In Google Docs, open File, then Version history, and use the option to name the current version. Give it a name that identifies the approval, rather than a vague name such as “final.”

Keep the approval message or decision record outside the document, and make sure it identifies the original file. A named version tells you which text to look for in version history; the decision record tells you who approved it and under what circumstances. Neither replaces the other.

Do this before making the working copy. Otherwise, a later edit to the original could become the version you name by mistake. If someone has already edited the original after approval, find the approved point in version history and confirm its wording with the approver before treating it as the reference. Google’s help for Docs and Drive is the place to check current menu names if your interface looks different.

The editable copy starts from the approved wording

Make the working copy from the approved Google Doc while its current text still matches the approved version. In the original, use File, then Make a copy. Give the new file a name that plainly marks it as working material. Open the copy and check its contents before inviting anyone to edit it. Copy settings and available options can vary, so also check whether comments or suggestions came across and whether they belong in the new draft.

Share the copy with the people doing the revisions. Give them the access they need on that file, rather than keeping them as editors of the approved original. Check the sharing settings on both files separately; do not assume the copy has the same audience as its source or that it is private.

A file copy is useful because revisions to it do not change the original file. The copy is not, however, a record of approval on its own. If your team drafts a client proposal from a form response, treat that generated or revised draft as working material until someone approves its actual wording.

Sharing settings reduce edits to the approved original

To lock an approved Google Doc from routine edits, change collaborators who no longer need to edit the original to Viewer access in its Share settings. Check both the people listed individually and the General access setting. If a broad group or anyone with the link can edit, changing only an individual’s role will not protect the file. Use restricted access or view access where appropriate for your workplace.

The owner can still edit the original, and some workplace or shared drive permissions may be managed outside the file. Google Docs therefore does not turn a named version into an unchangeable master. The practical rule is to limit who can edit the approved file, tell those people not to revise it, and direct all new wording to the copy. If the original must not be altered by anyone with access, ask whoever manages your organisation’s records what controlled storage or retention process applies.

If the original remains shared, check it occasionally or arrange email alerts when a shared Google Doc changes. An alert helps someone notice an unexpected edit; it does not prevent one.

A clear handoff prevents drafts being mistaken for approval

The handoff should identify the approved original, the editable copy, and the place where the approval decision is recorded. In your message to colleagues, say that the original contains the approved wording, the copy is for proposed changes, and changes to the copy need fresh approval before anyone treats them as final. Share each file with the right access and check the links yourself before sending the message.

Keep the links in a place the team already uses, such as the project record or handoff message. Avoid sending an unqualified link described only as “the document.” If someone opens the working copy later, its file name and the handoff should both make its draft status clear. If someone edits the approved original by mistake, stop using its current text as the reference until you compare it with the named approved version and resolve the discrepancy.

For an agreement that needs a signature, approval of the wording and signing are different steps. The guide to sending a Google Docs agreement for signature covers that separate task. Keep the signed record with the agreement process rather than treating an editable working copy as evidence of a signature.

Sources consulted

• Google Docs Editors Help (support.google.com)
• Google Drive Help (support.google.com)

Start a free course