Note

What is a written scheme of investigation (WSI)?

Rolling hills divided into hedgerowed fields, seen from a high vantage point.

A Written Scheme of Investigation (WSI) is the document that sets out how an archaeological contractor will meet a planning condition before, during, or after groundworks. It's the method statement: scope, techniques, timetable, and reporting standard, agreed with the local planning authority's archaeological curator before anyone puts a spade in the ground.

If a planning condition has landed on your desk with wording like "no development shall commence until a written scheme of investigation has been submitted to and approved by the local planning authority," this is what that clause is asking for.

What goes into a WSI

A WSI typically covers the site location and planning history, a summary of known and potential archaeology (usually lifted straight from the desk-based assessment), the proposed fieldwork method, whether that's trial trenching, strip-map-sample, a watching brief or geophysical survey, the staffing and timetable, and the reporting and archiving arrangements at the end. Most curators work to a broadly similar template, though every county has its own quirks, its own preferred paragraph order, its own views on trench percentages.

The document has to satisfy two readers at once. The curator checking it against their brief, and the contractor's own project team who'll actually be standing in a trench six weeks later working to whatever the WSI committed them to.

Where it sits in the planning process

A WSI almost always follows a desk-based assessment, not the other way round. The DBA is what tells you whether there's likely to be anything here worth conditioning for in the first place. It pulls together the HER data, historic mapping, aerial photo interpretation, geology and any previous intervention nearby, and it's usually that document that recommends the planning condition the WSI then responds to.

This is where a lot of field directors feel the squeeze. The DBA gets written against a tight planning timetable, sometimes before a site visit is even possible, and the quality of that early read shapes everything downstream: how much trenching the WSI proposes, how the curator scopes their brief, how big a surprise turns up once the diggers arrive. A cropmark layer dropped into the DBA stage, showing buried ditches or wall lines already pushing through as differential crop growth, gives you something firmer than a guess to build that scope around. Buried Feature Detection reads NIR imagery over the site during the growing season for exactly that purpose, ahead of the WSI getting drafted.

Conditions that catch people out

A few clauses turn up often enough to be worth flagging on their own.

Pre-commencement vs. pre-occupation conditions. A pre-commencement WSI has to be discharged before any groundworks start, including site clearance. Miss that and the condition's been breached even if the archaeology itself was never at risk.

Staged conditions. Some permissions split the archaeological work into phases, evaluation first, then a second WSI for mitigation once the evaluation results are in. Each stage needs its own discharge.

Non-archaeological conditions bundled into the same clause. Ecology, arboriculture and drainage sometimes get folded into the same numbered condition as the archaeology. Read the whole condition, not just the bit with "archaeological" in it.

A WSI is agreed in writing with the curator before fieldwork starts, and it's the document the local planning authority will hold you to if the final report doesn't match what you said you'd do. Getting the scope right at the DBA stage, before the WSI is even drafted, saves the awkward conversation later about why a trench came up empty where the geophysics said it would and nobody checked the aerial photos at all.

If you're scoping a WSI against a desk-based assessment this season, it's worth seeing what a NIR cropmark pass over the site turns up before you commit to a trenching percentage.

Get started

← Back to the blog