Save the result while it is still available
THE RENDER OFFICE shows one current result in the browser tab. A useful image needs to be saved before another successful generation replaces it or the page is reloaded. Do not assume that the membership account acts as a saved-image archive.
Create the project folder and a short session log before generating. When a candidate is worth keeping, save the file and record its prompt and settings immediately. Reconstructing those details from memory at the end of a long session is unnecessary work and can produce an inaccurate record.
Give every candidate a stable identity
Use a simple candidate identifier that appears in the filename and the log. For example, a tableware project could use tableware-candidate-01.png. The name identifies the source; a separate status field records whether it is under review, rejected, selected, or approved for a specific purpose.
Avoid renaming several files final, final-new, and final-approved. A status can change without erasing the candidate's identity. Keep the original image intact and save crops or finished layouts as related files so a later revision still has a full source.
| Field | What to preserve |
|---|---|
| Candidate identifier | The identifier used in the source filename |
| Brief version | The assignment and acceptance criteria |
| Prompt and settings | Exact input, mode, format, and quality |
| Review status | The decision, reviewer, and intended use |
| Related files | Editable layouts and approved exports |
| Open issues | Anything still needing correction or verification |
Keep prompts as explanations, not guarantees
Record why a prompt was useful: it created room for the headline, described a lighting relationship clearly, or helped the reviewer compare directions. That note is more reusable than a generic label such as perfect product prompt.
A repeated prompt does not guarantee the same image or exact continuity. When reusing a previous brief, update the product facts, placement, and acceptance requirements. Compare the new result with the new assignment rather than assuming that a previously successful phrase will solve it.
Separate working files from approved delivery
Keep candidate images and exploratory notes in a working area. Put approved exports in a clearly identified delivery area with their intended destinations. Retain the relationship to the original image and editable design file so an export does not become an orphan.
For translated or differently sized versions, record the language and placement beside the export. One candidate may produce several files with different approval states. A revised headline in the German layout should not silently imply that the Japanese version has also been reviewed.
Make the record safe and useful to share
Share the brief, prompt, selected images, and review decisions with the people who need them. Keep API keys and account credentials out of filenames, prompt libraries, screenshots, and handoff notes. Credentials are not part of the creative record.
At project close, confirm that the final files open and that their source links are understandable. Archive the rejected directions with a short reason when they offer useful learning. The goal is a record that lets another person continue the work without guessing which image or instruction mattered.
Start with one campaign decision.
Explore the studio against your next brief. Generation requires ChatGPT sign-in, an active membership, and your own OpenAI API key. OpenAI usage is charged separately.
Explore THE RENDER OFFICE studio