Uploading “price-list-final-2.pdf” beside “price-list-final.pdf” leaves customers and staff guessing which link is current. When the same shared PDF is meant to be updated, Drive’s file-version controls provide a more deliberate route than accumulating similarly named files.

First confirm that the selected item is the actual PDF you intend to maintain. Check its owner, sharing audience and content. Keep a local copy of the outgoing version if it is a business record that needs independent retention.

Replace the intended file

In Drive on a computer, select the PDF and use More, Manage versions, then Upload new version. Choose the replacement deliberately. These controls are for uploaded files such as PDFs and images; Google Docs and Sheets have their own version-history interface.

Before the upload, inspect the new PDF itself. Check the issue date, page count, prices or other changed details. A well-managed file history cannot correct an accidentally exported old document. If another person owns the Drive file, uploading a new version does not make you its owner.

Check both the current result and retention

Afterward, open the original shared link and inspect the changed content. If recipients must rely on it, verify the intended recipient experience too. Record the update date and what changed in a simple release note outside the filename.

Review the older version in Manage versions. Google says older versions can be removed after 30 days or when 100 newer versions exist unless retained with Keep forever. Use the retention control for a required version and download an independent copy when the business needs one.

For example, a workshop could verify that the new two-page information sheet shows the revised collection instructions and that last month’s issued copy remains retrievable. This is a suggested check, not a claim about a completed AEPC document release. Avoid deleting history merely to make the version list look tidy.

References: Google Drive file versions.