How to collect assets from photographers, agencies and colleagues

Every DAM conversation is about finding and sharing. Almost nobody talks about how assets get in. Which is odd, because delivery is the one moment when everything you'll later need to know about an asset is still in somebody's head.

The photographer knows what the shoot was for, who's in frame, and what the client agreed to. The agency knows which files are the finished versions. The colleague at the trade fair knows which stand is in the picture. Twenty-four hours later? All of that's gone, and you're holding IMG_8842.jpg and a link that expires on Thursday.

Collecting assets well comes down to one move: give every photographer, agency and colleague a permanent upload link into your library, and capture rights and context at the moment of delivery, while the person who knows is still paying attention.

The default intake process, and why it fails

For most teams it looks like this:

1. Photographer uploads to WeTransfer or a personal Drive
2. Emails a link to whoever commissioned the shoot
3. That person downloads a zip, keeps the good ones, drops them in a folder
4. Everyone else finds out the photos exist by asking

Five failure modes, all of them predictable:

The link expires. Nobody downloads within seven days because the event ran long. The photographer re-sends. Or doesn't.

One person is the bottleneck. Assets only exist once the commissioner has processed them. If they're on holiday, the campaign waits.

Context evaporates. The photographer's knowledge never leaves their head. Nobody writes down who's in the pictures, whether releases were signed, or what the licence actually permits.

Rights are never captured. This is the expensive one. Two years later somebody wants that shot for a paid campaign and there's no record of what was agreed. So one of two things happens: the asset gets used anyway, or a perfectly good asset sits unused because nobody can confirm it's safe. Both cost money.

The delivery is the only copy. The selects get kept; the rest quietly disappears. Six months later you need a different crop from the same shoot, and it's gone.

None of this is the transfer tool's fault; it was built for sending, not keeping. Why teams outgrow WeTransfer looks at the alternatives, including when a transfer tool is honestly all you need.

What good intake looks like

One principle: capture context at the point of delivery, from the person who has it, and make delivering so easy that they actually do it.

Three components.

1. A permanent, personal upload link

Give every contributor (photographer, agency, regional office, the volunteer with a phone at your event) a durable link that drops files straight into the right place in your library. No account. No software. No expiry date.

This matters more than it sounds. Every extra step between "I've finished the edit" and "the client has the files" is a step where the process quietly reverts to WeTransfer. If uploading to your library is harder than emailing a link, they'll email a link.

The link should be scoped: it accepts uploads into one defined area, it doesn't let anyone browse the rest of the library, and you can revoke it the day the contract ends.

2. A short form at the point of upload

This is where the value gets created. Ask for the two or three things only the uploader knows:

• What is this? (shoot, event, campaign, picked from a list rather than typed)
• What may we do with it? (licence terms, and whether model releases were obtained)
• Who or what is in it? (optional, and increasingly AI's job)

Stop at three fields. Every field you add measurably lowers the odds the form gets filled in, and a skipped form is worth exactly nothing. AI will describe what an image shows the moment it arrives (AI search in a DAM explains how), so don't spend your three questions on things a model can answer.

The rights question is the one that pays for the whole exercise. One dropdown (full use / campaign only / internal only / editorial only) plus an expiry date where relevant, and you've prevented most of the licensing incidents teams otherwise discover the hard way.

3. Review before publication

Uploads land in a staging area, not the main library. Someone with context checks them, confirms or corrects the metadata, and approves.

This keeps quality up without recreating the bottleneck. The reviewer isn't filing from scratch. They're approving assets that already arrive with descriptions, rights and context attached. A few minutes' work, not an afternoon. And crucially, the assets exist and are backed up from the second they're uploaded, before anyone has reviewed a thing.

Working with external photographers

Some practical detail here, because this is the most common case, and the most valuable one.

Put it in the brief. Delivery method belongs in the commissioning email, right next to the shot list and the deadline: "please upload to this link when the edit's done". Retrofitting a new process after the shoot never works.

Ask for the whole edit, not the selects. Storage is cheap; reshoots aren't. If the photographer delivers 400 processed images and you use 12, the other 388 are next year's campaign. Take them, archive them, and let search dig them up later.

Agree the licence in writing, then record it on the asset. The contract lives in a folder somewhere. The licence needs to live on the file. When someone opens that image in three years, the terms should be right there, no email archaeology required.

Ask them to embed IPTC. Most photographers already fill in creator, copyright and caption fields in Lightroom. Those travel inside the file and import automatically. It costs them nothing and gets you accurate attribution for free.

Support their tools. A Lightroom export plugin that publishes straight from the catalogue removes the last bit of friction. If your DAM offers one, set it up during onboarding, not as a footnote three months in.

Working with agencies

Agencies produce more than finals. They produce the layers underneath. That distinction matters most on the day the relationship ends.

Specify deliverables, including working files. Layered PSDs, INDD packages with links, editable video projects, the fonts they used. Skip this and a small change to a brochure means recommissioning the agency that made it.

Give them a scoped workspace, not a shared drive folder. They upload into it, they see what they need, and they lose access cleanly when the engagement ends. Revoking a workspace is a click; chasing files off an agency's server is a conversation.

Write an offboarding step into the contract. Everything delivered, in the DAM, before the final invoice gets paid. One clause, and it prevents the most common form of asset loss there is.

Collecting from colleagues

Internal contributors are the biggest untapped source in most organisations. Sales teams photograph installations. Site managers document projects. Regional offices run local events. And almost none of it ever reaches the central library.

The reason is always the same: the path is unclear and the effort goes unrewarded.

Make the path a single link. Not "request access to the DAM, wait for provisioning, log in, find the right area". One URL. Works on a phone. Uploads straight from the camera roll.

Ask for one thing. Where and what. That's enough for the library to be useful; AI fills in the rest.

Close the loop. Tell people when their photo gets used. It's the only reliable way to keep voluntary contribution alive, and it costs nothing.

Smulders runs this at construction-project scale, where the people holding the camera are on site and the people who need the images are in a tender team somewhere else entirely.

Handling volume from events

Events flip the problem on its head: not too few contributors, but too many files, too fast, with people wanting them immediately. Several photographers shooting at once, thousands of frames, and a communications team that needs the first images live within the hour.

The pattern that works is upload-as-you-go, not deliver-at-the-end: photographers push batches during the event, AI describes and clusters them on arrival, and the social team pulls from a live stream of material instead of waiting for a handoff. Distributing event photos covers the whole playbook.

A checklist

• Every regular contributor has a permanent upload link
• Links are scoped to a destination and revocable
• No account or software required to upload
• Upload works from a phone
• A form captures purpose and rights, in three fields or fewer
• Rights are a controlled list, not a free-text note
• Uploads land in review, not directly in the library
• Contributors are told when their material is used
• Delivery method is written into briefs and contracts
• Agency contracts specify working files and an offboarding handover
• Photographers are asked to embed IPTC metadata

Frequently asked questions

How should photographers deliver files to a marketing team?

Through a permanent, scoped upload link into the team's asset library, with a short form capturing the shoot, the licence terms and whether model releases were obtained. Transfer services work fine for delivery but expire, so they should never be the archive.

What is an upload link or upload zone?

A public URL that accepts files into a defined area of a DAM without the uploader needing an account. It can enforce metadata on upload, route submissions to a review queue, and be revoked independently of any other access.

What metadata should we ask contributors for?

At most three fields: what the material is, what you may do with it, and optionally who is in it. AI handles visual description on ingest, so spend the questions on context a model can't infer, especially rights.

Should we accept the full shoot or only the selects?

The full edit. Storage costs far less than a reshoot, and unused frames from a past shoot regularly solve a future brief. Archive them with minimal metadata and let search surface them.

How do we stop agencies keeping our files?

Give them a scoped workspace inside your own library rather than a folder on theirs, specify working files as contractual deliverables, and make full handover a condition of the final invoice.