A downloaded PDF may be enough to run the next advertisement. When its telephone number needs changing, however, the editable original may be missing. A backup should therefore preserve the ability to continue working, as well as showing what was published. The useful test is whether another responsible person can produce a valid new version from the recovered material.
Start with one real project, such as a seasonal offer leaflet. Gather its source file, images, final output and the information needed to use them. That may include approval status, usage permissions and notes about required fonts. Check whether each resource is actually saved or merely available through a link that could stop working.
Define the material that matters
You do not necessarily need to keep every intermediate draft forever. First identify the work that would be difficult or expensive to recreate. For a small business, that could include website copy, original photographs, print artwork, campaign text and approved design templates. A list of these groups exposes gaps more clearly than a general assurance that the marketing folder is backed up.
Distinguish files from a complete system. A collection of copy and photographs does not automatically preserve website settings, forms or functionality. If restoring a system is part of the requirement, ask the person responsible for its technology which additional components and access arrangements are needed. Record that dependency alongside the file backup plan.
Give each group an owner and a known storage location. Avoid having the only usable copy in a former contractor's personal account. Personal information and confidential documents should only be backed up where the intended access restrictions and agreed protective measures can be maintained. Adding another copy also creates another place that needs appropriate handling.
Account for changes and older versions
Backup frequency depends on the consequences of losing recent work. Ask a concrete question: what would we need to recreate if the latest available copy were seven days old? For an unchanged brochure, the answer may be very little. During a substantial website revision, several days of work could disappear. Use that difference to choose a suitable schedule.
Also check how long previous versions remain available. An accidentally overwritten passage may not be noticed immediately, and keeping only the newest copy will not solve that problem. Do not assume a synchronized working folder provides a complete backup without checking its behavior. Establish how deletion, overwriting and recovery work in your particular arrangement.
The BSI's guidance on backups covers basic questions including which data to protect and whether saved copies can be read. For a business workflow, the implication is straightforward: a successful copy notification is a useful starting point, but it does not demonstrate that the recovered material supports real work.
Run a small recovery exercise
Choose a completed project and restore its files into a separate test folder. Do not overwrite current working files. Record the date and the backup version so that the exercise can be traced to a particular copy. The responsible person should be able to perform the recovery using the instructions that would actually be available during a problem.
Open the source document next. Are the linked photographs present? Are the required fonts available? Can the text and contact details be edited? Export a fresh preview and compare it with the approved output. Differences may reveal missing resources or an unsuitable software version. The important result is usability, rather than simply the number of files that appeared.
Then test a different type of material, such as a text collection or an exported campaign report. Successfully recovering photographs tells you little about whether structured records retain their meaning. With a large collection, begin with a reasoned sample and record which groups remain untested. That distinction prevents a limited exercise from being mistaken for complete assurance.
Turn failures into usable instructions
If a file is missing, do more than add that one file. Find out why it fell outside the protected collection. Perhaps final photographs are kept in a second location, or linked resources are not included in the copy. Change the workflow so that future projects do not recreate the same gap. Then repeat the failed part of the test.
A short recovery note should identify the storage location, required permissions, sequence of actions and a backup contact. Do not put passwords in a broadly accessible document. Explain the approved route for obtaining access and check whether it would still be available if the normal working computer failed.
Keep the test record with the backup plan. It should state what was recovered, what did not work and who will resolve the remaining issues. Repeat the exercise after significant changes to storage or software. A backup becomes useful evidence of readiness when the path from saved material to usable work has actually been checked.
