TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
This is for contractors/freelancers in particular, but others can likely help also.
Scenario: You've been hired to write documents for a new client. You have an upcoming meeting to discuss the project. You want to create a list of questions for the client regarding the project documentation itself, administrative issues, etc.
I currently have some questions regarding audience analysis, type of documents required to meet their users' needs, status reporting, scheduling, document reviews, etc... Some of you more experienced writers/contractors likely have encountered situations where later you should have asked "question a" or you should have clarified "issue b" at the outset.
1. Do any of you currently use such an interview document so you'll be sure to cover all important issues at your kick-off meeting? (and to CYA regarding project scope, estimates, etc.)
2. Would you be willing to share your list of questions with me?
Please respond off line, but if anyone is interested in a summary, please let me know.
