Photography as Brand Infrastructure
Photography as Brand Infrastructure
Planning Project Imagery for the Work It Will Need to Do After Completion
AEC project photography is often commissioned for a specific reason. A project is nearing completion, an award deadline is approaching, a website needs updating, or leadership needs images for a presentation.
The assignment is scheduled around that immediate need, but the images rarely stay there. Over time, the same project may support proposals, sector presentations, recruiting, publications, stakeholder communication, and future business development.
That does not necessarily mean the photography was planned for those responsibilities. A firm can use photography constantly and still underleverage it. Reuse happens after delivery. Leverage begins when the responsibilities an image library is likely to carry are allowed to influence the original planning and scope. Photography cannot reliably solve communication problems it was never planned to address.
The Commissioning Trigger Is Not the Whole Assignment
The reason photography is scheduled matters, but it should not automatically define the entire image set. An award submission may create the immediate deadline while the firm reasonably expects the project to support future pursuits. A completion announcement may require only a few flagship images, while later sector marketing may depend on technical spaces, human use, site relationships, or supporting views that would never appear in the announcement.
The goal is not to anticipate every possible future use. The more useful questions are: What will this image library reasonably be expected to do after the immediate need that caused us to schedule photography? Would any of those foreseeable responsibilities materially change what we should photograph now?
If the answer is no, the original scope may be entirely sufficient. If the answer is yes, that is where a narrowly defined assignment can become an underleveraged one.
Used Imagery Is Not the Same as a Leveraged Image Library
AEC marketing teams are skilled at making available photography work. An image commissioned for one purpose may later appear in a proposal, recruiting presentation, or leadership deck. Using the same photographs in more places is not the same as building a more useful image library. A team can reuse an incomplete library for years simply because those are the files it has.
The more useful question is whether the project was documented with enough range to support the responsibilities the firm could reasonably foresee. That may require context, supporting views, human use, technical evidence, or a scale of photography the immediate assignment would not otherwise require.
If every image has to do everything, the image set was probably asked to do too little during planning. The objective is not more files. It is an appropriately complete image set.
Repeated use does not create a complete image library. The range of the original documentation determines what the project can make understandable later.
Appropriate Completeness Matters More Than Maximum Volume
Strategic planning should not become an argument for larger photography assignments by default. Everett High School is a useful example. The engagement focused on a targeted exterior renovation, and the final image library was comparatively small. Daylight, aerial, and twilight photographs each carried a different responsibility and provided enough range for the project.
The work was later used in a verified award submission, but the larger lesson is simpler: scope should be proportional to responsibility.
A complete image set may contain six photographs. Another project may require dozens. The determining factor is not volume. It is whether the final set contains the visual evidence the project actually needs.
Sometimes the Responsibility Is Larger Than the Individual Building
Michigan State University’s Grand Rapids Medical Mile provides a different example. The assignment involved several facilities, but the communication objective was not simply to create separate architectural records of each building. The larger responsibility was to make MSU’s accumulated institutional presence in Grand Rapids understandable.
Ground-level photography established the individual facilities. Aerial imagery showed their relationship within the larger corridor. The resulting imagery was later used in a university-president presentation concerning MSU’s regional investment.
The important point is not simply that the photographs appeared in a presentation. The communication responsibility influenced what visual evidence was required. Had the assignment been scoped only around individual building photographs, the larger institutional relationship would have been harder to communicate.
One Project May Carry More Than One Professional Responsibility
The same issue appears in multidisciplinary work. At University of Michigan Health-Sparrow, the completed project included public-facing architecture, clinical environments, technical systems, engineering interests, exterior relationships, and active healthcare operations.
A strong architectural portfolio selection could still have been incomplete for the organizations involved if those other responsibilities had never entered the planning process. This does not mean every stakeholder needs every image or that every project requires a larger shared scope. It means the team should recognize when one discipline’s preferred image set would not fully represent the significance of the completed work.
When Photography Begins to Function as Infrastructure
AEC firms can accumulate thousands of photographs without building a particularly useful project library. Quantity does not solve missing context, absent technical evidence, or an incomplete record of how the architecture is used.
Photography begins to function as infrastructure when the firm can rely on the image library beyond the moment that triggered production. Not because the assignment was large or every future use was predicted, but because foreseeable responsibilities were considered while there was still an opportunity to shape the work.
That is the difference between an isolated deliverable and a deliberately structured project image library. Once the team understands what responsibilities that library may need to carry, the next question is how those responsibilities become production requirements.
That is where The Briefing Structure begins.
Would you like keep up with our latest work?
Follow our happenings by subscribing to our social media accounts
connect with us
