Can An iPhone App Improve Your Legal Writing?, by Robert Ambrogi, Law Sites Blog
Can an iPhone app improve your legal writing? Kathleen Vinson thinks so. A professor of legal writing at Suffolk University Law School in Boston, Vinson has developed iWrite Legal, a free iPhone app designed to help legal writers improve their writing skills.
The app consists of three sections — Legal Writing Tips, Legal Writing Checklist and Additional Resources — all aimed at providing advice and guidance on writing, editing and proofreading a legal document.
The first section, Legal Writing Tips, is simply that — a collection of tips, no doubt gleaned from Vinson’s own experience teaching legal writing. Each tip occupies its own screen, with a heading such as ‘Finding the Time to Write,’ ‘Be Consistent’ and ‘One Point at a Time,’ followed by a paragraph that elaborates on the point. For example, under the heading, ‘Writing Efficiently,’ the app offers this tip:
Do you feel that it is taking a long time to draft a document? Good writing takes time but often what slows writers down is trying to edit while you write. Don’t edit/revise while you write or stop to think of the perfect word. Write quickly and then once you have completed a draft, edit slowly. If you have to, cover the screen while you type so you can fight the urge to edit while you write.
The second part of the app consists of four legal writing checklists. They cover the initial stages of writing, revising, editing and proofreading. For example, the checklist for the initial stages of writing lists items such as, ‘What is the purpose of the document?’, ‘What relief do you want from the court?’ and ‘Why is your client entitled to this relief?’ As you satisfy yourself that you have covered each element, touch that element in the app to check it off.
The final component of the app, Additional Resources, simply provides links to the Suffolk Law Legal Practice Skills program’s Twitter feed, YouTube video and Legal Writing Tips podcasts.
So will this app make you a better writer? . . . .