Website Content Collection Checklist: Request Logos, Photos and Copy
A client asset checklist and copyable request message for website projects, with a small Request setup that respects current Free limits.
A website project can stall because the logo is buried in a chat and nobody knows which product description is final. Give the client a concrete list: what to send, which version, where it belongs and when you need it.
This is a working checklist, not an automatic approval system.
Materials to request
| Material | Instruction |
|---|---|
| Logo | Send the approved file and explain light/dark background use. |
| Product photos | Identify the product and send the source within the upload limit, not a screenshot of a chat. |
| Page copy | Label each text with its page and mark it as final or draft. |
| Usage information | Name the owner, usage restrictions and person approving publication. |
Request only the current stage's assets. Keep account passwords and unrelated customer records out of the package.
Copyable message
Please send the approved logo and homepage introduction by [date] using [request link]. Add the project reference and mark items as final or draft. Tell me about usage restrictions. If a file exceeds the displayed limit, contact me first. I will review the submission and confirm separately.
Send this by email or your usual client messenger. Upload confirmation means receipt, not approval.
Make the request fit your plan
In LOCK.PUB, sign in to a connected account and open Create Request. Guest request creation is not available. A small Free request can use one file block for the logo and one memo block for the introduction.
Free allows 2 blocks, 3 submissions and 1 file per file block up to 5 MiB. Instruction blocks count too; put short directions in existing block descriptions. Each block consumes a monthly creation credit, and shared upload allowances apply.
Pro/Business allows 10 blocks and 100 submissions, with 5 files per file block, up to 10 MiB each. Image blocks have separate limits. This is not unlimited asset collection.
Review what arrived
Keep your unlock password private; only share the optional submit password. Ordinary submitters need no account, though configured Business recipient restrictions may require sign-in.
Read submissions in your dashboard after unlocking their encrypted content. Keep public instructions and filenames free of secrets. Track missing items and approval yourself: this workflow includes neither automatic reminders nor Google Drive synchronization.
See the request guide, then create a focused request for your project's next materials.
Create Request
Create RequestKeywords
You might also like
Google Forms File Upload Without Sign-In: What Actually Works
Why Google Forms requires sign-in for uploads, which alternatives accept files without registration, and how to set up a small file request.
Turn a Photo into a QR Code with Password Protection
Create an image link, display its QR code, download a PNG from the dashboard and check the recipient experience, with current limits.
Password Pusher Alternatives: Compare Hosted Sharing and Self-Hosting
Compare Password Pusher with LOCK.PUB for password handoffs: passphrase requirements, one-time access, hosted editions, self-hosting and encryption limits.