
A client's most valuable event picture is the one they can post while the room is still full. That means the work happens at the venue, in gaps you planned for, with a route off the card that does not need a desk. Here is the whole loop: what to agree beforehand, what to shoot first, how to run it from a phone, and what to do when the internet gives up.
At a corporate event, an image is worth the most while the thing it shows is still happening. The keynote quote lands while the hashtag is moving. The award shot is useful to the sponsor before the room empties. A week later the same file is an archive picture, still good, worth far less to the person who commissioned it.
So same day delivery is not a faster version of your normal job. It is a second, smaller job running alongside the first, with its own list, its own deadline and its own kit. The photographers who make it look easy are not editing quicker than you. They decided weeks earlier which fifteen minutes of the day belong to production, and defended those minutes.
Everything below assumes a live set: a handful of finished images that go out during the event, or before you leave the car park. The full gallery follows on your normal schedule, and event delivery timelines covers what that second promise should sound like. If a live set is new to your packages, price it rather than absorbing it: selling fast turnaround as an add on covers the menu version, and sizing a one off rush request covers the client who asks the week before.
Send photos quickly is not a deliverable. It is an anxiety with no shape, and if you accept it as the brief you will spend the day guessing what someone meant. Before the event, get the live set written down: how many images, of what, to whom, by when.
Five questions on the pre event call do most of the work.
Then insist on one named contact. Five stakeholders texting do you have any crowd shots is a faster way to lose the afternoon than any lighting problem. The producer collects requests, you send to the producer, everyone else reads the folder.
Keep the number small on purpose. Three to ten strong frames per major moment is usually plenty for a social team, and a big same day dump makes their job harder, not easier. They have to choose too.
Three to five edited images per named moment, sized for social, in the shared folder within thirty minutes of that moment ending, sent to one contact. The full gallery follows on the normal timeline. Everything you might argue about later is in that sentence.
Keep a short priority list separate from your full coverage list, and get those frames safe before you go looking for the rest of the story. For a conference that might be exterior branding, a busy registration desk, a wide of the keynote, a close of the speaker with the screen readable, an audience reaction, the award handover, the sponsor activation, and one energetic networking frame. Everything after that is the gallery.
While you shoot, think in finished posts. Leave air around the subject so the frame survives a square or a vertical crop. Wait the extra beat for a version with nobody in the foreground. Photograph signage when the text is readable. Take a wide and a close of the same moment so the team has a scene and a face rather than two similar scenes. These are small decisions in the room that save a fifteen minute search later, and pulling a vertical set gets far easier when the frames were shot with room to lose.
If you can put two people on the job, do. One stays on coverage, the other ingests, picks, edits and sends. Solo, schedule production into gaps the agenda already has: the transition between the keynote and the breakouts, the queue for coffee. Write those windows on the run sheet. What you must not do is disappear during the only award presentation of the day to build a folder.
The part most guides skip is the handoff from camera to something that can post. There are two routes, and the mistake is picking one for the whole day rather than choosing per moment.
| Route | What it needs | Where it wins | Where it bites |
|---|---|---|---|
| Card to phone or tablet | A card reader that fits your phone, or the camera's transfer app, plus one editing app you know well | One to five images during a changeover, standing at the back of the room, sent or posted within minutes | Large RAW files crawl, a phone screen in a dark ballroom flatters everything, and comparing two near identical frames is uncomfortable |
| Card to laptop | Laptop, fast reader, an SSD, power, and a folder template built before the event | Anything past about ten images, a set that must look consistent, files going to print or the lobby screen | You need a table, twenty uninterrupted minutes, and you are not in the room while you use them |
The phone route is what makes before you leave the venue realistic, and what makes it fast is file size. Shooting RAW plus a small JPEG gives you a file that lands on a phone almost instantly while the master stays untouched on the card. The gotchas, including what happens to your edits and file names, are in the RAW plus JPEG rush workflow.
The slow part of a live set is the first look: forty frames of one speaker and a decision to make about all of them, standing up, with ten minutes left. Kepla's picking app for iPhone, iPad and Mac is still being built. When it lands it checks a shoot against clear criteria and hands you a shortlist, so that first pass can happen on the phone in the room instead of on a laptop in a corridor. It never deletes, moves or renames a file. Everything it did not pick stays exactly where it was, one tap away. The booking page is live and free today.
A live image has to be accurate and quick, not perfect. Exposure, white balance, a crop, a straighten and a gentle contrast move carry almost every frame you send during an event. Do that much well and stop. Retouching, compositing and careful skin work belong to the gallery, and promising them live is how a thirty minute window becomes ninety.
Two things trip up phone edits at events. Stage lighting and LED walls throw color casts that look fine on a small bright screen and obviously wrong on a laptop the next morning, so judge white balance against something you know is neutral, like a white tablecloth or the venue signage. And a dim room makes you over brighten. Glance at one file on a laptop early in the day to calibrate your eye, then trust that reference.
Set your export before the event, not during it. Around 2,000 pixels on the long edge in sRGB is a common social size and leaves room to crop, with file names carrying the client and a sequence number so nobody is guessing which of six similar files is current. Keep a separate high resolution export for press or print and send it later. Do not let one enormous file hold up the live set.
Last, look at each image where it will live. A horizontal frame that reads well on a laptop can be unreadable once a story crop takes the sides off it. If vertical is part of the plan, send a deliberate vertical, not a landscape and an apology.
The reliable system is a short loop you repeat, not a heroic push at the end. Shoot the priority moment, ingest a small batch, pick fast, edit only the winners, export, send. A small set that arrives while the moment is live beats an ambitious one that arrives after everyone has gone home.
The keynote loop looks like this.
Time your own loop at the next event and write the real number down. Build the day's plan around that number rather than around optimism. If the loop runs long, the fix is almost always fewer images per moment, not faster clicking.
Avoid sending ten versions of the same podium gesture. A wide scene, an interaction, a reaction and a clean frame of the speaker do more work than a burst of near identical arms. The same instinct across a whole corporate shoot is in picking corporate work.
Pick one place for requests and one place for files, and say so at the start of the day. A shared channel, a thread with the producer, or a cloud folder with obvious subfolders all work. What fails is images going out by three routes, because within an hour nobody knows what has been sent and you answer the same question twice.
Name folders after the slot rather than the content: 1030-keynote, 1215-awards, 1600-networking. A team scanning a drive at speed needs to know when something happened. If the images are going to press, captions stop being optional and the filing conventions matter, which is the subject of getting the first ten out the door.
Two copies before any card gets formatted, every time, no exceptions for speed. The whole appeal of same day work is looking reliable, and a lost card at a corporate event costs more than the fee. Keep the card in the bag until the second copy is verified. Write the routine down once and then follow it without thinking, and a simple backup workflow is a good starting shape.
Your update message should be short and factual: what is in the folder, how many files, and what the pictures show. That lets a busy marketer act without opening every file, which is the actual product you are selling.
Live work fails in predictable ways, so decide the fallback while you are calm rather than at 4pm with a producer standing over you.
The internet. Venue wifi is busiest exactly when everyone wants to post. Test it early, bring a hotspot, keep local copies of every export, and never tell a client a gallery is live until you have seen it live.
Power and updates. Turn off automatic updates the week before. Carry a battery bank, a spare cable and more cards than you think you need. A phone at nine percent is a workflow failure, not bad luck.
The contact vanishes. Producers get pulled into rooms. Agree a second name at the start of the day, and a default: if nobody answers, files go to the shared folder and you send one message saying where they are.
The agenda moves. It always does. Photograph the run sheet on arrival, and when the award slot slides an hour, rewrite the priority list rather than holding two plans in your head.
Put a plain line in the agreement: delivery windows start when the images are safely on your drive, and can be extended for things outside your control. Same day delivery becomes a service you can sell repeatedly once it stops depending on everything going right.
For most live social needs, three to ten strong images per major moment is plenty. Agree the number by time block before the event rather than by total. A very large same day set slows the marketing team down, because now they have to choose too. Deliver the full gallery afterwards on your normal timeline, and say clearly which is which.
Yes, if the promise is a modest highlight set and the agenda has real breaks in it. Solo works when you schedule production into the gaps between sessions and keep the count small. For nonstop conferences, large awards shows, or a client who wants continuous posting, a second shooter or a dedicated editor is the more reliable answer.
Use the phone for one to five images during a gap, when speed matters more than a perfect crop. Use the laptop for anything larger, anything that has to look consistent across a set, and anything going to print or a big screen. Most photographers running same day work end up using both across a single event.
Test it when you arrive, but never depend on it. Uploads stall at busy venues exactly when everyone else is trying to post. Bring your own hotspot as a backup, keep local copies of every export, and confirm the gallery actually loads before you tell the client it is there.
Price it as an add on rather than folding it into your day rate, because it changes how you staff and schedule the job. Work out the extra hours, any second person, and the capacity it uses up, then quote one flat number. Treat the live set and the full gallery as two separate deliverables with two separate deadlines.
Kepla for Mac clears the obvious misses from a card, names the reason on every frame it sets aside, and leaves the choosing to you. Nothing is ever deleted, moved or renamed. Free through the private preview · the first hundred photographers keep it at $99 a year.