Logo Revisions Case Study

The Business Problem

After a logo was edited, the new proof could still show the original logo. The systems were reusing the previous copy of the image rather than the updated one, so a customer who had asked for a change saw exactly the same artwork again. That meant another round of emails, a confused customer, and a risk that the wrong artwork would be approved for production. Some logos with missing or unusual colour settings could also stop a proof image from being produced at all.

The Solution

wildesoft.net traced the problem through the full revision path: create a proof, reject it, edit the logo, recreate the proof and send it to the customer. Logo images in proofs are now always fetched fresh, so the latest version of a logo appears on screen and in what the customer receives. Logos with missing or invalid colour settings now fall back to a safe default rather than failing, so a proof can always be created.

The Result

When ACE revises a logo, the customer sees the revision straight away. Proof rounds are shorter, customers aren't left wondering whether their feedback was acted on, and there is far less risk of the wrong artwork being approved.

See all case studies for Logo Manager