Small creators and businesses generate valuable records without noticing: drafts, design files, dated emails, invoices, version histories. When a project wraps up, those records are scattered across laptops, chat apps and cloud folders. This checklist guides a start-stop-continue audit of how you kept the records around your creative or commercial work. It concerns organisation only. It is informational, it does not interpret any law, and it is no substitute for the view of a qualified advocate on questions of intellectual property.
Before the audit: choose the scope and gather the trail
Select one completed project. Define it in a sentence, for example “the logo and packaging refresh from spring”. Collect the records that touch it: folders of files, email threads, invoices, approval messages and any written agreements. Place them in front of you, physically or on one screen, and block thirty minutes. Mark each item you cannot locate quickly; those are your first findings.
Section A: where records lived
Tick each statement that is true of your last project.
- All working files lived in one clearly named location.
- The location had a dated version history, or I saved dated copies at each milestone.
- Final approved versions were kept apart from drafts.
- At least one backup existed outside the device I worked on.
Every unticked line is a candidate for the Start column. If two or more are unticked, begin there. A typical entry reads: “Start saving a dated copy of each approved version into a separate folder.”
Section B: who did what, and when
Records of contribution matter when several people work on one piece of output. Check the following.
- I can show who produced each major component.
- Any outside help, such as freelancers or tools, is noted in writing with dates.
- Written terms for outside contributions were saved with the project folder.
- Messages that confirmed key decisions were saved in a place other than a chat app.
The reason for this section is practical rather than legal: clear records make later questions easier to answer for everyone involved. Whether a given record has any legal effect is a question for a qualified professional, not for a checklist. If you ever need to find one, local listings such as one Guwahati listing under the IP heading and its Madurai counterpart show what city-level directories look like. They are starting points for your own research, and their presence here implies no recommendation.
Section C: habits that cost time
This section feeds the Stop column. Tick each statement that describes your project.
- I spent time searching for a file whose location I should have known.
- I kept several near-identical copies and was unsure which was final.
- I accepted instructions or approvals in conversations that left no record.
- I shared working files through channels I could not later trace.
Each ticked line points to a habit to stop. Phrase the entry as a replacement: “Stop approving changes by voice; confirm each in a short written message and file it”.
Section D: practices that earned their keep
Now look for strengths. Tick every statement that held true.
- File names followed a consistent pattern.
- I left myself a brief note whenever a work session closed.
- Invoices and receipts were filed on the day they arrived.
- Someone else could have found any file without asking me.
These ticks feed the Continue column. They are easy to lose in the next burst of activity unless you name them. Write each as a promise to your future self.
A structural comparison from another field
One more way to test your folder structure is to compare it with the way a well-organised public website lays out its content. BestPilotsNow presents itself as an aviation discovery platform and splits its pages into separate areas for people, schools, courses and resources. Your project folder could follow the same idea: one area for drafts, one for approved versions, one for agreements and one for money records.
A worked example of the audit
Consider a two-person studio that finished a brand refresh. Section A leaves three lines unticked: no dated copies, no separate folder for approved versions, no backup beyond one laptop. Section B shows that a freelancer contributed an illustration and that the only record is a chat thread. Section C shows that several approvals happened on a call. Section D shows that file names were consistent and that invoices were filed promptly.
The resulting lists are short and concrete. Start: a dated approved-versions folder, a second backup and a written note for each outside contribution. Stop: approving changes on calls without a follow-up message. Continue: the naming pattern and the habit of filing invoices on the day they arrive. The studio ends up with one sheet of paper it can begin acting on the very next Monday.
Convert the ticks into three lists
Take your unticked Section A and B lines and write the strongest three as Start entries. Take your ticked Section C lines and write the strongest three as Stop entries. Take your ticked Section D lines and write the strongest three as Continue entries. Next to each, add a first action, a date and a place where you will see the reminder.
A completed page might look like this.
- Start: dated copies of each approved version; written confirmation of key decisions; a second backup location.
- Stop: voice-only approvals; scattering files across messaging apps.
- Continue: consistent file names; end-of-session notes; filing invoices on the day they arrive.
Running the audit as a team
If several people worked on the project, each should complete the checklist alone first, then compare. Differences are informative: one person may believe approvals were always written down while another remembers a call. Resolve these by looking at the actual records, not by debating memory. Merge the results into a single page and hand each entry to whoever is closest to the task it concerns. Keep the tone about the process, not about individuals, so the discussion stays productive.
Scoring yourself without obsessing
Count the ticks in Sections A, B and D, and the ticks in Section C. A project with many ticks in A, B and D and few in C has sturdy habits. A project with the reverse pattern needs attention. Resist the urge to compute a precise score; the point of the count is to direct the conversation, not to grade yourself.
Small habits that make the audit easier next time
Three tiny routines pay off disproportionately. First, create the project folder and its four sub-areas on the first day, before any work begins; an empty structure invites tidy habits. Second, end each work session by dropping a two-line note into the folder, saying what changed and what is pending. Third, add a calendar entry during the project’s last week, titled with the audit’s name, so the review is scheduled before the busy period swallows it.
Each routine costs only a few minutes, and together they make the audit itself almost trivial, since most of its answers are already waiting in the folder.
How often to run it
Run it again at the close of every significant project and review last time’s page before you begin. If the same unticked line appears in two consecutive audits, the entry was too ambitious or lacked an owner; shrink it to one small action. Over a year, your pages will form a quiet record of how your working habits matured.
What this audit deliberately leaves out
It does not assess whether your work is protected, who owns it or what rights apply. Those are legal questions with answers that depend on facts and jurisdiction. If you have doubts, speak to a qualified advocate and bring your well-organised records with you; they will make that conversation shorter, clearer and, very likely, less costly.
Related posts:

A Six-Week Checklist for Preparing to Meet an Advocate

Five Myths About Keeping a Record Before You See an Advocate

IAMOps Choices Compared: Keys, Bundles and Console Edits

Nine Ideas for a Shutdown Routine at a Legal Office Desk

A KubernetesSecOps Checklist for Online Advocate Directories
