Procedure for submitting a course design:
1) Obtain a two word pseudonym by going to a random word generation site like
this one. This is your pseudonym for the course design non-competition. Feel free to use your pseudonym from a previous non-competition, or obtain a new one, as you like.
2) Download the map:
lower res or
higher res. The lower res appears to be 1:15,000 at 100 dpi, judging by the scale bar. The higher res is 300 dpi at 1:10,000.
3) Design a relay. Choose an assembly area appropriate to a few hundred participants, with suitable exchange logistics between legs, including a way for people to know when the previous leg teammate is on their way (radio control(s), spectator control or leg, or so forth).
4) Draft the courses, either using software, or by hand using pen, purple ink, straight edge and circle guide. Create one map image for each leg of the relay, showing all forks for that leg as well as the leg number (1st leg, 2nd leg, etc.), difficulty (easy, intermediate, difficult), range of lengths (depending on the forks taken), and range of climbs. Also create a map image showing all legs and all forks.
Purple Pen does not seem to support relay courses, so you may prefer to draft using Open Orienteering Mapper or some paid software.
If hand drafting, scan the map with the drafted course, or take a highly legible photo. Make sure to write your pseudonym and leg number on the map image.
I'd suggest labelling controls with control code rather than sequence, and producing a single control description with all controls for all legs and all forks. On the map images, label each fork uniquely to aid discussion. For a four-way fork, you could label each fork A1, A2, A3 and A4. For another three way fork, B1, B2 and B3.
Remember that it's useful for forks, especially the first fork, to be "equal", so that a top orienteer would spend the same time regardless of which fork. If forks are unequal when there are many orienteers from many teams near each other, the orienteers with the shortest fork quickly get caught up by the others. Their later teammates then have longer forks when the field is likely more spread out, and the effect of packs is on average less pronounced. Note the effect not just of length but climb, runnability, visibility.
Make sure that easy and intermediate legs are the expected difficulty. In the stress of a relay, someone might not see an obscure easy route to the control and panic. Catching features and obvious relocation points may be useful for the easy and intermediate courses, even more so than usual. Keep a sensible balance between challenge and fun.
Letting participants see the progress of their team (and others) can make the event much more fun. Radio controls are nice; so are spectator legs, even if they are seen from a distance. (Participants or organizers could use binoculars to identify distant orienteers passing a visible control.)
Consider the locations marked "private" as out of bounds. I doubt that the courses will be used for an event, but people do sometimes do training.
7) Send the image files or PDFs to me at jimbakerwp at gmail dot com, with your pseudonym and "forest relay" as the subject of the email (so that I can easily keep track of them). Or, upload the image files or PDFs to a free hosting site and send me the link(s), same subject line. Don't bother sending the map file.
8) Soft submission deadline January 15, 2017. I'll start posting submissions in mid January, one every week or so, with a hiatus from mid May through early June if I happen to get that many. I'll keep posting submissions as long as I receive them though, within some limits of fatigue.
I'll suggest the relay format above, but leave it open to whatever forest relay you're interested in setting and submitting. If some people would prefer to take it as a challenge to set a beginner, advanced beginner or intermediate course in partly forested terrain, that's fine too. Label your submission accordingly.