There's little argument that investigating and identifying business needs (i.e. requirements) is a critical task of business analysis. However it's of little use correctly identifying business needs if the people can't then effectively document them - to the clients who will be paying for the solution and to the developers who will be building it. In todays time poor world they need to address both audiences in a single document. This paper - based on IRM's writing better requirements workshop - takes a top down view of the requirements life-cycle. The paper looks at where business requirements come from and what analysts can do to turn them into solution requirements that developers can work with.