Coastal Practical Skills

• Every fieldwork enquiry starts with an aim — a focused question about ONE stretch of coast, because you can't measure the whole coastline.
• Hypotheses are testable statements; the null hypothesis is the "opposite" statement that keeps your data collection unbiased.
• Risk assessments are essential — coasts bring risks like tides, slippery rocks, unstable cliffs and weather.
• Sampling (systematic, random, stratified) is how you pick fair, unbiased sites — with an opportunistic backup if access is blocked.
• Equipment — tape measures, ranging poles, clinometers, callipers, quadrats — each tool matches a specific measurement job.
• Key data collection methods: beach profiles, sediment (pebble) analysis, longshore drift tracking, groyne measurement, rip-rap measurement.
• Photographs and field sketches are qualitative data — they capture what numbers can't.

Why you can't just "go and measure the coast"

Imagine someone asks you to "study a river." That's impossible to actually do — a river might be hundreds of kilometres long, with a delta, floodplain, source and mouth. You'd need to pick ONE specific question about ONE specific stretch. Coasts work exactly the same way. That's why every piece of coastal fieldwork starts with a tightly focused aim.

Aim vs. Hypothesis — what's the actual difference?

These two get mixed up constantly, so let's separate them clearly:

• An aim is a purpose — what you're trying to find out. It often starts with "To investigate..." or "To explore...". Example: "To investigate how wave energy along X beach changes beach morphology."
• A hypothesis is a statement you can test and either support or reject with evidence. Example: "Coastal management strategies used at beach Y have taken conflicting views into account."

Think of the aim as the destination on a map, and the hypothesis as the specific claim you're checking is true along the way.

The null hypothesis — the most misunderstood idea here

This one trips a lot of students up, so let's build it from scratch. A null hypothesis is simply the opposite of your hypothesis. If your hypothesis says something IS happening, the null hypothesis says it is NOT happening.

Why bother with this at all? Because it protects you from bias. If you go out into the field already convinced your hypothesis is true, you might unconsciously only record evidence that supports it, and ignore evidence that doesn't. By setting up a null hypothesis alongside it, you force yourself to test both possibilities fairly. Whichever one the evidence actually supports — that's the one you accept. If you can't prove your original hypothesis, the null hypothesis must be true instead.

After the aim and hypothesis are set

Four things happen next, in this order:

1. Select the sites (this involves sampling — see Topic 3)
2. Decide on the equipment to be used
3. Consider health and safety — complete a risk assessment
4. Decide on data collection methods