Reference organization
How to organize reference PDFs and share separate copies safely
A reference library becomes difficult to use when filenames stop explaining what a file is, which version it represents, and why someone received it. You do not need a complicated naming system to improve that situation. You need a few consistent decisions about source identity, working copies, and handoff. This guide covers practical document handling, not a guarantee of confidentiality or a replacement for your organization’s information policies.
1. Build folders around a recognizable task
Start with the project or deliverable name, then separate source material from review work and outgoing copies. Use labels a colleague can understand without asking you. A small project might need only three folders: Sources, Working review, and Handoff. A larger project may need a separate supplement folder or a dated review-round folder.
Fictitious example for organization practice: the “Harbor education deck” folder contains “Sources,” “Working review — round 1,” and “Handoff — 2026-09-05.” These names describe a filing convention, not automatic workflow states. A file placed in Handoff has not thereby been medically approved, and a folder called Sources does not make its contents an authoritative reference list.
2. Give each PDF a name that distinguishes its role
Choose a short pattern and apply it consistently. Include a recognizable source identifier, a document type such as main article or supplement, and a revision marker for working files. Avoid long chains of “final,” “new,” and initials with no explanation. Keep sensitive personal or client information out of filenames when your policy requires it.
For an entirely invented document, a name such as “REF-014_Harbor-study_supplement_working-r01.pdf” distinguishes identity, document type, and working revision. Keep the full bibliographic details in your reference list or a separate index. A filename is a navigation aid, not a substitute for checking publication details inside the document.
3. Separate original sources from working copies
Before annotating, decide where an unchanged source copy belongs under your team’s policy. Make a working copy for marks and notes, and name it accordingly. Do not overwrite your only source copy merely to make the folder look tidy. Where a corrected publication or replacement PDF arrives, identify the new source version explicitly.
In Easy Annotation, Make a copy lets you choose a destination while preserving the original item. Organize moves an item to another folder; it is not a backup operation. When rearranging files, check the folder breadcrumb first and then verify the destination. Use the item’s actions menu if drag-and-drop is inconvenient or you are navigating by keyboard.
4. Prepare the copy before inviting a recipient
Choose the exact file or folder you intend to send. Remove unrelated material from the handoff selection, not from your underlying evidence record. If sharing a folder, inspect its contents and subfolders rather than relying on the folder name. Confirm that you are permitted to distribute the source material and any annotations to the intended recipient.
A separate, clearly named handoff copy can make the boundary easier to explain. Keep that copy stable while the invitation is outstanding: the recipient receives a copy when accepting, so do not assume the invitation freezes the file at the moment you send it. For a specific revision, prepare it first and avoid continuing edits to that handoff item.
5. Understand what separate-copy sharing does
Easy Annotation’s Share a copy action emails an invitation to another registered account. When the intended recipient accepts, they receive a separate copy; they do not gain edit access to your original. Verify the account email address before sending. If entering several addresses, separate them with commas and check the confirmation for any unregistered recipients who were not sent an invitation.
Do not treat separate copies as a live shared document. Later edits to your original are not a promise of updates in the recipient’s copy. Likewise, a reviewer’s changes should not be assumed to appear in yours. Agree how revised material will be returned, which person will reconcile it, and which revision everyone should use for the next round.
6. Verify the handoff rather than assuming delivery
Send a short accompanying message with the project, revision, purpose, and requested next action. Ask the recipient to confirm they can access the expected material. An invitation being sent is not the same as the recipient accepting it or completing a review. Avoid putting confidential excerpts into an email just to explain where to look.
If your process uses a downloaded PDF or ZIP instead, inspect the downloaded contents before passing them on through an authorized channel. Download ZIP includes files currently in the chosen folder and its subfolders, so check for unrelated material. Do not assume deleting your workspace copy recalls a downloaded file or a separate copy someone has already received.
7. Close a review round without losing context
Keep a compact record of the revision shared and the questions still open. Reconcile returned comments into a named next revision rather than silently replacing the previous handoff. Before deleting anything, follow your retention policy and check whether a permitted backup is needed. Deletion in Easy Annotation cannot be undone; deleting a folder also deletes the files currently inside it.
- Correct source, revision, and destination confirmed.
- Distribution permission and intended recipients checked.
- Handoff copy inspected and kept stable for acceptance.
- Return path and responsibility for reconciliation agreed.
The takeaway
Clear names and explicit handoffs make separate copies understandable. Treat sending, acceptance, review, and reconciliation as distinct steps, and never rely on a filename as proof of approval or access control.