Architectural Photography Approval: The Two-Client Problem

Why a single-client approval process breaks on architecture jobs

Most photo approval workflows assume one client with one set of priorities: review the gallery, mark selects, send notes, sign off. That model holds for a portrait session or a small product shoot. It doesn't hold here, because the two people reviewing an architectural gallery aren't evaluating the same thing.

The firm is judging craft: does the shot represent the design intent, is the perspective correction clean, does it belong next to the rest of their portfolio. The developer is judging risk and usage: is there a visible crack in the facade, a parked contractor van in frame, a competitor's signage across the street, anything that makes the image unusable in a leasing deck or a press release. Those two lenses genuinely conflict sometimes — a wide, dramatic angle the firm loves can be the one angle that shows a neighboring lot the developer would rather not advertise next to.

When both parties get the same undifferentiated review link, you end up fielding two rounds of notes that don't reference each other, reconciling them yourself, and often re-presenting a set that satisfies neither reviewer fully. A typical version: the firm asks for a different crop on the hero exterior to straighten a lens-correction issue, while the developer, looking at the same original frame, asks you to swap that exterior out entirely because a competitor's billboard is visible in the background. You now owe two edits to two people who don't know about each other's note, on a shot neither of them realizes the other is also revising. The problem isn't that the developer or the firm is being difficult. It's that nobody defined what each one is actually being asked to approve, or in what order.

Split the review: what the firm signs off on vs. what the developer signs off on

The workable version of this splits approval into two passes with different scope, run in a fixed order rather than in parallel. The firm reviews first, for craft and technical accuracy. Only the frames that clear that pass go to the developer, who reviews for usage and commercial risk. Neither party is asked to weigh in on the other's domain.

This ordering matters as much as the split itself. Reviewing craft after commercial approval wastes the firm's time on frames that were never going to be used; reviewing commercial fit before craft approval means the developer signs off on something that might still get technically rejected. Firm first, developer second, keeps each round meaningful.

It also changes what each reviewer needs from the gallery itself. The firm typically wants to see full exteriors and interiors together, in shoot order, so they can judge how the set reads as a whole. The developer usually only needs the subset earmarked for a specific use — the leasing deck, the press kit, the website hero — and reviewing the full uncurated set just slows them down with frames that were never going to be used commercially. Scoping the developer's link to the firm-approved subset, rather than sending the same gallery twice, is what keeps the second pass fast.

Name a tie-breaker before the shoot, not during the dispute

Splitting scope removes most conflicts, but not all of them — a shot can pass both reviews individually and still have the firm and the developer disagree on which of two similar frames should be the hero image. That disagreement is normal. What causes it to stall a project is not having already answered, in the contract or the shoot brief, who wins.

This is the same principle that applies to any multi-reviewer creative approval: a group can debate, but exactly one person has to be able to end the debate. Without that, feedback rounds don't converge, they just alternate.

Some jobs add a third party into this mix — a marketing agency handling the developer's leasing campaign, briefed to select from your delivered set rather than review the shoot directly. When that's the case, treat the agency as an extension of the developer's review, not a third independent reviewer: they work from the firm-approved, developer-approved set, and any new note they raise routes back through the developer, not straight to you. Adding a genuinely independent third sign-off is what turns a two-round process into an open-ended one.

Bound the revision rounds before you start

Two-tier review doubles your reviewer count, so it's worth being explicit about how many rounds each tier gets. A common structure — and a reasonable default if you don't already have one — is two rounds per reviewer: an initial pass and one consolidated revision, with anything past that billed as a change order. That's not a mandate, it's a starting point that gives both sides room to ask for something while stopping the loop from running indefinitely.

Write the round limit into the shoot brief, not just the fine print of the invoice terms, and define what counts as one round: a single consolidated set of notes gathered and sent together, not a running stream of individual comments trickling in over several days. A round that never formally closes because notes keep arriving one at a time isn't really bounded, even if the contract technically caps it at two.

The turnaround math is worth doing out loud with both parties, because it's what makes the bound feel fair rather than arbitrary. If each reviewer commits to a 3-business-day turnaround per round, two rounds each, run in sequence (firm, then owner, not simultaneously, since the owner shouldn't be reviewing frames the firm might still reject) works out to at most 4 review passes × 3 business days = 12 business days from first proof to final sign-off, worst case. Most jobs won't use every round, but quoting that ceiling upfront — instead of an open-ended "we'll get you notes soon" — is what gets a leasing or launch deadline actually respected.

A sequence that works for firm-and-developer shoots

In practice, the order that avoids re-litigating earlier decisions looks like this:

1. Culled set to the firm. Send your edited selects — not the full card — scoped to craft review only.
2. Firm's technical pass. Firm approves or flags frames on composition, retouching, and portfolio fit. Rejected frames don't move forward.
3. Firm-approved set to the developer. The owner only ever sees images the firm has already cleared, so their review is exclusively about usage.
4. Developer's commercial pass. Owner approves for marketing use, flags anything with visible defects or competitive exposure.
5. Named tie-breaker resolves any remaining disagreement on the handful of frames both parties flagged differently.
6. Final delivery to both parties, with the same final set — not two different galleries with different frames in them.

The version of this that fails is sending the full unfiltered gallery to both parties at once and hoping they self-organize. They won't, because they're not reviewing for the same thing, and the notes that come back reflect that.

Interiors and exteriors are worth splitting further within step one if the shoot covers both, since the firm's craft standards for each differ — lighting balance and styling matter more for interiors, verticals and material rendering matter more for exteriors. Reviewing them as one undifferentiated set makes it harder for the firm to give feedback that's specific enough to act on, and specific feedback is what keeps a round from needing a second round.

What this looks like with review software instead of email

You can run this two-tier sequence over email threads, but it's easy to lose track of which version each party last saw, especially across the 12-business-day window above. If you're already tracking approvals for other shoot types — see our notes on whether you actually need a DAM or just a structured approval workflow — the same tool that handles a single-client review can usually scope a second review link to the developer, gated behind the firm's sign-off, without you manually re-uploading a filtered set for each stage. Appruva supports exactly this kind of staged, scoped review: one link for the firm, a second link that only unlocks the firm-approved frames for the developer, with the named tie-breaker able to see both rounds of notes side by side.

If a chunk of your architectural work overlaps with commercial real estate listings for the same developers, the delivery-side version of this same problem — getting a finished set out fast once approval closes — is worth reading too: how fast real estate photo delivery actually needs to be.