CLIENT FILE NAMING - MANUAL CONVENTION

A suggested convention to adapt, not an automatic Droplana feature.

[Client]_[Document]_[Period-or-date]_[Revision].[extension]

FICTIONAL EXAMPLES
MapleVine_BankStatement_2026-08.pdf
MapleVine_ReviewReport_2026-09-20_v01.pdf
MapleVine_ReviewReport_2026-09-24_v02.pdf

BEFORE A HANDOFF
[ ] Use a document name the client recognises.
[ ] Include the period when it matters.
[ ] Give each revision a clear number or date.
[ ] Tell the client which exact file to use.
[ ] Explain the change in a comment on the relevant file.
[ ] Keep or delete older files according to the agreed retention policy.

Do not rely on 'final', 'final2' or an approval marker to choose a version.
Uploading a revised file creates another file; it does not overwrite the
original. Droplana does not compare revisions or automatically supersede
files. Approved, Rejected and unset are the available file statuses;
either side can change or clear the marker.

A filename is an organisational aid, not an access boundary. One client's
portal can contain several engagements; it is not a permissioned project
folder system.

Template source: https://droplana.com/instructions