When you edit images with text prompts, the result can look effortless. The hard part shows up a week later, when a client asks for "the same thing, but for the spring range," and nobody remembers which prompt produced the approved version. A simple edit log fixes that. It takes a minute per image and saves hours of guessing.
Why a log matters more with prompt-based editing
With layer-based editing, the history lives inside the file. With prompt-based editing, the history lives in your head unless you write it down. Small wording changes ("soft window light" versus "warm window light") can shift the whole mood, so the exact words are part of the deliverable. A log also helps you be honest with clients about what was changed and what was left alone.
What to record for every image
Keep one row per final image. A spreadsheet is enough. Record:
- Source file: the original photo name, stored untouched in a separate folder.
- Goal: one plain sentence, such as "move the product to a kitchen counter scene, keep label readable."
- Prompts in order: every prompt you ran, including the ones you threw away, numbered.
- Kept version: which step produced the approved image.
- What must not change: faces, logos, product shape, text on packaging.
- Checks done: a short note that you compared the label, colours and proportions against the original.
- Approval: who approved it and when.
Write prompts you can reuse
Prompts are easier to reuse when they are split into a fixed part and a variable part. The fixed part describes the shared look: "soft daylight from the left, light grey background, no hard shadows." The variable part describes the one thing that changes: "the blue bottle" or "the second team member." Save the fixed part at the top of the log so the next batch starts from the same words.
Review before delivery
Before sending images to a client, open the original and the edited version side by side. Check the details that prompt edits can quietly alter: lettering on products, the number of fingers, jewellery, logos and the edges where a subject meets a new background. Note any fix in the log. If a detail could not be kept accurate, tell the client rather than hoping they will not notice.
A small habit that scales
The first time, an edit log feels like extra admin. By the third project it becomes the fastest way to match an earlier look, hand work to a colleague or answer a client's question about what was changed. We use this habit ourselves when testing edits in Nano Banana AI, and it works the same way with any tool that edits images from text instructions.
Start with five columns today and add more only when you miss them.
Top comments (0)