That reference image needs a receipt

The message in today's archviz discussion is ordinary: make the render look right, like the Scandinavian image attached. The attachment gets downloaded, renamed “ref-final.jpg,” and fed to an image model. Two days later the output is in a client deck. Nobody can say who made the reference, where it came from, or whether it was meant to control light, furniture, materials, or the whole room.

Reference images now do more work than many prompts. Midjourney can use visual references, Veras can take design references, and ComfyUI graphs can condition a generation with image adapters, edges, depth, or other controls. A mixed workflow may pass one image through several systems. The reference can shape an output even when no pixel is directly pasted into the final frame.

That makes the reference a project input. Treat it like one.

The missing record between mood board and render

Architecture offices already track survey files, consultant models, product samples, and client comments. Image references often escape that discipline because they feel informal. They arrive through email, Pinterest, a screenshot, a vendor page, a studio archive, or a client's camera roll. The image moves into a prompt folder while its origin stays in the conversation that delivered it.

This creates three separate problems. The team cannot reproduce the visual direction after the original operator leaves. A reviewer cannot tell which parts of an output were intentionally borrowed as cues. The practice cannot quickly answer a source or use question when the image reaches publication.

A provenance register solves the record problem. It does not determine whether a use is legally permitted, and it is not a substitute for legal advice. It makes the evidence visible early enough for the right person to decide.

Seven fields are enough

Keep the register beside the project image inputs, not in a personal notes app. A spreadsheet, database row, or small text file is enough. Use one row per source image, even when ten images sit on the same board. A board-level record hides the one photograph whose status differs from the rest.

Give every image a stable ID

Use the ID in filenames, prompts, generation notes, and review comments. The source file might be named REF-INT-014_original.jpg, while a cropped working copy becomes REF-INT-014_crop-lighting.jpg. Do not overwrite the original. Hashing files can help detect duplicates, but a human-readable ID is what keeps the trail usable during a deadline.

Record the source at intake

Save the direct page URL when one exists, the access date, and the person who supplied it. A search-results page is not the source. Neither is a Pinterest board that points to a magazine page that credits a photographer. Follow the chain until the creator or publisher is named, or mark it unknown. “Found online” is not provenance.

Name what the image is allowed to control

A reference role is a design instruction. It might control color temperature, daylight direction, camera height, material pairing, planting density, furniture character, or graphic treatment. Write the role narrowly. “Overall vibe” gives the model and the reviewer no boundary.

If the team cannot name the reference role, it cannot tell whether the output followed the brief or copied the picture.

Separate design facts from visual cues. A client-owned photo of the existing room may provide window positions and retained finishes. A published interior may provide only a warm-neutral material relationship. A product image may identify an exact chair, but it does not prove that the chair meets the project's performance requirements.

Track the route, not just the upload

The same reference behaves differently depending on the system and control. In one tool it may influence broad style. In another, an edge map derived from it may guide composition. A crop might steer material color while a depth map controls form. Record the tool, feature or node, crop, weight or strength when exposed, prompt version, and generation ID.

This sounds heavy until it is reduced to a line: “REF-INT-014, cropped to wall and window, style cue, strength 0.35, run 2026-09-09-03.” That line explains far more than “used reference.” It also lets the team reduce or remove one influence without rebuilding the entire workflow.

Where a tool hides settings, save what it does expose. Capture the project or job ID, date, account, model name, and a screenshot or export of the settings panel. Do not invent precision that the interface does not provide.

Use a three-state permission gate

Permission status should be simple enough to stop work. Green means the project team has recorded a basis for the planned use, such as a studio-created image, a client-provided image with written approval for that purpose, or a source under terms the practice has reviewed. Amber means the image may be used for internal direction while its status is checked. Red means it is excluded from generation and delivery.

Unknown is amber, not green. So is “the client sent it.” A sender can have a copy without holding the rights needed for every later use. Route ambiguous cases to the practice's designated reviewer. The register should link to the decision, not attempt to replace it.

Apply the gate again when use changes. An internal option study, a planning submission, a paid campaign, and a competition board are different contexts. Approval for one does not automatically travel to the next.

Review influence before release

Put the reference beside the candidate output at the final image review. Check for distinctive furniture arrangements, artwork, signage, branded objects, uncommon facade patterns, recognizable people, and composition that follows the source more closely than the stated role required.

The test is not limited to copied pixels. Ask whether a reasonable reviewer would identify the source as the dominant creative content of the result. If the answer might be yes, reduce the reference strength, narrow the crop, combine independent references for separate roles, return to text direction, or replace the source with a studio-made study.

Also inspect the opposite failure. A team may cite five references, then produce an output that ignores the approved sources and invents a different material story. Provenance supports design control as much as risk control. It tells the reviewer what the image was supposed to learn.

A fifteen-minute studio setup

Create a REFERENCES folder with ORIGINALS, WORKING, and DECISIONS subfolders. Add a register with the seven fields. Assign one person on each project to clear amber rows before external release. Put the reference ID into the generation filename or sidecar note. Add a release checklist item: “reference register reviewed.”

For old projects, do not attempt to reconstruct every source at once. Start with active deliverables and references currently driving generations. Mark unknowns honestly. The goal is a reliable record from today forward, plus targeted repair where current risk or project value justifies it.

Our take: references are not decoration

The current tool conversation focuses on which model follows a reference most accurately. Studios need the adjacent question: can we account for the reference after the accurate result arrives?

A good register improves the render brief, reproduction, review, and source decisions at the same time. It gives the designer permission to use strong visual direction without turning the project's image folder into an archaeological dig.

The prompt gets versioned. The model gets named. Give the picture a receipt.

Written from the 9 September 2026 intel sweep, which surfaced continued use of attached style references in mixed AI architecture workflows. This operational framework is not legal advice. Practices should set permission rules with qualified counsel and review current tool terms for each planned use.