How do I keep track of drafts and file versions?

Version confusion usually starts small: two people edit different copies, a file named "final_FINAL2" appears, and suddenly nobody knows which draft has your preceptor's comments. A simple system from day one prevents most of it.

Pick a naming convention and stick to it

A reliable pattern is project, document, date, and version, for example "FluCampaign_Brief_2026-10-14_v3." Putting the date in year-month-day order keeps files sorted correctly. Avoid the word "final" until something truly is, and even then add the date.

Keep one working copy

If your site uses Google Drive, OneDrive, or SharePoint, work in the shared file and rely on its version history rather than emailing attachments back and forth. If you must work offline, clearly mark which copy is current and merge changes the same day.

Handle feedback deliberately

When someone reviews a draft:

• Save the commented version as its own file, such as "_v3_preceptor-comments"
• Make a new version for your revisions with changes accepted
• Note what changed in a line or two, either in your log or a simple change list

This protects the revision record, which is useful evidence of how your work developed, and keeps you from submitting a marked-up file by accident.

Archive, do not delete

Move old drafts into an archive folder until your practicum and final evaluations are complete. You may need to show how a product evolved or recover a section you cut. Version control chaos covers tool options, including basic Git for analysis code.

Respect your site's systems

Store site files where your organization requires, and follow its rules on local copies and personal devices. Your own folders should hold only what you are permitted to keep.