The file arrived. Which file was it?

A customer rings in November and wants the same leaflet again. Same everything, just 2000 this time.

You find the job. You find the quote, the delivery note and the invoice. What you cannot find is the file — it came through a free transfer link in March, and the link expired seven days later. Somebody has the artwork. The designer, maybe. If they still have the client. If they still have the drive.

This is not a rare event. It is the most common way a simple reprint turns into a week.

Four routes in, four ways to fail

Email attachment. Fails at the size limit, so the customer zips it, splits it, or downsamples it to make it fit — and the file that arrived is no longer the file they designed.

A free transfer link. Works perfectly for seven days and then ceases to exist. It is a delivery mechanism that the whole trade quietly treats as an archive, and it was never that.

A shared cloud folder. The best of the four and still fragile: the customer renames, moves, tidies or revokes, and the link saved against the job points at nothing. Worse, the file can change under you after approval and nobody has to tell you.

Physical media. Reliable, slow, and the label says "final".

Which one did we print?

Open any job folder in any shop and you will find leaflet.pdf, leaflet-final.pdf, leaflet-FINAL2.pdf and leaflet-final-USE-THIS.pdf. Three of them are the same size and none of them is dated in a way that helps.

The question nobody can answer six months later is which one went on the plate. That question is not academic — it is the whole of the reprint, and it is most of the argument when a customer says the colour is different this time.

The file belongs to the job, not to a person

Most print files live in an individual's inbox. That works until the individual is on holiday, or leaves, or their laptop dies, or the customer simply had their personal address and used it.

A file attached to a job is findable by whoever is standing at the counter. A file attached to a person is findable by that person.

Approval is a name and a date

"They approved it" is not a record. Approved by this person, from this address, on this date, referring to this file is a record — and it costs nothing at the moment it happens.

The moment you need it is the moment it is worth most and is hardest to reconstruct: an unhappy customer, a reprint someone has to pay for, and two people remembering the same phone call differently.

The preflight belongs in the record too

If the file was fixed before it printed — bleed added, a spot converted, fonts outlined — then that fix is part of what was printed. Six months later, "the same file" means the fixed one, not the one the customer sent.

Keep the report next to the file. It is the difference between reprinting a job and re-solving it.

Five things to do this week, without buying anything

• one folder per job, named with the job number, and the customer's file goes in it the day it arrives
• when a file goes to plate, copy it into that folder as printed.pdf — one name, always the same name, whatever the customer called it
• stop treating expiring links as storage: download on the day the link arrives, every time
• save the approval message next to the file, not in a mailbox
• if you have nothing better, write the preflight changes in a text file in the folder — a sentence beats a memory

None of that needs software. It needs a rule that everyone follows, which is harder. That is the honest case for software in this corner of the trade: not that it does something impossible, but that it makes the rule automatic in the week when everyone is too busy to keep it.

Where we sit

This is the part of the workflow PressCal grew out of. Every job gets its folder without anyone naming it, files that arrive by email land against the job instead of in somebody's inbox, and PressKit sends large files out on links that belong to you rather than to a service that forgets them.

If you already have a rule that works, keep it. The rule is the valuable part.