How I organize Canva files for repeat clients

Graphic Design
1

I used to lose more time searching for old Canva designs than actually editing them, so I have settled into a simple system that works for me, and I wanted to share it in case it helps anyone else.

First, I keep one folder per client, and inside it a folder per project, rather than letting everything pile up on the home screen. Second, I name files in a consistent way: client name, project, and what it is, so a search actually finds it later. Third, before I edit a finished design for a new round, I make a copy and edit the copy, so the approved version stays untouched.

Finally, once a project is done, I move the working copies into an archive folder instead of deleting them. Clients do come back months later asking for a small change, and having the old file ready saves a rebuild.

It is nothing fancy, but it has stopped the usual mess of files called Final, Final 2, and Final Really Final. How do you organize your Canva files? Do you use folders, a naming system, or something else entirely?

1 Like
2

That’s a good starting point, and really, it doesn’t matter whether you’re using Canva, InDesign, Illustrator or anything else. Good file organisation is good file organisation.

I’d probably take it a step further and assign every job a unique reference number. That number follows the project from the initial brief right through to the final invoice. It makes everything much easier to track, especially when you’ve got multiple jobs for the same client.

Even if the reference number is something like S2 (for Smurf2) and the date S2311 (or 113 depends), and then the job for the day S2311001 - ends up being the invoice number. Next one is S2311002.
That goes on the invoice, and you makes traceability easier.

You don’t need anything particularly fancy either. Even an Excel spreadsheet can track job numbers, client details, dates, instructions, revisions, approvals and invoices. There are plenty of dedicated project management systems available too, depending on the size of the business.

I’d also keep a record of who requested changes, what was requested, when it was requested and who approved it.

Years ago, I used to keep a phone book-sized notepad beside me. Every instruction was written down with the date, time, who gave it and exactly what they wanted changed. They’d sign off on the instruction too.

Sounds a bit excessive, but 14 months later when someone asked why something was changed, I could pull out the notebook and say, well, on this date at 11:14 am, you requested this particular change, and here’s your signature approving it.

These days, of course, you’ve got emails, project management systems and digital approval trails, so it’s much easier to maintain that history.

And I’d absolutely agree with keeping an archive. Not just the working files, but the actual approved artwork, supplied assets, fonts and licensing information where applicable, and a copy of whatever was delivered to the client. Even if they never come back with another change, it’s worth having.

I’d also make sure the archive is backed up somewhere independent. Having everything neatly organised is one thing, but losing access to the account or the files is another matter entirely.

You always need 2 backups of the backup that are stored separately.

Ultimately, I think the most important thing is consistency. A simple system that everyone follows is far better than an elaborate one that nobody uses.

And whatever system you choose, make sure someone else could pick up the job tomorrow and understand exactly where everything is and what stage it’s at.

2 Likes
3

The reference number idea is the missing piece in my setup, Smurf2. I can find a file fast enough, but tracing it back to the invoice and the approved version is where I still waste time.

Your point about the archive holding the approved artwork, not just the working files, also landed. I have been archiving the working copies and assuming that was enough, when really it is the delivered version that matters if a client comes back months later.

One question: do you put that reference number in the Canva file name itself, or just in the folder and the spreadsheet? I am wondering which one survives when a file gets copied or renamed by a client.

4

Yeh, I’d definitely put it in the filename, as well as the folder and spreadsheet.

That reference number follows the job through the entire process, from the initial brief to the final invoice.

In traditional print artwork, you can also put the reference number in the slug area, outside the actual artwork and bleed. That way, even if someone renames the file, you can still identify the original job number by opening the artwork.

I don’t think Canva supports a proper slug area, which is a pity, as it’s quite useful for this sort of thing.

But there’s another important distinction. You can’t really control what happens to a file once a client copies or renames it. What you can control is your own records.

So I’d keep the original working file, the final approved version, and a copy of exactly what was delivered to the client. All under the same job reference, with the approval correspondence recorded against it.

That way, if the client comes back 14 months later with a completely renamed file, you can still trace the job through your own records.

And I’d use separate version numbers for revisions. The job number stays the same, but the revision changes. That way you’re not just identifying the job, you’re identifying exactly which version was approved and supplied.

Essentially, the filename is useful, but the job reference and its history are what really tie everything together.

1 Like
5

That clears it up, thanks — putting it in all three places makes a lot more sense than picking just one. If the filename gets changed by the client, the folder and spreadsheet still carry the same reference, and if I’m searching inside Canva, the filename does the work.

I really like the three-copy idea too: working file, approved version, and exactly what was delivered. I’ve had that awkward moment where a client sends back a renamed file and I’m not quite sure which version it actually was, so keeping the delivered copy untouched feels like cheap insurance.

Keeping the job number fixed and only changing the revision number is the part I’ll adopt straight away. It stops that creeping confusion where every small tweak starts to look like a brand new job. Do you ever add a short note in the spreadsheet when a revision is approved, or is the version number on its own enough for you to trace it back later?