The collection run sheet
A practical checklist for the pictures guests take
Put a wedding guest photo checklist beside the seating plan, not inside a photography contract. Its job is to make a few ordinary decisions clear: who invites contributions, where the link lives, which moments are welcome, and who checks that the files actually arrived. Guests can then enjoy the wedding rather than becoming an unpaid production team.
How-to walkthroughs and honest comparisons of the options.

Give every collection job a named owner
Start with responsibility rather than equipment. A collection can be beautifully prepared and still be neglected because each person assumes someone else is checking it. Write a person's name beside the guest invitation, the printed signs, the upload test, and the final download. These are separate jobs even when one person takes several of them. The couple should approve the choices without having to answer every phone question between speeches. A friend can explain a sign without being given account access, and a venue coordinator can place stationery without becoming responsible for private photographs.
Assign these before buying stationery
- Choose the event owner who will control settings and remain contactable after the wedding. Confirm which email address receives event information and who will notice the collection's closing date.
- Name a guest helper who knows the upload route. Their role is to demonstrate on their own phone, explain the browser page, and find the host when a setting needs attention.
- Ask one person to check physical placement after the room is laid. A florist moving a stand or a caterer adding a menu can hide a code that was readable during setup.
- If a screen is planned, name its operator separately. Do not assume the person answering upload questions can also watch a projector and review submissions throughout dinner.
Keepsake includes two extra event managers. Informal help with signs or announcements does not grant management permissions, and other packages should not be planned around extra manager access.
Choose moments guests can capture without intruding
A useful request fills the gaps around professional coverage. It does not tell guests to crowd the aisle, repeat the formal group list, or record an entire ceremony through a raised phone. Ask the photographer and celebrant where phones should stay away. Then select optional prompts for the parts of the day where guests already have a natural view. Someone sitting beside a grandparent may catch a conversation the couple never sees. Someone waiting for transport may photograph the cheerful aftermath. Neither needs a timed assignment or a promise to deliver a fixed number of images.
- Before the ceremony
- Welcome hugs, friends arriving together, or a view of the finished room can be useful. Do not ask guests to enter private dressing spaces or interrupt preparations for a photograph. Respect any unplugged period announced by the couple.
- During the reception
- Invite a table portrait when everyone is comfortable, a detail someone made by hand, or a candid conversation. Let people finish eating first. A request should never make a guest feel watched while they are resting or looking after a child.
- At the end of the evening
- A goodbye, a dance with friends, or the last shared laugh can round out the collection. Avoid encouraging photographs of someone distressed, intoxicated, or needing assistance. Being memorable does not make a moment appropriate to share.
Prepare phones without making guests do homework
Keep the technical preparation proportionate. Candid Photos opens in a guest's browser; guests do not need an app, an account, or a password. They still need a working internet connection to send files, and the browser may ask them to complete the details and consent fields shown on the upload form. A message before the wedding can explain the destination and reassure people that they can send selected photographs later. There is no need to ask everyone to practise in advance or change camera settings they do not understand.
For willing helpers
Charge a phone and bring the cable that fits it. Save the guest address somewhere easy to find. Open that address on the phone you intend to use, rather than assuming that a successful host login proves the guest journey works. Keep a harmless test image ready for the venue check.
For ordinary guests
Ask them to keep their original files and choose only pictures they are happy to contribute. If a photograph is stored in a cloud library rather than on the device, retrieving it may also need connectivity. They should not delete originals after selecting files or assume that selection means delivery.
For anyone who needs assistance
Offer a short demonstration and let the guest keep hold of their own phone. Read the instructions aloud if helpful, but let them choose the images and enter their own details. A companion can help with permission; a public table is not the place to browse someone else's camera roll.
Turn the invitation into one clear action
Use a single destination consistently across the wedding website, table signs, and later reminders. Sending guests to different chats creates a second sorting job and makes it harder to know what reached the couple. The invitation needs four pieces of information: what to share, where to send it, whether other guests may see it, and when it would be useful to receive it. Leave detailed troubleshooting off the decorative sign. A short address beneath the code gives guests another route when their camera does not recognise the print.
Wording to adapt to the actual settings
- Before the day
- We would love a few photographs from your view of the wedding. Our guest collection opens in your browser, with no account to create. Keep this link for the day or send your favourites afterwards. Please respect the phone-free ceremony and ask before sharing a close portrait.
- At the table
- Taken a picture you would like us to keep? Scan the code or type the address below, choose your photographs, and follow the upload instructions. Please leave the page open until it confirms the result. Our helper can point you in the right direction if you need a hand.
- If pictures may reach the room screen
- Selected guest photographs may appear on the reception screen. Only send pictures you are comfortable showing in the room, and ask anyone prominently pictured first. A screen notice belongs beside the upload invitation, not in an explanation given after someone's image has already appeared.
Proof the printed route at the finished table
Check the destination before the design
Copy the guest link from the correct event and open it without relying on the host's signed-in session. Confirm the couple's names and event details. Do not substitute the separate slideshow address: a screen link is not the route guests should use to contribute.
Print a real sample
Test the actual paper, printer, and final scale. A code that works on a bright laptop display may be blurred after printing or obscured by a reflective sleeve. Preserve its square shape and clear surrounding margin. Keep decorative marks and text outside the code itself.
Scan in the room
Put the sample beside the real menu and flowers, under the lighting guests will have. Test from a comfortable seated position and with another phone if available. Move the stand if a candle reflection or tall arrangement forces people to lean across glassware.
Make the fallback legible
Read the typed address aloud and check every character against the event link. It should be large enough for someone to use without photographing the whole table. Keep spare signs with the helper so a spill or a last-minute seating change does not remove the only instruction.
Record two separate results: the camera recognised the code, and the destination opened. The first tests the print; the second tests the address and connection. If the camera offers a link but the browser stalls, redesigning the stationery is unlikely to solve the immediate problem. That distinction prevents unnecessary reprinting on the morning of the wedding.
Agree the visibility rules before anyone contributes
Decide what guests can browse, whether the host will approve submissions first, and whether a room display is appropriate. These are different choices. The host can switch on approval to hold submissions for review; describe that as an operational setting rather than attaching it to a package. Guest gallery visibility is another setting, and an upload-only guest page should not be treated as proof that a separate slideshow cannot show photographs. Test the whole intended arrangement. Guests should understand the audience before they send a family picture, not after an enthusiastic relative shares the address elsewhere.
- Ask the couple about children, guests who do not want to be pictured, and any sensitive family circumstances. Give the helper a discreet way to receive concerns without placing names on public signs.
- Tell contributors whether photographs are for the couple, available in the guest gallery, or intended for the room screen. Upload permission is not permission to reuse an image in a supplier portfolio.
- Keep the guest link within the intended invitation group. A link that is easy to use is also easy to forward, so avoid publishing it in an open social post unless that wider audience is genuinely intended.
- Give guests a person to contact about a picture. If something inappropriate reaches a live display, the screen operator should be able to blank the output while the host handles the content.
Run a small end-to-end rehearsal
A rehearsal should prove delivery, not merely show that the landing page loads. Join the same guest network that visitors will use, complete any venue sign-in page, and send a harmless photograph through the printed code. Wait for the file's result. The host should then locate it in the collection, including the review area if approval is enabled. If there will be a slideshow, test that separately on the display machine. Keep the test small so it does not consume a meaningful part of the event allowance, and remember that a quiet-room test cannot guarantee performance once the venue fills.
Capacity decisions for the rehearsal sheet
- A limited trial
- Preview is free and allows 20 photos, no videos, 10 contributors, 500 MB, and seven days online, with no downloads. Its written guestbook and live slideshow are separate optional USD 9 add-ons each. Use it knowingly as a trial, not as an unexamined plan for a large wedding archive.
- The intended collection
- Check the chosen photo count, video count, storage allowance, and closing period against the invitation you are making. These are separate limits. Asking for lengthy clips changes storage needs even if the number of contributors stays the same. Package prices are one-off US-dollar charges per event, not a subscription promise.
- The result to record
- Write down which phone, room, and network were tested and whether the host found the file. If a test fails, keep the message and time rather than writing only 'Wi-Fi bad'. That detail lets the next helper distinguish an access problem from a file or account limit.
Close the loop after the last dance
Before guests leave
Leave a route home
Make the guest address available in the wedding message thread or website so the table stand is not the only way back. Say that later uploads are welcome within the collection's open period. Guests with weak reception can keep their pictures and deliberately return on a better connection; there is no offline delivery guarantee.
After the wedding
Send a specific reminder
Ask for photographs people have not already sent, especially moments the couple missed. Give a real date chosen within the event's remaining online period. A personal thank-you and a direct link are more useful than a daily request to empty an entire camera roll. Do not pressure someone who has chosen not to contribute.
Before the collection closes
Verify the handover
On a package with downloads, assign time to download the collection and open representative files. Check that important contributions are present and keep a separate backup in storage controlled by the couple. Original-quality downloads are included with Celebrate and Keepsake; Gather provides standard downloads. An online collection with a closing date is not the final archive.
Mark the checklist finished only when the couple knows where the saved files are. A successful party and an empty handover folder are different outcomes. If a planner or friend has managed the work, send a short final message with the saved location, any outstanding uploads, and the date after which the online collection should no longer be relied on.
Checklist questions that arise on the day
Should we give every table a photography assignment?
Optional prompts are kinder than quotas. Ask for a table portrait or a favourite detail if people want to participate, but avoid duties that interrupt the meal or exclude guests who are not comfortable using a phone.
Does a finished progress bar mean the picture is visible to everyone?
Not necessarily. Check the upload result, and remember that a received submission can be waiting for the host's review. Guest gallery visibility and room display settings also affect where an accepted picture can be seen.
Can one guest upload on behalf of a relative?
They can help with the relative's permission and agreed file selection. Do not assume possession of someone else's phone gives permission to inspect or share its contents. Keep the contribution and its intended audience clear.
What should we remove from the checklist if time is short?
Drop elaborate photo prompts before dropping the link test, consent notice, or named handover owner. A small collection that reaches the couple safely is more useful than an ambitious plan nobody has time to operate.
Prepare the collection, then let the wedding happen
Create the event, test one guest upload, and put names beside the few jobs that remain. Once the route, audience, and handover are settled, the checklist can stay with the helper while everyone else enjoys the day.
Guides and comparisons
Put one link on the tables and let everyone contribute.
Create a collection, print the table stands, and the photographs your guests took are waiting for you the morning after. Guests never install anything and never make an account.