• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
Log in

  • About
    • The GradFund Team
    • Success Stories
  • Advice
    • Blog
    • Planning When to Apply
    • Proposal Writing Advice
  • Fellowships and Grants
    • Search for Fellowships and Grants
    • SGS Managed Awards
    • SGS Competitive Awards
  • Resources
    • GradFund Self-Paced Guide to Grants and Fellowships
    • Research Development Support
    • Funding Directories
  • Questions
    • Frequently Asked Questions
    • Contact Us
  • Meet With Us

Unpacking Jargon—Part One

Posted on November 5, 2018 by JORIE HOFSTRA

Jargon serves important functions in any field of activity. It lends accuracy and efficiency to communication within a subfield, and terms that begin as jargon may eventually enter into common use: consider the current popularization of specialized terms like “intersectionality,” “epigenetic,” or “VPN.” But in grant writing, jargon can be risky. The need for precision and the need to demonstrate your immersion in your field must be balanced against the need to communicate clearly to a diverse audience of reviewers. Reviewers may come from outside your subject area, from different fields, or even from outside academia. Your proposal must communicate to reviewers that you know what you are talking about, and that you have something important and interesting to contribute, without making them feel confused or frustrated. Moreover, your proposal must be coherent and possible to be understood quickly by reviewers, as they have limited time to read each application. Finally, some funders prioritize the ability to communicate research to the public or to students, and your proposal gives evidence of your communication skills. Study the funder’s materials closely to learn about their reviewers and review criteria, so you can adjust the level of technical detail and jargon in your proposal accordingly. When in doubt, it is wise to err on the side of clarity and readability by replacing, unpacking, or defining highly technical or theoretical language.

One way to limit your use of jargon is to begin a draft by describing your work in plain language. To avoid slipping into your academic writing mode, you may even want to speak into a recorder or to a friend rather than sit down and write at this point. Once you have described your project in plain language, as jargon-free as possible, put it in writing. Then look for the areas where more specific detail or technical language is needed, and elaborate on those areas, using jargon as sparingly as possible.

Another strategy is to ask someone outside your field to read a draft of your proposal. Learn about what kinds of reviewers will assess your application, and match your readers to the expected composition of the review committee. Ask your readers to mark words and phrases that they find unclear, or that they think would be difficult for readers who are unfamiliar with your area.

Part Two of this post [link] offers more specific advice for addressing jargon that you or your readers have identified.

Filed Under: Proposal Writing Advice Tagged With: eliminating jargon, revision tips

Stay in Touch!

Our newsletter will keep you informed about new funding opportunities and upcoming deadlines, as well as information about GradFund services and other resources that will help you search for and apply to funding opportunities.

* indicates required





Reader Interactions

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Search Awards

Make an Appointment →

Get personalized help finding funding and writing applications

Founded in 2000, GradFund’s mission is to assist Rutgers graduate students in securing merit-based research grants and fellowships to support their graduate study and research. Read about our history and approach to working with graduate students. Learn more →

Copyright © 2025 Rutgers, The State University of New Jersey, an equal opportunity, affirmative action institution. All rights reserved. Log in