Products /

Templates / Contents preview · v0.1

Site Analysis
Starter Kit.

Six editable templates for one site question and the evidence behind it.

Keep source statements, interpretation, actual field observations and open actions in a package the next reviewer can follow.

Original v0.1 archive · 8 files · 5,962 bytes · Markdown and CSV, optional YAML

Who it is for and what it does

Use the kit when early site work needs a clear record of what is known about a site, what it means and what still needs checking before design decisions advance. It is written for landscape architects and the planners, designers and agency reviewers they work with.

The kit is a set of templates. You supply the sources, the analysis and the professional judgment; the templates keep them organized and linked, from site question to handoff.

Template contents

  1. Scope brief. Name the decision, the site question, the study area, exclusions and the conditions that would stop the work.
  2. Source register. For each source behind your site inventory (survey, base map, GIS layer, plan, report or photograph), record its date, units and reference, what it says, your interpretation, its limits and its permissions.
  3. Field-check log. Plan what to observe on site and why. Record the observer, date and actual observation separately from interpretation; checks not yet made stay pending.
  4. Graphic brief. Specify each map or diagram: the finding it shows, its sources, extent, legend, caption and the uncertainty that changes its meaning. You make the graphic in your own drawing or GIS software.
  5. QA checklist. Check links, units, dates, revisions, permissions and whether a recipient can follow the package.
  6. Handoff note. State what the package supports, what it does not, the files, the open actions and who owns them.

The original archive also includes a quick-start README and an optional YAML file that links the record IDs. Eight editable files; no datasets, source maps or software plugins.

File inventory

The archive contains one folder, field-method-site-analysis-starter-kit/, with these files. The original v0.1 blank templates are preserved; distribution is held pending approval.

  • README.md — quick start, file list and review limits.
  • 01-scope.md — the question, intended decision, study boundary and exclusions.
  • 02-evidence.csv — source statements, interpretation, dates, limits and permissions.
  • 03-field-checks.csv — planned checks and actual dated observations, when performed.
  • 04-graphic-brief.md — instructions for a graphic you produce in your own tools.
  • 05-qa.md — named review, unresolved items and corrections.
  • 06-handoff.md — file list, intended use, recipient and next actions.
  • trace.yml — optional links between the project-local record IDs.

Intended use after release

After download approval, start with one site question. Copy the folder, complete the scope, then build the source register and field checks around that question. Adapt them to the landscape systems the question involves: terrain, water, soils, vegetation, microclimate, habitat, circulation or cultural resources. Brief one map or diagram that shows the finding and its limits. Review the package and test it with the person who will use it.

Markdown files are plain text and open in any text editor; CSV files open in a spreadsheet. No database, account or special software is required. Keep your original sources separate and respect their permission and attribution terms.

A fictional record to follow

This example illustrates the record structure. It is an invented courtyard project, not a site assessment, customer project or completed set of templates. No plan, dataset, measurement or site visit is supplied.

Q01 — The question. Which path locations need a current field check before a concept plan is revised? The scope is a record of evidence and open checks; no accessibility, grading or compliance finding is proposed.

Record Illustrative entry State
E01 / Source A plan is needed to identify the paths to compare. Its author, date, reference and permissions have not been recorded. Source missing
FV01 / Field check Plan a comparison of the source plan with current path locations. Observer, date and actual observations remain empty until a visit occurs. Not performed
G01 / Graphic brief Prepare a comparison graphic only when the source is available; label any unverified current conditions and link E01 and FV01. Not prepared
QA01 / Review Check source identity, reference, actual observations and the graphic’s stated limits before handoff. Not reviewed
H01 / Handoff Give the next reviewer the question and open actions. Hold the concept-plan revision until the missing evidence has been reviewed by the responsible person. Decision held

The useful output here is the open-action record. A filled row does not turn the missing plan into evidence or an unperformed check into an observation. You can hand off a held decision when the recipient can see the reason and the next action.

Limits and review status

This is a review edition of a record-keeping kit, not a validated professional method or a jurisdictional standard. It does not perform analysis or replace source assessment, site visits or qualified professional review, and it supplies no engineering, grading, drainage, accessibility, compliance or constructability conclusion.

The blank templates are original Field Method material. Download held pending founder content and usage-terms approval. No license or permission to use the template files is granted by this contents preview. Third-party site data and Trolley Barn research figures are not included in the original archive.

Common questions

Do I need GIS software? Not to complete the templates; a text editor and a spreadsheet are enough. Any analysis or mapping you record needs its own appropriate tools and checks.

Does the kit do overlay or land suitability analysis? No. It can document an overlay or suitability study you carry out, including its layers, weighting decisions and limits, but it performs no analysis itself.

Is this a completed site assessment? No. It organizes your evidence and reasoning; it does not fill gaps or make a decision for you.

Can I use a different kind of site evidence? After release approval, the editable templates are intended to support that. Adapt the scope and source register to the question, keep each source’s provenance and note where a template does not fit.

Does the kit include site datasets or completed maps? No. The held archive contains only the eight blank files. The fictional example on this page illustrates their relationship and is not a dataset or completed assessment.

Does this save or reopen a Landscape Workspace project? No. These records are separate editable files. Use the workspace’s own exports for its generated maps, model and photo package; its current project JSON does not restore the complete workspace.

Use the handoff workflow to compare the record with the current pilot’s export steps. The Landscape Workspace provides preliminary site inventory and drawing exports for San Diego County; the kit can record sources and review actions from that tool or from your own software.