---
title: "A source-image intake note before a creative image edit"
url: https://memory.wiki/PikXK5ny
updated: 2026-11-12T13:56:47.125Z
source: "api"
---
# A source-image intake note before a creative image edit

A clear intake note saves a designer from discovering an exact requirement after generating a promising concept. Use this note when someone supplies a portrait, room photograph, or product image and asks for a different visual direction. It is a reusable planning document, not a record of a completed assignment.

## Write down what the file can support

Check who owns the photograph and whether the proposed use is permitted. Keep the original file, rather than relying on a screenshot from a chat. Inspect the subject at a useful viewing size: blurred packaging, a tiny face, or a dark corner gives a generator less reliable detail to work from.

Identify the requested change in one sentence. Then distinguish a creative preference from a production requirement. A watercolor look or a warmer palette is a creative direction. A readable ingredients panel, a precise floor dimension, or a person's recognizable identity needs checking against evidence beyond a generated image.

| Intake field | Note to capture |
| --- | --- |
| Original | Filename and permitted use |
| Goal | The single change this concept should explore |
| Reference details | Features to compare after generation |
| Exact requirements | Text, dimensions, colors, and product identity |
| Final use | Intended size, crop, and file format |

## Define the handoff before generating

Agree whether the next deliverable is a mood-board candidate, a direction for a designer, or a production-ready asset. A generated room can help a discussion about materials without proving a layout will fit. A product scene can help select a background without guaranteeing that the original label survived.

If the project needs exact product pixels, plan an original-product cutout and a separate layer-compositing step. If the project needs readable final typography, plan to typeset and proof it independently. These decisions are easier to make before reviewing a beautiful but inaccurate image.

[AI Image to Image](https://ai-image-to-image.io/?utm_source=memory.wiki&utm_medium=referral&utm_campaign=image_editing_guides&utm_content=description_link) provides a browser-based reference-image workflow for exploring these concepts. It uses whole-image generation and does not supply protected masks or a layer editor. Save the intake note with the original, prompt, and chosen result, then review the actual downloaded file before using it publicly.


---

## Summary
A structured intake note helps designers clarify project requirements and distinguish creative preferences from production necessities before generating images. This planning process ensures that teams identify essential constraints and define the appropriate handoff stage to avoid inaccuracies in the final output.

## Themes
- AI image intake planning
- creative workflow management
- production requirement verification
- asset handoff strategy

## Key takeaways
- An intake note should be used as a reusable planning document rather than a record of completed work.
- Source images should be inspected at a useful viewing size to ensure sufficient detail for generation.
- The intake note must capture the original filename, permitted use, goal, reference details, exact requirements, and final use.
- Generated images should not be used as proof for layout dimensions or product label accuracy.
- The final deliverable type should be defined as either a mood board, a design direction, or a production ready asset before generation begins.

## Insights
- Distinguishing between creative preferences and production requirements prevents reliance on generated images for tasks requiring factual accuracy.
- The quality of the source image directly impacts the reliability of details in the generated output.
- Planning for manual compositing or independent typesetting is necessary when exact product pixels or readable text are required.

## Open questions / gaps
- What specific verification methods should be used to ensure a generated image meets production requirements?