Questions about references, credit, and permission

Can a private mood board contain copyrighted images?

The answer depends on the source, use, agreement, access, and applicable law. A private workflow does not create automatic permission. Record sources and seek appropriate advice when risk warrants it.

Does crediting the creator make reuse acceptable?

Credit supports attribution but does not automatically grant the rights required for a particular use. Verify the applicable licence or obtain permission.

Are AI-generated images automatically safe for commercial use?

Do not assume so. Check the tool terms, account plan, inputs, recognizable content, project context, and any required permissions or review.

Who should own the source log?

Assign a named person. Creative, production, legal, procurement, or the client may own different checks, but the handoff should make responsibility and status visible.

Separate reference use from production use

A reference can help a private team discuss light, composition, material, type, or atmosphere. That does not automatically grant permission to publish, advertise with, modify, distribute, or sell the image. Mark every item as inspiration, candidate asset, original work, or approved production asset so its role is visible.

Do not promise that a private board is automatically lawful in every situation. Copyright, contract, privacy, publicity, trademark, confidentiality, and platform terms can all matter. Requirements vary by material, use, and jurisdiction. Use appropriate professional advice when the project or risk requires it.

Capture a source log during collection

Record the original page URL, creator or provider when known, date collected, licence or permission status, intended role, and person responsible for follow-up. Save the direct source rather than only a search-results page or copied file. A screenshot without origin information becomes difficult to verify later.

Give every board item a short identifier that connects it to the log. The board can stay visually clean while the log holds details. If the source disappears, keep the record of where it was found and do not infer rights from the missing page.

Keep the source register beside the complete mood board workflow from collection through approval.

Use status labels that a client can understand

Label reference only, permission needed, licensed, original, public domain claim to verify, or replace before release as appropriate to the workflow. Avoid a single approved label that could mean visual approval, legal clearance, or final production selection. Those decisions are different and may have different owners.

Explain the status in the handoff. A client approving the visual direction should not accidentally approve unlicensed reference assets for publication. Record which decision was made, who made it, and what must happen before final delivery.

Reference status and handoff audit

Keep visual approval, production selection, and permission as three separate decisions.

Reference only

Used to discuss a principle, with source recorded.

Next check: Replace or clear before public production use.

Candidate asset

A specific final use is being considered.

Next check: Verify owner, licence, releases, scope, and restrictions.

Original or commissioned

Creation and agreement are documented.

Next check: Confirm ownership, delivery, and approved uses.

Approved production asset

Permission evidence matches the intended release.

Next check: Archive the agreement with the final asset.

Design the source record for the final handoff

The safest log is not an archive created after approval. It is part of collection from the first reference.

Traceability. Save the direct source and creator information when available. Search thumbnails, copied files, and screenshots are poor records because they separate the image from its origin and terms. Add a collection date and stable item identifier, then connect the visual board to the detailed log. If a page disappears, do not invent a licence from memory.

Status. Use language the whole team understands: reference only, candidate, permission needed, original, licensed, or approved for the named use. Avoid one ambiguous approved marker. Visual approval does not equal permission, and permission for one placement may not cover another. Show the current status and the exact decision that remains open.

Responsibility. Assign the person who verifies licences, releases, agreements, and replacement. A warning without an owner and deadline is likely to survive into production. Separate creative approval from legal or production clearance when different people own those decisions. Include unresolved items in the handoff rather than hiding them in a folder name.

Scope. Store the permitted media, territory, duration, edits, attribution, and other relevant limits with the asset. Approval for one campaign or format may not cover later reuse. Record model, property, location, or artwork releases when relevant to the project. Requirements vary, so use qualified advice rather than treating the source log as a legal conclusion.

Treat generated and found images with the same discipline

Record the tool or source, account or plan used, creation date, prompt or process when useful, editing history, and any relevant terms. Generated output can still raise questions about permitted use, recognizable people, brands, protected characters, source material, or confidential inputs. Do not label it rights-free without checking the applicable terms and context.

For found images, credits and links support attribution and traceability but do not automatically create permission. For commissioned or employee-created work, confirm the agreement that governs ownership and use. Keep the evidence with the project rather than relying on memory.

Run an asset replacement and clearance review

Before public release, list every reference that survives into the final work. Replace inspiration-only material with original, commissioned, or appropriately licensed assets. Confirm scope, duration, territory, media, edits, attribution, model or property releases, and any delivery restrictions relevant to the project.

Archive the final source log, licences, permissions, releases, and replacement decisions with the approved design. The mood board should remain a record of reasoning, not an accidental folder of production assets. A clear archive also helps future collaborators avoid reusing a reference outside its approved scope.

See how reference status becomes a production responsibility in a photography board and shot list.

Source and handoff controls

  • Save the direct source during collection.
  • Record creator, date, status, and intended role.
  • Label inspiration separately from candidate assets.
  • Do not treat credit as permission.
  • Review generated and found images with the same discipline.
  • Archive replacement and clearance decisions.

Create a source log for the current board

Give every reference an identifier, direct source, creator or provider when known, collection date, status, intended role, and follow-up owner. Mark which items are inspiration only and which may be candidates for final use. Before public release, replace or clear every surviving reference and archive the supporting agreement with the final asset.

Keep source status visible throughout the complete mood board workflow from collection to production handoff.

Start a sourced mood boardExplore all guides