84
Technical Report Writing Technical Writing By William S. Pfeiffer

Technical Report Writing Technical Writing By William S. Pfeiffer

Embed Size (px)

Citation preview

Page 1: Technical Report Writing Technical Writing By William S. Pfeiffer

Technical Report Writing

Technical Writing By

William S. Pfeiffer

Page 2: Technical Report Writing Technical Writing By William S. Pfeiffer

1. The Writing Process: Achieving Speed and Quality

2. Structure: Achieving Order and Design

3. Writing Handbook: Achieving Clarity and Design

Page 3: Technical Report Writing Technical Writing By William S. Pfeiffer

Chapter-1

The Writing Process: Achieving Speed and Quality

Page 4: Technical Report Writing Technical Writing By William S. Pfeiffer

Definition of Technical Writing

We do three main types of writings:

1. Academic;

2. Personal;

3. Technical;TYPEAcademic

Personal

Technical

PURPOSEDisplay knowledge

Enlighten,Entertain

Get something done

AUDIENCETeachers,Students,

Friends,Yourself

Supervisors,Subordinates,Customers

EXAMPLEResearch Paper

Journal,Letters

Reports

Page 5: Technical Report Writing Technical Writing By William S. Pfeiffer

The term “Technical Writing” is originally referred only to writing done in the fields of technology, engineering, and science, but it has come to mean writing done in all professions and organizations. Technical writing can be distinguished from other prose by features related to its

1. purpose.

2. writer, and

3. reader(s),

Page 6: Technical Report Writing Technical Writing By William S. Pfeiffer

Purpose: Getting something done

With such writing you strive to get something accomplished for your organization, for a customer, or for both. Academic writing displays knowledge, and personal writings entertains or enlightens. Although technical writing may sometimes have these goals too, its main purpose is practical, for example to change a policy, to offer a new product, or to explain a procedure.

Writer: Conveying your knowledge to the Reader

Page 7: Technical Report Writing Technical Writing By William S. Pfeiffer

As writer, you have something to tell your readers. Usually you know more about the topic than they do –that’s why writing to them. Readers benefit knowledge you provide and make changes accordingly.

Readers: Understanding their Diverse Needs

Understanding their diverse needs, your job would be simpler if each document were directed to just one reader. But actual technical writing is not easy. Instead a document often has many readers with mixed technical backgrounds and with different needs.

Page 8: Technical Report Writing Technical Writing By William S. Pfeiffer

Thus the fabric of technical writing is formed by the special combination of three elements as shown in the figure on the next slide.

1. A practical purpose

2. A writer more informed about than the audience

3. Readers with diverse needs

Page 9: Technical Report Writing Technical Writing By William S. Pfeiffer

Technical WritingTriangle

Technical Writing

Practical Purpose

Informed W

riter

Reader

s with

Diver

se

Needs

Page 10: Technical Report Writing Technical Writing By William S. Pfeiffer

NINE STEPS TO BETTER WRITING

Most good writers are made, not born. They work hard at perfecting the process of writing. The written product may appear effortlessly produced, but actually it results from a disciplined approach to composition. This discipline is embodied in a nine step plan. If you follow this plan, you will learn that there is no mystery to improving the efficiency and quality of your writing.

Page 11: Technical Report Writing Technical Writing By William S. Pfeiffer

Of the main stages of writing—planning, drafting and revising—the first deserves the most attention, but often receives the least. The first seven steps concern the planning process. Then steps 8 and 9 offer suggestions for drafting and revising your draft.

Step-1: Write a Brief Purpose Statement

A one- or two-sentences statement helps get you started. It becomes the lead-in to your outline and then often becomes the first words in the document itself.

Page 12: Technical Report Writing Technical Writing By William S. Pfeiffer

Writing a purpose statement forces you to decide exactly why you are writing. It directs your effort and becomes the lens through which you view the entire writing project.

A purpose statement can begin with a simple phrase like “The purpose of the report is to --------.” or it can include more subtle phrasing. Whatever wording you choose, strive to write a passage that clearly sets forth your intentions.

Page 13: Technical Report Writing Technical Writing By William S. Pfeiffer

Purpose Statements

Example-1: This report presents the findings of our fieldwork at Trinity Dam, along with our recommendation that the spillway be replaced.

Example-2: The purpose of this report is to compare and contrast two packages, from Ufone and Warid being considered for the Punjab University. This report draws conclusions about the package best suited for the Punjab University.

Page 14: Technical Report Writing Technical Writing By William S. Pfeiffer

Note that a purpose statement only indicates why you are writing. It does not present summary points such as conclusions or recommendations. It gives direction, not results, and intends only to get you started in the technical writing process.

Step-2: Consider the Obstacles your Readers Face

In an ideal world, readers would anxiously await your documents and give them their undivided attention. Consider following assumptions about the audience members:

Page 15: Technical Report Writing Technical Writing By William S. Pfeiffer

They are always interrupted

Meetings, phone calls, emails lunch, and even business trips may interrupt them as they read your document.They are impatient

They want you to deliver the goods quickly and clearly. While they read, they are thinking, “What’s the point?” or “What does this have to do with me?” or “so what?”They Lack your Technical Knowledge

Page 16: Technical Report Writing Technical Writing By William S. Pfeiffer

They may not understand the technical knowledge you use. Thus they will feel insulted—or just plain lost—if you speak in terms they cannot understand.Most Documents have more than One Reader

Readers share decision making with others. Your document may be read by persons of different levels and with different needs.

Keeping these points in mind, next you need to determine the technical levels and decision making authority of your readers.

Page 17: Technical Report Writing Technical Writing By William S. Pfeiffer

Step-3: Determine Technical Levels of your Readers

How much do your readers know about the subject? To answer this question, you can place most readers into one of the four categories that follow:Category 1: Managers

Managers often are removed from the hands-0n-details of the topic. They need brief summaries, background information, and definitions of technical terms.

Page 18: Technical Report Writing Technical Writing By William S. Pfeiffer

Category 2: Experts

Experts have a good understanding of the technical aspects of your topic, They need supporting technical details, helpful tables and figures, and even appendices of supporting information.Category-3: Operators

Operators—such as field technicians, office workers, or sales force –apply the ideas in your document to their job. They need (a) clear organization so that they can find sections relevant to them, (b) well written procedures

Page 19: Technical Report Writing Technical Writing By William S. Pfeiffer

and (c) clarity about how the documents affects their job.Category-4: General Readers

General Readers, also known as “Laypersons” have the least amount of information on your topic and often are outside an organization—for example, citizens reading a report on the environmental impact of a factory proposed for their community. They need (a) definitions of technical terms, (b)frequent use of graphics, and (c) clarity about how the document affects them.

Page 20: Technical Report Writing Technical Writing By William S. Pfeiffer

Step-4: Determine Decision-Making Levels of Your Readers

Your readers can also be classified by the degrees to which they make decisions based on your document. During the planning process you can classify your readers into the following three groups:Decision Makers

The decision-makers translate your document into action. Decisions can be made by an individual or by a committee.

Page 21: Technical Report Writing Technical Writing By William S. Pfeiffer

Advisers

Also advisers do not make decisions themselves, they have the ear of people who do. Busy executives hire their services to analyze the technical points of the document. Final decision may rest on recommendations that flow from this analysis.Receivers

Some readers are not part of the decision making process. They receive information from the

Page 22: Technical Report Writing Technical Writing By William S. Pfeiffer

Document and make necessary adjustments, say in their jobs accordingly.

Step-5: Find Out What Decision Makers Want

You need to focus on the needs of the most important readers—those who make decisions. Three suggestions follow:Write Down What You Know About

Decision Makers

Specifically try to get answers to these six questions:

Page 23: Technical Report Writing Technical Writing By William S. Pfeiffer

1. What is their educational background?

2. What is their technical literacy on the topic?

3. What main question(s) do the want answered?

4. What main action do you want them to take?

5. What style or format do they like in the documents?

6. What personality traits may affect their reading?

Talk with Colleagues Who Have Written to the same Readers

Page 24: Technical Report Writing Technical Writing By William S. Pfeiffer

Someone else in your organization may know the needs of your of the decision makers for your document. Ask around the office to see if your colleagues can help you answer the six preceding questions.Remember That All Readers Prefer

Simplicity

When you are not able to find out much about the decision maker, remember one essential point that they prefer documents as short and simple as possible. The popular KISS Principle is always the best rule to follow.

Page 25: Technical Report Writing Technical Writing By William S. Pfeiffer

Step-6: Collect and Document Information Carefully

Whether you gather information yourself or get it from other sources, be careful during the research phase of the planning process. First your reader may want to know exactly how you developed supporting data, second your professional reputation. Some suggestions follow:Record Notes CarefullyCarefully Transfer Information from Notes to

DraftUse the Right Citation System

Page 26: Technical Report Writing Technical Writing By William S. Pfeiffer

Step-7: Write an Outline

Completing an outline is the single best way to write both quickly and well. This section answers three main questions:Why is an Outline so important?

Here are the main reasons:

Organization: It forces you to grapple with matters of organization at a time when it is easy to change the structure of the document—that is before you have committed words to draft.

Page 27: Technical Report Writing Technical Writing By William S. Pfeiffer

As you add and delete ideas on the page and shift points from main to secondary topics, you are thinking about the best way to satisfy the reader’s needs.

Visualization: It shows you—visibly—whether you have enough supporting information. For example, if your outline indicates one subheading for a topic, you know that you need either to do more research or to delete the topic.

Review: It is much easier to make changes at this stage than later.

Page 28: Technical Report Writing Technical Writing By William S. Pfeiffer

What should it look like?• Start as points spread over a page without any

recognizable hierarchy.• Evolve to a recognizable list of main and

supporting points• Change shape during the drafting process as

you adjust points of emphasis

Outline is messy business because it reflects the thinking you do before you write. What Steps should you use in writing an

0utline?

Page 29: Technical Report Writing Technical Writing By William S. Pfeiffer

Record Random Ideas Quickly

This process involves the free association of ideas. To stay on track, write your purpose statement at the top of the page. Then scribble down as many points as possible that relate to the topicShow Relationships

Surveying your page of ideas, locate the three or four main points that indicate the direction your document will take. Circle them. Then draw lines to connect these main points to their many supporting points

Page 30: Technical Report Writing Technical Writing By William S. Pfeiffer

Draft a Final Outline

Your messy outline now must be cleaned up to make it useful to you as you write. You can either use the traditional format with roman numerals etc or you can simply use dashes and indenting to indicate outline levels. Whatever format you employ, the final outline should reflect the three main features.

Depth: Be sure that the entire outline has enough support to develop the draft.

Balance: Include adequate detail for all your main points.

Page 31: Technical Report Writing Technical Writing By William S. Pfeiffer

When you subdivide a point, have at least two breakdowns—any object divided has two parts.

Parallel Form: Give points in the same grouping the same grammatical form, both to make the outline easier to read and to ease the transition later to parallel text in the first draft.

Step-8: Write Your First Draft QuicklySchedule Blocks of Drafting Time

Writing requires concentration. Close your door if you have one, head to an empty office, or write at home—just do whatever you must to keep from being interrupted during the writing time.

Page 32: Technical Report Writing Technical Writing By William S. Pfeiffer

Don’t Stop to Edit

Editing uses a different part of your brain. When you stop to correct grammar or spelling errors, you derail the drafting effort. Save editing for later.Begin with the Easiest section

A well structured outline gives you the luxury of starting with almost any part of the document.Write Summaries Last

Summaries sections—like the executive summary for a formal report—usually get written last.

Page 33: Technical Report Writing Technical Writing By William S. Pfeiffer

Step-9: Revise in Stages

During revision, you must attend to matters of content, style, grammar, and mechanics. Here you review the draft several times, correcting a different set of problems on each run through. This effort to focus your attention on specific problems yields the best result.

Four stages of Revision follow:Adjust and Reorganize Content

Here you expand sections that need more development, shorten some sections and change the location of some passages.

Page 34: Technical Report Writing Technical Writing By William S. Pfeiffer

Edit for Style

Style refers to changes that make your writing smoother, more readable, and more interesting. Here are options to consider: Shorten your sentences Improve clarity Change passive-voice sentences to active Define technical terms Add headings, lists, and graphics Replace longer words with synonyms that are

shorter or easier to understand.

Page 35: Technical Report Writing Technical Writing By William S. Pfeiffer

Edit for GrammarEdit for Mechanics

Examples of mechanical errors include the following: Omitted words or/and phrases Misspelled words Inconsistent margins Wrong pages

Page 36: Technical Report Writing Technical Writing By William S. Pfeiffer

Writing in GroupsGroup writing is common in today’s organizations, which emphasize team work at all levels and in all activities. For example a successful proposal or technical manual may result from the combined effort of technical specialists, marketing experts, graphics designers, word processors etc. At its best, group writing benefit from the collective experience and specialties' of all participants.

Page 37: Technical Report Writing Technical Writing By William S. Pfeiffer

Here are the five points to have proper group writing:

Guideline-1: Get to know your group Spend some time talking to group members

before the project begins, establishing a personal relationship, or

Use the first session for informal chatting, before you get down to business

Guideline-2: Set clear goals and ground rules What is the main objective?

Page 38: Technical Report Writing Technical Writing By William S. Pfeiffer

How will tasks be distributed?How the conflicts be resolved/What’s the schedule for the work?

Guideline-3: Use brainstorming techniques Ask the group recorder to take down ideas as

quickly as possible Write ideas on large pieces of paper affixed to

the walls in a room Use the ideas written on the wall sheets to

suggest additional ideas.

Page 39: Technical Report Writing Technical Writing By William S. Pfeiffer

Distribute the results of the exercise to group members after the meeting

Meet again to choose ideas of most use in the project

Guideline-4: Agree on a revision processAvoid making changes for the sake of one

individual’s preferenceSearch areas of agreement among members,

not areas for disagreementMake only those style and grammar changes

that can be supported by rules

Page 40: Technical Report Writing Technical Writing By William S. Pfeiffer

Ask the group’s all rounder best stylist to complete a final edit

Guideline-5: Use Computers to communicate

Whether the group members are in the same building or spread out across world, they can benefit from using computers to communicate about the project. This technology falls under two categories:

Asynchronous: such software permits members to post message to each other and to alter the document, though not at the same time that other group members are making contributions.

Page 41: Technical Report Writing Technical Writing By William S. Pfeiffer

Synchronous: Software of this type allow group members to carry on simultaneous computer “conversations” about a document in real time.

Page 42: Technical Report Writing Technical Writing By William S. Pfeiffer

Chapter-2

Structure: Achieving Order& Design

Page 43: Technical Report Writing Technical Writing By William S. Pfeiffer

Three main sections follow: Basics of Organization

It describe the main rules of technical writing and the three principles that flow from it.

ABC Format

Outlines a three- part pattern of organization—abstract, body, conclusion—that applies to all technical documents.

Page Design

It explains simple formatting techniques that can improve any technical document.

Page 44: Technical Report Writing Technical Writing By William S. Pfeiffer

Organization:

Organization is the arrangement of information within a document.

Structure Rule-1: Write Different parts for Different readers

Most of us avoid reading even short documents straight through. Instead we scan key parts—especially near the beginning and end—and then search for information of most importance. Some readers focus on general overviews, whereas other consider technical sections most important to their jobs.

Page 45: Technical Report Writing Technical Writing By William S. Pfeiffer

In other words you cannot count on readers to digest information in the same order you present it. You can use this fact to your advantage by writing different sections of your document for different readers. Structure Rule-2: Emphasize Beginnings

and Endings

Most of us read fiction and essays much differently than we read technical documents. With the former, we read patiently until plot information and new knowledge come our way.

Page 46: Technical Report Writing Technical Writing By William S. Pfeiffer

With the latter, we rush to find essential information and are impatient when we don’t find it quickly.

In technical writing you must accommodate impatient readers by placing important information where they want it—at the beginning and end of the document.Structure Rule-3: Repeat Key Points

Most people will read your document selectively—not sequentially from beginning to end. This fact means that important information should be repeatedly, especially in long documents. The main principle of technical writing—write for your readers and not for yourself.

Page 47: Technical Report Writing Technical Writing By William S. Pfeiffer

ABC Format

ABC Format, the diamond pattern is used because it implies the following important points about the Abstract, Body, and the Conclusion.

Abstract: provides introductory and summary information. It is represented by the narrow top of the diamond because it is brief and leads into the body.

Body: supplies all supporting details for the document. It is represented by the broad expansive section of the diamond. It is the longest part of the document.

Page 48: Technical Report Writing Technical Writing By William S. Pfeiffer

Conclusion: gives readers what they need to act. It is represented by the narrow bottom section of the diamond because it is brief and leaves away from the body section.

The terms abstract, body, and the conclusion refer to generalized parts of a document, not to specific headings. The exact headings used to represent these sections in a document will vary, depending on the document you are writing and the organization where you work. Think ABC Format as a general organizational pattern

Page 49: Technical Report Writing Technical Writing By William S. Pfeiffer

ABSTRACT

ABC FORMAT

CONCLUSION

BODY

Diamond Pattern

Page 50: Technical Report Writing Technical Writing By William S. Pfeiffer

ABC Rule-1: That abstract gives the “Big Picture”

The abstract component gives readers, especially decision makers, both introductory and summary information. Specifically it gives answer to following four questions:

Purpose: Why are you writing?

Scope: What work did you do?

Results: What main points the decision makers want to know?

Page 51: Technical Report Writing Technical Writing By William S. Pfeiffer

Contents: What main sections follow?

ABC Rule-2: The Body gives supporting Details

The document body gives details of your work. It is specially useful to technical readers who want to see the support of your conclusion or recommendations. As such it answers following three questions:

Background: What led up to the Project?

Methods: How did you gather information?

Data: What information resulted from the field, lab, or office work conducted during the study?

Page 52: Technical Report Writing Technical Writing By William S. Pfeiffer

Follow four general guidelines for the document body:• Use Lead-Ins at the beginning of Sections

Lead-ins give readers a road map for what follow. Readers need such direction finders, in the same way they need an overview at the beginning of the whole document.• Include Listings

Bulleted or numbered lists are easier to read than long paragraphs of text, as long as, you keep lists from becoming too long. Five to nine items are a maximum.

Page 53: Technical Report Writing Technical Writing By William S. Pfeiffer

• Use Graphics

Graphics draw attention to important points. They are especially useful in presenting data to technical readers, most of whom expect effective graphics.• Separate Facts from Opinions

Be clear about where opinions begin and end. Body sections usually move from facts to opinions. To make sections clear, preface your opinions with phrases like “We believe that” or “I think that.”

Page 54: Technical Report Writing Technical Writing By William S. Pfeiffer

ABC Rule-3: The Conclusion provides a Wrap- Up

Generally it answers questions like the following:

Results: What are your conclusions and recommendations?

Action: What happens next?

Emphasis: What single point would you like to leave with readers?

Personal Reader: What can you add that will enhance your relationship with readers?

Page 55: Technical Report Writing Technical Writing By William S. Pfeiffer

Page Design

This means the look of the document.

Design Rule-1: Use White Space Liberally Frame Text with 1″ to 1½″ Margins Experiment with Double Column Skip Lines Between Paragraphs in Single-

spaced Text Use slightly more space above Headings than

Below Them

Design Rule-2: Use Headings & Subheadings often

Page 56: Technical Report Writing Technical Writing By William S. Pfeiffer

Headings are labels used to introduce new sections and subsections. Besides helping readers stay on track, they provide visual relief from the monotony of text and assist in finding specific information later. Following are some suggestions;• Use your Outline to Create Headings and

Subheadings• Use Substantive Wording for Headings• Establish a Clear Visual Ranking of Headings

Design Rule-3: Use Lists Frequently

Page 57: Technical Report Writing Technical Writing By William S. Pfeiffer

• Use Bullets and Numbers• Punctuate, Space, and Capitalize Lists

properly• Use Proper Lead-Ins and Parallel Structure

Lists should be preceded by lead-ins that should be complete grammatical units followed by colons. For example, “We have planned to” should be replaced by “We have planned the following activities:” Also items in the same list should have parallel grammatical form.

Page 58: Technical Report Writing Technical Writing By William S. Pfeiffer

Chapter-3

Writing Handbook: Achieving Clarity and Conciseness

Page 59: Technical Report Writing Technical Writing By William S. Pfeiffer

ABBREVIATION RULES

1. Don’t use abbreviations when confusion may result They were required to remove creosote from the

site, according to the directive from EPA. Environmental Protection Agency

2. Use parentheses for clarity Environmental protection Agency (EPA)

3. Include a glossary when there are many abbreviations. A glossary simply collects all the terms and

Page 60: Technical Report Writing Technical Writing By William S. Pfeiffer

abbreviations and places them in one location for easy reference.

4. Use abbreviations for Units of Measures Most technical documents use abbreviations for

units of measures. Do not include a period unless the abbreviation could be confused with a word. Examples are; mi, ft, in.,lb

5. Avoid spacing and periods in most abbreviations that contain all capital letters

Examples are EPA, WAPDA Some common expectations include professional titles

and degrees.

Page 61: Technical Report Writing Technical Writing By William S. Pfeiffer

P.E., B.S., and M.A.

6. Be careful with Company Names Abbreviate a company or other organizational

name only when you are certain that officials from the organization consider the abbreviation appropriate (officials mean those who matter)

WAPDA, NHA, WASA are examples of commonly acceptable organizational abbreviations.

Page 62: Technical Report Writing Technical Writing By William S. Pfeiffer

Vowel / vowel sound

a, e, i, o, u

“an” is used before vowels / vowel sounds

Consonant

Letter which cannot be sounded by itself:

once (once begins with the consonant sound of “w”)

“a” is used before consonants

A / An

A occurs before words that start with consonant sound.

Page 63: Technical Report Writing Technical Writing By William S. Pfeiffer

• a three-prolonged plug;• a once-in-a life time job

An occurs before words that begin with vowels / vowel sound.

•an earthly paradise;•an hour;•An eager new employee

A Lot / Alot

The correct form is the two word phrase: a lot (Alot is not acceptable usage)

Page 64: Technical Report Writing Technical Writing By William S. Pfeiffer

• My father had a lot of patience.

“a lot” should be replaced by more formal diction in technical writing.• They retrieved many soil samples from the

site (not a lot of).

Accept(v) / Except (preposition)• I accepted the service award from my office

management.• Everyone except Jonah attended the

conference.

Page 65: Technical Report Writing Technical Writing By William S. Pfeiffer

Advice(n) / Advise(v) / Inform(v)• The consultant gave us advice on starting a

new retirement plan for our employees.• She advised us that this plan would be useful

for all our employees.• She informed (not advised) her clients that they

would receive her final report by March 08.• Inform (to provide information);

Affect(v) (to influence) / Effect(n) (result)• His progressive leadership greatly affected the

company’s future.

Page 66: Technical Report Writing Technical Writing By William S. Pfeiffer

Agree to / agree with• Agree to means that you have consented to an

agreement, offer, proposal, etc. Agree with only suggests that you are in harmony with a certain statement, idea, person.• Representatives from our firm agreed to alter

the contract to reflect the new scope of work.• We agree with you that more study may be

needed before the plant is built.

All Right / Alright

All right is an acceptable spelling; alright is not.

Page 67: Technical Report Writing Technical Writing By William S. Pfeiffer

All right is an adjective that means “acceptable,” an exclamation that means “outstanding,” or a phrase that means “correct.”• Khalid suggested that the advertising copy was

all right for now but that he would want changes next month.• Upon seeing his article in print, Khalid

exclaimed “All right.”• The five classmates were all right in their

response to the tricky questions on the quiz.

Page 68: Technical Report Writing Technical Writing By William S. Pfeiffer

All Together / Altogether• All together is used when items or people are

being considered in a group, or are in the same location. Altogether is a synonym for “entirely” or “completely.”• All together, the sales team included 50

employees from 15 offices.• The three firms were all together in Lahore for

the conference.• There were altogether too many pedestrians

walking near the dangerous intersection.

Page 69: Technical Report Writing Technical Writing By William S. Pfeiffer

Allusion / illusion / Delusion /Elusion

Allusion is a noun meaning “reference.”

Illusion is a noun meaning “misunderstanding.”

Delusion is a noun meaning “a belief based on self deception.”

Elusion is a noun meaning “the act of escaping”• His report included an allusion to the upcoming

visit by the secretary Information Technology.• She harbored an illusion that she was certain to

receive the promotion.

Page 70: Technical Report Writing Technical Writing By William S. Pfeiffer

• He had delusions that he soon would become company President.• The main points of the report eluded him

because there was no executive summary.

Already / All ready

All ready is a phrase that means “everyone is prepared,” whereas already is an adverb that means something is finished or completed.• They were all ready for the presentation to the

client.• George had already arrived at London.

Page 71: Technical Report Writing Technical Writing By William S. Pfeiffer

Alternately / Alternatively

Alternately is a derivative of alternate and is used for events or actions that occur “in turns”• They used a backhoe during some portions of the

project. Alternately they switched to using hand shovels.

Alternatively is a derivative of alternative and is used when two or more choices are being considered.• We suggest that you use deep foundations at the

site. Alternatively you could consider spread footings.

Page 72: Technical Report Writing Technical Writing By William S. Pfeiffer

Alumna / Alumnae / Alumnus / Alumni

These terms are directly derived from Latin.

An alumna is a female graduate, whereas an alumnus is a male graduate. The plural forms are alumnae fie females and alumni for males. Some writers prefer to use the plural form alumni in situations that involve both male and female graduates.

Amount / Number

Amount is used in reference to items that can not be counted, whereas number is used is used to indicate items that can be counted.

Page 73: Technical Report Writing Technical Writing By William S. Pfeiffer

• In the last year we have greatly increased the amount of computers paper ordered for the Punjab University.

• The last year has seen a huge increase in the number (not amount) of computers.

Anticipate / Expect

Anticipate is used when you mean to suggest or state that steps have been take beforehand to prepare for a situation. Expect only means you consider something likely to occur.

Consul / Council / Counsel

Page 74: Technical Report Writing Technical Writing By William S. Pfeiffer

Consul: A noun meaning an official of a country who is sent to represent the country’s interest.

Council: A noun meaning an official group or committee.

Counsel: A noun meaning an adviser or advice given or a verb meaning to provide an advice.

Continuous / Continual

Continuous or continuously are used in reference to uninterrupted.

Continual or continually are used with activities that are intermittent or repeated at intervals.

Page 75: Technical Report Writing Technical Writing By William S. Pfeiffer

• Because it rained continuously till 09 Hrs, we are unable to find even a minute of clear sky to put our equipment into the Laboratory.• We continually checked the water pressure for three

days before the equipment arrived.

Criterion / Criteria

Coming from the latin language, criterion and criteria are the singular and plural forms of a word that means “rationale or reasons for selecting a person, place thing or idea.

Data / Datum

Coming from latin, the word data is the plural form of datum.

Page 76: Technical Report Writing Technical Writing By William S. Pfeiffer

• The data show that there is strong case for building dam at the other location.• This particular datum shows we need to

reconsider the recommendations put forth in the original report.

Traditionalists in the engineering community still consider data a plural form in all cases. However some writers have considered data a plural form in some cases when it means “facts” and a singular form in other cases when it means “information.”

Page 77: Technical Report Writing Technical Writing By William S. Pfeiffer

Farther / Further

Farther refers to actual physical distance, whereas further refers to non-physical distance.• The projector was moved farther away from the

screen.• As he read further along in the report, he began to

understand the complexity of the project.

Imply / Infer

The person doing the writing or speaking “implies.” The person reading or hearing “infers.” Thus the word imply requires an active role, whereas the word infer requires a passive role.

Page 78: Technical Report Writing Technical Writing By William S. Pfeiffer

When you imply a point, your words suggest rather than state a point. When you infer a point, you form a conclusion.• The Engineer implied that there would be

tough competition for that $ 5(M) project. •We inferred from his remarks that the firm

selected for this work must have completed similar projects recently.

Its / It’s

It’s is used as a contraction for “it is” or “it has.”

Its is a possessive pronoun. “Its” is not a word.

Page 79: Technical Report Writing Technical Writing By William S. Pfeiffer

Numbers Follow the 10-or-over Rule

In general, use figures for numbers of 10 or more, words for numbers below 10.Do Not Start Sentences with Figures

Begin sentences with the word form of numbers, not with figures.• Three technicians at the site;• 15 reports submitted last month;• Forty-five containers were shipped back to

London.

Page 80: Technical Report Writing Technical Writing By William S. Pfeiffer

Use Figures as Modifiers

Whether below or above 10, numbers are usually expressed as figures when used as modifiers with the units of measurement, time and money.• 4 in, 7 hr, 36 sq.ft, Rs.5 per hourUse Figures in a Group of Mixed Numbers.• For that project, they assembled 15 samplers, 4

rigs, and 25 large containers.Use the Figure Form in Illustration Titles• Figure 3, Table 14-B

Page 81: Technical Report Writing Technical Writing By William S. Pfeiffer

Be Careful with Fractions

Express fractions as words when they stand alone, but as figures when they are used as a modifier or are joined to whole numbers.•We have completed two-thirds of the project, using 2⅓-in pipe.

Use Figures and words with Numbers in Succession•We found fifteen 2-ft pieces of pipe in the bin.Avoid Placing Figures in Parentheses• The second party will pay the first party forty-

one dollars. In case you consider it necessary,

Page 82: Technical Report Writing Technical Writing By William S. Pfeiffer

the parentheses amount is placed immediately after the figure, not after the unit of measurement.• The second party will pay the first party forty-

one (41) dollars.Use Commas in Four –digit Figures• 15,000; 1,258; 6,003;Use Words for Ordinals• The judge informed the first, second and third

choices (not 1st, 2nd, and 3rd ) in the design competition.

Page 83: Technical Report Writing Technical Writing By William S. Pfeiffer

Per cent / Percent / Percentage

Per cent and Percent have basically the same usage and occur with exact numbers. The one word percent is preferred. Even more common in technical writing, however, is the use of the percentage sign (%) after numbers. The word percentage is only used to express general amounts, not exact numbers.•A large percentage of the defects can be linked to the loss of two experienced inspectors.•Ali obtained 84 % marks in his MBA.

Page 84: Technical Report Writing Technical Writing By William S. Pfeiffer

Number of / Total of

If the phrase is preceded by the, it takes a singular verb, because emphasis is placed on the group.

If the phrase is preceded by a, it takes a plural verb, because emphasis is placed on the many individual items.• The number of projects;• A number of projects;