A workshop launch, with the handoff filled in

Imagine a business commissioning a creator to promote an autumn workshop. The creator needs a square digital card for a venue screen and a smaller version for a campaign message. The business has approved a link with source, medium, campaign and partner details. This is a fictional production scenario; it uses one of our measured test URLs to make the handoff concrete.

The approved URL is the 199-byte workshop example in the download. Its campaign name is autumn_2026, its medium is qr and its content field identifies a fictional creator partner. Those details stay in the URL for both outputs. The creator does not remove them to reduce the amount of information in the code.

https://example.com/events/autumn-workshop?utm_source=printed_card&utm_medium=qr&utm_campaign=autumn_2026&utm_content=creator_partner_A%20square_artwork&utm_term=early_access&ref=workshop-series-2026

The example delivery note specifies a 540 × 540 pixel PNG, with a 90 × 90 pixel QR region beginning at x=378, y=378. It uses the measured level-M encoding: a 57-module grid, a four-module quiet zone and one whole pixel per module. The final footprint is 65 × 65 pixels, centered within that reserved region.

The designer resizes the background first and inserts that grid afterward. The note identifies the saved file and records the measured result: ZXing-C++ and quirc both returned the exact original URL. It also records the alternative result: neither recovered the URL from the corresponding PNG made by shrinking the completed master. These two results come from our experiment, not a real client campaign.

The business still needs to confirm the actual venue display and the intended phone journey. If the smaller version will be recompressed or resized by another service, the team checks the resulting file or display as well. We have not measured that service, and the original pass does not establish what happens after another transformation.

Suppose the brief later requests a 360 pixel card while keeping the same relative QR area. The box becomes 60 pixels wide, but this code needs 65 modules including its margin. Under our whole-pixel recipe, it cannot be prepared. The designer should flag the layout conflict and agree on more space or a different delivery treatment, rather than report a successful export that was never possible.

That is the value of a specific handoff: the discussion happens while the artwork can still change. The team can retain its approved link, identify which output needs attention and avoid treating a successful large mockup as approval of every later file.
