McCulley/Cuppan Inc

01/11/2022

Learn more about our new book: Writing for the Biopharmaceutical Regulatory Reader

Writing for the Biopharmaceutical Regulatory Reader written by Gregory Cuppan and Stephen Bernhardt

10/04/2019

User Experience should be part of the document development process

User Experience, commonly referred to as UX, is a major point of consideration in many industries that create products for various types of consumers. Documents associated with drug and device development and registration are indeed products.

08/09/2019

Change in dates for Atrium sponsored medical writing workshop in Copenhagen that I will co-facilitate. The new dates are on 29-31 October.

08/08/2019

“The whole idea behind lean writing is that the document user is an impatient reader...”

The basic rule in scientific communication is to write for the end-user. Nearly all agree with this tenet and nearly the same number would suggest that most documents produced by their organization embody the spirit of the rule.

03/07/2019

We’ve moved the blog back to the website. Check out Greg’s latest on Maximizing Intellectual Capital.

Document review in pharma and medical device enterprises is a system of diverse and complex functions that requires proficiency in technology, process discipline, and most importantly intellectual...

01/01/2019

08/17/2017

The recently revised McCulley/Cuppan Document Standards© are now up on the website. We'd appreciate your feedback!

10/21/2016

New website is live! Check it out and let us know what you think. We've got more information on training sessions coming in the next month.

04/23/2016

New website coming soon!

08/24/2011

Thanks for the great comment on our blog: "If the doc is clear...then put aside your perfectionism" http://ow.ly/6bpds

03/21/2011

At McCulley/Cuppan, our consultants have backgrounds in the life sciences, engineering, rhetoric, and medical writing. (Not all consultants are pictured here.)

03/01/2011

...Reviewers should note how the messages & arguments in a doc will be interpreted by the document user. (2/2)