Scenario · Content and search
Please add these before-and-after cases
“Please add these cases.” Usually with a folder of photos attached and nothing else.
A folder of before-and-after photos with no instructions is the single most common request on the desk, and the part that quietly goes wrong isn't the upload — it's the multi-megabyte phone photos nobody shrinks, the alt text nobody writes, and the case gallery nobody checks afterward for a broken pair. This handles the mechanical half — sizing the images properly, drafting alt text, and auditing the finished gallery for anything half-uploaded or broken — so the only judgment call left for a person is confirming the pairing and the permission to publish, which no tool can safely guess at.
What to ask for
See it work
A real run of Gallery & before/after audit:
FAIL
8 image(s) · 3 pair(s) · 0 composite case(s) · 2 unpaired
[error] 1 gallery image(s) are broken — missing-case.jpg
[warn] 2 before/after image(s) have no partner — a half-uploaded case looks complete to whoever added it: before "missing-case.jpg" · after "yH5BAEAAAAALAAAAAABAAEAAAIBRAA7"
report: ./out/gallery-and-before-after-audit-gallery-and-before-after-audit.html
text: ./out/gallery-and-before-after-audit-gallery-and-before-after-audit.txtThe captured report, exactly as a run hands it to a client —open the full report ↗
The most common request there is, and the one most likely to arrive as an email with photos and no instructions. The work is mechanical; what goes wrong is upstream of the work — unoptimised phone photos at eight megabytes each, a before with no after, alt text nobody wrote.
- Confirm the pairing and the permission before touching an image. Which before goes with which after, which procedure each pair belongs to, and that these are cleared for publication. If the request does not say, ask — a guessed pairing is worse than a late reply.
- Optimise the photos locally, before they go anywhere near the site. Straight off a phone or a
clinic camera they are multi-megabyte JPEGs with names like
IMG_4021.jpg. Convert them to web-ready sizes with clean, descriptive filenames in one pass. This is the step that stops a gallery becoming the reason the page is slow. - Write the alt text. Every case image needs it, and a gallery is exactly where it gets skipped. Generate it, then read it — the automated pass is a draft, and a clinical image is not the place to publish a description nobody checked.
- [manual] Upload and build the gallery entry in the CMS. Place the pair, set the procedure category, and publish. By hand, because the pairing is the one thing no tool can verify and getting it wrong publishes a patient’s photo against the wrong claim.
- Audit the gallery you just changed. Run the gallery check on the live page: it catches the half-pairs, the images that never load, and the ones still too heavy after upload. Then check the page’s links and images for anything broken, and capture the page across devices so you can see the gallery as a visitor does — case galleries break on mobile more than anywhere else.
- Attach the gallery report to the ticket. It states what is on the page now, which is a better answer than “added” and takes the same effort.
Why this one is worth a procedure
It is the single busiest kind of work on the desk, it arrives with the least structured information, and every step except the upload is already automated. That combination is exactly where an unwritten procedure costs the most: the tools exist, so the variance is entirely in whether whoever picked up the ticket remembered to run them.
What this does not cover
Consent and clinical accuracy. Nothing here can tell you whether the patient agreed to have these photos published, whether the pairing is honest, or whether the result shown is representative — those are the practice's calls and they are the ones with real consequences. It also cannot pair photos for you: which before belongs to which after is read off the filenames or the request, and a mislabelled pair passes every check in this procedure.