Free template
Ask a client for the content you need in one clear list. The request explains what each item is for, the format you need and when; the internal checklist tracks what has arrived, what has been approved for use, and whether you have permission to use it.
Enlarge preview: Content request — for your clientSend it when the project starts; update the status column as things arrive.
Each item you need, what it is for, the format and specifications, who provides it and by when, how to send files without passwords, and what permission images need.
Blank and an example · Word and PDF
Enlarge preview: Asset collection checklist — internalKeep it for your team, one line per requested item.
Intended use, specification, who is responsible, due and received dates, who reviewed it, status (received is not approved), whether usage rights are confirmed, where the file is, and internal comments.
Blank and an example · Word and PDF
Choose a document, a version and a format. After the first download, the others need no new form.
Word files open in Microsoft Word, Google Docs, Apple Pages and LibreOffice; we checked them in LibreOffice. US Letter landscape; change the paper size for A4. The example uses an invented web studio and florist.
Received means you have the file. Approved for use means you have checked it against the specification — the right size, the final wording — and, for images or other people’s material, confirmed you are allowed to use it. Only approved items should go live.
Not automatically. The request asks clients to send only images they own or have permission to use and to say where each came from, and the checklist has a column for confirming usage rights before an image is approved.
By inviting you as a user. The request asks clients not to send passwords, and the checklist reminds your team never to record them.