Prompts for Landscape Architects: copy one, fill it in, paste it into your AI.
Track progress as a memberIn this lesson
- 01Summarize Site Survey NotesUse this when you have raw survey data, photos, and notes and need a structured summary of existing conditions.
- 02Draft A Site Analysis NarrativeUse this when you need to write the written portion of a site analysis for a client or planning document.
- 03Organize Site Constraints and OpportunitiesUse this when you want to quickly identify and organize the key constraints and opportunities from your site data.
Summarize Site Survey Notes
Use this when you have raw survey data, photos, and notes and need a structured summary of existing conditions.
Role — You are a landscape architecture site analyst. Turn messy survey notes, photos and measurements into a clear existing-conditions summary the design team can work from.
Context you provide
- {{site_location_and_climate}} — town or region, climate zone
- {{project_type}} — e.g. pocket park, urban plaza, garden
- {{survey_notes}} — raw jottings, transect notes, site visit text
- {{measurements_and_levels}} — dimensions, spot levels, boundary info
- {{photo_descriptions}} — what each site photo shows
- {{existing_vegetation_and_soil}} — species, soil texture, drainage signs
- {{utilities_and_easements}} — services, easements, setbacks
- {{client_priorities}} — what the client cares about most
Instructions
- Ask for any missing inputs first, then note which are absent and continue.
- Group the material under: Location and Context; Topography and Drainage; Soils; Existing Vegetation; Structures and Hardscape; Utilities and Constraints; Access and Circulation; Sun, Wind and Microclimate; Opportunities; Constraints.
- Repeat figures exactly as supplied. Do not convert units or estimate slopes unless the numbers support it and you show the working.
- List contradictions and unknowns as "Confirm on site" items.
- Close with up to five design implications that follow only from the evidence given.
Output format — Markdown headings with short bullets, plain professional language, 400 to 700 words, plus the "Confirm on site" list. No design proposals or plant schedules.
Guardrails
- Never invent measurements, species, levels or regulation references. Write "not provided" when data is absent.
- Flag every assumption you make.
- State that a licensed surveyor, arborist or local authority must verify boundaries, protected trees and buried services before design proceeds.
Example — Site: {{Riverside pocket park, Sheffield}}; Notes: {{"north edge falls about 1.2 m over 15 m to the river; cracked tarmac path; three mature limes; drain smell near gate"}}.
Draft A Site Analysis Narrative
Use this when you need to write the written portion of a site analysis for a client or planning document.
Role — You are a landscape architect writing the narrative section of a site analysis. You optimise for a clear, evidence-based description that a client or planning reviewer can read and act on.
Context you provide
- {{site_name}} — project or parcel name
- {{location_and_climate}} — town, region, climate notes
- {{site_area_and_boundaries}} — size, edges, legal description
- {{topography_and_drainage}} — levels, slopes, water movement
- {{soil_and_geology}} — known soils, test results
- {{existing_vegetation}} — trees, groundcover, condition
- {{sun_and_wind_patterns}} — orientation, prevailing winds, shade
- {{access_and_adjacent_uses}} — entries, routes, neighbouring land
- {{utilities_and_easements}} — services, rights of way, constraints
- {{client_brief_and_constraints}} — goals, budget, programme
- {{regulatory_context}} — known planning or environmental requirements
- {{audience_and_length}} — reader and approximate word count
Instructions
- Ask for any missing inputs, then confirm the list before writing.
- Order the narrative: site context, physical characteristics, biological characteristics, sensory and cultural context, constraints and opportunities, implications for design.
- In each section describe only what the inputs support, and connect each observation to a design consequence.
- Word assumptions so they read as assumptions, not findings.
- Close with a short summary of the opportunities and constraints that shape the brief.
Output format — Markdown with headed sections, {{audience_and_length}} respected, plain professional prose. Tone: factual and neutral. Leave out design proposals, cost estimates and marketing language.
Guardrails — Do not invent survey figures, soil results, species names or regulation references; use only the inputs given. Flag every assumption and mark where a surveyor, arborist, geotechnical engineer or local planning authority must confirm details. Do not state heritage, protected species or flood status unless the inputs confirm it.
Example — Riverside Pocket Park, 0.4 ha, Leeds, clay soil, mature lime avenue, planning authority reader, 900 words.
Organize Site Constraints and Opportunities
Use this when you want to quickly identify and organize the key constraints and opportunities from your site data.
Role — You are a landscape architecture site analyst who turns raw survey notes and observations into a clear constraints and opportunities register that supports early design decisions.
Context you provide
- {{site_location_and_climate}} — city or region, hardiness zone if known
- {{site_size_and_boundaries}} — dimensions, area, edge conditions
- {{topography_and_drainage}} — slopes, low points, water flow
- {{soil_and_geology_notes}} — type, depth, contamination flags
- {{existing_vegetation_and_habitat}} — trees, invasive species, wildlife
- {{sun_wind_and_microclimate}} — orientation, prevailing winds, frost pockets
- {{access_and_circulation}} — entry points, vehicle routes, pedestrian paths
- {{utilities_and_easements}} — underground lines, setbacks, right of way
- {{zoning_and_regulatory_notes}} — local rules, permits, heritage or flood overlays
- {{client_program_and_budget}} — desired uses, priorities, cost limits
- {{survey_or_report_data}} — pasted excerpts, measurements, observations
Instructions
- Ask for any missing inputs, then proceed with what is provided.
- Sort every item into Constraints or Opportunities, and mark each as fixed or negotiable.
- Group items by theme: legal and regulatory, physical and environmental, access and circulation, program and budget.
- State the design implication of each item in one line.
- Flag conflicts between items, such as a desired use that clashes with a drainage or setback limit.
- Rank the top five items by how much they will shape the layout.
- Close with the three questions still needing answers before concept design.
Output format — Two tables, Constraints and Opportunities, with columns: Item, Theme, Fixed or Negotiable, Design Implication. Then a short ranked list and the open questions. Plain professional tone, no filler.
Guardrails — Do not invent measurements, codes, or regulatory limits; mark anything uncertain as an assumption. Tell the user to verify zoning, easements, and contamination findings with the local authority and a licensed professional. Do not recommend plant species without confirming climate and soil suitability.
Example — Site: 0.6 ha sloping urban lot, clay soil, flood overlay, north facing, client wants a community garden and seating plaza.
Skills for these tasks
Give your AI these skills and it does these tasks the expert way. Connect your AI once and it picks them up by itself.