guidance for coaches

[kamocat]

In my experience as a programmer, There's been a lot of people not understanding what's necessary to create functional code.
That's all fine and dandy, when they have their own job. But when they're your coach, you run into problems.
They don't know what to expect of you. They don't know how to support you. They sometimes don't know how to tell whether a problem with the robot is due to programming, wiring, field communications, or mechanical.

I'd like to relieve rookie teams from a lot of that stress and misunderstanding.

Is there a document that would help solve this problem, or do I have to make one?