These materials were made possible thanks to the generous support from the Kemper K. Knapp Bequest Committee.
On this page, the UW-Madison Writing Center Writer's Handbook offers advice on writing abstracts and answers questions such as: including:
On the "Abstracts: Examples" page, you will also find sample Undergraduate Symposium abstracts from a variety of disciplines.
What is an abstract?
An abstract is a concise summary of a larger project (a thesis, research report, performance, service project, etc.) that concisely describes the content and scope of the project and identifies the project’s objective, its methodology and its findings, conclusions, or intended results.
Remember that your abstract is a description of your project (what you specifically are doing) and not a description of your topic (whatever you’re doing the project on). It is easy to get these two types of description confused. Since abstracts are generally very short, it’s important that you don’t get bogged down in a summary of the entire background of your topic.
As you are writing your abstract, stop at the end of every sentence and make sure you are summarizing the project you have undertaken rather than the more general topic.
Do abstracts vary by discipline (science, humanities, service, art, or performance)?
Abstracts do vary from discipline to discipline, and sometimes within disciplines.
Abstracts in the hard sciences and social sciences often put more emphasis on methods than do abstracts in the humanities; humanities abstracts often spend much more time explaining their objective than science abstracts do.
However, even within single disciplines, abstracts often differ. Check with a professor to find out about the expectations for an abstract in your discipline, and make sure to ask for examples of abstracts from your field.
What should an abstract include?
Despite the fact that abstracts vary somewhat from discipline to discipline, every abstract should include four main types of information.
What should my Objective/Rationale section look like?
What is the problem or main issue? Why did you want to do this project in the first place?
The first few sentences of your abstract should state the problem you set out to solve or the issue you set out to explore and explain your rationale or motivation for pursuing the project. The problem or issue might be a research question, a gap in critical attention to a text, a societal concern, etc. The purpose of your study is to solve this problem and/or add to your discipline’s understanding of the issue.
Some authors state their thesis or hypothesis in this section of the abstract; others choose to leave it for the “Conclusions” section.
What should my Methods section look like?
What did you do?
This section of the abstract should explain how you went about solving the problem or exploring the issue you identified as your main objective.
For a hard science or social science research project, this section should include a concise description of the process by which you conducted your research. Similarly, for a service project, it should outline the kinds of service you performed and/or the process you followed to perform this service. For a humanities project, it should make note of any theoretical framework or methodological assumptions. For a visual or performing arts project, it should outline the media you employed and the process you used to develop your project.
What should my Results/Intended Results section look like?
What did you find?
This section of the abstract should list the results or outcomes of the work you have done so far. If your project is not yet complete, you may still want to include preliminary results or your hypotheses about what those results will be.
What should my Conclusion section look like?
What did you learn?
The abstract should close with a statement of the project’s implications and contributions to its field. It should convince readers that the project is interesting, valuable, and worth investigating further. In the particular case of the Undergraduate Symposium, it should convince readers to attend your presentation.
How should I choose my title?
You probably already have some idea for a title for your project. Consider your audience; for most projects, it is best to choose a title that is comprehensible to an audience of intelligent non-specialists.
Avoid jargon; instead, make sure that you choose terms that will be clear to a wide audience.
What my project isn't finished? What if my results didn’t turn the way I expected?
More often than not, projects are not completely finished by the time presenters need to submit their abstracts. Your abstract doesn’t need to include final results (though if you have them, by all means include them!).
If you don’t yet have final results, you can either include any preliminary results that you do have, or you can briefly mention the results that you expect to obtain.
Similarly, unexpected or negative results occur often. They can still be useful and informative, and you should include them in your abstract. Talk with your mentor to discuss how such results are normally handled in your discipline.
In any case, whether you have complete, partial, projected, or unexpected results, keep in mind that your explanation of those results – their significance – is more important than the raw results themselves.
How can I fit all of this into just 125 words?
Bestraightforward. Don’t worry about making your abstract “flow”. Don’t worry about writing a long or elaborate introduction or conclusion, and as we suggested above, don’t include too much background information on your project’s general topic. Instead, focus on what you have done and will do as you finish your project by providing the information we have suggested above.
If your abstract is still too long, look for unnecessary adjectives or other modifiers that do not directly contribute to a reader’s understanding of your project. Look for places where you repeat yourself, and cut out all unnecessary information.
How should I start writing my abstract?
Re-examine the work you have done so far (whether it is your entire project or a portion of it). Look specifically for your objectives, methods, results, and conclusions.
After re-examining your work, write a rough draft without looking back at the materials you’re abstracting. This will help you make sure you are condensing the ideas into abstract form rather than simply cutting and pasting sentences that contain too much or too little information.
Bring your draft to the Writing Center to get feedback from a writing instructor. Call 263-1992 to make an appointment.
What stylistic techniques will make my abstract most effective?
Avoid jargon. Jargon is the specialized, technical vocabulary that is used for communicating within a specific field. Jargon is not effective for communicating ideas to a broader, less specialized audience such as the Undergraduate Symposium audience.
Discipline-specific sentence: Hostilities will be engaged with our adversary on the coastal perimeter.
Revised for a more general audience: We will fight on the beaches.
Discipline-specific sentence: Geographical and cultural factors function to spatially confine growth to specific regions for long periods of time.
Revised for a more general audience: Geographical and cultural factors limit long-term economic growth to regions that are already prosperous.
Discipline-specific sentence: The implementation of statute-mandated regulated inputs exceeds the conceptualization of the administrative technicians.
Revised for a more general audience: The employees are having difficulty mastering the new regulations required by the law.
(Examples excerpted from Lantham, Richard. Revising Prose; McCloskey, Donald N. The Writing of Economics; and Scott, Gregory M. and Garrison, Stephen M., The Political Science Student Writer’s Manual.)
Be concise. Don’t use three words where you can communicate the same idea in one. Don’t repeat information or go into too much detail. Don’t just cut and paste sentences from your research paper into your abstract; writing that is appropriate for long papers is often too complicated for abstracts. Read more about general principles of writing clear, concise sentences.
Useshort, direct sentences. Vary your sentence structure to avoid choppiness. Read your abstract aloud, or ask someone else to read it aloud to you, to see if the abstract is appropriately fluid or too choppy.
Usepast tense when describing what you have already done.
Check with a professor in your field to determine whether active or passive voice is more appropriate for your discipline. Read more about active and passive voice.
Don’t cite sources, figures, or tables, and don’t include long quotations. This type of material takes up too much space and distracts from the overall scope of your project.
What kind of feedback should I seek to make sure my abstract is effective?
Work with a professor or another student in your field throughout the entire process of writing your abstract. People familiar with work in your field will be able to help you see where you need to say more and where you need to say less and will be able to help with clarity and precision as well.
Bring your draft to the Writing Center to get feedback from a writing instructor. Call 263-1992 to set up an appointment.
Finally, ask someone you know (a roommate, friend, or family member) who specializes in a different field to read your abstract and point out any confusing points. If you can make your abstract understandable to an intelligent non-specialist, you’ve probably made it effective for the audience of a standard conference or symposium.
Continue reading for examples of abstracts from many disciplines.
(Works Consulted: LEO Writing Abstracts, ©1995, ‘96, ‘97, ’98 The Write Place; Writer’s Workshop, University of Illinois, Urbana, adapted by Kitty O. Locker, 1997.)
Guidelines on writing a research proposalby Matthew McGranaghan
This is a work in progress, intended to organize my thoughts on the process of formulating a proposal. If you have any thoughts on the contents, or on the notion of making this available to students, please share them with me. Thanks.
This is a guide to writing M.A. research proposals. The same principles apply to dissertation proposals and to proposals to most funding agencies. It includes a model outline, but advisor, committee and funding agency expectations vary and your proposal will be a variation on this basic theme. Use these guidelines as a point of departure for discussions with your advisor. They may serve as a straw-man against which to build your understanding both of your project and of proposal writing.
Proposal writing is important to your pursuit of a graduate degree. The proposal is, in effect, an intellectual scholastic (not legal) contract between you and your committee. It specifies what you will do, how you will do it, and how you will interpret the results. In specifying what will be done it also gives criteria for determining whether it is done. In approving the proposal, your committee gives their best judgment that the approach to the research is reasonable and likely to yield the anticipated results. They are implicitly agreeing that they will accept the result as adequate for the purpose of granting a degree. (Of course you will have to write the thesis in acceptable form, and you probably will discover things in the course of your research that were not anticipated but which should be addressed in your thesis, but the minimum core intellectual contribution of your thesis will be set by the proposal.) Both parties benefit from an agreed upon plan.
The objective in writing a proposal is to describe what you will do, why it should be done, how you will do it and what you expect will result. Being clear about these things from the beginning will help you complete your thesis in a timely fashion. A vague, weak or fuzzy proposal can lead to a long, painful, and often unsuccessful thesis writing exercise. A clean, well thought-out, proposal forms the backbone for the thesis itself. The structures are identical and through the miracle of word-processing, your proposal will probably become your thesis.
A good thesis proposal hinges on a good idea. Once you have a good idea, you can draft the proposal in an evening. Getting a good idea hinges on familiarity with the topic. This assumes a longer preparatory period of reading, observation, discussion, and incubation. Read everything that you can in your area of interest. Figure out what are the important and missing parts of our understanding. Figure out how to build/discover those pieces. Live and breathe the topic. Talk about it with anyone who is interested. Then just write the important parts as the proposal. Filling in the things that we do not know and that will help us know more: that is what research is all about.
Proposals help you estimate the size of a project. Don't make the project too big. Our MA program statement used to say that a thesis is equivalent to a published paper in scope. These days, sixty double spaced pages, with figures, tables and bibliography, would be a long paper. Your proposal will be shorter, perhaps five pages and certainly no more than fifteen pages. (For perspective, the NSF limits the length of proposal narratives to 15 pages, even when the request might be for multiple hundreds of thousands of dollars.) The merit of the proposal counts, not the weight. Shoot for five pithy pages that indicate to a relatively well-informed audience that you know the topic and how its logic hangs together, rather than fifteen or twenty pages that indicate that you have read a lot of things but not yet boiled it down to a set of prioritized linked questions.
Different Theses, Similar Proposals
This guide includes an outline that looks like a "fill-in the blanks model" and, while in the abstract all proposals are similar, each proposal will have its own particular variation on the basic theme. Each research project is different and each needs a specifically tailored proposal to bring it into focus. Different advisors, committees and agencies have different expectations and you should find out what these are as early as possible; ask your advisor for advice on this. Further, different types of thesis require slightly different proposals. What style of work is published in your sub-discipline?
Characterizing theses is difficult. Some theses are "straight science". Some are essentially opinion pieces. Some are policy oriented. In the end, they may well all be interpretations of observations, and differentiated by the rules that constrain the interpretation. (Different advisors will have different preferences about the rules, the meta-discourse, in which we all work.)
In the abstract all proposals are very similar. They need to show a reasonably informed reader why a particular topic is important to address and how you will do it. To that end, a proposal needs to show how your work fits into what is already known about the topic and what new contribution your work will make. Specify the question that your research will answer, establish why it is a significant question, show how you are going to answer the question, and indicate what you expect we will learn. The proposal should situate the work in the literature, it should show why this is an (if not the most) important question to answer in the field, and convince your committee (the skeptical readers that they are) that your approach will in fact result in an answer to the question.
Theses which address research questions that can be answered by making plan-able observations (and applying hypothesis testing or model selection techniques) are preferred and perhaps the easiest to write. Because they address well-bounded topics, they can be very tight, but they do require more planning on the front end. Theses which are largely based on synthesis of observations, rumination, speculation, and opinion formation are harder to write, and usually not as convincing, often because they address questions which are not well-bounded and essentially unanswerable. (One 'old saw' about research in the social sciences is that the finding is always: "some do and some don't". Try to avoid such insight-less findings; finding "who do and who don't" is better.) One problem with this type of project is that it is often impossible to tell when you are "done". Another problem is that the nature of argument for a position rather than the reasoned rejection of alternatives to it encourages shepherding a favored notion rather than converging more directly toward a truth. (See Chamberlain's and Platt's articles). A good proposal helps one see and avoid these problems.
Literature review-based theses involve collection of information from the literature, distillation of it, and coming up with new insight on an issue. One problem with this type of research is that you might find the perfect succinct answer to your question on the night before (or after) you turn in the final draft --- in someone else's work. This certainly can knock the wind out of your sails. (But note that even a straight-ahead science thesis can have the problem of discovering, late in the game, that the work you have done or are doing has already been done; this is where familiarity with the relevant literature by both yourself and your committee members is important.)
A Couple of Models for Proposals
A Two Page (Preliminary Proposal) Model
Here is a model for a very brief (maybe five paragraph) proposal that you might use to interest faculty in sitting on your committee. People who are not yet hooked may especially appreciate its brevity.
In the first paragraph, the first sentence identifies the general topic area. The second sentence gives the research question, and the third sentence establishes its significance.
The next couple of paragraphs gives the larger historical perspective on the topic. Essentially list the major schools of thought on the topic and very briefly review the literature in the area with its major findings. Who has written on the topic and what have they found? Allocate about a sentence per important person or finding. Include any preliminary findings you have, and indicate what open questions are left. Restate your question in this context, showing how it fits into this larger picture.
The next paragraph describes your methodology. It tells how will you approach the question, what you will need to do it.
The final paragraph outlines your expected results, how you will interpret them, and how they will fit into the our larger understanding i.e., 'the literature'.
The (Longer) Standard Model
The two outlines below are intended to show both what are the standard parts of a proposal and of a science paper. Notice that the only real difference is that you change "expected results" to "results" in the paper, and usually leave the budget out, of the paper.A Basic Proposal Outline: Introduction Topic area Research question Significance to knowledge Literature review Previous research others & yours Interlocking findings and Unanswered questions Your preliminary work on the topic The remaining questions and inter-locking logic Reprise of your research question(s) in this context Methodology Approach Data needs Analytic techniques Plan for interpreting results Expected results Budget Bibliography (or References) The Basic Thesis Outline Introduction Topic area Research question (finding?) Significance to knowledge Literature review Previous research others & yours Interlocking findings and Unanswered questions Your preliminary work on the topic The remaining questions and inter-locking logic Reprise of your research question(s) in this context Methodology Approach Data needs Analytic techniques Plan for interpreting results Results Discussion and Conclusions Bibliography
Another outline (maybe from Gary Fuller?).Introduction Topic area Research Question and its significance to knowledge Literature review Previous research Your preliminary work on the topic The remaining questions and their inter-locking logic Reprise of your resulting question in this context Methodology Approach to answering the question Data needs Analytic techniques Plan for interpreting results Budget Expected results Bibliography / References
Each of these outlines is very similar. You probably see already that the proposal's organization lends itself to word-processing right into the final thesis. It also makes it easy for readers to find relevant parts more easily. The section below goes into slightly more detail on what each of the points in the outline is and does.
The Sections of the Proposal
A good title will clue the reader into the topic but it can not tell the whole story. Follow the title with a strong introduction. The introduction provides a brief overview that tells a fairly well informed (but perhaps non-specialist) reader what the proposal is about. It might be as short as a single page, but it should be very clearly written, and it should let one assess whether the research is relevant to their own. With luck it will hook the reader's interest.
What is your proposal about? Setting the topical area is a start but you need more, and quickly. Get specific about what your research will address.
Once the topic is established, come right to the point. What are you doing? What specific issue or question will your work address? Very briefly (this is still the introduction) say how you will approach the work. What will we learn from your work?
Why is this work important? Show why this is it important to answer this question. What are the implications of doing it? How does it link to other knowledge? How does it stand to inform policy making? This should show how this project is significant to our body of knowledge. Why is it important to our understanding of the world? It should establish why I would want to read on. It should also tell me why I would want to support, or fund, the project.
State of our knowledge
The purpose of the literature review is to situate your research in the context of what is already known about a topic. It need not be exhaustive, it needs to show how your work will benefit the whole. It should provide the theoretical basis for your work, show what has been done in the area by others, and set the stage for your work.
In a literature review you should give the reader enough ties to the literature that they feel confident that you have found, read, and assimilated the literature in the field. It might do well to include a paragraph that summarizes each article's contribution, and a bit of 'mortar' to hold the edifice together, perhaps these come from your notes while reading the material. The flow should probably move from the more general to the more focused studies, or perhaps use historical progression to develop the story. It need not be exhaustive; relevance is 'key'.
This is where you present the holes in the knowledge that need to be plugged, and by doing so, situate your work. It is the place where you establish that your work will fit in and be significant to the discipline. This can be made easier if there is literature that comes out and says "Hey, this is a topic that needs to be treated! What is the answer to this question?" and you will sometimes see this type of piece in the literature. Perhaps there is a reason to read old AAG presidential addresses.
Research Questions in Detail
Your work to date
Tell what you have done so far. It might report preliminary studies that you have conducted to establish the feasibility of your research. It should give a sense that you are in a position to add to the body of knowledge.
Overview of approach
This section should make clear to the reader the way that you intend to approach the research question and the techniques and logic that you will use to address it.
This might include the field site description, a description of the instruments you will use, and particularly the data that you anticipate collecting. You may need to comment on site and resource accessibility in the time frame and budget that you have available, to demonstrate feasibility, but the emphasis in this section should be to fully describe specifically what data you will be using in your study. Part of the purpose of doing this is to detect flaws in the plan before they become problems in the research.
This should explain in some detail how you will manipulate the data that you assembled to get at the information that you will use to answer your question. It will include the statistical or other techniques and the tools that you will use in processing the data. It probably should also include an indication of the range of outcomes that you could reasonably expect from your observations.
In this section you should indicate how the anticipated outcomes will be interpreted to answer the research question. It is extremely beneficial to anticipate the range of outcomes from your analysis, and for each know what it will mean in terms of the answer to your question.
This section should give a good indication of what you expect to get out of the research. It should join the data analysis and possible outcomes to the theory and questions that you have raised. It will be a good place to summarize the significance of the work.
It is often useful from the very beginning of formulating your work to write one page for this section to focus your reasoning as you build the rest of the proposal.
This is the list of the relevant works. Some advisors like exhaustive lists. I think that the Graduate Division specifies that you call it "Bibliography". Others like to see only the literature which you actually cite. Most fall in between: there is no reason to cite irrelevant literature but it may be useful to keep track of it even if only to say that it was examined and found to be irrelevant.
Use a standard format. Order the references alphabetically, and use "flag" paragraphs as per the University's Guidelines.
Tips and Tricks
Read. Read everything you can find in your area of interest. Read. Read. Read. Take notes, and talk to your advisor about the topic. If your advisor won't talk to you, find another one or rely on 'the net' for intellectual interaction. Email has the advantage of forcing you to get your thoughts into written words that can be refined, edited and improved. It also gets time stamped records of when you submitted what to your advisor and how long it took to get a response.
Write about the topic a lot, and don't be afraid to tear up (delete) passages that just don't work. Often you can re-think and re-type faster than than you can edit your way out of a hopeless mess. The advantage is in the re-thinking.
Very early on, generate the research question, critical observation, interpretations of the possible outcomes, and the expected results. These are the core of the project and will help focus your reading and thinking. Modify them as needed as your understanding increases.
Use some systematic way of recording notes and bibliographic information from the very beginning. The classic approach is a deck of index cards. You can sort, regroup, layout spatial arrangements and work on the beach. Possibly a slight improvement is to use a word-processor file that contains bibliographic reference information and notes, quotes etc. that you take from the source. This can be sorted, searched, diced and sliced in your familiar word-processor. You may even print the index cards from the word-processor if you like the ability to physically re-arrange things.
Even better for some, is to use specialized bibliographic database software. Papyrus, EndNote, and other packages are available for PCs and MacIntoshs. The bib-refer and bibTex software on UNIX computers are also very handy and have the advantage of working with plain ASCII text files (no need to worry about getting at your information when the wordprocessor is several generations along). All of these tools link to various word-processors to make constructing and formating your final bibliography easier, but you won't do that many times anyway. If they help you organize your notes and thinking, that is the benefit.
Another pointer is to keep in mind from the outset that this project is neither the last nor the greatest thing you will do in your life. It is just one step along the way. Get it done and get on with the next one. The length to shoot for is "equivalent to a published paper", sixty pages of double spaced text, plus figures tables, table of contents, references, etc. is probably all you need. In practice, most theses try to do too much and become too long. Cover your topic, but don't confuse it with too many loosely relevant side lines.
This is not complete and needs a little rearranging.
The balance between Introduction and Literature Review needs to be thought out. The reader will want to be able to figure out whether to read the proposal. The literature review should be sufficiently inclusive that the reader can tell where the bounds of knowledge lie. It should also show that the proposer knows what has been done in the field (and the methods used).
The balance may change between the proposal and the thesis. It is common, although not really desirable, for theses to make reference to every slightly related piece of work that can be found. This is not necessary. Refer to the work that actually is linked to your study, don't go too far afield (unless your committee is adamant that you do ;-).
Krathwohl, David R. 1988. How to Prepare a Research Proposal: Guidelines for Funding and Dissertations in the Social and Behavioral Sciences . Syracuse University Press.
Recent National Science Foundations Guidelines for Research Proposals can be found on the NSF website, www.nsf.gov.
Chamberlain, T.C. "The Method of Multiple Working Hypotheses", reprinted in Science, Vol 148, pp754-759. 7 May 1965.
Platt, J. "Strong Inference" in Science, Number 3642, pp. 347-353, 16 October 1964.
Strunk and White The Elements of Style
Turabian, Kate. 1955 (or a more recent edition) A Manual for Writers of Term Papers, Theses and Dissertations, University of Chicago Press.
Mortimer J. Adler and Charles Van Doren. 1940 ('67, '72 etc). How to Read a Book. Simon and Schuster Publishers. New York City, NY.