ItemlumePRODUCT CREATIVE / PRODUCTION AND HANDOFF
Which Krea Realtime Candidate Should I Send for Approval?
Realtime Edit responds as you draw rather than waiting for a Generate click. That makes the active canvas an exploration surface, not a stable approval reference. Choose a particular result, retain the actual review file and identify the corresponding input state before asking a teammate to approve it. A later brushstroke should not silently replace the version they reviewed.
Recognize a live input rather than an unsubmitted edit
Krea’s January 2026 description says its Realtime Edit canvas updates with brushstrokes and can reinterpret a webcam or shared screen continuously. If you expect to finish a whole sketch and then submit it once, this interaction model explains why the result changes before you finish drawing. It does not establish that every other Krea image tool behaves the same way.
Name the present task: explore an arrangement, choose a candidate, or deliver a fixed composition. When those stages are mixed, a useful bottle placement can disappear while you adjust an unrelated decorative mark. A teammate saying “the one on the left” has not identified a reproducible review object.
Separate the input, displayed candidate and retained review file
Keep a short record of what supplied the live input: a sketch, a camera view or a particular shared window. Then identify the selected output independently. The input helps explain the idea, but it is not interchangeable with the exact image a designer or merchant is approving.
Use only the saving or export route actually available in the selected workflow; the cited Realtime article does not document a freeze control or automatic version history. Confirm that the selected result has become a real retained file, open that file and record its exact name or path, version/time and input source state. If it cannot be retained and reopened, mark the item awaiting delivery rather than treating the live view as an approved file.
| Object | What it establishes | What it does not establish |
|---|---|---|
| Live sketch or feed | Current exploration input | A fixed approved output |
| Displayed candidate | A possible visual direction | A file another person can reopen |
| Retained review file | Specific composition for a decision | Accurate merchandise without inspection |
The Krea Realtime Edit article establishes the live-input behavior; the approval record here is an editorial handoff proposal, not a documented export feature.
For the chosen file’s reference lineage, continue with the source-traceability guide.
Make Feedback Refer to a Retained Object
Proposed manual review, not executed Krea generation or export: record whether a retained candidate exists and can be reopened. Identify its input source, including the actual sketch or shared window and the relevant state or time, separately from the output filename. Do not imply that those notes can reproduce an identical generated result.
Specify what the reviewer is deciding, such as composition and headline space, and what remains unapproved, such as a product label that needs the real reference. Keep the feedback with that exact candidate; continuing live exploration does not overwrite the record of an earlier review.
Approve a defined state and carry the decision forward
Ask the reviewer to respond to the named file and the decision it supports. “Approve the plinth arrangement” is narrower than approving the candle’s label or claiming the concept is ready for a product listing. Record any product details that must be replaced or checked during final production.
When exploration continues, retain a separate candidate rather than overwriting the accepted review reference. Before final publication, compare the actual delivery file with the chosen composition and authoritative merchandise. The documented live interaction is useful for ideation; it does not guarantee product accuracy or make an active feed a permanent approval record.
Realtime candidate approval record — actual observations
Save a copy of this record and enter actual inputs, actions and observations. Keep incomplete checks pending; do not prefill success.
| Record | Actual value to complete |
|---|---|
| Retained file exists and reopens, or awaiting delivery | |
| Exact review filename or path, version and time | |
| Input type, source identity and relevant state/time | |
| Composition decision requested and explicit exclusions | |
| Authoritative product reference still required | |
| Reviewer feedback and actual decision on this candidate | |
| Later candidate identity, if exploration continues | |
| Final delivery file and comparison with the chosen reference |
Sources and further reading
Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.
Frequently asked questions
Is the changing image evidence that my last edit was never submitted?
Not in Realtime Edit. The documented workflow responds continuously to drawing rather than waiting for a separate Generate action. Verify which tool you are using.
Can a reviewer approve the moving canvas instead of a saved result?
They can discuss it, but a fixed deliverable needs an identifiable retained file. Otherwise later input changes can make the review reference ambiguous.
PREPARE ASSETS FOR YOUR NEXT STEP
Create supporting product assets in Itemlume.
Create new product creative assets in the workspace, then continue in your chosen tools. Third-party software procedures described in this guide take place in those applications; this workspace link does not imply an integration. Check current capabilities, account access and credit quotes.
Explore asset creation tools Check pricing and credits