What you actually need before you open a drawing tool
A site plan is a scaled, top-down drawing of a property showing the boundary, the structures on it, and the distances between them. Contractors need one whenever a job changes what sits on the land or where — a fence, a deck, an addition, a shed, a concrete pad, a pool. Before opening any tool, three things need to be in hand: the lot dimensions, the footprint sizes of the main structures, and the measurements that locate those structures relative to the property lines.
Lot dimensions typically come from a plot plan, a purchase document, or municipal parcel records — SiteBuildHub's Resources library covers field-measurement workflows if you're capturing dimensions on site rather than pulling them from records. Structure locations get tape-measured or laser-measured on site. Write every number down before opening a drawing tool. The actual drawing goes fast once the measurements are ready; almost all the time loss in site-plan drawing comes from stopping mid-drawing to go re-measure something.
This guide walks through the same process whether you're using SiteBuildHub's Site Plan Maker or any other scaled browser tool — the steps are about the drawing method, not one specific product.
Step 1: Set up a scaled sheet before you draw anything
The single thing that separates a site plan from a doodle is scale. Every shape you place needs to be proportional to every other shape, which means the sheet needs a defined scale before the first line goes down — not after. In a browser tool with a scaled grid, one square typically equals one foot, so anything drawn on the grid is automatically proportional without manual conversion.
If you're working from a residential site plan template, start there rather than a blank canvas — a template usually arrives with a property line, a house footprint, a driveway, and sample dimensions already placed, which gives you a working reference instead of an empty grid. If you're starting blank, draw the property boundary first as a rectangle at the lot's true dimensions. Everything else gets positioned inside that boundary, so getting it right first prevents having to rescale the whole drawing later.
Step 2: Place structures and features at their real footprint
Draw the house as a rectangle at its actual footprint size, positioned the measured distance from the front and side property lines — this is the anchor everything else gets measured against, so use your field measurements here, not a rough estimate from a photo. Add the garage, driveway, deck, shed, and any other existing features as rectangles and polygons. Snap-to-grid keeps edges aligned and dimensions honest instead of drifting a few inches per shape.
Then add the proposed work — the new fence line, the addition, the concrete pad — and make it visually distinct from existing structures with a label or a different line style. Anyone looking at the finished drawing, including a client with no construction background, should be able to tell instantly what already exists and what's being proposed.
Step 3: Dimension and label everything that matters
Run dimension lines along the property boundaries, across structure widths, and — most importantly — on the setback distances from the proposed work to the property lines. Setbacks are usually the first thing a permitting office checks and the first thing a neighbor dispute centers on, so get those dimensions right and visible before anything else on the sheet.
Label each feature with clear text: "EXISTING HOUSE," "PROPOSED DECK," "GRAVEL DRIVE." Fill in the title block with the project name, client, your company, and the date. A drawing without a title block is hard to identify six months later when a related job comes up at the same address.
Step 4: Export the drawing and file it properly
Export the finished plan as a PNG for embedding in proposals, or as a PDF for a standalone document — see how to create a contractor drawing PDF for a client for the specifics of preparing a client-ready export. Save the drawing itself, not just the export, so the next job at the same property — the fence after the deck, the shed after the fence — starts from a plan you've already made instead of from scratch.
One caution worth repeating clearly: a drawn site plan documents your measurements, it doesn't establish legal boundaries. Where boundary accuracy actually matters — a fence close to a property line, a permit application — use survey pins or a licensed surveyor, and confirm what your local permitting office accepts before submitting any drawing as part of an application.
A decision framework: how much detail does this specific job need
Not every site plan needs the same level of detail. Use the table below as a starting point, and adjust based on what the specific job and jurisdiction actually require.
| Job type | Minimum detail needed | Extra care required |
|---|---|---|
| Fence quote | Perimeter, gates, obstacles | Confirm property line if fence runs close to it |
| Deck or addition | Setbacks, footprint, height | Check local permit requirements before finalizing |
| Shed or detached structure | Setbacks, footprint | Confirm setback rules — these vary widely by lot size |
| Concrete pad or driveway | Footprint, slope direction, drainage note | Flag nearby utilities before excavation |
| Permit submission of any kind | Everything above, plus surveyed boundaries where required | Confirm with the local permitting office what they accept |
Common mistakes that make a site plan unusable later
A handful of avoidable mistakes account for most of the rework and confusion that shows up after a site plan gets used for a quote or a permit application.
- Drawing without setting a scale first, which forces a full redraw once real measurements come in
- Estimating structure dimensions from a photo instead of using field measurements
- Leaving setback distances undimensioned, even though they're usually the first thing reviewed
- Skipping the title block, so the drawing is unidentifiable months later
- Treating a hand-measured boundary as survey-accurate when the job genuinely requires one