Forum Replies Created
-
Posts
-
Amanda, I love your presentation. Not too much info (therefore not overwhelming), but you get your message across perfectly. I made the mistake of branding my EHD boxes with my logo on the top as per most photographers. Adam’s suggestion of doing this with the client’s name instead on the top (and a sticker of my biz on the inside or bottom) makes it more client-centric; which is as it should be IMO. Oh well, next time!
But I need to do the nice “before and after” text block like Adam, even though its pretty obvious 🙂 It looks better that way!
We had this situation many times. A recent client gave us a folder called “Private” but we still saw her images while sorting, despite not wanting to (there were also dupes she was unaware of). What we tell clients to do is to literally remove them from the collection – if small enough in size they can live on a thumb drive. That way they are truly separate and private.
But yes, seeing photos you wish you could unsee is par for the course. Every job we’ve done has them. Even if they aren’t private images, some are just gross ones (i.e. images of  kid’s injuries that concerned parents send their doctors and then forget to delete, or the ever-popular giving birth photos). I get a bit queasy seeing these images, honestly. But it’s an inevitable part of the job (and then there’s financial info, legal info etc – a whole different ball game).
Here’s a question about this. Back in Jan 2017, I was working with a client and using the long Digital naming convention for each file (month/day/year/who-what-where-when etc ie 07_01_1980_Morgan’s 16th birthday_GreenLeafCafe_Boston_MA). Two things I’m finding, three years later : (1) Custom naming is too time consuming and few clients will be willing to pay for the many many additional hours of work, and (2) naming seems to be a superfluous step and can’t be seen on your iPhone or in an APL. No one really looks for photos based on names.
With that said, if I do a maintenance/subscription service with this client, moving forward the naming will be inconsistent with how I was naming back in 2017. Will that inconstancy seem strange in a client’s growing collection? Should there be any concern there?
Recent Comments