What should happen to your unfinished creative projects?

Explain the project, not just the folder

An unfinished novel, a collection of recordings or years of research can mean a great deal to its creator. To someone else, the same work may look like a confusing set of folders. A short project guide can explain what you were making, which version matters and what you would like someone to understand if you could no longer explain it yourself.

This is different from recording the story behind a finished keepsake. An unfinished project may have competing drafts, missing pieces and material that was never intended for an audience. Start with one project rather than trying to catalogue everything you have ever made.

Give the next reader a starting point

Imagine a family member opening a folder containing three manuscripts labelled final, final-new and final-really. A note identifying the current working draft would save them from guessing. Record the project's name, its purpose, the date of your guide and the exact file or document a reader should open first.

Describe the status in plain language: a rough outline, an edited draft, a demonstration recording or a collection still being sorted. If an unusual application is needed, name it and explain which files depend on it. Where practical, keep a readable reference copy alongside the working material, and check that it opens.

A practical checklist

• Name the project and explain it in two or three sentences.
• Identify the current version and distinguish it from experiments or duplicates.
• List supporting notes, reference material and any important physical originals.
• Explain specialist file formats without including account passwords or access codes.
• Identify a person who understands the work, after checking they are comfortable being named.

Separate preservation from sharing

Keeping a project is not the same as finishing it or publishing it. Write down those wishes separately. You might want a draft preserved for family, a recording kept private or someone consulted before any public sharing. Avoid leaving a vague instruction such as “do something with this” when you have a more specific preference.

A project can also contain other people's words, images, performances or private information. Do not assume that possessing those files settles who may use them. If ownership, permissions or the legal effect of your wishes matters, seek qualified advice and make appropriate formal arrangements. A project guide is context, not a substitute for those arrangements.

Keep private material out of the handover by default

Read through the material before deciding what someone should receive. Research notes may contain interview details; a manuscript may include personal comments; an archive may contain correspondence that belongs in a more restricted collection. Select deliberately rather than handing over a whole folder because it is convenient.

Keep a simple inventory of what you chose to include and what remains elsewhere. Do not put passwords, recovery codes or payment details into the project guide. For anything that another person needs to work on with you now, arrange suitable access directly rather than relying on a future conditional release.

Use Vaultence for a selected document handover

You can upload a project guide and selected supporting documents to a vault, then configure the intended recipients and release rules separately. Uploading a guide alone does not establish who should receive it. Check that the documents selected in the relevant rule match the handover you intend.

Do not assume that a link in the guide gives a recipient access to an external drive or creative platform. Any access arrangements for those services need separate attention. Vaultence's conditional document release is not immediate collaboration, emergency access or permission to publish someone else's work.

Test one small handover and keep it current

Ask a trusted person to read a non-sensitive version of the guide and explain which file they would open first. Can they tell what is unfinished and which material should remain private? You can test those instructions without triggering a real document release.

Review the guide after a major revision, a change of storage location or a change in your wishes. Update the selected documents and recipient arrangements when necessary. The aim is not to oblige someone to complete your work. It is to leave enough clear information for them to understand what you made and decide what questions to ask next.