One message per diagram. That is the whole fix, and everything below is just how to execute it.
When a tutor says your site analysis is unreadable, they are almost never criticising the research. They are telling you the drawing has no hierarchy — eleven findings fighting over the same square of paper, six hues at identical saturation, arrows for wind and arrows for pedestrians and arrows for views all drawn at the same weight, and a legend nobody is going to decode while you stand there talking. That is a graphic failure, not a research failure. Which is good news. Graphic failures are fixable in an afternoon.
The single synthesis drawing with everything on it is the thing that ruins most crit boards. It feels efficient. It reads as noise. The moment you put sun, wind, noise, footfall, views, vehicular access and a conservation area boundary onto one plan, every finding demands the same visual priority, so none of them get it.
Split it. Five diagrams, in a fixed order, each answering one question in under three seconds:
Base map — where is this, what is the grain, where is the boundary.
Context — figure-ground, land use, heights, anything listed or protected.
Movement — how people and vehicles arrive, and where they don't go.
Environment — sun, wind, noise, whichever of them actually bites on this site.
Constraints and opportunities — the synthesis, and the only one allowed to be an argument rather than a record.
That order is not decorative. It is the order in which a panel can absorb information: location, then setting, then behaviour, then forces, then your conclusion. Break it and the panel spends the first thirty seconds working out which way north is instead of listening to you.
Cut Everything That Isn't Evidence
Before you open any software, run the findings through one test: does this change the design? Not "is this interesting", not "did I spend a Saturday measuring it". Does it change the plan, the section, the orientation or the massing?
Soil type is interesting. It changes nothing at a Part 1 crit unless you are arguing for a raft foundation. Prevailing wind matters if you are proposing a courtyard. Bus routes matter if your entrance strategy depends on them. Three or four findings will win the crit. Twelve will lose it, because twelve findings means no findings — it means you haven't decided.
Then write the caption before you draw. One sentence per diagram, active voice, stating the consequence rather than the observation. Not "noise levels are high to the south". Instead: the only quiet edge is the north boundary, so habitable rooms go there. If you cannot write that sentence, the diagram has no message and you are about to spend three hours decorating a plan.
If the gathering side is where you are genuinely stuck rather than the drawing side, our ultimate guide to architectural site analysis covers what to investigate and how. This article assumes the notebook is already full.
Three Colours. That's It.
The rainbow overlay happens because students use hue to distinguish everything, and hue is the loudest tool in the box. Use it for one thing only.
A palette that works on any site, for any brief:
Grey for the base. Linework at around 40–60% black, building fills at 8–15%. The base map is reference. It should sit down.
One accent hue per diagram, used for the subject of that diagram and nothing else. Movement gets one colour. Environment gets another. Keep it consistent across the set so the panel learns your code by diagram three.
One alarm colour — I use a warm red — reserved for the single most important finding on the whole board. Used once, it is devastating. Used six times, it is wallpaper.
Everything else is done with tone and weight. Two different site conditions in the same family? Same hue, different tint. Existing versus proposed? Same hue, dashed versus solid. Magnitude? Line weight. You have far more graphic range in tone and weight than you do in hue, and it never turns into a fruit salad.
Arrows Are a Language, Not a Decoration
Most arrow chaos is a consistency problem. Fix the grammar and the same information stops looking like noise.
Weight means magnitude. The primary approach route is a fat arrow. The secondary is thinner. Same shape, same colour, different weight.
Dash means intermittent or potential. Solid is constant and existing. Seasonal wind, occasional service access, a possible future link — dashed.
Never mix arrow species. Pick tapered filled arrows or stroked arrows with heads. Not both on one board.
Two arrow types per diagram, maximum. If you need three, you need two diagrams.
Direction logic stays fixed. Incoming things point at the site. Views point out from a station point. Don't flip the logic halfway through the set.
And this is the part nobody says: arrows are the laziest way to draw a field condition. A view is a cone or a wedge, not a line. Noise is a graded band that fades with distance. Sun is an arc with a tint. Overshadowing is a shape on the ground. Swap half your arrows for areas and tones and the diagram gets quieter and more accurate at the same time.
The A1 Test — Where Most Boards Die
A diagram that looks beautiful at 60% zoom on a 27-inch monitor can vanish when it is printed at A1 and pinned two metres away from a tutor with a cold. Two habits solve this permanently.
Set the document up at final size. One artboard per diagram, all the same dimensions, at the size it will actually print. If you draw at A3 and scale up later, turn on Scale Strokes & Effects in Illustrator's transform preferences or your 0.5pt lines will stay 0.5pt while the drawing triples — which is exactly how boards end up looking like circuit diagrams.
Weights that survive a studio plotter, as a starting point rather than gospel: 0.25pt only for hatching and texture, 0.5pt for base linework, 1–1.5pt for the diagram's subject, 2pt dashed for the site boundary. Never use Illustrator's hairline default and hope. And nothing under about 8pt for annotation on an A1, with titles at 24pt or more — otherwise the caption you wrote so carefully is unreadable from where the panel stands.
Test it before you commit to a £14 plot. Print one A4 crop at 100% scale, pin it up, and walk back two metres. Anything you cannot read from there is decoration. Light greys are the usual casualty — 20% black on screen frequently plots as nothing, so push background tones to 30–40% and check.
The Illustrator-Over-CAD Workflow, Properly
The production method that makes a consistent set genuinely fast is boring and repeatable. Export the base from CAD or your GIS/OS extract as a PDF or DWG, place it into Illustrator, lock that layer, and never draw on it again. Everything else goes on named layers above it — context, movement, environment, annotation — and the layer order mirrors the diagram order, so you can switch a set of five on and off from one file.
The tool moves that do most of the work are unglamorous. Offset Path for setback lines, buffer zones and site boundaries drawn inward or outward from an existing edge. The Scissors tool for trimming the overlapping junk that CAD exports always bring with them — in the ArchAdemia Illustrator course we spend real time on this in the block-drawing lesson, because uncut overlapping lines are the single most common reason a vector drawing looks scruffy when it prints. Global swatches so you can recolour all five diagrams in one click when your tutor decides the palette is too cold. Align and the alignment of strokes to path, so line weights don't jump between elements. Symbols for trees, people and cars, so the entourage across the set matches.
Use artboards, not five separate files. Same size, same crop, same north, same scale on all of them, exported as a single multi-page PDF. Consistency is what allows a panel to compare diagram two with diagram four, and rotating the site between drawings is the fastest way to lose them entirely.
Make It Speak Without You
Assume you will be asked to stand aside while the panel reads the board. Each diagram needs a title top-left, your one-sentence caption underneath it, a north point, a scale bar, and labels placed on the thing they describe rather than in a legend at the bottom. A legend is a last resort — it forces the reader to look away from the drawing and back again, twice, for every symbol.
On the board itself, run the set left to right, top to bottom, in the five-diagram order. Same size, same margins, aligned to a grid. The panel should be able to follow your reasoning without you saying a word, so that when you do speak, you are adding the argument rather than reading out the drawings.
Output
Set the document to CMYK from the start if it is going to print. Electric RGB cyans and greens collapse into something muddy on a plotter, and finding that out at 9am on crit day is a specific kind of pain. Export as PDF with press-quality settings, keep everything vector, and if you have placed an aerial photograph or a scanned contour survey, make sure it is 300ppi at final printed size — not 300ppi at thumbnail size, stretched.
Export PDF, not JPEG. Text stays text. Lines stay lines.
A site analysis diagram is not a receipt for the hours you spent on site. It is an argument that a specific design move is the obvious one. If your five diagrams end with a plan-shaped conclusion the panel can see coming, you have done it. Nobody has ever awarded a mark for the number of arrows you managed to fit in.
