Purpose
This methodology gives the Fieldlight Institute a repeatable way to document places undergoing institutional transition. It reframes the site-specific logic of Above the Institute into a general practice that can be used with campuses, civic buildings, industrial sites, cultural institutions, research facilities, neighborhoods, and infrastructure whose function or identity is changing.
The method treats a place as more than a collection of buildings. A site is a spatial system, a lived institution, a store of memory, and a public record in motion. Documentation therefore must do more than capture appearance. It must clarify relationships, preserve continuity, identify what is at risk of disappearing, and leave a record that future stewards can understand and use.
METHOD IN ONE SENTENCE
Document the institution while change is still legible: spatially, historically, operationally, and publicly.
Methodological stance
Fieldlight documents institutions from a position of stewardship. The purpose is neither promotional capture nor nostalgic preservation. It is to create a faithful, interpretable record of a place at the threshold between what it has been and what it may become.
The institution is understood as a coherent organism embedded within a wider civic, social, and ecological field.
Transition is treated as a condition worthy of documentation in its own right—not merely an inconvenient interval between stable identities.
Spatial clarity and historical continuity are pursued together; neither an architectural survey nor an oral history is sufficient alone.
Interpretation is explicit. The methodology distinguishes observation, testimony, inference, and recommendation rather than collapsing them.
The resulting record should remain useful to the people who inherit responsibility for the site.
TONE AND PRACTICE
Factual, reflective, forward-looking, non-invasive, and preservation-minded. The work informs and contextualizes rather than dramatizes. Its governing habits are restraint, accuracy, and long-form attention to site.
What this methodology is—and is not
| It is | It is not |
|---|---|
| A structured practice of institutional memory | A branding or marketing campaign |
| A layered record of space, people, operations, and change | A collection of attractive images without context |
| A basis for stewardship, interpretation, and future decisions | A substitute for legal, engineering, archival, or conservation due diligence |
| A public record calibrated to consent and risk | A demand that every observation or artifact become public |
Core principles
Stewardship before extraction
Documentation should leave the place and its custodians with greater clarity, continuity, and usable knowledge than before. Access is not ownership. Visibility is not permission.
Continuity across change
The record should show what persists, what changes, what disappears, and what remains unresolved. Continuity does not require freezing a place in time.
Spatial clarity
Buildings, circulation, boundaries, adjacencies, thresholds, utilities, landscape, and surrounding urban systems should be documented as relationships—not isolated objects.
Interpretive documentation
A useful record explains why a feature, route, ritual, or absence matters. Interpretation should remain traceable to evidence and clearly distinguish fact from analysis.
Public record with governed access
The public value of documentation does not eliminate privacy, safety, or custodial responsibility. Publication is a designed layer of the record, not its automatic default.
Transition as evidence
Temporary conditions—vacancy, partial use, scaffolding, improvised circulation, archived signage, changing access—are evidence of institutional change and should be recorded deliberately.
Plural knowledge
Administrative records, lived experience, maintenance knowledge, architectural evidence, and public memory each reveal different parts of the institution.
Ethical commitments
Name the commissioning relationship, intended audience, and intended uses of the record.
Obtain permission appropriate to the site, people, equipment, and materials being documented.
Avoid exposing security-sensitive, personally identifying, culturally restricted, or operationally vulnerable information.
Do not manufacture coherence. Contradictions, gaps, disputed histories, and unknowns belong in the record.
Preserve authorship, attribution, dates, locations, file lineage, and revision history.
Return copies, indexes, and usable derivatives to the institution or community when feasible.
The seven-phase method
The phases are sequential enough to support planning, but iterative in practice. New evidence may require returning to the frame, expanding consent, revising the spatial model, or changing the public release plan.
01 Frame the transition
Define the institutional change being documented and the reason the record matters now.
Core actions
Identify the transition: closure, sale, merger, adaptive reuse, vacancy, relocation, redevelopment, governance change, mission shift, or another threshold.
State the central documentation question in plain language.
Identify who currently holds authority, knowledge, responsibility, and risk.
Define the intended audiences and decisions the record may support.
Record assumptions, exclusions, uncertainties, and time constraints at the outset.
Minimum record
Project brief and transition statement
Preliminary stakeholder and authority map
Scope, exclusions, access conditions, and review pathway
Initial risk and sensitivity register
Review questions
What is changing, and what may become impossible to see later?
Who needs this record, and what should they be able to understand from it?
What is outside scope—and why?
02 Establish the source record
Create a traceable baseline before interpretation or public presentation begins.
Core actions
Gather available plans, maps, photographs, policies, inventories, timelines, websites, correspondence, and prior documentation.
Record source, date, creator, rights, custody, format, and known limitations for each item.
Create a stable file structure and naming convention before field capture.
Hash, version, or otherwise preserve original files where provenance is material.
Separate canonical source, working derivatives, interpretation, and public-facing materials.
Minimum record
Source register
File and metadata standard
Canonical source archive with read-only originals
Known-gaps list
Review questions
What evidence already exists?
Which records are authoritative, and which are partial or contested?
What has no surviving record?
03 Read the site as a system
Document how the place works spatially and how it relates to the city, landscape, infrastructure, and communities around it.
Core actions
Survey the site from multiple scales: region, district, parcel, building, room, threshold, detail.
Trace approaches, circulation, access points, barriers, sightlines, adjacencies, service routes, and informal paths.
Document how buildings, landscape, utilities, signage, objects, and surrounding streets operate together.
Use aerial, elevated, street-level, interior, and detail views where permissions and safety allow.
Record temporal conditions such as light, occupancy, weather, maintenance, noise, and patterns of use.
Minimum record
Annotated site map and spatial narrative
Systematic image set with capture log
Route, threshold, and adjacency diagrams
List of spatial questions requiring follow-up
Review questions
What becomes visible only from above, from within, or through movement?
Where does institutional identity live physically?
Which relationships would be lost in a building-by-building inventory?
04 Gather lived and operational knowledge
Record the institution as experienced, maintained, governed, and remembered by people.
Core actions
Interview a deliberate range of participants: stewards, staff, residents, students, neighbors, operators, alumni, maintenance workers, leaders, and critics.
Ask how the place actually functioned, including informal practices that formal records omit.
Document rituals, routines, repairs, workarounds, contested meanings, and forms of care.
Invite participants to identify spaces, objects, or absences that carry meaning.
Preserve consent terms and distinguish attributable, anonymous, restricted, and background material.
Minimum record
Interview and consent log
Transcripts or field notes
Operational knowledge record
Thematic index of memories, practices, and contested accounts
Review questions
Who knows the institution differently because they cared for it, used it, or were excluded by it?
What knowledge exists only in practice?
Where do official and lived accounts diverge?
05 Interpret the transition
Build an evidence-based account of what the institution has been, what is happening now, and what remains at stake.
Core actions
Triangulate spatial evidence, source records, interviews, and field observations.
Identify continuities, ruptures, absences, dependencies, and unresolved questions.
Separate direct observation, sourced fact, participant testimony, and Fieldlight interpretation.
Name the institution's public value without flattening complexity or dispute.
Develop a small number of interpretive themes that organize the record without forcing every artifact into one narrative.
Minimum record
Interpretive framework
Transition timeline
Evidence-to-claim notes
Draft institutional narrative and thematic pathways
Review questions
What changed materially, operationally, symbolically, and civically?
What remains continuous despite the transition?
What cannot yet be concluded?
06 Construct the layered record
Assemble a durable corpus in which source, interpretation, and public presentation remain connected but distinct.
Core actions
Maintain canonical originals, preservation derivatives, working files, and public derivatives as separate layers.
Assign persistent identifiers or stable paths to significant artifacts.
Link photographs, maps, transcripts, timelines, essays, and source records through shared metadata.
Create both human-readable and machine-readable indexes.
Document revisions, removals, restrictions, and changes in custodianship.
Minimum record
Canonical archive
Machine-readable manifest and human-readable index
Cross-media relationship map
Rights, restrictions, and retention schedule
Review questions
Can another steward reconstruct how this record was made?
Can a reader move from interpretation back to source?
Which parts must remain restricted, and under what review conditions?
07 Publish, return, and steward
Create a public reading surface and stewardship plan without confusing publication with the full archive.
Core actions
Select materials according to public value, consent, security, rights, and interpretive usefulness.
Design the public surface as a guided reading experience rather than a raw archive dump.
Return usable records and documentation to participating stewards or institutions.
Publish the methodology, provenance statement, limitations, and correction pathway alongside the work.
Assign responsibility for maintenance, future access decisions, updates, and eventual transfer.
Minimum record
Public reading surface or field report
Custodial handoff package
Publication and access statement
Maintenance, review, and succession plan
Review questions
What should the public be able to see, understand, and verify?
Who will care for the record after publication?
How can the record remain alive without becoming unstable or ownerless?
Record architecture
The methodology produces a layered record rather than a single deliverable. Each layer has a distinct purpose and level of authority.
| Layer | Purpose | Typical contents |
|---|---|---|
| Canonical source | Preserves authoritative originals and provenance. | Original files, scans, raw captures, source metadata, rights records |
| Field record | Documents what was observed and gathered during the project. | Capture logs, field notes, maps, interviews, environmental observations |
| Interpretive layer | Explains relationships, meaning, transition, and public value. | Essays, timelines, annotations, diagrams, thematic pathways |
| Public surface | Makes selected material legible and navigable to intended audiences. | Reading pages, exhibits, reports, selected media, captions |
| Stewardship layer | Keeps the corpus governed over time. | Access rules, review dates, corrections, transfer records, maintenance responsibilities |
Minimum metadata
Identifier; title or short description; creator or recorder; capture or creation date; location; format; source or custodian.
Rights and consent status; access level; sensitivity; permitted uses; expiration or review date where applicable.
Relationship to site, event, person, or other artifact; version; checksum or integrity reference where appropriate.
Interpretive status: observed, sourced, testified, inferred, proposed, disputed, or unknown.
Public release levels
Open. Suitable for unrestricted public access and reuse under stated terms.
Contextual. Publicly viewable only with interpretive framing, attribution, or use restrictions.
Controlled. Available to approved researchers, custodians, or participants under defined conditions.
Restricted. Withheld because of privacy, safety, cultural sensitivity, rights, or operational risk.
Embargoed. Temporarily withheld until a date, event, consent change, or review condition is met.
Field documentation standards
Photography and moving image
Capture orientation views before details so every image can be located within the larger system.
Maintain an unedited preservation copy; record substantive edits and derivative crops.
Use repeated vantage points when change over time is part of the inquiry.
Include scale, direction, date, and location metadata when they improve interpretation.
Do not publish sensitive access, security, or infrastructure details merely because they were visible.
Aerial and elevated documentation
Aerial work is used to reveal spatial relationships unavailable from the ground: campus coherence, circulation, boundaries, adjacency, infrastructure, landscape, and the institution's position within the city. It must follow applicable laws, permissions, safety practices, and privacy constraints. Aerial imagery should clarify the site—not aestheticize or surveil it.
Interviews and testimony
Explain the project, intended uses, recording method, and withdrawal or correction process before participation.
Record the participant's relationship to the institution and the period their knowledge covers.
Preserve the difference between memory, opinion, direct observation, and institutional record.
Do not use a single authoritative voice to stand in for the whole institution.
Maps, diagrams, and annotations
Maps and diagrams should make relationships legible without implying false precision. Every interpretive diagram should identify its evidence base, date, scale or level of abstraction, and author. When a spatial claim is inferred rather than measured, say so.
Writing and interpretation
Write so that the record can be understood without prior insider knowledge.
Name what is known, how it is known, and where uncertainty remains.
Avoid institutional euphemism when documenting closure, displacement, conflict, neglect, or extraction.
Avoid reducing a complex institution to a single redemptive or tragic narrative.
Preserve the language of participants where it carries meaning, while maintaining context and consent.
Governance
Every project should identify a named documentation lead, a custodial authority, a rights and consent reviewer, and a publication decision-maker. One person may hold multiple roles in a small project, but the responsibilities should remain explicit.
Documentation lead. Maintains scope, standards, field practice, synthesis, and final quality.
Site or community steward. Provides access, context, local accountability, and custodial perspective.
Archive custodian. Maintains canonical files, metadata, integrity, permissions, and transfer history.
Interpretive reviewer. Tests clarity, evidence, plural perspective, and distinction between source and inference.
Publication authority. Approves public release, redaction, restrictions, correction, and withdrawal decisions.
Decision gates
Gate 1 — Scope approved: purpose, authority, access, risks, and intended use are clear.
Gate 2 — Fieldwork ready: permissions, capture plan, metadata standard, and safety procedures are in place.
Gate 3 — Interpretation ready: claims are traceable; conflicts and unknowns are visible.
Gate 4 — Publication ready: consent, rights, security, context, and accessibility have been reviewed.
Gate 5 — Handoff complete: custody, maintenance, correction, and succession responsibilities are assigned.
Quality criteria
Spatially clear. A reader can understand the site as a system and locate significant relationships.
Historically continuous. The record connects past, present transition, and possible futures without pretending the change is complete.
Interpretively honest. Observation, source, testimony, inference, and recommendation remain distinguishable.
Traceable. Artifacts and claims can be followed back to origin, date, author, and custody.
Plural. The record includes materially different forms of knowledge and does not erase conflict.
Governed. Access, publication, correction, retention, and transfer are deliberate.
Useful. Future stewards can act, orient, preserve, teach, or decide with greater clarity because the record exists.
Project review worksheet
Use these prompts to adapt the methodology to a specific institution or site.
Transition
What threshold is the institution crossing?
What is likely to become invisible, inaccessible, or misremembered?
What decisions or public questions make documentation timely now?
Authority and participation
Who can authorize access and publication?
Who holds knowledge that formal leadership may not hold?
Who bears risk if the record is incomplete, misleading, or overexposed?
Place
What are the essential scales, routes, thresholds, and adjacencies?
Which conditions are temporary but historically significant?
What must be documented from above, within, outside, or over time?
Record
What canonical sources exist?
What machine-readable structure will connect media, testimony, and interpretation?
What must remain restricted or reviewed later?
Public value
What should a member of the public understand after encountering this work?
What might a future steward need that a present audience does not?
How will the project remain accountable after publication?
Recommended project outputs
A concise transition brief and project scope.
A source register and provenance statement.
An annotated spatial record combining maps, images, routes, and system relationships.
A lived and operational knowledge record built from interviews and field observation.
An interpretive essay or field report with traceable claims.
A canonical archive with machine-readable manifest and governed access levels.
A curated public reading surface.
A custodial handoff and long-term stewardship plan.
Revision notes
This document is intentionally editable. During review, the Fieldlight Institute should decide which elements are mandatory across all projects, which are scalable according to site and budget, and which require separate technical protocols. Future versions may add templates for consent, metadata, capture logs, transition timelines, evidence-to-claim review, public release, and custodial handoff.
PROPOSED NEXT DEVELOPMENT
Test the methodology against the original Above the Institute concept and one non-arts site. Revise wherever the method depends too heavily on a campus, a single medium, or a cooperative institutional partner.
Working definition
Institutional transition documentation is the disciplined creation of a spatial, historical, operational, and interpretive record while a place's identity or function is changing. Its purpose is to preserve continuity, clarify relationships, support stewardship, and create public value without turning access into extraction or publication into ownership.
Source lineage
This methodology was developed from Anni McHenry's January 2026 proposal, Above the Institute: An Interpretive Aerial and Narrative Record of a Campus in Transition. The original proposal centered the former San Francisco Art Institute campus during its transition into University of California stewardship. This document retains its commitments to non-invasive visual documentation, restrained narrative, institutional care, preservation, continuity, flexible public and archival use, and the value of recording a site before reuse is complete while traces of prior identity remain visible.