dying of thirst

[Gnitworp]

probably helped that I had been warned before I started that the courses were a little on the long side.

You were lucky - I did Brown instead of Blue because I thought it would be on the short side!

[cbg]

probably helped that I had been warned before I started that the courses were a little on the long side.

You were lucky - I did Brown instead of Blue because I thought it would be on the short side!

An what do you think of the "dynamic risk assessment" which resulted in a water point being put out during the event? Immediately in front of Brown #24 on the front edge of a wood; I assumed that the Landrover was just the normal interference by other area users, and was working out which side of it to go pass, until they 'forced' a white cup into my hands! Unfair? Undoubtedly, but with some runners out for 2 hours we are particularly adverse to anyone being suspected of succumbing to heat injury ... that's what comes from an employer's duty of care. But the quite a few more who were out for longer on Blue (50% longer than 6.7km) there was nothing.

Some more planning lessons needed, apologies, but value for money ... ...

[Gnitworp]

The usual unlimited juice etc at Download was much appreciated in the circumstances

[IanD]

hat do you think of the "dynamic risk assessment" which resulted in a water point being put out during the event?

Must have happened after I passed, but good idea!

Was there a "dynamic risk assessment" for the control feature (61 - between thickets) which was being demolished by a JCB as I punched? Only one of the thickets was standing as I passed through, and I think it's life expectancy was measured in seconds.

[Steve]

Courses were 50% longer than stated." Brown course advertised as 7.9km was actually 12.9km.

This was my paranoid fear all the way through planning my last event, to the extent I measured the courses as many ways as I could think of - right up to handing the maps over to the start team!

I think a foolproof way of checking you have the correct scales set up is to draw a marked route along the scale bar on the map and check its length is equal to the length of the scale bar.

[graeme]

The way to check is to test run. There's nothing foolproof about using the scalebar on the map, especially with certain areas in Perthshire...

There's nothing wrong with a 12.9km brown course if it is really 4.5 min/k terrain.

[AndyC]

Scale being right is a fundamental check for the controller to make. I got it wrong once a long time ago (on a local event where there was no controller) in the opposite direction i.e. courses were too short -not a single complaint and noticing the mistake was delayed because an exceptionally good orienteer ran every course "slowly" as training so I expected fast times at the head of each course!
Won't make that mistake again either as planner or controller - A good controller I've worked with checks the map against OS before his first visit and was pleased to learn that I'd checked a feature (a lake) on the OS 1:50k, the OCAD and by pacing it on my first visit.