What a 2D site plan is (and isn’t)
A 2D site plan is ideal for
- Listing packages and property documentation sets
- Portfolio-wide consistency across multiple properties
- Showing plot outline, orientation, access and key external elements (as provided)
A 2D site plan is not
- A cadastral/legal survey document
- A replacement for engineering/site design drawings
- Automatically derived from public map data unless supplied by the client
What we can show (based on your inputs)
We include the following elements when provided or clearly indicated in your source material:
- Plot/parcel outline
- Building footprint(s)
- Driveway / access route
- Garden / terrace / key exterior zones
- Orientation indicator (north arrow)
- Simple labels (minimal, template-aligned)
Inputs (what to send)
Send one of the following input sets:
Option A: Measurement / sketch based
- Site sketch with key dimensions
- Building footprint measurements (if separate)
- Notes for access, boundaries, and key features
Option B: Existing documentation
- Existing site plan PDF / scan
- Markups indicating what to keep / remove
- Template/style reference for presentation
Optional (if you have it)
- Reference photos (helps verify context)
- Client template / SOP (preferred)
Deliverables (what you receive)
Outputs
- PDF / PNG / JPG (standard)
- DWG / FML (when required)
Delivery
- Batch-ready folders and file naming aligned to your workflow
Site plan styling rules (how we keep output consistent)
To keep plans consistent across batches, we align on:
- Plot boundary style (line weight, color)
- Building footprint emphasis
- Labeling approach (minimal vs detailed)
- Orientation + scale placement
- Export set + file naming rules
If you already have a template, we follow it. If not, we propose a standard style and keep it consistent.
Common clarifications (to avoid revisions)
- Should plot boundaries be shown as approximate or dimensioned (only if you provide dimensions)?
- Do you want labels for exterior zones (garden/terrace/parking) or minimal labeling?
- Should neighboring context be shown or excluded?
Samples
