My agency currently includes wireframes in our project definition documents. Each key page is described along with its wireframe, basic interaction, input fields etc.
However, I'm not sure if this is an effective way to show the wireframes. The large amount of textual information between wireframes seems to break the flow and interaction between pages.
What about other deliverables such as the user journey? Should they be separated out of project management focused documents?
Thanks for the responses, but perhaps I should have worded my question better!
What I meant to ask was: if you're emailing the client a project definition document for their review and sign-off, would you include wireframes and interaction notes in it? Keeping in mind that project definition documents contain other project-related information, is it better to package wireframes separately?