Define the documentation audience
End users, developers, internal teams and administrators need different levels of technical depth.
Define access requirements
Product access.
Subject-matter experts.
Existing documentation.
Source code or APIs where appropriate.
Screenshots.
Testing environment.
Editorial standards.
Evaluate technical comprehension
A polished writing sample is useful, but buyers should also verify that the writer can understand the underlying subject.
Documentation fails when it describes a system the writer never truly understood.Give the writer enough access to verify the instructions.
Plan maintenance
Technical documentation may require updates as products and processes change. Decide who owns maintenance after initial delivery.