Stop the old spec, quote or artwork going out.
Document version control for a business comes down to one question. Which spec, quote, artwork or leaflet is approved right now, and who still holds the old one?
A Friday cut from Tuesday's measurement chart
Take an export garment unit on a buyer's summer programme. On Tuesday the buyer's fit comments lengthen the sleeve, and the pattern master issues a new measurement chart. On Friday the cutting master lays fabric from the PDF on the floor computer, saved from an earlier mail. Two files had the same name, and the newer one never reached the person holding the scissors.
It happens with a revised quote sales never resent, artwork sent to the printer before a label change, and a leaflet forwarded months ago. The cost arrives later: a rejected shipment, a reprint, an invoice at a price nobody signed.
Version control means three things. One version is current. Every earlier one stays on file with its reason. Anyone holding an old copy is told it no longer counts.
The trouble is rarely a missing file. It is the extra one.
Why a shared drive folder is not version control
Most teams already have one. It still lets the wrong file out.
File names carry the history
A file called spec-final-v3-revised-NEW.pdf tells you someone was worried, not which version was approved.
Copies leave the folder
A file attached to a mail or posted in a WhatsApp group lives on. Updating the folder does nothing to the copy on the factory's phone.
Nobody signs anything
A folder cannot say who approved a file, or whether the buyer's comments were applied. Overwrite it and even the earlier version is gone.
Access is all or nothing
Give a buyer folder access and they may see another customer's styles or prices. So files get emailed instead, and copies multiply. That needs roles and permissions.
The file never meets the order
A folder does not know which order, batch or job used a file. Six months on, nobody can say which spec a lot was made to.
Ten trades, ten versions of the same mistake
The paperwork differs. The way it goes wrong hardly does.
The buyer's comment missed the cutting table
In textiles, a tech pack changes at every sample round and size breakdowns move after the PO. Each buyer sees only their own styles, so files go out one mail at a time.
A leaflet forwarded long after it was withdrawn
In pharmaceuticals, medical or regulatory reviewers decide which promotional version may be shown. Representatives still carry a PDF forwarded last year.
Stores issued against yesterday's quantity
In manufacturing, a customer revises a confirmed order and the BOM moves a revision. Planning knows; stores issue material for the old quantity anyway.
Two safety data sheets for one product
In chemicals, a customer asks for the current SDS and last month's COA. Sales finds two SDS files, while a distributor passes an older product sheet to its buyers.
Cut three was approved, cut four went out
In media and entertainment, a later cut fixes an audio glitch but was never signed off. The schedule should point at the approved file until someone approves the swap.
The recipe changed, the batch sheet didn't
In food processing, a recipe is adjusted for a new supplier's material. Batches made before the change must record the older recipe, or a complaint cannot be explained.
Which proposal did the customer sign?
In renewable energy, a rooftop proposal is revised as panel and inverter choices change. Purchase needs the signed revision, not the newest file on a sales laptop.
The deck the client approved, or the next one
In professional services, feedback on drafts scatters across email. When scope grows quietly, nobody can show which version the client accepted.
The itinerary changed after confirmation
In travel and tourism, a hotel swap or a traveller dropping out creates a new itinerary. Vouchers, payments and supplier copies must match it.
Bandwidth upgraded before the link went live
In telecom, an enterprise customer upgrades an order midway. The network team, the fibre partner and billing all need the amended version.
Draft, approve, lock, recall, link.
Changes stay drafts until someone signs.
Each edit creates a draft with its reason, while the approved version stays in use.
A named person approves against a rule.
The approver sees what changed since the last approved version, and only roles you choose may approve.
Approval freezes the version.
An approved version cannot be edited; the next change starts a fresh draft.
Everyone with the old copy hears about it.
Everyone who got the earlier version receives the new file with a notice, and opens are recorded.
The version sticks to the work.
Each order, batch or job records the version it used, and older orders keep their history.
Settle these before anything is built
Your answers shape the record more than any screen.
- Which document comes first: spec sheets, tech packs, quotes, SDS and COA, artwork or leaflets.
- What counts as a new version, and what is only a typo fix.
- How versions are numbered, and whether buyers' own references sit beside yours.
- Who may approve each type, in-house and on the customer's side, and who stands in for them.
- Which outsiders receive files, and which orders, batches or jobs each document attaches to.
- How much of the old folder is worth importing, and who checks it.
We start from one document that caused real trouble, and read the folder, the mail threads and the order it went with. The pattern is usually plain from the files alone: three people can edit, nobody approves, and the copy that matters lives outside the office.
The first release covers one document type and the people who touch it. For a garment exporter, the measurement chart. For a chemicals trader, the SDS and COA that travel with each dispatch. The next type reuses the same record.
Some decisions stay with your people. We do not write SDS content, set hazard classes or approve promotional claims; your technical, quality and medical reviewers do, and the software makes their decisions hard to bypass. Your ERP or Tally stays the books.
Every approval and share leaves a dated entry, which is what an audit trail is for. If approval itself is the bottleneck, see approval workflows. When a version must follow a lot to the customer, batch and serial traceability picks up from here.
What owners and quality heads ask before we start
Can buyers approve a tech pack or sample version themselves?
They can. Each buyer gets a login limited to their own documents, sees what changed since the last round, and records an approval that locks that version. Many teams open this to buyers only after the internal records have settled.
Does quote revision tracking work the same way as technical files?
Yes. Each quote revision keeps its prices and terms, and the accepted one is locked, with the order and invoice pointing back to it. A price dispute becomes a lookup, not a search through sent mail.
What about distributors and job workers who already hold old files?
Nobody can delete a PDF from someone else's phone. We can know who received each version and send them the replacement with a notice. Their login then offers only the current file.
Do we have to stop using our shared drive?
Not on day one. Drafts can stay where your designers like them. The approved version moves to the new record, which becomes the only place outsiders get files from.
Can software make sure an old file never goes out again?
Not completely; anyone can forward a PDF from their gallery. But the approved version becomes easy to find, older ones are marked superseded, and you can see who was sent what.
Send us the file that went out wrong.
Tell us which document caused the last reprint, rejection or dispute. We will read how it moves today and suggest the smallest first release that stops it.