Skip to stories
All book ideas
The File Called Final Again cover

Original book ideaPractical nonfiction

The File Called Final Again

Give the current file an obvious home and make the older versions useful again.

Create my bookRead sample

ImagineYourBook writes a fresh draft from this idea.

Introduction

Kavita sent Ellis a file called FINAL at nine in the morning. At eleven she sent FINAL2. After lunch he received a file called FINAL USE THIS, which had an earlier concert date and a picture of the old piano.

They did have the right file. It was open on Kavita's laptop. The other files were photographs of the work at different moments, except that they could all be edited and sent to the printer. They had the powers of the current file without the responsibility.

You can begin with one document people actually need. Ask where someone should go to find the working copy. Name the place plainly in the group message or link to it from a document people already use. Give the working copy a stable, useful name. If it moves, change the signpost in the same moment. A good file name helps someone find a copy. A good system gives them a way to tell which copy to trust.

Keep milestones when they answer a real question. A draft approved by the venue can help if you later need to check what changed. A copy from just before a new illustration can help you compare the designs. Use a date and a short phrase describing the difference. Keep sensitive details out of names that will appear in shared folders. Use permissions appropriate to the people who should see the work.

Ellis put the current poster in the concert folder and gave Kavita an editing link. The older files went into a subfolder. She kept the one with the wrong date because it also had a useful picture of the piano. They wrote a short note about what had been approved.

The following Thursday a singer asked whether the poster had gone to print. Kavita found the current copy without opening a single attachment. She sent the link and looked up from her laptop while the kettle was still boiling.

Your idea. Your book.

Create my book

Created with ImagineYourBook. Free to use as inspiration.

Chapter plan

Develop this idea

Follow one document from first version to publication, and let the mistakes happen in a plausible small team. A useful method needs a clear owner, location and rule about who changes the working copy. Explain how to preserve a useful milestone without turning every save into an archive. Include a low-tech version for readers whose tools offer no built-in version history.

  1. Open with three allegedly final posters.
  2. Name the live file and the person allowed to replace it.
  3. Choose an obvious shared location and access level.
  4. Make a copy when experimenting and label the fork clearly.
  5. Name milestones by what changed instead of by optimism.
  6. Write a small note describing a consequential revision.
  7. Reduce personal information in shared links and file names.
  8. Practice finding an older version and restoring a copy.
  9. Move one project without tidying the entire drive.
  10. Agree on a simple rule for the next group project.
Series possibilities
  • A practical book about leaving shared digital work usable during a handover.

Add your twist

More options