Filed correctly, and still wrong

A revised purchase order comes in by email on a Tuesday afternoon, an amendment to one that went out three weeks earlier. Whoever opens it saves the attachment into the customer's folder, same as always, and the day moves on. Nobody sets it beside the original quote to check the two agree, because that is not exactly anyone's job — it belongs to whoever happens to be free, which today is nobody. Three weeks later a shipment goes out short. Someone finally holds both documents up together and finds the quantity in the amendment was lower than the one everyone had been building against since. The order was filed in the right place, under the right customer, on time. That is what makes it worse: nobody did anything wrong, and the mismatch still reached the loading bay before a person caught it.

Why we build it this way

The obvious fix is a portal: one web form, one inbox, one place documents are supposed to arrive so the business finally controls the format. We think that solves the wrong problem. A supplier who has sent purchase orders by email for years does not switch to your portal because you built one — they keep emailing, and now there are two places to check instead of one. Paperwork arrives however the sender finds easiest, whether that is an email, a photograph of a printed sheet, or a form dropped into a shared folder. It will never be uniform, and asking it to be is asking the wrong people to change.

The part actually worth fixing is not where a document lands. It is what happens the moment after. Filing something quickly is not the same as filing it correctly, and correctly does not mean "in the right folder" — it means checked against what the business already believes to be true. A changed quantity, a new drawing revision, a rate that has moved since the last quote: none of that is visible from the document alone. It is only visible next to the record it is meant to update.

So the part we put the most care into is the comparison — reading a new document against the one it replaces, or the record it belongs to, and being plain about what changed. A system that only files things faster has done half the job and called it finished.

How it works, roughly

Setup is the set of records something can arrive against — accounts, orders, drawings, candidates — and where each kind of document belongs once it is read. From there, it reads:

• Whatever actually arrives — an email attachment, a photograph of a printed sheet, a scanned form, a file dropped into a shared folder
• What the document appears to be — a quotation, a purchase order, a drawing revision, a résumé — and which existing record it belongs to
• The version of that record already on file, so the new document is read next to what it is meant to update, not on its own

Where the new document agrees with the record, it files itself and the day moves on with one less thing to remember. Where it does not — a quantity, a revision number, a rate that has changed — it does not file quietly and does not refuse the document either. It flags exactly what disagrees, and leaves the reconciliation to a person who can pick up the phone and ask. Nothing gets corrected on the system's own authority.