Writing the DR plan is generally not performed in a single clean swoop of activity, so sort out the good, the bad, and the ugly. Fix the obvious first, such as system account information, server names, and disk space.
Good technical documentation is a challenge because at one extreme, technical documentation is often written by technical experts who dislike writing and give it as little effort as possible, with no formal criteria. Or at the other extreme, the documentation is written by artisan technical writers who lack the formal technical criteria needed to evaluate the effectiveness of the product in view of the needs of the readers.
The previous chapters of this book have stated what is needed in a DR plan. This question really asks how you write the required information to an acceptable level where the documentation is readable and actionable. In essence, a technical resource can read the document and know what steps are required to be...