A client approves a view during a design workshop. Weeks later, a cropped version appears in a public campaign without its option label. No new pixels were generated, but the image’s meaning changed. Responsible handover therefore begins with intended use, not export resolution. Approval should identify the audience, channel, revision and claim being approved.
Separate internal exploration, stakeholder presentation, statutory submission and marketing release. A single asset may support several uses, but each deserves an explicit check. For a planning submission, consult the relevant authority and specialists about required visual material. Do not rename an atmospheric concept view as a verified view simply because the deadline has moved.
Make the issue record readable
The delivery package should include a clear file name, revision identifier, status, camera reference and concise description. Record who approved the architecture and who approved publication. These may be different people. Include known limitations where they affect interpretation, such as indicative planting, unresolved facade materials or an illustrative lighting condition.
A caption should identify the proposed project as proposed. “Illustrative concept view; landscape and materials under development” communicates more than a vague “artist’s impression,” provided it accurately describes the work. A completed-building photograph and a speculative representation must never be presented as interchangeable evidence.
Keep a rights ledger
List the architectural model, source photography, texture libraries, entourage, typefaces and generative services used. For each, record the source, applicable terms, permitted use and any attribution requirement. Keep copies of relevant permissions and licence records. A subscription invoice by itself may not establish that every asset can be redistributed in every form.
Creative Commons licences illustrate why details matter: attribution, commercial-use and adaptation conditions vary by licence. A photograph available to view online is not automatically free to upload or publish. The same caution applies to screenshots, reference boards and material scans that entered the workflow informally.
“AI-assisted” describes a process. It does not settle ownership, permission or responsibility.
Copyright treatment of generated material varies with jurisdiction and the nature of human contribution. Service terms may address contractual use without resolving every third-party claim. Where an image has significant commercial value or legal exposure, obtain advice for the actual project rather than relying on a broad statement about who owns AI output.
Protect people and confidential work
Source photographs may contain identifiable people, vehicle plates, addresses or private information on a desk. Removing a name from a file does not necessarily anonymize its contents. Review the image itself and any embedded metadata. For UK projects, the Information Commissioner’s Office provides guidance on data protection; use the relevant local regulator where another jurisdiction applies.
Confirm whether project agreements permit assets to be processed by a hosted service. Consider where data is stored, who can access it, whether it may be retained for training and what deletion mechanisms exist. An enterprise account may have different terms from a free account under the same brand. Check the service and contract actually being used.
Provide provenance without overstating it
The Coalition for Content Provenance and Authenticity, known as C2PA, develops standards for recording content provenance. Credentials can help communicate origin and edits when the workflow supports them. They do not prove that a building is accurately represented, and their absence does not establish that an image is false.
Keep an ordinary internal record even when technical provenance tools are available. Preserve the issued file, its baseline, approval notes and essential production information. Agree a retention period tied to contracts, project needs and applicable obligations. Do not keep confidential material indefinitely merely because storage is inexpensive.
Deliver for actual use
Ask where the image will be seen. A projected workshop view, a printed board and a mobile webpage need different export checks. Confirm dimensions, compression, color profile and cropping with the recipient. Provide descriptive alternative text for web use, drawing on the principles of the W3C Web Content Accessibility Guidelines, while avoiding claims that the image itself cannot support.
- Context: Proposed status, revision, purpose and limitations remain attached.
- Permission: Sources, people, tools and publication rights have been checked.
- Approval: Named reviewers have accepted the defined release, not every future reuse.
- Archive: The studio can retrieve what was issued and explain why.
Finally, tell recipients when they need to return for approval: a new crop that hides context, a changed caption, a different campaign or an edited image can all alter the argument. The aim is not to make sharing difficult. It is to ensure that the public presentation remains connected to the design the studio is prepared to defend.