Start with a list of everything you did not create
Before you polish a design, make a simple asset list. Include photographs, illustrations, icons, textures and fonts, including any that arrived inside a template. Record the file name, where you obtained it, who supplied it if known, and where it appears in your project. A table or project note is enough; the aim is to avoid searching for an asset’s origin just as you are ready to publish.
Separate assets you made yourself from those supplied by someone else, but do not assume that a purchase or download gives you every possible right of use. A template, for example, may contain editable text and image placeholders alongside sample imagery or fonts with separate terms. If an asset’s source is unclear, flag it now. Replacing one uncertain image early is usually simpler than rebuilding several finished pages later.
Define the intended use before reading the license
Write down what you plan to make and how people will receive it. A slide deck shown during a meeting, a printable planner sold to customers, a social post and an editable template can involve different uses of the same asset. Note whether the finished file will be public or private, free or paid, flattened or editable, and whether collaborators will need access to the original image or font files.
This short use description makes license language easier to evaluate. Instead of asking whether an image is simply “free,” ask whether its terms cover the specific way you will use and distribute it. For a font, check the relevant setting: desktop design work, a website, an app or another form of distribution may be addressed separately. If the license does not clearly cover your intended use, treat that as a question to resolve rather than permission to proceed.
Check the terms at the source
Find the license or usage terms associated with the actual asset, not just a caption on a search result or a copy saved in an old folder. Look for permitted uses, restrictions, attribution requirements and any limits that matter to your project. For images, pay particular attention to rules about resale, editable products, modification and use as a prominent design element. Also check whether the asset contains recognizable people, logos or artwork that may raise separate usage questions.
For fonts, confirm which files and weights your license covers and whether you may share the files with collaborators or include them in a deliverable. Using a font to create a finished graphic is not necessarily the same as giving someone the font file so they can edit a template. If you cannot locate clear terms, contact the provider for clarification or choose an alternative with terms you can verify. This workflow is a way to organize checks, not a substitute for advice on a specific rights dispute.
Save evidence and make the decision visible
For each asset you keep, save a copy of the relevant license text or a record of where you found it, along with any receipt or permission message. Record the date you checked it and a brief note explaining why you believe the intended use fits. Terms can vary by provider and license option, so keep the information tied to the particular asset and transaction rather than relying on a general note such as “licensed images.”
Give each item a useful status: approved for this project, needs clarification or replace. If attribution is required, draft the credit while you still have the creator and license details in front of you, then plan where it will appear in the finished work. When a collaborator supplies an asset, ask for its source and applicable terms before marking it approved. A clear record helps a future editor understand your choice without retracing the entire project.
Run a final check on the file you will share
Usage checks are not finished when the first draft is approved. Review the final export and any source files you plan to hand over. Make sure placeholder images have been removed, required credits are present and no unapproved asset slipped in during revisions. If recipients will receive editable files, check whether those files include images or fonts they may not be permitted to reuse independently. Where appropriate, explain which assets a recipient must license or replace before editing.
Keep the asset list with the project so you can revisit it if the design changes. Turning a private deck into a public download, or a personal planner into a product, is a good reason to check the terms again. The practical habit is simple: identify the asset, describe the use, verify the terms, document the decision and review the final delivery. It makes rights questions part of your normal design process instead of a last-minute obstacle.
