Credit portal




How to write a notarized statement

how to write a notarized statement

NOTE FOR CERTIFICATION PROGRAM: the CCP Technical Paper requirement is only 2,500 words not the 3,500 words as required for other AACE technical submittals.

View the Webinar

How to Write a Technical Paper

James D. Whiteside. II PE

ABSTRACT— The Association for the Advancement of Cost Engineering International “Official Guidelines for Preparing Papers” describes how to structure and format a paper for publication, yet writing a 3,500 (CCP Technical Paper word count is 2,500) word paper is intimidating. This paper describes a useful story board technique and a basic organizational format to get most technical authors past the "writer's block." The paper is intended to assist the first time author, as well as the seasoned author. Sensitive items such as addressing copyright, legal review, and proprietary data will be presented. Advanced writing tips will show how to select an editor, avoid common grammatical mistakes, incorporate technical reviews, and how to address the audience. The goal is to transform knowledge authors into recognized world-class authorities by helping them communicate their ideas on paper.

Keywords: Authors, copyright, formatting, legal reviews and technical writing

In the past few years, the Technical Board has noticed that the quality of manuscripts submitted for Annual Meetings has sharply deteriorated. Papers are submitted without a table of contents, bibliographies, and sometimes there are no papers at all for many presentations. The Association for the Advancement of Cost Engineering International (AACE International) has author guidelines published on its website [1]. One page in the guidelines addresses the minimum essentials for bibliography, units of measurements, style, etc. of the structure for technical papers submitted for publication. Technical papers serve as a reference library to the membership and future AACE International members in developing Recommended Practices. Therefore, it is important to seek to develop a common style and minimum standard to better serve the project controls community. This paper provides explanation on the format, and general guidelines that AACE International expects in a technical paper.

The Title

The title is the author’s introduction of the subject to the reader. An effective title will be descriptive and easy to remember. If the title can be remembered, then chances are the reader will take the time to remember the author’s name as well. To be effective, a title should be about six words or less.

Technical papers should not have ambiguous titles such as “10 Things We Remembered in the Bog After the Big Storm”. It would be more appropriate to title the paper, “Project Control Issues After Hurricane Katrina.” The reader is given several items of interest: a period of time (Hurricane Katrina), a location (US Gulf Coast), a subject (project controls). Ambiguous titles do not clearly convey the topic to the audience. Instead they indicate that the paper is only useful to a small local audience of people who already know the author, or it is a paper to attract people seeking entertainment instead of continuing their education. If the title is unclear, the paper may not attract the intended audience.

Address the Audience

The first decision of authoring is to decide what audience will benefit the most with the material.

Potential audiences for technical material include the following.
  • Those who are new to the subject, industry, or discipline.
  • Those who have an intermediate level of experience and want to expand their knowledge. And,
  • Those who are experts in the field who are looking for multiple applications of similar ideas.
It is important to pick an audience and write the paper to meet their experience level. This will keep their interest and allow the author to leave out non-essential elements. For example, writing a paper to an audience new to oil refining will require more definitions for terms related to the industry. Basic refining terminology can be abbreviated when writing the same paper for experts in the field who are more interested in the advanced application and not the basic theory.

If the technical material is not understood, then it is meaningless because there is no audience that will understand it. The material should always be instructive. Sometimes, when an author writes for a fixed circle of readers, the material becomes dependant on these “insiders” knowing what is trying to be conveyed. Always write for complete strangers. If writing on thermodynamics, it may be appropriate that the audience should be familiar with thermodynamics. If introducing a new concept in thermodynamics, then it would be appropriate to first build a brief introduction leading to the new concept.

Getting Started

Start collecting data a year or two ahead of time. Technical papers are generally focused on data, data interpretation, validation, and application. Otherwise, it is not a technical paper. For any paper, plan on a few weeks to write a 3,500 (CCP Technical Paper word count is 2,500) word paper. For technical papers, be sure that the data is solid, the equations are correct, and that the results are repeatable. If the results are not repeatable, then the paper has limited value to contributing to the advancement of the technology body of work.

Always start with the abstract and be sure that the paper addresses all the points of interest of the abstract when the paper is finished. The paper is “sold” to the reader by the title and the abstract. If the paper fails to meet the reader’s expectations of the title and abstract, then the author looses creditability.

A technical paper should be self contained and not dependant on a publisher to make it useful. A magazine publisher will drop the table of contents, equation, and figures if they are not needed. A book publisher will incorporate these into a single master table at the front of the book. However, a technical paper is the most useful standalone instrument an author has to place themselves into the technical community.

A technical paper is the reflection of the author. This paper does not address publication issues, but it makes it far easier on the publisher if the author can show the publisher how the paper is intended to look for clarity.


Writer’s block can paralyze an author and result in ideas not being shared. Most authors find it easier to discuss their ideas than to commit ideas to paper. They can weave a good story to present their ideas and most authors are really good at the art of story telling. Story telling to a technical mind is nearly abhorrent behavior. Technical minds want to convey facts and data. They do not want to tell “stories.” There has to be a compromise.

Storyboarding is the process of taking events or facts and placing them into an order that makes sense to an audience. This process is useful to the technical minded author; the ordering facts from basic input to the final conclusion. To start the storyboard process, place every idea, fact, figure, on a separate piece of paper. Do not attempt to organize the ideas at this stage.

Next take each of the idea sheets and tape them to a wall or place them on the floor or table. Start organizing the ideas from inputs to final conclusion. Review the story to be sure that it flows smoothly. If there is a gap in the flow, then create another sheet of paper with the idea to fill the gap. Remove redundant ideas.

There are many styles of technical papers. The style of a technical paper follows an outline set by the table of contents. Each subject in the table of contents should have a heading in the paper. Each subject should have a few paragraphs to develop the topic and explain why it is important. It is more important to understand what is going to be interesting to the reader than using the paper as a dumping ground for ideas. Where possible, connect the following topic from the previous topic to transition the reader through the paper. A collection of disjointed or dissimilar topics is like reading a dictionary. If a topic appears out of place, either reorganize the paper, consolidate the topic with another similar topic, or decide if the topic can be removed without seriously affecting the content. If in

doubt, ask a technical reviewer or the editor to assist.

Once ideas flow smoothly, it is time to insert transitions between ideas. Transitions are working examples of the idea to bring about clarity. Be brief and do not create a story behind the example because it is not important and could detract from the technical presentation. An example is only to be illustrated to move from the last point into the next. Illustrations help readers get a mental picture of the point so that they are prepared to move to the next new topic in the story.

Now that the storyboard is complete, the paper is ready to write. Take the first paper and create a header and write a paragraph about the idea. Create doodles/hand sketches of figures for transitions. Once the story board has been converted from a set of ideas into a set of paragraphs and sketches place them on the wall or floor again and read through the paper for clarity. This would be a good time to have a technical reviewer look through the paper for clarity.

Finally, work can begin in earnest. It is time to commit each idea sheet into a fully developed set of paragraphs and convert sketches into final figures. When this is done, a draft copy is ready for commenting by the editor and technical reviewers. Do not throw away the storyboard because in the process of commenting, the storyboard serves as the master outline of the paper. This storyboard will also be useful in preparing the presentation. Resist major changes at this time. Major changes should have been addressed during the storyboard phase.

Getting Comfortable

When converting the storyboard into a final paper, it is not unreasonable to find a place (both mentally and physically) to get comfortable while writing. Keeping disruptions to a minimum is good. Consider taking a few weeks of vacation away from work. There is always that favorite chair, desk, room, and even a season of the year that helps an author get into the same writing mode as last time. Writing is a tactile event. This means that it is a habit that is improved by physical objects. For example, some people can not read the morning paper without drinking coffee from their favorite coffee mug. Once a writing habit has been created, that habit will serve the author well on the next paper.

The Abstract

The purpose of an abstract is to entice potential customers to purchase the material or attend the presentation. Abstracts between 100 to 175 words are generally well received. Longer abstracts tend to be short versions of the material. Once a potential customer has finished reading the long version, there is a high likelihood that they will not attend the presentation or purchase the material.

When writing an abstract, keep the best material in the paper. Do not give away good ideas for free. Authoring a paper is a commercial enterprise. The abstract sells papers, books, invites authors to conferences, etc.

Length of Paper

The length of a technical paper is not to exceed 5,000 (CCP Technical Paper word count is a minimum of 2,500 words) words [1]. This includes everything from the title to the final bibliography. If the subject requires more, then consider writing a second paper. The length of a technical paper is about right for a chapter in a book. Most authors do not start out writing a book. However, most authors tend to write many papers in their area of expertise and eventually have enough material for a book. Also, the length of the paper allows for multiple authors to contribute to a book.

Units of Measure

Units of measure should be international (metric). Experienced audiences will be quick to judge and evaluate data using their reference, metrics. Consider including both international (metric) and English units for data. This would allow the reader to use their metrics to judge the data in the paper for authenticity. If the reader can quickly assess that their data experience matches the data in the paper, then the reader will continue to read. Otherwise, if the reader has difficulty relating to the units used in the paper they will quit reading.


It pays to have a translator. Translate the paper into the language of the country in which the paper is going to be published. For example, a paper intended for an audience comprised mostly of readers from the US, should use the regularly used syntax of those readers. The same would apply also if the technical paper was to be published in Spanish for publication in Spain. Many great ideas are lost in a poor translation.

The biggest common mistake in translating into English is using run-on sentences. Run-on sentences have multiple ideas forced into one sentence. Keep sentences simple. A technical paper is a tough assignment. Most of the best books are those which the author uses one idea per sentence.

Tenses such as has, had, been, will, and would need to make sense through out the paper. Pick a tense and keep the theme of the paper in that particular tense. The easiest tense to choose is the present tense.

Selecting an Editor

The function of an editor is to review the technical paper for clarity. For this reason, choose an editor who is not a technical expert because they bring objectivity to the review. It is good that they have a general understanding of the topic so that they can suggest improvements to style and content. When multiple authors contribute to writing a paper, an editor can help them adapt their style to ensure that the paper reads as though it was written by a single author. When readers have to try to understand ways in which multiple authors express the same ideas in the paper, the paper’s value is questioned. Again, not only must the paper have grammatical clarity, it must also be written with a common style and expression.

Once an editor has been found and the author is happy with the level of success the paper has acquired, then consider using the same editor in future papers. Editors control the image, the expression, and the style of the author. Editors help maintain the standard expression of the author, which is protected by copyright laws. If there is any infringement case, then the author’s best defense is to demonstrate that over time and through many papers, that the expression of the author remains unchanged. If it can be shown that the author’s expression in papers has persistent changes, then there may be some doubt of authorship cast upon the author, and the author may not have a solid case for pursuing infringement. Many companies, organizations, and highly successful authors go to extremes to protect the “look and feel” of their body of work.

Technical Review

Choose technical reviewers for the expertise they have in the field related to the paper. It is important to be confident that the paper is checked for deficiencies in data, theory, and application.

It is important to have different reviewers for every paper that is written. Fresh reviewers that are familiar with the area of expertise but may not have any association with the author are the best technical reviewers. They have no vested interest, nothing to gain or lose from the paper; therefore, can offer the most constructive criticism. Reviewers can range from theoretical to application. The target audience will help determine the mix of reviewers. If the paper is mostly theoretical, then having more doctorate reviewers would be appropriate. Practitioners in the field would be best suited for how the subject works in the real world. Always include both where practical. The practitioners will tell you if they can apply the methodology and the doctorates will point out deficiencies in concepts.


When using an equation such as the example that follows, show the equation and then explain each of the variables from left to right. When text is read from left to right, the reader can easily follow the variable explanation from top to bottom.

dS/S = exp (μX (dT) + std X ∈ X (dT) 1/2 )) (equation 1)

Category: Forex

Similar articles: