ACI 2014 Technical Committee Manual

Prepared by the ACI Technical Activities Committee

PREFACE

The purpose of ACI, as stated in the 1904 Charter, is: To organize the efforts of its members for a nonprofit public service in gathering, correlating, and disseminating information for the improvement of the design, construction, manufacture, use, and maintenance of concrete products and structures.

By adhering to this purpose, professionals in the concrete industry recognize ACI as a neutral platform for producing reliable technical information.

Each committee member willingly contributes his or her training and knowledge for the benefit of the public at large. By maintaining a high standard of professional and technical ability in its committee memberships, ACI publishes reliable information on concrete and its applications.

ACI has over 110 technical committees, and each has a unique mission related to a specific knowledge area, but all committees are expected to serve the public consistent with the 1904 chartered purpose.

The characteristics of ACI technical committee operations include:

(a) Open committee membership

(b) Balance/lack of dominance

(c) Coordination and harmonization of information

(d) Transparency of committee activities to public

(e) Consideration of views and objections

(f) Resolution through consensus process

The technical committee documents of the American Concrete Institute represent the consensus of the committee and ACI. Technical committee members are individuals who volunteer their services to ACI and specific technical committees.

ACI technical committee members are expected to:

(a) Hold the safety, health, and welfare of the public as their top priority

(b) Be truthful in presenting information and data during discussions, debates, and ballots concerning technical issues

(c) Act in a professional manner

(d) Conduct themselves in a manner that will bring credit to the Institute

(e) Not state that they are official representatives of an ACI committee unless authorized by the Technical Activities Committee (TAC), nor state they are official representatives of ACI unless authorized by the Board of Direction

By adhering to these characteristics, ACI committees have a reputation for operational integrity.

TAC is always looking for ways to improve and streamline committee procedures.

Comments are welcome and can be e-mailed to:

discussion@concrete.org

American Concrete Institute

38800 Country Club Drive

Farmington Hills, Michigan 48331

telephone: (248) 848-3700

fax: (248) 848-3701

www.concrete.org

TABLE OF CONTENTS

PREFACE

PART 1—ORGANIZATION AND OPERATION OF TECHNICAL COMMITTEES

CHAPTER 1—ORGANIZATION

1.1—Technical Activities Committee (TAC)

1.1.1 TAC Design Standards Committee (TDSC)

1.1.2 TAC Construction Standards Committee (TCSC)

1.1.3 TAC Repair and Rehabilitation Committee (TRRC)

1.2—Technical committees

1.2.1 Number designations

1.2.2 Comparison of subcommittee and task groups

1.2.3 Subcommittees

1.2.3.1 Editorial subcommittee

1.2.3.2 Steering subcommittee

1.2.3.3 Liaison subcommittee

1.2.4 Task groups

1.3—Innovation Task Groups

1.4—Committee establishment, reorganization, and discharge

1.4.1 Establishment

1.4.1.1 Request to establish a new technical committee

1.4.1.2 Request to establish an ITG

1.4.2 Reorganization

1.4.2.1 Reorganization with discharge of members

1.4.2.2 Reorganization with retention of members

1.4.3 Discharge

1.5—Joint committees and committee cooperation with other organizations

1.5.1 Cooperation

1.5.2 Joint committees

1.6—Membership categories

1.6.1 Voting members

1.6.1.1 Qualifications

1.6.1.2 Requirements

1.6.1.3 Privileges

1.6.1.4 Term

1.6.1.5 Appointment

1.6.2 Associate members

1.6.2.1 Qualifications

1.6.2.2 Requirements

1.6.2.3 Privileges

1.6.2.4 Term

1.6.2.5 Appointment

1.6.3 Consulting members

1.6.3.1 Qualifications

1.6.3.2 Requirements

1.6.3.3 Privileges

1.6.3.4 Term

1.6.3.5 Appointment

1.6.4 Liaison members

1.6.4.1 Qualifications

1.6.4.2 Requirements

1.6.4.3 Privileges

1.6.4.4 Term

1.6.4.5 Appointment

1.7—Committee membership

1.7.1 Application for membership

1.7.2 Appointments and membership changes

1.7.3 Appointments to joint committees

1.7.4 Overlap of membership between committees

1.7.5 Appointment not approved

1.7.5.1 Committees with restricted membership

1.7.6 Membership termination

1.7.7 Resignation from membership

1.7.8 Appeal of membership action

1.8—Balance of interests

1.8.1 Producer

1.8.2 User

1.8.3 General interest

1.8.4 Consultants

1.8.5 Membership termination to achieve balance

1.9—Committee officers

1.9.1 Chair

1.9.1.1 Chair qualifications

1.9.1.2 Chair candidates

1.9.1.3 Chair appointment

1.9.1.4 Chair term

1.9.1.5 Chair resignation

1.9.2 Vice chair

1.9.3 Secretary

CHAPTER 2—TECHNICAL COMMITTEE OPERATIONS

2.1—Mission

2.2—Goals

2.2.1 Develop new documents

2.2.2 Maintain existing documents

2.2.3 Sponsor convention sessions and related publications

2.2.4 Develop seminars

2.2.5 Develop video information

2.3—Meetings

2.3.1 Conducting committee meetings

2.3.2 Quorum

2.3.3 Administrative actions

2.3.4 Convention committee meetings

2.3.5 Interim committee meetings

2.3.5.1 Physical interim meetings

2.3.5.2 Virtual interim meetings

2.3.6 Closed meetings

2.3.7 Visitors

2.3.8 Agenda

2.3.9 Minutes

2.4—Communication

2.4.1 Correspondence within a committee

2.4.2 Correspondence between committees

2.4.3 Correspondence with TAC and ACI headquarters

2.4.4 Discussion in outside publications

2.4.5 Coordination among committees

2.5—Breakfast meeting for technical committee chairs

2.6—Technical committee certificates

2.6.1 Voting member certificates

2.6.2 Chair certificates

2.6.3 Outstanding service by committee members

2.6.4 Del Bloem Distinguished Service Award

2.7—Committee-related finances

2.7.1 ACI Foundation funding

2.7.2 Concrete Research Council (CRC)

2.7.3 Strategic Development Council (SDC)

2.7.4 Committee work expenses

2.8—Staff assistance

CHAPTER 3—BALLOTING

3.1—Voting methods and rules

3.1.1 Administrative ballots

3.2—Letter ballots

3.2.1 Passage of letter ballot items

3.2.2 Initiation and format

3.2.3 Time frame

3.2.4 Distribution

3.2.5 Votes

3.2.5.1 Affirmative votes

3.2.5.2 Affirmative votes with comments

3.2.5.3 Negative votes with reason

3.2.5.4 Abstentions

3.2.5.5 Ballots not returned

3.2.5.6 Comments from nonvoting members

3.2.6 Analysis and further action

3.2.6.1 Updating results

3.2.6.2 Revising and reballoting

3.2.7 Subcommittee letter ballots

3.2.8 Patented items

3.3—Meeting ballots

3.3.1 Passage of item by meeting ballot

3.3.2 Exception to the 40 percent rule

3.4—Consideration of negative votes

3.4.1 Withdrawal of negative vote (no change to document)

3.4.2 Unrelated to ballot item (no change to document)

3.4.3 Nonpersuasive (no change to document)

3.4.4 Persuasive (technical change to document)

3.4.5 Appeals

3.5—Ballot summaries

3.6—Procedures when ACI is the minor sponsor

PART 2—ACI STANDARDS

CHAPTER 4—DEVELOPMENT OF STANDARDS

4.1—Description

4.1.1 Design standards

4.1.1.1 Code requirements

4.1.1.2 Code cases

4.1.1.3 Acceptance criteria

4.1.1.4 Design specifications

4.1.2 Construction standards

4.1.2.1 Construction specifications

4.1.2.2 Material specifications

4.1.2.3 Test methods

4.1.2.4 Inspection services specifications

4.1.2.5 Testing services specifications

4.2—Procedures

4.2.1 New standard

4.2.2 Revising existing standards

4.2.2.1 Reapproval

4.2.2.2 Revision

4.2.2.3 Withdrawal

4.2.3 Maintenance of the content of ITG standards

4.2.4 Committee editorial review

4.2.5 Circulating draft standards

4.2.6 Coordination of ACI standards

4.2.6.1 Industry standards

4.2.6.2 Interaction among standards-writing committees

4.2.6.3 Proposed changes from outside of committee

4.2.6.4 Coordination among technical committees

4.2.6.5 Standards sponsored with other ACI technical committees

4.2.6.6 Coordination with the Construction Liaison Committee

4.2.6.7 Coordination with TCSC and TDSC

4.2.6.8 Coordination of terminology

4.2.7 Translation of ACI standards

4.2.8 Patented items

4.2.9 Errata

4.3—Writing standards

4.3.1 Format

4.3.2 Units

4.3.3 Notation

4.3.4 Style

4.4—TAC review

4.4.1 Submission package

4.4.2 Staff editorial review

4.4.3 TAC review

4.4.3.1 TAC review group

4.4.3.2 Review comment classifications

4.4.4 TAC decision

4.4.4.1 Standard approved

4.4.4.2 Responding to TAC comments

4.4.4.3 Standard not approved

4.5—Public discussion process

4.5.1 Release for public discussion

4.5.2 Public discussion

4.5.2.1 Code case

4.5.2.2 Provisional standard

4.5.3 Committee closure

4.5.4 Release for publication

4.5.5 Adoption as an ACI standard

4.5.6 Approval as an American National Standard

4.6—Appeal process

4.6.1 Standards under development

4.6.2 Published standards

4.6.3 Technical grounds

4.6.4 Procedural grounds

CHAPTER 5—FORMAT AND LANGUAGE FOR CODES

5.1—General

5.2—Organization

5.2.1 Front matter

5.2.2 Code chapters

5.2.3 Back matter

5.2.4 Article titles

5.2.5 Section and subsection titles

5.2.6 Provision numbering

5.3—Language

5.3.1 Verb usage

5.3.2 Adjectives and adverbs

5.3.3 Gender-specific language

5.3.4 Conditional phrases

5.3.5 Comparative phrases

5.4—References

5.4.1 References to provisions and chapters

5.4.2 Compliance phrases

5.4.3 Referenced standard style

5.5—Commentary to a code

5.5.1 General

5.5.2 Commentary references

CHAPTER 6—FORMAT AND LANGUAGE FOR CONSTRUCTION SPECIFICATIONS

6.1—General

6.2—Format

6.2.1 Single-item specifications

6.2.2 Numbering within single-item specifications

6.2.3 Multi-item specifications

6.2.4 Numbering within multi-item specifications

6.2.5 Description of title page

6.2.6 Description of Part I, General

6.2.6.1 Scope

6.2.6.2 Interpretation

6.2.6.3 Definitions

6.2.6.4 Referenced standards

6.2.6.5 Personnel certification programs

6.2.6.6 Plant certification programs

6.2.6.7 Submittals

6.2.6.8 Delivery, storage, and handling

6.2.6.9 Quality assurance and control

6.2.7 Description of Part 2, Products

6.2.7.1 Materials

6.2.7.2 Mixtures

6.2.7.3 Fabrication

6.2.7.4 Source quality control

6.2.8 Description of Part 3, Execution

6.2.8.1 Preparation

6.2.8.2 Sequence

6.2.8.3 Installation

6.2.8.4 Post-installation testing

6.2.8.5 Repair

6.2.8.6 Protection

6.2.9 Description of Notes to Specifier

6.2.9.1 General notes, foreword to checklists, and list of references

6.2.9.2 Mandatory requirements checklists

6.2.9.3 Optional requirements checklists

6.2.9.4 Checklist format

6.3—Language

6.3.1 Tolerances

6.3.2 Verb usage

6.3.3 Gender-specific language

6.3.4 Subjective language

6.3.5 Time-related requirements

6.3.6 Qualitative requirements

6.3.7 Repetition of items

6.3.8 Jargon and slang

6.3.9 Approved

6.3.10 Responsibilities

6.3.11 Referral phrase

6.3.12 Compliance phrases

6.3.13 Article use

6.3.14 Pronouns

6.3.15 Options

6.3.16 Conditional phrases

6.4—Referenced standards

6.4.1 Standards in specification text

6.4.2 References in checklists

6.5—Appendixes

PART 3—GUIDES AND REPORTS

CHAPTER 7—DEVELOPMENT OF GUIDES AND REPORTS

7.1—General

7.2—Description of guides and reports

7.2.1 Guides

7.2.1.1 Handbooks and manuals

7.2.1.2 Technical notes (TechNotes)

7.2.2 Reports

7.2.2.1 Emerging Technology Report (ETR)

7.2.3 Errata

7.3—Development

7.3.1 New guides and reports

7.3.2 Existing guides and reports

7.3.2.1 Reapproval

7.3.2.2 Revision

7.3.2.3 Withdrawal

7.3.2.4 ITG guides and reports

7.3.3 Documents sponsored with other ACI technical committees

7.3.4 Restrictions on circulating drafts

7.3.5 Coordination of information

7.3.5.1 Technical committees

7.3.5.2 Construction Liaison Committee

7.3.5.3 Terminology

7.3.6 Translation of ACI documents

7.3.7 Guides and reports authored by ACI chapters

7.4—Writing guides and reports

7.4.1 Format

7.4.2 Units

7.4.3 Notation

7.4.4 Style

7.4.5 Editorial review

7.5—TAC review

7.5.1 Submission package

7.5.2 Staff editorial review

7.5.3 TAC review

7.5.3.1 TAC review group

7.5.3.2 Review comment classifications

7.5.4 TAC decision

7.5.4.1 Document approved

7.5.4.2 Responding to TAC comments

7.5.4.3 Document not approved

7.6—Appeal processes

7.6.1 Guides and reports under development

7.6.2 Published guides and reports

7.6.3 Technical grounds

7.6.4 Procedural grounds

CHAPTER 8—FORMAT AND LANGUAGE FOR GUIDES AND REPORTS

8.1—Format

8.1.1 Outline

8.1.2 Description of required front matter

8.1.3 Description of chapters

8.1.4 Description of back matter

8.1.5 Numbering and titles

8.2—Language

8.2.1 General principles

8.2.2 Clarity

8.2.3 Gender-specific language

8.2.4 Vague language

8.2.5 Conditional phrases (use of if, when, and where)

8.2.6 Active versus passive voice

8.2.7 Acceptable and unacceptable terminology

8.3—References

PART 4—STYLE

CHAPTER 9—ACI TECHNICAL WRITING STYLE

9.1—Equations

9.1.1 Equation numbering

9.2—Figures

9.3—Tables

9.4—Lists

9.5—Grammar

9.5.1 Numbers

9.5.2 Hyphens

9.5.3 Serial comma

9.5.4 Footnotes

9.5.5 Parentheses and brackets

9.5.6 Abbreviations

9.5.7 Capitalization

9.5.8 Per versus “/”

9.5.9 And/or

CHAPTER 10—NOTATION AND DEFINITIONS

10.1—Notation

10.1.1 General

10.1.2 Rules for making notation

10.1.3 Format

10.1.4 Notation use in text

10.2—Definitions

10.2.1 ACI Concrete Terminology

10.2.2 Responsibility for definitions

10.2.2.1 CT Task Group

10.2.2.2 Process for submitting terminology

10.2.2.3 Revising the CT

10.2.2.4 Referencing the CT

10.2.2.5 Publication of the CT

10.2.3 Format

CHAPTER 11—UNITS OF MEASUREMENT

11.1—Policy

11.2—Inch-pound units

11.3—SI units

11.4—Hard versus soft conversion

11.4.1 Soft metric conversion

11.4.2 Hard metric conversion

11.5—Format for unit names and abbreviations

11.5.1 General

11.5.2 Percentages, decimals, and fractions

11.5.3 Degrees

11.6—Conversion of units

11.6.1 Conversion factors

11.6.2 Significant digits

11.6.3 Rounding

11.6.4 Reinforcing bar designations

11.6.5 Degree of precision

11.6.6 Mass versus weight

11.6.7 Decimal point and implied tolerances

PART 5—SESSIONS AND VIDEO PRODUCTS

CHAPTER 12—CONVENTION SESSIONS AND RELATED PUBLICATIONS

12.1—Committee planning

12.2—TAC approval

12.2.1 Session moderator training

12.3—Sponsorship of technical sessions at non-ACI conventions

12.4—Convention session procedures

12.4.1 Initiating a session

12.4.2 Preliminary TAC approval

12.4.2.1 Deadlines for preliminary TAC approval

12.4.3 Time allotted for presentations

12.4.4 Sessions honoring prominent ACI members

12.4.5 Speakers

12.4.5.1 Calls for papers

12.4.5.2 Selecting speakers

12.4.6.3 Notifying speakers

12.4.6 Final TAC approval

12.4.6.1 Deadlines for final TAC approval

12.4.7 Staff assistance

12.4.8 Presentation materials

12.5—Publication of session papers in an ACI Special Publication

12.5.1 SP from conferences outside ACI conventions

12.5.2 SP honoring an individual

12.5.3 Preliminary TAC approval

12.5.4 Preparation of papers

12.5.5 Review of papers

12.5.6 Final TAC approval

CHAPTER 13—DEVELOPMENT OF VIDEO PRODUCTS

13.1—Initial approval

13.2—Funding request

13.3—Secondary approval

13.4—Final approval

13.5—Revision

PART 6—POLICIES

CHAPTER 14—DOCUMENT-RELATED INSTITUTE POLICIES

14.1—Publication

14.1.1 Stand-alone document

14.1.2 ACI Manual of Concrete Practice

14.2—Legal and directional statements

14.2.1 Disclaimer on first page of guides and reports

14.2.2 Disclaimer on inside front cover

14.2.3 Statement describing ITG reports

14.2.4 Statement describing Emerging Technology Reports

14.2.5 Translation disclaimer

14.2.6 Metric unit conversion disclaimer

14.2.7 Patent disclaimer

14.2.8 Certification statement

14.3—ACI metrication policy

INDEX

PART 1—ORGANIZATION AND OPERATION OF TECHNICAL COMMITTEES

CHAPTER 1—ORGANIZATION

1.1—Technical Activities Committee (TAC)

The Technical Activities Committee (TAC) is responsible for the oversight of technical committee activities; the development of ACI standards; and the technical content of convention programs, archival publications, and special publications of the Institute, including peer-reviewed articles in periodicals and symposium volumes. TAC reviews all technical committee documents and is the final authority on technical issues in all publications.

Each TAC member is assigned liaison responsibilities for several technical committees, is designated as the TAC contact, and is listed on the committee roster on the website as the TAC contact. TAC contacts are expected to keep TAC abreast of the activities of the committees. Chairs should keep the TAC contact fully aware of committee activities and progress and are encouraged to contact them for advice or information.

TAC establishes subcommittees to assist in its oversight responsibility. Actions of TAC subcommittees are subject to review and approval by TAC. TAC subcommittee chairs are appointed by the TAC chair.

1.1.1 TAC Design Standards Committee (TDSC)

The TDSC assists technical committees by providing advice on the proper development and maintenance of design standards, managing design standards codes in the correct format and language, and managing code development by the Institute.

1.1.2 TAC Construction Standards Committee (TCSC)

The TCSC assists technical committees in preparation and maintenance of construction standards in the correct format and language, and in management of code development by the Institute.

1.1.3 TAC Repair and Rehabilitation Committee (TRRC)

The TRRC advises TAC on issues related to repair and rehabilitation, including evaluation, maintenance, and protection. TRRC coordinates the efforts of technical committees as they report information on existing concrete and masonry construction.

1.2—Technical committees

TAC forms technical committees and assigns each a mission (2.1). A technical committee mission identifies the knowledge area the committee is responsible for and is usually not document-specific. The chair of each technical committee is responsible for organizing and populating the committee to achieve the mission. Committee size is influenced by several factors, such as the mission, balance of interests, geographic location of the committee members, and the current committee goals. ACI often attracts structural engineers, educators, and materials specialists. Committees are encouraged to expand expertise and participation by including architects, specifiers, Contractors, younger members, and those outside the mainstream of ACI activity.

Technical committee chairs may create long-standing subcommittees and short-term task groups within the main committee to assist with committee work.

Changes to a document proposed by a subcommittee or a task group must be approved by the main committee.

ACI committee members are expected to contribute to the committee’s work products, including written works. All work products of ACI committees belong to ACI. Technical committees are consensus bodies. By participating in committees, ACI committee members acknowledge that the rights to such work products, including any copyright, reside with ACI.

1.2.1 Number designations

Staff assigns a number to each committee. Technical committees are organized into five groups based on their scope:

100—General

200—Materials and properties of concrete

300—Design and construction

400—Concrete reinforcement and structural analysis

500—Specialized applications and repair

Staff also assigns designations for subcommittees and task groups. Subcommittees use the committee number followed by a letter. Task groups use the committee number with “TG” followed by a sequential number. For example, Committee 318-A is a 318 subcommittee and Committee 318-TG7 is a 318 task group.

1.2.2 Comparison of subcommittee and task groups

Table 1.2.2 is a summary of the similarities and differences between subcommittees and task groups.

1.2.3 Subcommittees

For committees with a broad mission, it may be beneficial to establish long-standing subcommittees to address different aspects of the committee’s work.

The main committee chair establishes the subcommittee. The chair submits a title, mission, goals, and roster to ACI. The subcommittee consists of a chair and voting members. There are no other categories of membership for a subcommittee. Voting members do not have to be members of the main committee. Subcommittee ballots typically are not bound by main committee balloting rules. Unless otherwise directed by the chair, simple majority of those voting carries the issue. Although subcommittee members who are nonvoting members of the main committee may participate and vote on subcommittee ballots, they do not vote on main committee ballots. Refer to 3.2 on formal balloting.

The chair of the main committee approves the roster for all subcommittees and the policies and procedures proposed by subcommittees.

1.2.3.1 Editorial subcommittee

An editorial subcommittee provides a uniform editorial review of each document. The subcommittee usually consists of an individual or a small group with editorial experience. Part 4 is a primary resource for an editorial subcommittee.

1.2.3.2 Steering subcommittee

In a large committee, a steering subcommittee may be established to assist the chair by providing input on committee actions and plans.

1.2.3.3 Liaison subcommittee

Liaison members represent outside organizations and are appointed to facilitate exchange of information with ACI. Such organizations may include technical societies, trade associations, and standards-developing organizations. Committees with liaison members must have a designated liaison subcommittee.

1.2.4 Task groups

Task groups are established by the main committee chair to perform short-term tasks for the committee. Members of task groups must be members of the main committee. The chair submits a title, mission, goals, and roster to staff. A website will be created for the task group. The task group website is visible to the public and functions the same as a main committee webpage. The task group consists of a chair and voting members. There are no other categories of membership for a task group. Members of task groups must be members of the main committee. The task group is not bound by balloting rules.

1.3—Innovation Task Groups

Innovation Task Groups (ITGs) are temporary technical committees that are formed to accelerate the development of a specific document, usually on new technology. TAC forms ITGs and assigns their mission (1.4.1.2). An ITG may not be joint with other organizations. Include a general description of the topic being evaluated and the type of document to be created in the ITG’s mission. Include the document(s) to be produced and a tentative time schedule in the goals. The rules for technical committees presented in this manual apply to ITGs.

1.4—Committee establishment, reorganization, and discharge

1.4.1 Establishment

TAC considers and approves requests to establish new technical committees or ITGs, and appoints the committee chair and TAC contact. The title and mission of the new committee are published in Concrete International.

1.4.1.1 Request to establish a new technical committee

To request a new technical committee, send the following information to the Managing Director of Engineering:

(a) A proposed title and mission for the committee

(b) An explanation of why a new ACI committee should be established

(c) A list of potential members

(d) A slate of candidates for the position of chair

(e) A list of short-term goals of the committee

(f) A discussion of potential overlap and conflict with other committees

Additionally, TAC may request a representative of the proposed committee to attend the TAC meeting when formation of the new committee is discussed.

1.4.1.2 Request to establish an ITG

To request establishment of an ITG, send the following information to the Managing Director of Engineering:

(a) Background information on how the new technology innovation will fit into ACI’s general mission

(b) Advantages of the new technology over existing technology in that field

(c) List of competing technologies, if any

(d) List of technical papers, reports, and other publications that address the new technology

(e) List of field demonstration projects, if any, using the new technology

(f) A statement demonstrating the maturity of the new technology to warrant the development of an ITG document for the transfer of this technology

(g) List any ACI technical committee(s) whose mission includes this technology

(h) Title and mission for the ITG

(i) A slate of members and at least one candidate for chair

(j) A target time to complete the mission of the ITG

1.4.2 Reorganization

Occasionally, it may be necessary for TAC to reorganize a committee or merge committees. The reasons for such steps may include:

(a) The committee has completed its assigned mission and a smaller committee is needed to maintain committee documents

(b) The mission or direction of the committee needs to be changed

(c) Committee reorganization is needed to accomplish the assigned mission

(d) A standards-only writing committee is beginning a new cycle; ACI Committees 301, 318, and 562 are reorganized on a regular basis

Upon reorganization, TAC may appoint a new chair and discharge all members or appoint a new chair who is responsible for reviewing current membership.

1.4.2.1 Reorganization with discharge of members

If TAC appoints a new chair and discharges the committee membership, all committee members are notified of the reasons for the discharge and given an explanation of future plans. Former committee members can apply for reappointment.

1.4.2.2 Reorganization with retention of members

If the present membership is to be retained, subject to review, the chair must:

(a) Review the activity of voting committee members and change the classification to a nonvoting status (1.6.3.5) or terminate committee membership (1.8.5) of those who have not demonstrated adequate activity

(b) Review the overall committee composition and decide on committee membership changes to obtain balance of interests (if required) and to maintain a reasonable size to accomplish tasks

(c) Add new committee members who have expertise related to the committee’s mission and who can provide vitality to the committee

The chair may request a statement from a committee member on their desire to continue to serve. If a response to the request is not received in a reasonable time (2 months is recommended), the chair may consider it to signify a lack of interest and decide to terminate that individual’s committee membership.

A membership questionnaire (on the Chair/Officer Work Area of the committee web page) may be used to ask committee members if they desire to continue as active members, change membership status, or resign.

1.4.3 Discharge

TAC may discharge a committee that has completed its mission, is inactive, or is ineffective.

TAC discharges an ITG when the ITG document(s) is published.

1.5—Joint committees and committee cooperation with other organizations

1.5.1 Cooperation

ACI committees can informally cooperate with other organizations, as long as committee operating procedures are not impacted. If, however, that cooperation includes formal activities, such as technical documents, conferences, or symposium sessions, these activities must be approved by TAC.

Individuals who want to be involved in creating industry-specific technical information on material properties of concrete or design, construction, inspection, and repair of concrete structures, should join ACI committees. Individuals who want to be involved with test method or specifications for reinforced concrete-related materials should join ASTM International committees. This division of responsibilities between ACI and ASTM was formalized in 1936.

1.5.2 Joint committees

ACI technical committees can become joint committees with one or more cosponsoring organizations. According to ACI policy on joint committees, joint committees may be formed when the following criteria are met:

(a) Objective of the proposed activity is desirable and within the field of ACI endeavor

(b) Interests of both societies would be served equally well

(c) Joint participation will avoid duplication of effort

(d) Joint participation will speed document development

(e) Joint participation will bring wider acceptance of results

(f) Joint participation offers greater prospect of funds for research and experimentation than acting singly

(g) Prospective membership would be harmonious, even though there might be anticipated differences of opinion

(h) ACI will receive full recognition in any publicity given the joint committee

Joint committee status may be initiated by the ACI Board of Direction. The Board, or the ACI Executive Vice President on behalf of the Board, may determine that it is in ACI’s strategic interest for a committee to begin cooperative efforts with another organization. In that case, TAC will work with the committee to determine the most appropriate means for cooperation.

Joint committee status requests can also be submitted to TAC. An existing committee may request to become a joint committee with another organization when at least 75 percent of committee voting members vote in favor of the proposed arrangement. The chair must forward comments from negative voters to TAC. This is considered an administrative ballot and negative votes need to be resolved.

The following questions should be addressed in the request to TAC:

(a) What is the proposed title and mission for the joint committee?

(b) Who will be the lead sponsoring organization?

(c) How will the interests of both organizations be served?

(d) How will the joint sponsorship speed and bring a wider acceptance of results?

(e) What are the committee goals and the anticipated time frame for achieving these goals?

(f) After achieving these goals, does the proposed committee anticipate a change in committee or sponsorship status?

(h) Where and how often would the joint committee hold regular meetings?

There are two options under which a technical committee can operate as a joint committee: (1) ACI is the major sponsor and another sponsoring organization is the minor sponsor; or (2) ACI is the minor sponsor and another sponsoring organization is the major sponsor.

When ACI is the major sponsor, joint committees are to operate in accordance with the ACI Technical Committee Manual. The minor sponsor may provide technical input during the TAC document review and provide names of individuals for TAC to consider when creating a chair slate. The committee is designated as a joint committee in all communications.

When ACI is the minor sponsor of a joint committee, the balloting and operating procedures are determined by the major sponsor. All items approved by the joint committee are submitted to the Managing Director of Engineering for review by TAC. ACI requires that the committee is designated as a joint committee in all communications.

When a joint sponsorship is approved by TAC and the Board, a formal memorandum of understanding (MOU), including a specific agreement on committee operations, must be developed with the other organization(s). The ACI Executive Vice President is responsible for the execution of MOUs.

1.6—Membership categories

ACI technical committees have four categories of members: voting members, associate members, consulting members, and liaison members. Information about the qualifications, requirements, privileges, term, and appointment for all membership categories is given in 1.6.1 through 1.6.4. All membership changes must be emailed to headquarters along with a reason for the change in membership.

1.6.1 Voting members

1.6.1.1 Qualifications

Voting members must be able to contribute to accomplish the committees’ goals. They must have the training, knowledge, experience, time, and facilities to perform the work. Voting members do not have to be ACI members but it is strongly recommended.

1.6.1.2 Requirements

Voting members are required to participate actively in committee work by contributing technical information, promptly returning all committee ballots, replying to correspondence, and regularly attending committee meetings.

Voting members need to supply an email address to participate in committee activity.

Regular attendance at committee meetings is important because that is where members usually arrive at consensus on major issues, resolve negative votes on letter ballots (3.4), solve problems, plan future activities, and accomplish much of their work.

Meeting schedule conflicts are difficult to avoid because of the number of ACI committees and the varied interests of the voting members. Before granting voting member status to an applicant, the chair should verify that the applicant will be able to attend meetings and participate actively in the committee work. If an applicant cannot attend these meetings, another membership category may be desirable. The chair may waive meeting attendance requirements under justified circumstances, provided the voting member contributes to the work of the committee.

1.6.1.3 Privileges

Voting members receive minutes, information on items being balloted, and correspondence; may express opinions and make motions during committee meetings; vote on all ballots; have the right to appeal committee action; and have access to the committee’s web page.

1.6.1.4 Term

Voting membership has no set term.

1.6.1.5 Appointment

The chair appoints voting members of technical committees based on the applicant’s personal knowledge and expertise. Appointment as a voting member is not based on affiliation or employment. An applicant’s affiliation or employment will be considered, however, in determining balance of interests (1.8).

ITG voting members are appointed by the ITG chair. Voting members are appointed at two stages: 1) at the formation of the ITG; and 2) after the first draft is completed but before the first ballot of the document. At formation, the voting membership shall include the chair and at least three other individuals. After the first draft, at least three additional voting members shall be appointed; however, membership should not exceed 10 voting members. These additional voting members should represent a wide range of interests outside the ITG and have no direct economic interest in the outcome of the document.

It is assumed that the information published in an ITG document will be included in a later ACI committee document; therefore, to facilitate communication and connection with related technical committees, the ITG chair is encouraged to appoint members from related technical committees as voting members on the ITG.

1.6.2 Associate members

1.6.2.1 Qualifications

Associate members must be ACI members or be a member of a cosponsoring organization in the case of a joint committee.

1.6.2.2 Requirements

Associate members have no formal committee responsibilities.

1.6.2.3 Privileges

Associate members receive minutes, information on items being balloted, and correspondence; may express opinions, but not vote, during committee meetings; may express opinions, but not vote, on all ballots; and have access to the committee’s web page.

1.6.2.4 Term

An associate membership term is for 4 years. When the term expires, the chair should evaluate the person’s participation and may change the membership status to voting or consulting, reappoint the individual as associate member for another 4 years, or terminate committee membership.

When individuals no longer maintain their ACI membership, their associate memberships on technical committees are also terminated.

1.6.2.5 Appointment

Associate members are appointed in two ways:

1) A person applying for voting membership may be appointed as an associate member by the chair for a variety of reasons, including maintaining balance of interests within the committee or limiting voting membership changes during balloting of a committee document.

2) All ACI members (individual, organizational/sustaining representatives, student, young professional, honorary, and fellow) can be appointed to a maximum of three technical committees. A person maintaining a membership in an organization that cosponsors ACI joint technical committees can be appointed to a maximum of three such joint committees. Chair review of membership requests is not required for an appointment as an associate member. Note: ACI Committees 301, 318, 562, and ITGs do not have associate members.

1.6.3 Consulting members

1.6.3.1 Qualifications

Consulting members do not need to be ACI members, but should have the expertise within the mission of the committee.

1.6.3.2 Requirements

Consulting members have no formal committee responsibilities.

1.6.3.3 Privileges

Consulting members receive minutes, information on items being balloted, and correspondence; may express opinions, but not vote, during committee meetings; may express opinions, but not vote, on all ballots; and have access to the committee’s web page.

1.6.3.4 Term

Consulting membership has no set term.

1.6.3.5 Appointment

Consulting members of technical committees are appointed by the chair based on the applicant’s special expertise or a long-time association with the committee or its mission.

After a document is drafted, the chair of an ITG may appoint up to three nonvoting consulting members in addition to the voting members. These consulting members act as outside reviewers and are asked to provide a detailed review of the document.

1.6.4 Liaison members

1.6.4.1 Qualifications

Liaison members are appointed based on their affiliation with the related organization. Liaison members need not be ACI members, but should have the expertise within the mission of the committee. If the liaison member’s affiliation with the related organization is terminated, the liaison membership on the ACI technical committee is also terminated.

1.6.4.2 Requirements

Liaison members are expected to facilitate the exchange of information between the ACI technical committee and the related organization.

1.6.4.3 Privileges

Liaison members receive minutes and information on items being balloted, may express opinions and vote during subcommittee meetings, are expected to vote on all subcommittee ballots, and have access to the main and subcommittee web pages.

1.6.4.4 Term

Liaison members are appointed for a 3-year term and may be reappointed.

1.6.4.5 Appointment

Liaison members are appointed to ACI liaison subcommittees as voting members and to the main committee as nonvoting liaison members.

1.7—Committee membership

1.7.1 Application for membership

Each prospective committee member (either main committee or subcommittee), regardless of membership category, is to submit a committee application (found on the ACI website), which will be forwarded to the chair of the appropriate technical committee.

With the exception of the chair and associate members, ACI membership is not required, but is desirable, for technical committee membership. All committee members are encouraged to join ACI.

1.7.2 Appointments and membership changes

Chairs should add new members on a regular basis and remove inactive members. Effective committees should have sufficient turnover so that new ideas are constantly considered.

The chair shall decide on all membership changes, including appointments to all membership categories, (except associate membership), terminations, or changes of membership status, and notify the Managing Director of Engineering. These actions will be checked by staff for TCM compliance. The effective appointment date shall be when the membership changes appear on the committee website. No changes in membership voting status can be acted on during an open letter ballot. For example, a member can’t change from voting member to associate or associate to voting while a letter ballot is open.

ACI staff sends the individual and chair a formal appointment, termination, or status change notice showing the effective date.

Committee members accepting committee appointments give ACI permission to post their contact information on the ACI website in a password-protected area, accessible by other ACI committee members.

1.7.3 Appointments to joint committees

When ACI is the major sponsor of a joint committee, appointment of members conforms to ACI guidelines. When ACI is the minor sponsor of a joint committee, appointment of members conforms to the other society’s guidelines. Written agreements between ACI and other organizations may regulate membership of joint committees when a different arrangement is desired.

1.7.4 Overlap of membership between committees

The chair should review the missions of closely-related committees and develop overlapping membership where desirable, because cross-representation aids coordination. Sometimes it is necessary to use capable voting members in multiple committee assignments. Voting membership on more than three technical committees, however, is generally discouraged.

1.7.5 Appointment not approved

The chair may decline an application for voting membership for various reasons, including lack of qualifications, the inability to attend committee meetings, committee balance, timing of a critical ballot, or committee size. Adding voting members just before conducting a critical letter ballot is not advisable because new voting members may not have knowledge of past committee discussions.

1.7.5.1 Committees with restricted membership

In general, membership in ACI technical committees is open to all qualified individuals. TAC allows the chairs of ACI Committees 301, 318, and 562 to restrict membership allowing membership by invitation only. These committees have a set membership during the document cycle, and some qualified applicants may not receive appointment.

1.7.6 Membership termination

The chair should periodically review each voting member’s performance. Voting members should regularly attend meetings, answer correspondence, and return letter ballots. Contact inactive voting members and encourage them to become more active, consider resigning, or become an associate or consulting member of the committee. Because of ACI’s stringent voting requirements, voting members who do not return ballots may stop a committee from successfully balloting a document. Failure of a voting member to participate actively in committee activities may result in termination of membership.

When a voting member’s inactivity is documented, the chair may decide to change the individual’s membership status to associate or consulting, or may terminate the membership. These actions become official when staff acts on the chair’s decision. Before terminating membership of a voting member, the chair is encouraged to discuss the situation with the TAC contact.

1.7.7 Resignation from membership

Committee members resign by notifying the chair and the Managing Director of Engineering of such intent. Staff sends an official notice confirming the resignation.

1.7.8 Appeal of membership action

Individuals may appeal a membership action to TAC, such as a membership termination or a membership application that has been declined. The person submits the appeal to the Managing Director of Engineering. The committee’s TAC contact reviews the appeal and recommends action to TAC. The person may request to attend the TAC meeting where the appeal is considered.

1.8—Balance of interests

All committees should have broad-based membership to ensure balanced coverage, including members who represent interests materially affected by the committee’s documents. All materially affected interests should have the opportunity for fair and equitable participation. ACI is an international organization and committee documents should reflect practices that are broadly applicable. Wide geographical distribution of committee members guards against publication of documents that are restricted to local practices.

To support the development of competent and objective standards by ACI committees, standards-writing committees are to have a balance of voting member interests. Each voting member of a committee who prepares or has jurisdiction over standards shall be classified by the chair as Producer, User, or General Interest, as defined in 1.8.1 through 1.8.3. ACI requires that the combined number of voting members classified as User and General Interest shall equal or exceed the number of voting members classified as Producer. A member’s classification shall be related to the mission of the committee, and so a member’s classification can be different on different committees. Committees that develop ACI standards must be in balance all the time. The roster for which the balance of interest is determined should match the roster on the date of final letter ballot of the document before submission for TAC review.

Members may appeal their classification to the committee chair and ultimately to TAC. Committees seeking exceptions to the strict requirements of this section can request TAC consideration. Balance of interests is not required in subcommittees or task groups.

Committees that only prepare guides and reports are not required to conform to the requirements of this section. Membership should ensure balanced coverage of the subject.

Questions regarding committee balance will be resolved by TAC. TAC will consider many factors affecting balance. This will include the total number of producer members on the committee and the number of members from a particular number of members representing a specific product. More than one voting member from the same organization is discouraged on any committee. Voting membership of three or more individuals from a single organization must be approved by TAC.

1.8.1 Producer

A voting member affiliated with a producer interest shall be classified as a Producer. A producer interest is an organization, trade association, or individual that produces, markets, or sells materials, products, or systems covered in the committee’s mission.

1.8.2 User

A voting member affiliated with a user interest shall be classified as a User, provided that the member could not also be classified as a Producer. A user interest is an organization that purchases or uses materials, products, or systems covered in the committee’s mission. For example, a design engineer who is a member of a committee writing a design guide would be classified as a User, but would be classified as General Interest on a committee dealing with concrete materials.

1.8.3 General interest

A voting member not classified as Producer or User shall be classified as General Interest. For example, an employee of a government agency or a university is usually classified as General Interest.

1.8.4 Consultants

A consultant retained by a producer interest or by a user interest under an indefinite continuous arrangement that includes ACI committee membership shall be classified as Producer or User, respectively. Consultants representing themselves or affiliated with an employer not classified as a Producer Interest or User Interest shall be classified as General Interest.

1.8.5 Membership termination to achieve balance

To achieve balance of voting member interest, the chair may terminate voting memberships or change them to nonvoting categories. This is done only after the chair has shown that a substantial effort has been made to obtain balance by adding new voting members.

When a change of employment produces a change in classification that results in an imbalance in voting interests, a voting membership can be terminated or changed to another membership category. Reappointment as a voting member can be considered when balance of voting member interest is achieved and if the person requests reappointment.

1.9—Committee officers

1.9.1 Chair

Each technical committee shall have a chair and a TAC contact. All other committee officer positions are established at the chair’s discretion.

The chair is responsible for leading the committee to accomplish its mission and goals. The chair has many specific responsibilities, including:

(a) Initiating voting and consulting membership actions, including appointment, membership recruitment, evaluation, changes of voting category, and discharge

(b) Preparing and distributing meeting agenda and minutes in a timely manner (approximately 3 weeks before and after a meeting)

(c) Maintaining communication with the TAC contact

(d) Conducting committee meetings

(e) Establishing task groups and subcommittees as needed

(f) Scheduling committee meetings

(g) Initiating committee letter ballots

(h) Producing letter ballot summaries

(i) Submitting committee documents to TAC

(j) Submitting biannual reports to TAC after each convention (including ITGs)

(k) Providing leadership training for possible successors

(l) Attending the TAC chair breakfast workshop at each convention (2.5)

(m) Maintaining committee’s web pages

1.9.1.1 Chair qualifications

A chair of an ACI technical committee must be a member of ACI. Prior service as vice chair or secretary and voting membership on the committee augment the candidate’s experience.

The success of any committee effort depends largely on the skills of the chair. Chairs of ACI technical committees must be able to perform the chair responsibilities outlined in 1.9.1 and possess the following strengths:

(a) Demonstrated ability and knowledge in the field covered by the committee

(b) Demonstrated leadership ability

(c) Administrative ability and initiative

(d) Available time and facilities to perform the work

(e) Ability to attend all ACI conventions

1.9.1.2 Chair candidates

Chairs are responsible for preparing a number of individuals to assume the committee leadership to ensure continuity. Each year, chairs are asked to identify at least three possible replacements, in order of preference, with specific ratings in various categories. ACI staff will notify all committee members of the impending conclusion of their chair’s term one convention before the chair term ends. Voting committee members interested in the position may submit their name to the outgoing chair to be included on the list of candidates for TAC consideration.

1.9.1.3 Chair appointment

Appointment and reappointment of technical committee chairs are among TAC’s most important responsibilities. TAC considers the advice of chairs when appointing their successors, but chair appointments are TAC’s responsibility. TAC may interview the proposed candidates during the selection process.

TAC considers the chair qualifications of the candidates (1.9.1.1) and other factors when selecting chairs, including:

(a) Rotating the chairs among all qualified committee members to keep committee output vigorous

(b) Ensuring that an individual does not chair more than one ACI technical committee at a time

(c) Ensuring participation of all segments of the concrete industry in committee activities

1.9.1.4 Chair term

TAC usually appoints a chair for a 3-year term, which expires at the end of an ACI spring convention. A chair may be reappointed for one additional term.

Unusual circumstances are required to justify reappointment of a chair beyond 6 years.

ITG chairs are appointed for the duration of the ITG.

An incoming chair is granted officer rights on the committee web page 30 days before the term becomes effective. An outgoing chair will maintain officer rights on the committee web page for 30 days after the term ends. The website roster will show incoming and outgoing chairs with temporary classifications, such as incoming and outgoing chair.

1.9.1.5 Chair resignation

A committee chair resigns by notifying the Managing Director of Engineering and is asked to supply three replacement chair candidates.

1.9.2 Vice chair

A vice chair can assist the chair in administering the committee, and is appointed at the chair’s discretion. Appointment does not imply that the vice chair will become the next chair.

1.9.3 Secretary

A secretary is encouraged to support the chair by recording, preparing, and distributing meeting minutes; assisting with the balloting process; and handling correspondence. The secretary is appointed at the chair’s discretion.

CHAPTER 2—TECHNICAL COMMITTEE OPERATIONS

2.1—Mission

The main purpose of ACI technical committees is to disseminate information through publications within the scope of the committee mission. TAC gives the chair considerable authority to accomplish the committee mission. In most cases, missions are broad so as not to limit the document type a committee produces. Mission statements are usually in the form of: “Develop and report information on <topic>.” A change to the mission must be approved by committee ballot before submitting to TAC. This is considered an administrative ballot. Technical committee missions may be viewed in two categories: 1) general technical knowledge, such as fracture mechanics or durability; and 2) industry-specific knowledge, such as parking structures.

Committee missions are approved by TAC and posted on the committee web page. A committee request to change the mission will be considered by TAC.

2.2—Goals

Each committee periodically reviews and prepares specific goals that support the committee mission. Appointed chairs will be asked to submit the goals to be completed during their term. The chair submits information on the progress of the committee goals in the biannual report, which is then published on the committee’s web page. Any or all of the goals in 2.2.1 to 2.2.5 may be included.

2.2.1 Develop new documents

A committee may prepare an ACI document within the mission of the committee. TAC approval is required before developing a new ACI document (7.3).

2.2.2 Maintain existing documents

Technical committees are required to periodically reapprove, update, revise, or withdraw their documents. TAC approval is not required before updating a published document; however, the committee should inform TAC of the intent not to revise an ACI document. If the committee does not revise, reapprove, or withdraw a document within the 8-year period, TAC may reapprove or withdraw it without committee recommendation. Refer to 4.2.2.1 to 4.2.2.

2.2.3 Sponsor convention sessions and related publications

A committee may sponsor sessions or symposia at ACI conventions within the committee mission and may develop a related publication as an ACI Special Publication (SP). TAC approvals are required for the development of sessions and special publications as indicated in Chapter 12.

2.2.4 Develop seminars

ACI’s Educational Activities Committee (EAC) reviews, approves, and manages all ACI seminars. In cooperation with educational committees, a committee may develop ACI seminars or workshops within the committee mission. This includes suggesting qualified seminar topics, speakers, pertinent topics, or appropriate presentation materials following recommendations in Chapter 13.

2.2.5 Develop video information

A committee may develop video information. TAC approvals are required for the development of video products as indicated in Chapter 13.

2.3—Meetings

All technical committee meetings (except closed or virtual interim meetings) are open to visitors. The chair is encouraged to give a brief introduction of the committee work and periodically summarize progress during the meeting.

2.3.1 Conducting committee meetings

Committee chairs are to exercise control to ensure orderly discussion at meetings. This is particularly important in large committees. Use parliamentary procedures, known as Robert’s Rules of Order. Robert’s Rules of Order for passing a motion is superseded by ACI rules if the motion is related to technical committee documents. A presentation on parliamentary procedures is available on the left side of the ACI website under Technical, and then Committee Assistance. If the chair cannot attend the meeting, designate an individual to chair the meeting so that committee work can continue uninterrupted.

2.3.2 Quorum

For technical committee issues involving technical documents, a quorum is defined as 40 percent of all voting members who must be present at the meeting to conduct business. ACI Committee 318 must meet the requirements in 3.3.2.

For administrative actions unrelated to technical committee documents, such as motions regarding sessions, SPs, goals, and mission changes, a quorum is defined as half of all voting committee members.

2.3.3 Administrative actions

For passage of administrative actions at committee meetings, affirmative votes are required from at least 50 percent of the voting members present at the meeting. Administrative actions include motions regarding sessions, SPs, goals, mission changes, meeting times, and approval of minutes.

2.3.4 Convention committee meetings

Committee meetings take place at ACI conventions. ACI committees are expected to meet at every ACI convention. Committee chairs are responsible for scheduling and calling committee meetings. Committee officers can request meeting rooms through the committee’s website. Chairs communicate with ACI staff for guidance and to ensure sufficient early notification of and inclusion of the meeting in the convention booklet.

Committee members and ACI staff must be notified at least 21 days in advance if a scheduled meeting is to be canceled.

Only members that are physically present at the meeting can vote. A member cannot call or videoconference in to the meeting to cast a vote.

2.3.5 Interim committee meetings

Interim meetings (between ACI conventions) may be approved by TAC; however, such meetings are not to replace a convention meeting.

Chairs may submit a request for an interim meeting to the Managing Director of Engineering. A request must include a reason, agenda, anticipated participants, meeting location, and the meeting time and duration. The committee is permitted to vote on resolutions of negative votes. The agenda and minutes for the interim meeting must be posted on the committee website in accordance with 2.3.8 and 2.3.9.

2.3.5.1 Physical interim meetings

Chairs must submit a request to hold a physical interim meeting at least 3 months in advance. If approved, a notice of the meeting place and time will be published in Concrete International.

2.3.5.2 Virtual interim meetings

Chairs must submit a request to hold a virtual interim meeting to the Managing Director of Engineering at least 2 weeks in advance. If approved, no public notice is required because virtual meetings cannot accommodate visitors (an exception to 2.3.7). Committee members must be notified of the virtual interim meeting at least 1 week in advance. ACI staff will communicate the virtual meeting with committee members.

If the virtual meeting is approved, committees can use any conferencing system, such as teleconference, video conference, or online conference. ACI does not provide the conferencing system or staff support, and does not pay for the conferencing system.

2.3.6 Closed meetings

A closed committee meeting is permitted if the chair states that the matter under consideration is administrative rather than technical. For example, a meeting to discuss a slate of potential chairs is closed. Discussion of technical matters in a closed meeting is not allowed. For a closed meeting, the chair makes the usual arrangements through staff for the meeting room but is solely responsible for notifying members of the meeting. Closed meetings are not listed in the convention booklet. A closed meeting may only be attended by committee members and ACI staff.

2.3.7 Visitors

Visitors are welcome at committee meetings because committee work is of interest to the public, but their presence should not interfere with committee work. The chair should keep the presence of visitors in mind by periodically summarizing meeting progress.

2.3.8 Agenda

The chair should prepare the agenda in advance of the meeting and post it to the committee’s website. The chair should send a notification to the committee members and the committee’s TAC contact when the agenda has been posted and bring printed copies to the meeting for committee members and visitors.

2.3.9 Minutes

Record important deliberations, resolution of negative votes (Chapter 3), and decisions reached during committee and subcommittee meetings in the meeting minutes. Minutes provide a continuous record of committee work and help prevent repeated discussion of the same subject. Post minutes to the committee’s web page approximately 3 weeks following the meeting. Approve the minutes at the next committee meeting or by correspondence. Post minutes to the committee web page.

In addition to recording motions and voting results, the minutes should include the names of committee members and visitors in attendance and voting members not present.

2.4—Communication

Effective communication is vital to committee activity and progress. To ensure timely completion of committee work, concise correspondence with prompt attention and reply by members is necessary.

Committee chairs and secretaries are encouraged to use the committee web page to speed committee communication.

2.4.1 Correspondence within a committee

Make available to the entire committee correspondence related to committee activities. This allows the members to be up-to-date before meetings so that committee discussions are more effective.

Make correspondence available to the main committee officers so that they are aware of the work and better able to coordinate the total committee effort.

2.4.2 Correspondence between committees

Correspondence between committees usually occurs between the chairs, with copies sent to the Managing Director of Engineering. If committee members correspond on committee activities, send copies to the chairs of the respective committees.

2.4.3 Correspondence with TAC and ACI headquarters

The committee files at ACI headquarters are the official files. The chair can either post all important correspondence, agenda and minutes, complete records of ballots, and resolution of negative votes to the committee’s website as appropriate, or distribute copies to all committee members, the TAC chair, TAC contact, and the Managing Director of Engineering. Anything sent to staff for processing, such as a document submittal, must be accompanied by instructions. Refer to the ACI website Document Development page and the Committee Help page in Committee Assistance under the Technical tab. Any material received at ACI headquarters without instructions is regarded as an information copy and, after the contents are noted, is placed in the committee file.

Post draft documents to the website or distributed to all committee members, the TAC chair, the TAC contact, and the Managing Director of Engineering.

The ACI President and staff, other than the Managing Director of Engineering, do not need copies of correspondence unless it relates to Institute matters outside of technical committee work.

If a committee is joint with another organization, additional distribution of correspondence may be required.

2.4.4 Discussion in outside publications

If an outside publication publishes articles or comments on a technical committee’s area of expertise, a committee can respond by a letter to the editor or other appropriate means. The committee may reiterate published ACI information, but must not present new technical information without TAC approval. TAC must approve all letters written by committees to outside entities. Individual committee members may express their opinion as appropriate, but must indicate they do not represent ACI.

2.4.5 Coordination among committees

The missions of several committees may be closely related and the work of one committee may affect or overlap with another. To avoid publishing conflicting information in ACI documents, chairs must be aware of their committee’s work in relation to other technical committees, and reference other ACI documents when applicable. If a chair is unaware of another committee’s work, a visit to that committee’s web page is helpful. The TAC contact or staff can assist the chair in identifying related committee work.

2.4.6 Biannual report

Each chair is expected to submit a report of committee activities within 30 days after each convention through the use of a web-based form. The Biannual Report Submittal Form is available on the Committee Member Work Area of each committee’s web page. This report is available to committee members and helps TAC coordinate committee activities with other committees, and to evaluate the committee’s progress.

2.4.7 Questionnaires

Chairs may find it useful to gather information by using questionnaires. Carefully design questionnaires so as to elicit meaningful responses. Send a copy, along with a summary of the results or other appropriate information, to the Managing Director of Engineering. The summary should be made available to the committee and all respondents.

A membership questionnaire (on the Chair/Officer Work Area of the committee web page) may be used to ask committee members if they desire to continue as active members, change membership status, or resign.

2.5—Breakfast meeting for technical committee chairs

At each ACI convention, TAC holds a meeting for technical committee chairs. These meetings are designed to allow the committee chairs to meet and interact with their TAC contacts, find out what is expected of them as chairs, hear about new developments, and ask questions.

The technical committee chairs are expected to attend these meetings. If the chair is unable to attend a meeting, the chair is to name an alternate so the committee can be represented at each meeting. Only one person should represent the committee. At the spring meeting, the incoming chairs are also invited to attend.

2.6—Technical committee certificates

ACI recognizes technical committee members with the following types of certificates for technical committee participation and outstanding service by committee members.

2.6.1 Voting member certificates

As official recognition of appointment of a voting member, ACI sends an appointment notice.

2.6.2 Chair certificates

On behalf of TAC, ACI sends a certificate of appreciation to outgoing technical committee chairs. The certificate recognizes the contributions of the person for chairing a specific committee and the years of service.

2.6.3 Outstanding service by committee members

The committee chair may recognize a committee member who has performed outstanding service, such as:

(a) Extraordinary effort in the production or revision of a committee document

(b) Leadership and administrative skills in organizing and conducting a successful technical session

The chair shall obtain TAC contact approval before recommending this recognition to ACI. ACI issues the certificate with the committee chair and the TAC contact as signatories.

2.6.4 Del Bloem Distinguished Service Award

The Institute established a Distinguished Service Award in 1969 to recognize noteworthy work on ACI technical committees. The name of the award was changed to the Delmar L. Bloem Distinguished Service Award in 1972 in honor of the late Delmar Bloem who had demonstrated, over a period of many years, the characteristics and dedication required for the award. The award is given to a current (or recent) chair of a technical committee, or under special circumstances, to deserving individuals other than committee chairs, in recognition of outstanding performance.

One award may be given each year; however, there may be none or more than one recipient in any particular year.

Any ACI member can nominate another member. Nominators will submit to ACI Headquarters an email or letter emphasizing the chair or committee member’s outstanding performance on a particular committee.

Nominations submitted by January 31 will be considered by TAC at the spring meeting. TAC approves the candidates at their summer meeting, and submits names and citations to the Board for approval in the fall. The awards are granted the following spring and the recipients are listed on the ACI website and in Concrete International.

2.7—Committee-related finances

2.7.1 ACI Foundation funding

The ACI Foundation is a subsidiary of the American Concrete Institute that receives, administers, and expends funds for educational, research, and scientific purposes. The Foundation’s Concrete Research Council (CRC) reviews research funding requests and provides funds as available and appropriate. The Foundation’s Strategic Development Council (SDC) is a forum for the leaders in the concrete industry, government, academia, and customers to discuss and develop strategies and initiatives to overcome obstacles to technology acceptance. The SDC is a source of ideas for ACI committees and ITGs.

2.7.2 Concrete Research Council (CRC)

Each committee should list high-priority research topics in their biannual report that, if funded, would assist the committee in completing its mission. This list of identified needs is sent to the CRC chair for consideration. To assist committees, the CRC can:

(a) Endorse a research project

(b) Provide partial or full funding

(c) Locate a research team

(d) Secure funding outside of CRC

2.7.3 Strategic Development Council (SDC)

The SDC periodically identifies industry-critical issues that would benefit from development of ACI documents. The SDC coordinates with TAC at each convention regarding industry issues, including appropriate platforms for development of documents requested by the SDC, through an existing technical committee, the formation of a technical committee, or the formation of an ITG. Should the development of such an ACI document require funding, the SDC will manage the funding.

2.7.4 Committee work expenses

The Managing Director of Engineering can honor vouchers from a committee chair, or a person authorized by the chair, for postage or reproduction expenses incurred in committee work. ACI does not assume other committee expenses unless the Board of Direction specifically provides prior authorization.

2.8—Staff assistance

Although the ACI engineering staff is not large enough to provide a permanent liaison for each committee, staff can assist a chair with technical, editorial, or administrative tasks.

CHAPTER 3—BALLOTING

3.1—Voting methods and rules

Letter ballots and meeting ballots are the two methods of voting available to committees.

ACI’s consensus process consists of three rules applicable to letter and meeting ballots: the 1/2 rule, the 40 percent rule, and the 2/3 rule (refer to Table 3.1).

Balloting examples, including letter ballots, meeting ballots, and consideration of negative votes, are found on ACI’s website.

Proxy voting is not allowed.

3.1.1 Administrative ballots

Administrative ballots are ballots that do not require a resolution of negative votes. Examples of administrative ballots include:

(a) Changing a title, goal, or mission statement

(b) Selecting day and time of next meeting

(c) Requesting joint committee status

(d) Cosponsoring documents with other ACI technical committees

(e) Sponsoring a session or special publication (SP)

(f) Approval of committee meeting minutes

3.2—Letter ballots

Letter ballot—A letter ballot is an official written action to determine if an item has the consensus of a technical committee or ITG. Letter ballots can be used to vote on preparing new documents, revising or withdrawing existing documents, responding to TAC and public discussion comments, and administering administrative ballots.

A letter ballot consists of one or several items. Each item passes or fails separately, and may include as much content as desired: an entire document, a chapter, a section, several sections, a paragraph, or other information.

Members have the following voting options for each item on the letter ballot: affirmative, affirmative with editorial comments, negative, or abstain. Members are expected to return a vote on each item.

If a member votes negative on an item and has editorial comments that are not part of the negative, they must be clearly marked as editorial. If the comments are not clearly marked, the chair must communicate with the negative voter to clarify which comments are editorial.

TAC strongly encourages the use of the balloting feature on the committee website for all letter ballots.

3.2.1 Passage of letter ballot items

Items on a letter ballot pass if both the 1/2 Rule and 2/3 Rule are satisfied.

The 1/2 Rule is satisfied if at least half of all eligible voting members on the committee roster cast an affirmative vote.

The 2/3 Rule is satisfied if the number of affirmative votes is at least twice the number of negative votes.

A letter ballot item supersedes all previous ballots on that same item.

A summary of the process to analyze letter ballot results is shown in Fig. 3.2.1.

The final letter ballot is defined as the last letter ballot that contained an item that completed the document, allowing the committee to submit it for TAC review. A letter ballot item to find negative votes from previous ballots nonpersuasive is not considered a final letter ballot. Refer to the ACI website for balloting information and tools.

3.2.2 Initiation and format

A committee chair can initiate a letter ballot at any time, or a voting member can call for a letter ballot by making a motion at a committee meeting. To pass such a motion, a majority of voting members present at the meeting must vote affirmatively.

The chair formats the letter ballot items as deemed suitable. It is suggested to distribute the ballot items in portable document format (pdf) (not as word processing files) with page and line numbers. Committee members can then reference the page and line numbers when making comments using the document ballot form. The chair should upload the document ballot form, available on the ACI website, with the ballot.

3.2.3 Time frame

All letter ballots must specify a closing date, which should be no less than 30 days from the date of initiation.

To specify a balloting period shorter than 30 days, the chair must obtain approval from the committee’s TAC contact, and notify the Managing Director of Engineering of the approval. In such a case, the chair must ensure that all voting members received the letter ballot and have had the opportunity to vote. An acceptable method is for the chair to contact any voting member who has not responded a few days before the ballot closes.

There are no restrictions on the maximum number of days that may be specified for a balloting period. For example, the chair may extend the closing date if an insufficient number of ballots are received by the closing date. All voting members must be notified in the case of an extension and given the opportunity to vote or change their existing vote. All votes received, including negative votes received during the extended voting period, shall be included in the ballot analysis. Votes received after the closing date are not counted and do not have to be resolved. Balloting ends at 11:59 pm Eastern Standard Time.

3.2.4 Distribution

A letter ballot shall be distributed to all committee members. A letter ballot can be distributed by the web balloting feature of the committee’s ACI website or by e-mail. Web balloting is the preferred method, and chairs are encouraged to use the ACI website to issue and tabulate letter ballot results. If the chair prefers not to use the web balloting feature, the ballot must include the due date for ballot response, method to respond to the ballot, voting options, and ballot description. A notice of the web ballot shall be sent to the TAC contact. The results of the letter ballot must be placed on the agenda of the next committee meeting and reported in the minutes of that meeting.

3.2.5 Votes

Voting members, including the chair, are required to vote on every item on all letter ballots. For web ballots, submit a vote using the web ballot form or as required by the chair.

3.2.5.1 Affirmative votes

An ACI letter ballot must allow for members to submit affirmative votes. Affirmative votes require no further committee action.

3.2.5.2 Affirmative votes with comments

An ACI letter ballot must allow for members to submit affirmative votes with comments. An affirmative vote with comment is considered as an affirmative vote when determining if an item in a letter ballot passes. If the committee chair deems a comment is editorial and appropriate, the chair has the authority to implement the change if there are no objections by voting members; no further action by the committee is required.

If the chair or voting member believes that the comment is not editorial, or if there is doubt, the committee chair must change the vote to “negative” and ballot to resolve the negative (3.2.5.3).

The chair may also decide to relegate the changes suggested by the voter to new business to be addressed in a later revision of the document.

3.2.5.3 Negative votes with reason

An ACI letter ballot must allow for members to submit negative votes. If a committee member casts a negative vote on an item in a letter ballot, a reason for the negative vote must be included. If appropriate, the voter should provide alternative wording or a solution that would satisfy the voter’s concerns. All negative votes cast on an item in a letter ballot are considered by the committee using the resolution procedures described in 3.4.

If the negative voter does not provide a reason for the negative vote, the vote is recorded as a negative without comment. A negative without comment is considered an abstention when determining if a ballot item passes, does not need to be resolved by the procedures given in 3.4, and requires no further committee action.

3.2.5.4 Abstentions

An ACI letter ballot must allow for members to submit abstentions. Abstentions impact letter ballots because only affirmative and negative votes are counted when applying the 1/2 rule to determine if a ballot passes. Voting members usually abstain if they do not have enough relevant expertise to cast an educated vote, or if they have a conflict of interest with the item being balloted. In addition, only affirmative and negative votes are counted when applying the 2/3 rule to determine if a ballot passes.

3.2.5.5 Ballots not returned

If a member does not return a vote on a letter ballot, their ballot is recorded as not returned. An unreturned ballot is considered an abstention when determining if an item in a ballot passes, and can therefore impact the result in the same manner as an abstention. If an insufficient number of ballots are returned by voting members, items in the ballot will not receive enough affirmative votes to meet the 1/2 rule.

3.2.5.6 Comments from nonvoting members

Associate, consulting, and liaison members may submit comments on letter ballot items. The comments are not counted in the final ballot tally, do not affect the outcome of a ballot item, and do not have to be resolved. However, these comments must be distributed to the committee for review.

3.2.6 Analysis and further action

Once the letter ballot is closed, the chair reviews all votes received on individual items of the ballot and determines if each item satisfies the 1/2 and 2/3 rules. At this point, the chair shall notify the committee of the letter ballot results, including all editorial comments and negative votes received. Letter ballot items that do not pass can be revised and submitted for another letter ballot or withdrawn from further consideration.

If a ballot item passes but some members cast negative votes, further action by the committee is still required. All negative votes cast on a passing ballot item must be resolved by the committee using the procedures described in 3.4. If a negative cannot be resolved on an item that pertains to a revision of a document, the ballot item can be withdrawn and no change is made to the document that relates to the ballot item.

3.2.6.1 Updating results

Resolving negative votes using the procedures described in 3.4 may change the final vote tally. Therefore, if a ballot item initially fails to satisfy the 1/2 and 2/3 rules, the chair may resolve the negative votes in an attempt to pass the ballot item. In some cases, resolved negative votes on the ballot item are recorded as affirmative votes, and in other cases, they are recorded as abstentions.

3.2.6.2 Revising and reballoting

Even if an item passes, the chair may decide that too many negative votes have been received and it is not practicable to attempt resolving them, or that the ballot has identified major deficiencies in the document. In either case, the chair informs the committee members that the item will need to be revised and reballoted. Each ballot on an item supersedes the previous ballot on the same item, so the negative votes from the previous ballot do not have to be resolved.

3.2.7 Subcommittee letter ballots

Committees with subcommittees shall establish procedures for subcommittee letter ballots. The purpose of subcommittee ballots is to obtain the consensus opinion of that group, which is passed on to the main committee. The chair may require subcommittees to follow all of ACI’s consensus procedures; however, because an item approved by the subcommittee must still be balloted by the main committee to be accepted, there is no ACI requirement that negatives on subcommittee ballots be resolved. Reasons for unresolved negative votes on subcommittee ballots need to be forwarded to the main committee.

3.2.8 Patented items

During balloting of the document, the committee must be informed if the document refers to the use of patented technology. If a member believes that a committee document under ballot would require a user of the resulting ACI document to violate the intellectual property rights, such as patents or copyrights, that member is expected to alert the committee. If the committee includes information on patented items within a document, include the disclaimer in 14.2.7.

3.3—Meeting ballots

Meeting ballot— A meeting ballot is a vote taken at either a convention or interim meeting in response to a motion made by a voting member. Meeting ballots can be used to vote on whether an existing document should be revised or withdrawn, to resolve negatives on a meeting ballot, to respond to TAC review comments of an approved document, to respond to public discussion comments, and distribute administrative ballots. Meeting ballots cannot be used to ballot a new document or new revisions to a document.

A meeting ballot consists of a single item. This one item is in the form of a motion and may address different actions: resolution of all, several, or one negative vote; responses to all, several, or one TAC or public discussion comment; or other items. This one item passes or fails. Meeting ballots allow for flexibility in separating information that causes the ballot to fail, in reorganizing information included in the ballot item, and in immediately reballoting information that has consensus.

Only members that are physically present at the meeting can vote. A member cannot call or videoconference in to the meeting to cast a vote.

3.3.1 Passage of item by meeting ballot

The 40 percent and 2/3 rules must be satisfied for an item to pass by meeting ballot. The 40 percent rule is satisfied if at least 40 percent of all eligible voting members on the committee roster cast an affirmative vote. The 2/3 rule is satisfied if the number of affirmative votes is at least twice the number of negative votes. The committee must consider negative votes on the meeting ballot by using procedures in 3.4.

Meeting ballot results, including number of voting members present at the time of ballot, must be reported in the meeting minutes.

TAC recommends that the chair abstain on meeting ballots, unless the chair’s vote influences the outcome of the item being balloted. For example, the chair’s vote may be needed to meet the 40 percent rule.

3.3.2 Exception to the 40 percent rule

ACI Committee 318 uses the 1/2 rule instead of the 40 percent rule for the number of affirmative votes required to pass an item in a meeting ballot.

3.4—Consideration of negative votes

Some negative votes received on letter or meeting ballot items that have passed require further action by the committee. Negative votes on administrative ballots, such as selecting the day and time of the next meeting, do not require resolution.

Resolution not required

The following negative votes do not have to be resolved and no further action is required by the committee:

(a) Negative votes without comment received on a letter ballot

(b) Negative votes that have been withdrawn

(c) Negative votes on finding the reason for a previous negative vote unrelated to the balloted item

(d) Negative votes on finding the reason for a previous negative nonpersuasive

Resolution required

The following negative votes need to be resolved by the committee:

(a) Negative votes on letter ballots to approve new or revised wording in a document

(b) Negative votes on letter or meeting ballots to approve changes to a committee document in response to TAC review or public discussion comments;

(c) Negative votes on a letter or meeting ballot to approve revising a committee document to satisfy a persuasive negative vote or a resulting change to the document in response to TAC comments or public discussion

Methods of resolution

A negative vote is resolved through letter or meeting ballot in one of three ways:

(1) The committee may ballot to find that the reason for the negative vote is unrelated to the balloted item.

(2) The committee may ballot to find that the reason for the negative vote is nonpersuasive; giving reason for finding negative nonpersuausive.

(3) The committee may ballot to find that the reason for the negative vote is persuasive and approves a revision to the balloted item.

The balloted resolution of negative votes must be recorded in the meeting minutes. Figure 3.4 provides a summary of the process for resolving negative votes.

3.4.1 Withdrawal of negative vote (no change to document)

A voter may withdraw a negative vote during a committee meeting or in writing between meetings. Withdrawal of a negative vote must be recorded in the meeting minutes.

The voter may be willing to withdraw the negative vote based on either an editorial change or no change. If a voter withdraws a negative vote, the chair records the vote in the final vote tally as affirmative or as an abstention in accordance with the voter’s wishes.

The voter’s decision to withdraw a negative vote may be on the condition that the committee considers the item as new business. This agreement must be recorded in the committee minutes and the item is listed on the agenda for future meetings until action is taken.

3.4.2 Unrelated to ballot item (no change to document)

The chair, through an item on a letter ballot or a voting member at a meeting, may make a motion that the stated reason for the negative vote is unrelated to the balloted item.

By letter ballot

The chair issues a letter ballot with an item to find the reason given for a negative vote unrelated and provides supportive information. The ballot item must satisfy both the 1/2 and 2/3 rules to pass. Negative votes on this ballot item do not need to be resolved.

By meeting ballot

During a meeting, a voting member makes a motion that the reason given for a negative vote is unrelated and provides a statement to support the motion. The committee discusses the motion and then votes. The ballot must satisfy both the 40 percent and the 2/3 rules to pass. Negative votes on this ballot do not need to be resolved.

If a letter ballot item or meeting ballot to find a negative vote unrelated fails, the negative vote must be resolved under 3.4.3 or 3.4.4.

If the ballot to find a negative vote unrelated is successful, the ballot results and the committee’s reasons are reported in the meeting minutes. The vote is recorded in the minutes as an abstention. The comment may be considered as new business by the committee.

3.4.3 Nonpersuasive (no change to document)

The chair may issue a letter ballot or a voting member at a meeting may make a motion that the stated reason for the negative vote is nonpersuasive.

By letter ballot

The chair issues a letter ballot with an item to find the reason given for a negative vote nonpersuasive and provides a statement to support the action. The ballot item must satisfy both the 1/2 and 2/3 rules to pass. Negative votes on this ballot item do not need to be resolved.

By meeting ballot

During a meeting, a voting member makes a motion that the reason given for a negative vote is nonpersuasive, and provides a statement to support the motion. The committee discusses the motion and then votes. The ballot must satisfy both the 40 percent and the 2/3 rules to pass. Negative votes on this ballot do not need to be resolved.

If the ballot to find a negative vote nonpersuasive fails, the negative vote must be resolved under 3.4.4, or the committee must withdraw the item from further consideration and ballot a revised item. Ballot results are reported in the meeting minutes.

If the ballot to find a negative vote nonpersuasive is successful, the ballot results and the committee’s reasons are reported in the meeting minutes. The original negative vote is recorded in the minutes as a nonpersuasive negative.

3.4.4 Persuasive (technical change to document)

Unless the negative vote is withdrawn, is found to be unrelated, or is found to be nonpersuasive, the negative vote must be considered to be persuasive. The committee must vote to approve a technical change to the document in response to the negative vote.

By letter ballot

The chair issues a letter ballot with an item to accept the proposed change. The ballot item must satisfy both the 1/2 and 2/3 rules to pass. Negative votes on a successful ballot item must be resolved by another letter ballot or by meeting ballot.

By meeting ballot

During a meeting, a voting member makes a motion to accept the proposed change. The committee discusses the motion, considers suggested amendments, and then votes. The ballot must satisfy both the 40 percent rule and the 2/3 rule to pass. Negative votes on a successful ballot must be resolved by another meeting ballot or by letter ballot, unless the negative voter agrees that formal resolution of the negative vote is not required. Such an agreement shall be recorded in the minutes.

If a ballot to change a document in response to a persuasive negative vote fails, the negative vote must be resolved under 3.4, or the committee must withdraw the item and ballot a revised item that addresses the negative vote.

When a ballot to change a document in response to a persuasive negative vote passes unanimously, including an affirmative vote from the voter who cast the original negative, the original negative is recorded in the minutes as a negative. The minutes shall also record the affirmative vote on the motion to resolve the previous negative.

If a document is revised in response to a persuasive negative vote, the meeting minutes must report that the negative was found persuasive and give the approved technical change and the vote count.

3.4.5 Appeals

A member whose negative vote is found unrelated or nonpersuasive has the right to appeal. A note in the minutes is sufficient notice of this right. The appeal must be submitted to TAC and must state whether it is based on technical or procedural grounds. The appeal cannot be submitted before the committee balloting on the document is complete. Appeals are handled in accordance with 4.6 and 7.6.

3.5—Ballot summaries

The results of all letter and meeting ballots must be recorded in the committee minutes, as minutes are the official record of committee actions. If a separate ballot summary of a letter ballot was mailed to the committee, it must be attached to the minutes of the next meeting. Alternatively, the text of the minutes can summarize the ballot results.

Additionally, a formal ballot summary must be submitted to the Managing Director of Engineering for each letter ballot at the time the document is submitted to TAC for review. A ballot summary allows a complete ballot history to be maintained at ACI headquarters during the development and processing of a document to publication. The ballot summary must include:

(a) A list of the items balloted

(b) The date the ballot was initiated

(c) The closing date

(d) A list of voting members at the time of the final ballot

(e) For each item, the initial vote tally, including:

(i) The number of affirmative votes

(ii) The number of affirmative with editorial comment votes

(iii) The number of negative votes and names of each negative voter

(iv) The number of abstentions and names of voters who abstained

(v) The number of ballots not returned and the names of voters who did not respond

(vi) The resolution of each negative, including a summary for subsequent letter or meeting ballots

(f) For each item, the final vote tally if any votes changed due to consideration of negatives.

A copy of the ACI web ballot results page along with documentation on resolution of negative votes is sufficient.

3.6—Procedures when ACI is the minor sponsor

When ACI is the minor sponsor of a joint committee, the balloting and operating procedures are determined by the major sponsor. All items approved by the joint committee are submitted to the Managing Director of Engineering for review by TAC.

PART 2—ACI STANDARDS

CHAPTER 4—DEVELOPMENT OF STANDARDS

4.1—Description

Standardization is the most rigorous consensus process used by ACI. It provides the widest input and highest overall quality assurance for a document. The ACI standardization process is approved by the American National Standards Institute (ANSI) and is given in 4.5. Documents that go through this process are identified as ACI standards; however, the word “Standard” does not appear in the title. The phrase “An ACI Standard” appears on the cover of the standard. ACI standards are written in mandatory language and can be referenced by model codes, by authorities having jurisdiction over local building codes, persons or agencies that provide specifications, or in legal documents such as Project Specifications.

4.1.1 Design standards

ACI design standards identified in this section are directed to the design professional, not the construction team.

Design standards must be worded in explicit, mandatory language so that there is only one possible interpretation. Design standards shall cite only mandatory-language documents. References to nonmandatory-language documents such as guides, reports, papers, and research results can be made in a separate commentary.

When submitting revisions to a design standard for review by TAC, the committee must provide reason statements for the revisions, including background information, and an explanation of the significance of the revisions.

4.1.1.1 Code requirements

An ACI code provides minimum requirements for concrete or masonry structures within its scope to safeguard public safety, health, and general welfare. ACI codes are written with the expectation that they will be adopted by a model building code or by a regulatory agency.

An ACI code shall not have the effect of requiring proprietary items or methods, and shall not state that its provisions shall govern when in conflict with a referencing code or body. Use the phrase “code requirements” in the title.

ACI committees can publish commentaries to complement their codes, which often provide supporting documentation for code provisions. A commentary is organized to parallel the code section numbering. Not all code sections require corresponding commentary sections, but all commentary sections require a corresponding code section.

A commentary is written in nonmandatory language and can reference documents that are written in nonmandatory language. Commentaries may offer alternatives for satisfying specific provisions in the codes, and may refer to patented items that can be used to meet the intent of a specific provision. Because they are written in nonmandatory language, commentaries cannot be referenced by codes. Refer to Chapter 5 for format and language of codes and commentaries.

4.1.1.2 Code cases

A code case clarifies an existing code or provides new provisions for situations not covered by an existing code and might result in a new code requirement, which will be included in the next code edition. Specific requirements in code language provide rules for additions or alternatives not covered by an existing code. Code cases ensure that such clarifications or provisions are given general distribution.

The Managing Director of Engineering considers code case requests and, if accepted, a processing fee is charged.

Individuals requesting a code case must do so in writing. The Managing Director of Engineering acts as a liaison between the individual and the appropriate committee and is responsible for submitting requests to the committee. The code case will be published in Concrete International within 6 months of the date of approval. Refer to 4.5.2.1 for approval process.

A code case applies only to the designated edition of a code (for example, ACI 318-14) and not to other editions.

4.1.1.3 Acceptance criteria

An acceptance criteria document is a subset of a code and is written in such a form that its requirements can be coordinated directly with a specific code (for example, ACI 318-14). Acceptance criteria follow the code requirements format.

4.1.1.4 Design specifications

A design specification provides minimum requirements for concrete or masonry structures within its scope to safeguard the public safety, health, and general welfare. It is available for reference in legal documents other than building codes, such as federal government contracts. Design specifications follow the code requirements format.

4.1.2 Construction standards

ACI construction standards are written to direct the producers, testing agencies, and construction team and not the design professional. Construction standards are worded in explicit, mandatory language so that there is only one possible interpretation.

4.1.2.1 Construction specifications

Construction specifications are reference specifications that can be included as part of a contract between an Owner and a Contractor. Refer to Chapter 6 for format and language of specifications.

Titles of construction specifications should indicate that they pertain to construction.

4.1.2.2 Material specifications

Material specifications are reference specifications that prescribe requirements for materials used in projects, are written to the producer, are incorporated by reference in Contract Documents, and may be incorporated by reference into construction specifications or into Contract Documents.

ASTM committees have the general responsibility for developing material specifications for concrete-related products. In support of other ACI design or construction standards, and with TAC approval, ACI committees may develop material specifications. TAC and ACI staff will notify ASTM of this proposed activity and confirm that ASTM is not preparing a similar standard. Material specifications must be published as stand-alone documents and not as a section in a larger document.

The committee is to follow the document outline and format shown in the Form and Style of ASTM Standards (available at www.astm.org) for preparing a specification, but otherwise use ACI style (Part 4). After publication by ACI, if a material specification falls within the scope of an ASTM subcommittee, ACI staff sends the test method to the ASTM staff manager responsible for the committee that addresses that area of technology.

4.1.2.3 Test methods

Test methods prescribe means of testing for compliance of materials or construction methods that are proposed for or used in projects. They are written to the testing agency and may be incorporated by reference in material specifications, construction specifications, or Contract Documents. They are subject to the process rules as described for material specifications in 4.1.2.2.

Test methods are only to be developed when an ASTM standard test method has not been developed. The committee is to follow the document outline and format shown in the Form and Style of ASTM Standards (www.astm.org) for preparing a test method, but otherwise use ACI style. After publication, ACI staff sends the test method to the ASTM staff manager responsible for the committee that addresses that area of technology. ACI test methods must be withdrawn if ASTM subsequently develops a test method for the subject.

4.1.2.4 Inspection services specifications

Inspection services specifications are reference specifications written as part of a contract between an Owner and an inspection agency. There is no recommended format for this type of specification, but it should conform to ACI style.

4.1.2.5 Testing services specifications

Testing services specifications are reference specifications written as part of a contract between an Owner and a testing agency or between a Contractor and a testing agency.

4.2—Procedures

ACI standards are developed in a seven-step process:

(1) Preparation of a new document or revision of an existing document (4.2.1 and 4.2.2)

(2) Letter balloting of the draft document by the committee

(3) Submission of the committee-approved document for TAC review

(4) Revision of the document in response to TAC comments

(5) A 45-day public discussion period

(6) Submission of committee-approved responses to comments received during the public discussion period for TAC review

(7) Submission to Standards Board for final approval

It is not the intent of ACI to duplicate published work. Where satisfactory consensus standards exist for material specifications and test methods, such as those developed by ASTM International, those standards should be referenced in ACI documents.

4.2.1 New standard

Committees must obtain TAC approval before beginning work on a new ACI standard. The proposal, sent to the Managing Director of Engineering, should indicate why it is needed and include a preliminary outline. If a design standard is proposed, a list of ACI or other standards that are likely to reference the design standard must also be submitted. Proposed new standards will be reviewed by the appropriate TAC subcommittee (TAC Design Standards Committee or TAC Construction Standards Committee), which will then make a recommendation to TAC.

4.2.2 Revising existing standards

Committees are expected to revise, reapprove, or withdraw a standard within 8 years from its adoption date. When the Standards Board releases the standard for publication, it is officially adopted. TAC may remove those standards from the ACI Manual of Concrete Practice (MCP) that have not been reapproved or revised within 8 years of the adoption date. In the case of an ITG standard, the standard is removed from the MCP after 5 years.

If the committee does not revise, ballot reapproval, or ballot withdrawal (4.2.2.3) of a standard within the 8-year period, TAC may reapprove or withdraw it without committee action.

4.2.2.1 Reapproval

The committee may ballot to reapprove a standard because the information in an existing standard, while not new, is still valid. The first reapproval of a standard is for 5 years. The second and subsequent reapprovals (if any) are for 3 years. The committee is required to letter ballot the reapproval. The reapproval may include updating referenced standards and minor editorial improvements of notation, terminology, metrication, or other similar items. A reapproval must not include technical changes.

The committee must submit its recommendation for reapproval of the standard to TAC for approval. Include a letter ballot summary (3.5) and a statement that technological progress at this point does not require revision, or that the document is currently being revised but the revision is not complete. Include a summary of the updates to the document. Generally, TAC reviews only the committee’s ballot summary and the summary of updates. A reapproval does not change the year of adoption but the note “Reapproved” with the year of reapproval is added to the document number.

4.2.2.2 Revision

The committee should revise a standard when the information in the standard needs to be updated. The committee must letter ballot revisions according to Chapter 3 and submit the document to TAC for review. Upon adoption of a revised standard, the existing version is marked historical and no committee action is required. (A standard is designated historical when it has been superseded by a revision.) The revised standard’s number receives the new year of adoption.

Committees are to submit to TAC reason statements for revisions to ACI standards, including background information and explanations of the significance of the revisions.

4.2.2.3 Withdrawal

The committee should ballot for withdrawal of the standard when the committee determines that the information it contains is obsolete and should not be revised. A letter ballot of the committee is required. The recommendation for withdrawal should include a statement that, in the judgment of the committee, the standard is no longer useful or amenable to updating. The committee’s recommendation and related ballot summary must be submitted to the Managing Director of Engineering for review by TAC.

Upon TAC’s approval of the recommendation, the document is no longer included in the next edition of the ACI MCP. It may still be available for purchase from ACI as a historical standard.

4.2.3 Maintenance of the content of ITG standards

After an ITG standard is published, TAC will request an ACI committee to assume jurisdiction over the ITG standard. Related technical committee(s) may have been identified during formation of the ITG as described in 1.4.1.2.

The technical committee should:

(a) Review and revise the content of the ITG standard or incorporate the information into an existing committee standard

(b) Ballot the revised content of the ITG standard as soon as practicable because the ITG standard only has a 5-year life in the MCP

4.2.4 Committee editorial review

The committee’s editorial subcommittee or task group should edit a standard thoroughly before final committee letter ballot. When submitting the standard to TAC, the chair should state that the editorial subcommittee has completed its task.

The editorial subcommittee should review the standard for organization, sentence structure, grammar, redundancy, spelling, and typographical errors. Because many people contribute to a standard, it is essential that the subcommittee review the separate sections for consistency in style and format. Members of the editorial subcommittee need to be familiar with the format and style of ACI standards (Part 4).

4.2.5 Circulating draft standards

Mark drafts of ACI standards as “draft document, not for publication.” The chair may only circulate the draft to individuals outside the committee, TAC, and ACI staff to obtain expert technical advice not available in the committee or to ensure that all interested parties are given an opportunity to express viewpoints when developing an ACI standard.

Committee standards, at any stage of development, must not be released for publication other than to ACI or cosponsors of joint committees, except on approval of TAC. Similar restrictions apply to test data or unpublished technical information circulated in a committee.

Posting of draft standards on the committee’s ACI website is encouraged. Posting of draft documents on independent websites is not permitted.

4.2.6 Coordination of ACI standards

4.2.6.1 Industry standards

Table 4.2.6.1 lists committees that write the governing standards for a specific industry.

4.2.6.2 Interaction among standards-writing committees

ACI committees listed in Table 4.2.6.1 develop standards that are specific to an industry. ACI does not want to create standards with overlapping scopes; therefore, TAC limits the number of ACI design standards and construction standards to one for each industry for new and existing construction. For example, in the commercial building industry, ACI 318 is the design standard, ACI 301 is the construction standard, ACI 562 is the repair design standard, and ACI 563 is the repair construction standard. ACI committees whose topics are intended to address specific industry segments cannot write standards that would overlap existing ACI industry standards. As an example, ACI Committee 362 may not develop a design standard for parking structures because this application is covered by ACI 318 and ACI 301. A technical committee is free to create a standard within its mission if within its scope section there is a statement that prevents it from being used in conjunction with an ACI industry standard that covers the same scope. Project specifications should not reference two ACI standards on the same topic that may have differing information. For example, hot weather concreting is a topic that affects all industries; therefore, ACI Committee 305, Hot Weather Concreting, may write a construction specification on this topic. Further directions on the interaction of specifications and avoiding conflicts in Contract Documents are given in Chapter 6.

4.2.6.3 Proposed changes from outside of committee

Committees are permitted to propose changes to the ACI standards in Table 4.2.6.1, such as ACI 318. The proposed change has to be approved by the submitting committee in accordance with balloting procedures of Chapter 3. The communication should include the proposed change in strikeout/underline, reason for change, and technical background. The committee receiving the proposed change is expected to consider the change in a timely fashion and notify the submitting committee of the results.

4.2.6.4 Coordination among technical committees

Coordination with other technical committees is an important part of developing standards. Some reasons for coordination with other committees are:

(a) To incorporate or reference information from another committee standard

(b) To minimize instances of standards with parallel or overlapping scopes

(c) To minimize technical conflicts between committee standards

If there are substantial technical conflicts between the standards of two technical committees, the matter can be referred to TAC. It is acknowledged that standards submitted for TAC review may be in conflict with or vary from published ACI documents. If committees are aware of such conflicts, the submitted standard should substantiate identified conflicts.

4.2.6.5 Standards sponsored with other ACI technical committees

ACI committees may agree to cosponsor a standard when the scope of the standard overlaps their missions. Committees may request to jointly sponsor a standard when at least 75 percent of voting members from each affected committee vote in favor of the proposed arrangement. The chairs must forward the comments of negative voters to TAC. In such arrangements, one committee is the major sponsor and the others are minor sponsors.

The major sponsor committee is responsible to draft and ballot the standard. Members from the minor sponsor committees may assist in the development of the draft. The minor sponsor committees will ballot the final draft of the standard. At least 50 percent of voting members from the minor sponsor committees must vote in favor of the draft standard before it is submitted to TAC. The chair must forward the comments of negative voters from the minor sponsor to TAC, but the negative votes do not have to be resolved.

The standard designation includes all sponsoring committees. The standard’s roster includes only members of the major sponsor committee.

4.2.6.6 Coordination with the Construction Liaison Committee

Part of the ACI Board of Direction’s Construction Liaison Committee (CLC) mission is to review technical committee standards that deal with constructibility and economy. As part of the TAC review process, staff sends standards that contain sections on construction to theCLC for review.

4.2.6.7 Coordination with TCSC and TDSC

The TAC Construction Standards Committee (TCSC) and TAC Design Standards Committee (TDSC) assist committees in preparing construction standards and design standards. As part of the TAC review process, staff sends construction standards to TCSC for review and design standards to TDSC for review. These two subcommittees review draft standards for conformance to ACI format, style, and clarity of expression.

4.2.6.8 Coordination of terminology

Concrete-related terms are defined within “ACI Concrete Terminology” (CT) to increase understanding of ACI standards and promote consistent use of terminology in ACI standards. The CT is a standardized document.

Technical committees define terms in their standards, and are to ensure consistent usage within both the technical committee and ACI. The CT is available on the ACI website. Individuals may submit proposed CT changes to TAC. The CT is updated on a yearly basis.

TAC reviews each standard’s definitions at the time of submission for TAC review (10.2.2.1).

4.2.7 Translation of ACI standards

Upon TAC approval, translation of an ACI standard into a language other than English may be permitted and is considered an editorial change and no further balloting by the committee is required. In some cases, especially for ACI standards, it may be required to establish a task group or subcommittee to validate and approve the translation. For example, Subcommittee 318-S is responsible for the Spanish translation of ACI 318. The translated standard must be published with the translation disclaimer (14.2.5).

4.2.8 Patented items

ACI technical committee standards cannot and do not endorse or promote patented products or proprietary technology of any kind. ACI standards shall not refer directly to a particular patent or proprietary technology by use of trademarks or trade names. If a standard’s requirement can only be satisfied practicably by use of a patented material, product, process, procedure, or apparatus, full and apparent disclosure of the controlling patent shall be made within the commentary of the design standard or the optional requirements checklist of the specification.

ACI standards shall not mandate the use of patented items, but they may allow patented technology as a possible solution. During the balloting of such a requirement, the committee will be informed on the ballot that the ballot item includes references to patented technology. If a member believes that a committee standard under ballot would require the user of the resulting standard to violate the intellectual property rights (such a patents or copyrights), that member is expected to alert the committee. If the committee includes information on patented items within a standard, include the disclaimer statement in 14.2.7.

4.2.9 Errata

Errata are posted on the ACI website. When potential errors are discovered in an ACI standard, the committee chair has the authority to decide if a correction needs to be made and provides staff with the correction. The chair is not required to ballot the committee.

4.3—Writing standards

4.3.1 Format

Refer to Chapter 5 for format of codes. Refer to Chapter 6 for format of specifications.

4.3.2 Units

In accordance with ACI Board Policy (14.3), standards shall be published in two versions, one with in.-lb units and one with SI units.

This policy may be waived by TAC in exceptional circumstances. TAC approval to waive the requirements for two versions is required before submitting the standard to TAC. The application must describe the circumstances supporting a publication of one document with dual units.

The committee may prepare and ballot the second version or they may request that staff prepare the second version when it is considered an editorial conversion. If a committee considers a unit conversion editorial, no further balloting by the committee is required to approve the unit conversion. The chair can either decide if the conversion is editorial or initiate an administrative ballot. ACI standards are published with the unit conversion disclaimer (14.2.6).

For additional information on units, refer to Chapter 11.

4.3.3 Notation

Refer to Chapter 10 for information on notation.

4.3.4 Style

Refer to Chapter 9 for information on style.

4.4—TAC review

4.4.1 Submission package

Submit all materials required for submitting standards for TAC review to the Managing Director of Engineering at least 3 months before a TAC meeting; standards will be given first priority. Submitting the standard by the deadline does not guarantee placement in the next TAC standard review cycle. Submit the Standard Submittal Checklist with the standard. The checklist can be found on the ACI website. TAC typically selects the standards for review in the order received. With the submittal, the chair shall include:

(a) An electronic copy of the standard in Microsoft Word

(b) Original grayscale artwork

(c) Statement of the type of standard (4.1) being submitted

(d) A ballot summary of the final letter ballot(s) (3.5), including resolutions to all negatives

(e) A summary of revisions to the existing standard in the case of a revision

(f) A statement of balance of interest (1.8)

The committee is encouraged to provide a list of at least three potential external reviewers for the standard.

Standards prepared by joint committees may be subject to the review procedures of the sponsoring organizations. Discuss required submissions to such organizations with the Managing Director of Engineering for coordination.

4.4.2 Staff editorial review

TAC has directed staff to perform an editorial review of each standard that is submitted for TAC review. Staff reviews the standard for grammatical errors, misspelled words, and ambiguous statements, and checks the standard for compliance with ACI style. All staff-recommended editorial changes are sent to the chair for approval. Once the chair and staff have agreed upon editorial items, staff submits the edited standard to TAC for review.

4.4.3 TAC review

One of the most important functions of TAC is the review of technical committee standards. TAC reviews standards for:

(a) Technical content and correctness

(b) Potential conflicts, duplications, and overlaps with other ACI standards

(c) Compliance with ACI formats

(d) Clarity

(e) Mandatory language

The submitted standard is sent to all TAC members and to selected external reviewers who are experts on the subject matter and who are not members of the committee submitting the standard. ACI staff also forwards the standard to technical committees that have standards, guides, or reports that may cover the subject matter in the standard to help identify conflicts, duplications, and overlaps between committee standards. Reviewers are given 4 weeks to review the standard and submit comments.

TAC will review the entire standard, even if only one section has been revised.

4.4.3.1 TAC review group

Each standard is assigned to a TAC review group (RG) that is composed of a TAC member as review chief, two other TAC members as primary reviewers, and a staff liaison. All comments received from TAC members, external reviewers, TDSC, TCSC, CLC, staff, and chairs of coordinating committees are compiled as TAC review comments and distributed to the RG by the review chief.

The TAC RG reviews all comments and meets with a committee representative, usually the chair, to discuss the TAC review comments. The review chief leads the discussion on TAC’s behalf.

4.4.3.2 Review comment classifications

Reviewers classify each of their comments as primary (P), editorial (E), or secondary (S) and also provide specific page and line number references for each comment, or label them as “Page 0” and “Line 0” for general (G) comments that apply to the entire standard.

Primary (P) comments identify technical issues that the committee must address before publication of the standard.

Editorial (E) comments identify editorial issues that the committee must address before publication of the standard. The committee is expected to implement all E comments unless the committee agrees that the change is not an improvement or that it would change the intended meaning.

Secondary (S) comments identify technical or editorial issues that should be addressed either in this standard or the next revision of the standard.

General (G) comments identify issues general to the entire standard that the committee must address before publication of the standard.

4.4.4 TAC decision

After the RG meets with the committee representative, the RG makes a recommendation to TAC regarding the standard. TAC considers the recommendation and makes one of two decision on the standard:

1. Draft standard is approved for further processing, contingent upon satisfactory response to TAC review comments in a timely manner and Standards Board approval.

2. Draft standard is not approved for further processing, and it is returned to the committee for revision, reballoting, and resubmission (commonly called 3R).

The committee is notified of TAC’s decision, and the official TAC review comments are sent to the committee for consideration.

4.4.4.1 Standard approved

When the standard is approved, the committee should act promptly to prepare a response to each TAC review comment.

4.4.4.2 Responding to TAC comments

The committee must document its response to each TAC review comment. The committee can agree with a P, E, or G comment and make an appropriate change to the standard or disagree with reason. When the committee disagrees, a reason statement for the disagreement must be documented.

The committee can agree with an S comment and make a change to the standard, disagree (no documentation is required), or agree to take the issue up as new business.

Responses to TAC comments must be approved by the committee by either letter ballot or meeting ballot, regardless of whether or not the response resulted in a change to the standard. Include in the ballot the standard with the proposed changes resulting from the proposed responses to TAC comments (usually in strikeout/underline).

If a comment is strictly editorial and appropriate, the chair has the authority to implement the editorial change, and ballot by the committee is not required. If a voting member believes that the comment is not strictly editorial, or if there is doubt, the committee must ballot the proposed change.

After the standard has been revised in response to TAC review comments, the following shall be submitted to the Managing Director of Engineering:

(a) The revised standard in Microsoft Word® format showing the changes to the version approved by TAC using the strikeout/underline feature

(b) All original or revised artwork

(c) The comment form including the committee responses to the TAC review comments

(d) A ballot summary on the responses to TAC review comments, including any related committee minutes and negative withdrawals

When compliance with TAC review comments is verified, staff proceeds with preparing the standard for public comment.

If a committee decides to abandon a standard after TAC approval has been received, the committee is required to letter ballot this decision. The balloting summary of the decision to abandon the standard must be submitted to ACI staff. This ballot is considered an administrative ballot and the negatives do not need to be resolved.

Technical committees must respond to TAC review comments within 2 years of the review, otherwise the TAC approval is withdrawn. In such cases, the committee must resubmit the standard for TAC review and respond to a new set of TAC review comments. In exceptional cases, TAC may extend the time frame for acceptance of the committee responses upon written request from the committee chair with detailed explanation of the reasons.

4.4.4.3 Standard not approved

If the standard is not approved by TAC, the committee is usually expected to revise, reballot, and resubmit (commonly called 3R) the standard to TAC. The decision not to approve is usually the result of major technical deficiencies in the standard. Therefore, TAC expects a comprehensive effort by the committee before the standard is resubmitted.

When a standard is not approved, the TAC RG will indicate what they believe is necessary to revise the standard. Although TAC expects the committee to address issues raised during the TAC review when revising the standard, the committee is not expected to respond individually to each review comment.

4.5—Public discussion process

4.5.1 Release for public discussion

When TAC approves a proposed standard, the balloting history shall be given procedural review by the ACI Standards Board. Upon review of the standard’s balloting history, the Standards Board either approves opening the proposed standard for public discussion or returns the proposed standard to TAC with comments.

4.5.2 Public discussion

Proposed standards, other than code cases, approved by the Standards Board are made available for a 45-day public discussion and comment period. Upon TAC recommendation, the proposed standard, or its revision, is published for public discussion in an ACI periodical, on the ACI website, or both.

When the proposed standard is to be published for public discussion on the ACI website, an email that provides instructions on how to access the standard on the ACI website and how to submit comments is sent to all ACI members. A notice of availability for review is also published in Concrete International. The public discussions will begin no more than 30 days before the Concrete International issue in which a notice of availability is published. In addition, each issue of Concrete International includes a Public Notice page with a summary of standards open for public discussion.

4.5.2.1 Code case

A code case is adopted upon Standards Board approval and published in Concrete International with a number for each code case and the adoption date. A code case can lead to a change in the next edition of the code. With this action, the code case is completed.

4.5.2.2 Provisional standard

Upon TAC recommendation and Standards Board approval, a proposed standard may be published as an ACI provisional standard before or during the public discussion period. TAC establishes an expiration date for the provisional standard and such a standard shall not be reapproved. A provisional standard may be referenced by other standards. Once public discussion is completed, the term provisional is removed from the title of the standard.

4.5.3 Committee closure

The technical committee must prepare and ballot a response to all comments received by the Institute during the public discussion period. While the Institute and the committee welcome all comments, those that pertain to provisions that have not been changed in the current revision are usually considered as new business for the next revision. In this case, an acknowledgment, a short explanation, and proposed committee actions under new business is usually an appropriate closure response.

After the closure is prepared, it must be approved by the committee by either letter ballot or meeting ballot. The committee-approved closure is submitted to the Managing Director of Engineering for review and approval by TAC. Upon TAC approval, the closure balloting results are forwarded to the Standards Board. Otherwise, the closure is returned to the technical committee with comments.

4.5.4 Release for publication

Balloting of the closure wi be given procedural review by the ACI Standards Board. Upon Standards Board agreement that ACI’s procedures have been followed, the Standards Board releases the discussion and closure for publication in an ACI periodical, on the ACI website, or both, and recommends publishing the standard as an ACI standard. Otherwise, the Standards Board returns the balloting of the closure to TAC with comments. Upon publication of the closure and any approved revisions, the standard is complete.

4.5.5 Adoption as an ACI standard

When the Standards Board releases the standard for publication, it is officially adopted.

4.5.6 Approval as an American National Standard

Upon committee request and subsequent TAC approval, a proposed ACI standard may be submitted to the American National Standards Institute (ANSI). Upon successful ANSI processing, the ACI standard is adopted as an American National Standard.

4.6—Appeal process

Published committee standards or standards in the standardization process may be appealed by ACI members. Appeals of standards in process may be made on technical or procedural grounds. Appeals of published standards may be made only on technical grounds. Because appeals are normally heard at ACI conventions, all appeals must be submitted in writing to the Managing Director of Engineering at least 6 weeks before the convention for inclusion on the agenda of the hearing committee (TAC and Standards Board).

4.6.1 Standards under development

A voting committee member has the right to appeal a TAC or Standards Board decision on a committee standard under development by the appellant’s committee. The appellant must submit an appeal package to the Managing Director of Engineering. The main elements of an appeal are the appellant, standard under appeal, basis of appeal (technical or procedural), reason statement, and supporting documentation. If an appeal is upheld, the standard shall not be processed further in the standardization, and is returned to the committee with comments for possible revision and resubmittal.

4.6.2 Published standards

A current member of the Institute has the right to appeal technical provisions of a standard. The appellant must submit an appeal package as described in 4.6.1 to the Managing Director of Engineering. If a technical appeal is upheld, the originating committee shall ballot a revision to address the use raised by the appeal within the time limit established by TAC or the standard will be withdrawn by TAC.

4.6.3 Technical grounds

TAC is the Institute’s final authority on all technical matters. If an appeal on technical grounds is made, an item is placed on the agenda for the next scheduled TAC meeting and those interested are invited to attend the meeting.

4.6.4 Procedural grounds

The Standards Board is the Institute’s final authority on procedural matters pertaining to ACI standards. If an appeal on technical grounds is made, an item is placed on the agenda for the next scheduled Standards Board meeting and those interested are invited to attend the meeting.

CHAPTER 5—FORMAT AND LANGUAGE FOR CODES

5.1—General

Code requirements are written to the licensed design professional. They are not written to direct other members of the design and construction team, such as a Contractor or inspector.

A code provision should provide a single requirement.

Code provisions can include equations, lists, tables, or figures.

ACI codes may have attached nonmandatory text, called commentary (denoted with an “R” before the provision number), which is not considered part of the code.

5.2—Organization

5.2.1 Front matter

The organization of front matter of ACI codes is:

(a) Title—The title of the code should appear prominently on the first page, and it should read “Code Requirements for … and Commentary”

(b) Roster—All voting members (on the main committee and subcommittees) and consulting members at the time of the opening date of a document’s last letter ballot before submission for TAC review, are listed on the roster published on the front page of the committee document. Associate members are not listed. When a committee reapproves a code, the committee roster published with the original code is retained, and the roster of the current committee is not shown.

The chair may list other individuals who contributed to the document and should receive recognition.

Place an appropriate note immediately below the roster. The acknowledgement should not list specific contributions. An example of an appropriate note is: “Special acknowledgements to {list of individuals} for their contributions to this Code.”

(c) Synopsis—A one- or two-paragraph synopsis should state the code’s scope and purpose, and should inform without going into too much detail. Each synopsis is printed in Concrete International, and should therefore make sense when read independently of the code.

(d) Keywords—Keywords indicate significant topics covered by the code. The title, synopsis, and table of contents of the document are good sources for keywords. List up to 20 keywords. The keywords should reflect the code’s subject matter without being too general. For example, avoid listing “concrete” or “water-cement ratio.” List keywords in alphabetical order and separate them with semicolons. Do not use multiple forms of the same word as keywords.

(e) Table of contents—A table of contents includes titles of chapters and articles only. Do not include page numbers in the table of contents; page numbers are assigned by staff after final formatting of the document.

(f) Preface—A preface is a brief summary of the subject, scope, and purpose of the code. It may contain a general identification of important code changes.

5.2.2 Code chapters

The first three chapters in codes are:

Chapter 1—General

Chapter 2—Notation and definitions

Chapter 3—Referenced standards

The code’s remaining chapters provide requirements in the general order of design, construction, and inspection. Design chapters can include loads, analysis, structural systems, and member design and detailing. Construction chapters can include limits on materials, material properties, and formwork. Inspection chapters can include quality assurance and quality control requirements. Because ACI codes are directed to the design professional, code construction and inspection chapters instruct the design professional to include requirements in contract documents.

The following is a description of information to be included in Chapters 1, 2, 3, and a member chapter.

CHAPTER 1

GENERAL

Chapter 1 includes the items in the following list. ACI codes should only address construction issues as they relate to the code’s design assumptions. Where required, ACI codes can direct the design professional to include pertinent construction information in the contract document.

The adopting authority jurisdiction over an ACI code needs to be clarified to avoid confusion.

1.1 General

1.2 Scope

1.3 Purpose

1.4 Applicability

1.5 Interpretation

1.5.1 The official version of this standard is the English language version using inch-pound units published by the American Concrete Institute.

1.5.2 In case of conflict between the official version of the code and other versions of the code, the official version governs.

1.6 Construction documents

1.7 Testing and inspection

1.8 Language and units of measurement

NOTE: Use the language in 1.5.1 and 1.5.2 in all codes.

CHAPTER 2

NOTATION AND DEFINITIONS

2.1 Code notation

The terms in this list are used in the code and as needed in the commentary.

R2.1 Commentary notation

The terms in this list are used in the commentary, but not in the code.

Units of measurement are given in the Notation to assist the user and are not intended to preclude the use of other correctly applied units for the same symbol, such as feet or kip.

2.2 Code definitions

The following terms are defined for general use in this code. Specialized definitions appear in individual chapters.

R2.2 Commentary definitions

For consistent application of the code, it is necessary that terms be defined where they have particular meanings in the code. The definitions given are for use in application of this code only and do not always correspond to ordinary usage. A glossary of most-used terms relating to cement manufacturing, concrete design and construction, and research in concrete is contained in “ACI Concrete Terminology” available on the ACI website.

CHAPTER 3

REFERENCED STANDARDS

Codes can only reference mandatory language standards, or parts thereof.

Referenced standards should be developed by an open consensus process.

Avoid referencing standards that reference technical information presented in previous versions of the same code. Satisfying such references creates technical inconsistencies and conflicts with the current code.

Organize referenced standards according to the sponsoring group.

List sponsoring groups in alphabetical order.

CHAPTER X

MEMBER CHAPTER

A member chapter contains all the information, directly or by reference, required to design and detail the member. Below is a sample outline.

CHAPTER X

X.1 Article

X.1.2 Section

X.1.2.3 Sub-section

X.1.2.3.4 Paragraph

X.1.2.3.4(a) Sub-paragraph

5.2.3 Back matter

The back matter in codes may include appendixes and an index.

Appendixes are informational only and should not contain technical requirements.

An index may be created at the end of code development. Index terms are selected from definitions, chapter headings, section headings, and subsection headings.

5.2.4 Article titles

Article titles can be a single word or a short phrase with the first word capitalized. Use lower case for subsequent words.

5.2.5 Section and subsection titles

Titles can be a single word or a short phrase. Capitalize the first word and use lower case for subsequent words. All articles have a title, for example 1.1—General. Only sections that have subsections should have a title, for example, 1.1—General, 1.2.1 Materials. When multiple sections share a common subject, the common subject is followed by a colon, then by the specific aspect of that subject.

5.2.6 Provision numbering

Limit provisions to a maximum number of five levels, but four levels are preferred.

5.3—Language

5.3.1 Verb usage

1. Codes use only mandatory verbs

2. To direct or permit an action, “shall be” is normally used

3. To define a condition in present tense, “is” and “are” are normally used

4. Permissive verbs, such as “may” or “should” are never used in the code but can be used in the commentary

5.3.2 Adjectives and adverbs

Use adjectives or adverbs to achieve precision; they should not be ambiguous. Don’t use shortened or jargon terms.

When referring to the material, use “reinforcing steel” or simply “reinforcement.”

The adjective “special” is reserved for seismic applications, inspectors, and post-tensioned anchorage devices defined in AASHTO.

The adjective “structural” is unnecessary when describing members or concrete. Use the adjective “nonstructural” where appropriate.

Use the adjectives “compressive,” “tensile,” and “torsional” to describe force and stress. Do not use the nouns “compression” and “torsion” as adjectives.

Don’t use unenforceable adjectives or adverbs.

5.3.3 Gender-specific language

Avoid using gender-specific terms, such as “he,” “she,” “man,” or “woman” when possible. Such terms can often be replaced by “operator” or “person.”

5.3.4 Conditional phrases

Conditional phrases “if,” “when,” and “where,” are used in provisions where the action depends on whether a stated condition is satisfied. When so used, these words have the following meanings:

If—on condition that; in case that

When—at the time that; in the event that

Where—in whatever place

These definitions have subtle differences. For consistency, use “when” for cases that refer to time, use “where” for cases that refer to position or situation, and use “if” for all other cases.

5.3.5 Comparative phrases

There are many code provisions where a result must fall within certain limits.

Case I. Permitted value depends on the greatest or least of a list of values

Case II. Permitted value must fall within a range

Case III. Permitted value equals the greatest or least of value in a list.

5.3.6 Preferred words or phrases

Don’t use “a and/or b;” use “a, b, or both.”

Don’t use “either...or.” Although “either...or” is used in other contexts, “either” is not usually required within a code. The exception is when a sentence begins with “either.”

Don’t use “neither” or “nor.”

Preferred | Avoid
axial load (to describe an externally applied load) | axial force
axial force (to describe an internal member force) | axial load
calculate | compute
corbel | bracket for a wall or column
continuous (to describe a condition that exists over two or more adjacent members) | full length
full length (to describe the full extent of a single member) | continuous
shear force (to describe a shear action) | shear
shear (to describe a force value) | shear force
twice | double
flexural moment | bending moment
torsion | torque
directly (to describe relative position) | immediately

5.4—References

5.4.1 References to provisions and chapters

The entire code must be satisfied, so reminder references to related provisions are unnecessary. The commentary can be used to alert the user to related provisions.

If a code has member chapters, provisions in member chapters can reference provisions in other non-member chapters; however, provisions of other member or non-member chapters should not reference provisions of member chapters.

If cross referencing is necessary, check the cross references to ensure there is no circular logic path.

5.4.2 Compliance phrases

Use “conform to” instead of “satisfy” or “in accordance with” for compliance with material requirements.

Use “in accordance with” instead of “satisfy” or “conform to” for design actions.

Use “in accordance with” instead of “shall provide” for design selections.

Use “in accordance with” instead of “shall provide” for design selections.

5.4.3 Referenced standard style

A reference to a standard within a provision should include only its serial designation and not its title or date. Standards that are written in mandatory language and referenced in the code are considered referenced standards.

Include the date and title of the referenced standard in Chapter 3.

The latest version of the referenced standard is the preferred reference.

If a code includes exceptions to a referenced standard or a historical version of the standard is referenced, provide an explanation in the commentary. Consider asking the sponsoring group to revise the standard so that exceptions or reference to a historical standard are not needed.

5.5—Commentary to a code

5.5.1 General

A code must be understandable and usable without the need for a commentary. The commentary text, tables, figures, or illustrations must not interpret a code in a way that conflicts with the code text, or create ambiguity in the code. Commentary is denoted with an “R” designation before the provision number, including equations and figures.

Commentary may provide:

(a) Basis for a code provision including pertinent references

(b) Cross reference to related material in other standards or in other code sections

(c) References to address situations outside the stated limits of a provision

(d) Discussion highlighting new code provisions (remove this type of commentary in subsequent code versions)

(e) Explanation of how a provision may be used or refer to another section

Commentary should not:

(a) Repeat the code provision

(b) Provide general design education

(c) Provide design aids or examples

Commentary must not:

(a) Provide exceptions to the code provision

(b) Contain additional code requirements

(c) Use mandatory language, except to paraphrase or explain a code provision

Example

Use: Concrete for members subject to freezing-and-thawing exposures is to be air entrained in accordance with 5.3.3.

Instead of: Concrete for members subject to freezing-and-thawing exposures should be air entrained in accordance with 5.3.3.

5.5.2 Commentary references

A reference must be:

(a) Explicitly relevant

(b) In English

(c) Peer reviewed

A reference must not be:

(a) A company report or personal communication

(b) A laboratory report

(c) An unpublished proceeding

5.5.3 Cited reference style

Use author/date format for publications cited in the commentary.

In citing publications by author/date within parentheses in the text, do not place a comma between the author’s name and the year of publication.

CHAPTER 6—FORMAT AND LANGUAGE FOR CONSTRUCTION SPECIFICATIONS

6.1—General

ACI construction specifications are written to the Contractor and are intended to be referenced in Contract Documents. Construction specifications follow the single-item or multi-item format listed in 6.2. Follow the document outline shown in the Form and Style of ASTM Standards (available at www.astm.org) for preparing a material specification (4.1.2.2) or test method (4.1.2.3).

ACI specifications do not include commentaries. The attached Notes to Specifiers are written to specifiers in nonmandatory language and are not a part of the specification.

Single-item specifications address a single product or process, and are analogous to a Construction Specifications Institute’s (CSI) narrow scope specification.

Multiple-item specifications address more than one technical product or process, and are similar to a CSI’s broad scope specification.

The Notes to Specifiers usually include a list of cited references, a Mandatory Requirements Checklist, and an Optional Requirements Checklist.

The Mandatory Requirements Checklist identifies provisions that do not have a default requirement and specific requirements must be provided in the Contract Documents.

The Optional Requirements Checklist identifies some default requirements the specifier may want to change through the Contract Documents.

Reference to other ACI specifications in an ACI specification is allowed for specialty items, such as tolerances (ACI 117).

6.2—Format

6.2.1 Single-item specifications

ACI Construction specifications are written in the three-part section format of the Construction Specifications Institute (CSI). Part 1 covers general administrative requirements such as as definitions, submittals, referenced standards, and acceptance criteria; Part 2 addresses products and materials; and Part 3 deals with execution. The specification is followed by Notes to Specifiers and the Checklists, which are directed to the specifier and are not part of the specification. Below is an example of an outline for a single-item specification.

Outline for single-item specification

EXAMPLE

Title page—Title, roster, synopsis, keywords, and table of contents

Part 1—General

1.1—Scope

1.2—Interpretation

1.3—Definitions

1.4—Referenced standards

1.5—Submittals

1.6—Delivery, storage, and handling

1.7—Quality assurance and quality control acceptance of work

Part 2—Products

2.1—Materials

2.2—Accessories

2.3—Off-site fabrication

Part 3—Execution

3.1—Preparation

3.2—Transportation

3.3—Installation

3.4—Testing

3.5—Repair

3.6—Cleaning

Notes to Specifier

General Notes

Foreword to Checklists

Checklist references

Mandatory requirements checklist

Optional requirements checklist

Appendixes (if applicable)

6.2.2 Numbering within single-item specifications

Provisions in the specification are numbered sequentially.

6.2.3 Multi-item specifications

Below is the outline for a multi-item ACI specification. The first section provides general requirements and is followed by sections that address each technical subject within the scope of the specification. Each technical section includes three parts: General, Products, and Execution.

Outline for multi-item specification

EXAMPLE

Title page—Title, roster, synopsis, keywords, and table of contents

Section 1—GENERAL REQUIREMENTS

1.1—Scope

1.2—Interpretation

1.3—Definitions

1.4—Referenced standards

1.5—Submittals

1.6—Quality control

Section 2—(First item technical section)

Part 2.1—GENERAL

2.1.1—Description

2.1.2—Storage and handling

2.1.3—Testing and inspection

Part 2.2—PRODUCTS

2.2.1—Materials

2.2.2—Accessories

2.2.3—Off-site fabrication

Part 2.3—EXECUTION

2.3.1—Preparation

2.3.2—Transportation

2.3.3—Installation

2.3.4—Testing

2.3.5—Repair

2.3.6—Cleaning

Section 3—(Second item technical section)

Part 3.1—GENERAL

Part 3.2—PRODUCTS

Part 3.3—EXECUTION

Section 4 and beyond as needed

Notes to Specifiers

General Notes

Foreword to Checklists

Checklist references

Notes to Specifiers

Mandatory requirements checklist

Optional requirements checklist

Appendixes (if applicable)

6.2.4 Numbering within multi-item specifications

Provisions in the Specification are numbered sequentially.

6.2.5 Description of title page

(a) Title—The specification title appears on the first page of the draft document includes the word “specification for,” and indicates the subject matter.

(b) Roster—All voting members (on the main committee and subcommittees) and consulting members at the time of the opening date of a document’s last letter ballot before submission for TAC review are listed on the roster published on the front page of the specification. Associate members of the committee are not listed on the roster. When a committee reapproves a specification, the committee roster published with the original specification is retained, and the roster of the current committee is not shown.

The chair may list other individuals who contributed to the document and should receive recognition.

Place an appropriate note immediately below the roster. The acknowledgement should not list specific contributions. An example of an appropriate note is “Special acknowledgements to [list of individuals] for their contributions to this specification.”

(c) Synopsis—A one- or two-paragraph synopsis should state the specification’s scope and purpose, and should inform without going into too much detail. Each synopsis is printed in Concrete International, and should therefore make sense when read independently of the specification.

(d) Keywords—Keywords indicate significant topics covered by the specification. The title, synopsis, and table of contents of the document are good sources for keywords. List up to 20 keywords. The keywords should reflect the specification’s subject matter without being too general. For example, avoid listing “concrete.” List keywords in alphabetical order and separate them with semicolons. Do not use multiple forms of the same word as keywords.

(e) Table of contents—The table of contents includes (if applicable) part and article-level titles. Do not include page numbers in the table of contents; page numbers are assigned by staff after final formatting of the document.

6.2.6 Description of Part I, General

6.2.6.1 Scope

The scope provides a short statement that describes the specification’s application. A single-item specification whose content overlaps the scope of ACI 301, ACI 350.5, or ACI 530.1 may be referenced in Contract Documents that refer to these general specifications. In such cases, the Contract Documents should state clearly that the requirements of the single-item specification govern with respect to the topic covered by the single-item specification. The specification should clarify its relationship to the Contract Documents and referenced standards. The following example is the preferred wording.

EXAMPLE

1.1—Scope

1.1.1 This specification covers...

1.1.2 This specification supplements the Contract Documents and provides requirements for the Contractor.

1.1.3 This specification governs for construction within its scope, except the Contract Documents govern if there is a conflict.

1.1.4 This specification governs if there is a conflict with referenced material and testing standards.

1.1.5 The Contractor is permitted to submit written alternatives to any provision in this specification.

1.1.6 Do not use this specification in conjunction with ACI 301, ACI 350.5. or ACI 530.11 unless Contract Documents state that this specification governs for Work covered by 1.1.1.

1.1.7 Ignore provisions of this specification that are not applicable to the Work.

1.1.8 Values in this specification are stated in inch-pound units. A companion specification in SI units is also available.

1.1.9 The Notes to Specifiers are not part of this specification.

6.2.6.2 Interpretation

The interpretation provides the rules for interpretation of terms and explains key phrases and words. All specifications shall have an interpretation section that follows the scope. The following example is the prefererred wording.

EXAMPLE

1.2—Interpretation

1.2.1 Unless otherwise explicitly stated, this specification shall be interpreted using the following principles.

1.2.1.1 Interpret this specification consistent with the plain meaning of the words and terms used.

1.2.1.2 Definitions provided in this specification govern over the definitions of the same or similar words or terms found elsewhere.

1.2.1.3 Whenever possible, interpret this specification so that its provisions are in harmony and do not conflict.

1.2.1.4 Headings are part of this specification and are intended to identify the scope of the provisions or sections that follow. If there is a difference in meaning or implication between the text of a provision and a heading, the meaning of the text governs.

1.2.1.5 Footnotes are part of this specification. The meaning of the provision text governs in the event of a difference in meaning or implication between the provision text and a footnote to that provision.

1.2.1.6 Where a provision of this specification involves two or more items, conditions, requirements, or events connected by the conjunctions “and” or “or,” interpret the conjunction as follows:

“and” indicate that all of the connected items, conditions, requirements, or events apply

“or” indicates that the connected items, conditions, requirements, or events apply singularly

1.2.1.7 The use of the verbs “may” or “will” indicates that the specification provision is for in-formation to the Contractor.

1.2.1.8 The phrase “as indicated in the Contract Documents” means the specifier included the provision requirements in the Contract Documents.

1.2.1.9 The phrase “unless otherwise specified” means the specifier may have included an al-ternative to the default requirement in the Contract Documents.

6.2.6.3 Definitions

The following terms are unique to specifications and shall be included without modifications, if used, in the specification. Words capitalized in the definitions below should be capitalized throughout the specification. The introduction of the definitions references “ACI Concrete Terminology” (CT) for definitions. Do not repeat terms from the CT unless the definitions must be altered for the purposes of the specification. Terms not in the CT but important to the specification should also be listed. Write definitions in accordance with Chapter 10.

6.2.6.4 Referenced standards

Refer to 6.4.

6.2.6.5 Personnel certification programs

Reference only those personnel certification programs that are available.

6.2.6.6 Plant certification programs

Reference only plant certification programs that are widely available.

6.2.6.7 Submittals

List submittals to be furnished by Contractor, such as product data, shop drawings, samples, quality-control data, design data, and test reports. This list must be coordinated with provisions that require submittals. Administrative requirements, such as distribution and schedules for submittals, are given in other parts of the Contract Documents.

6.2.6.8 Delivery, storage, and handling

Specify requirements for packaging and shipping, acceptance at the site, and storage and protection. Allowances and unit prices are not included. Unless more restrictive requirements are intended, do not repeat packaging or other requirements that are included in referenced specifications for materials or products.

6.2.6.9 Quality assurance and control

Define qualifications for testing agencies and the interrelated responsibilities of Contractor, Owner’s testing agency, and Contractor’s testing agency.

6.2.7 Description of Part 2, Products

6.2.7.1 Materials

Provide statements describing primary materials and their accessories to be furnished. Refer to applicable standard specifications, and include separate provisions for each material specified. Accessories provide necessary aid for the preparation or installation of primary materials.

6.2.7.2 Mixtures

Provide mixture performance requirements, or mixture proportions and procedures for mixing materials.

6.2.7.3 Fabrication

Describe shop-manufactured, fabricated, or assembled items, such as requirements for shop assembly, shop or factory finish, and tolerances.

6.2.7.4 Source quality control

List tests and inspections required at the source. Include statements for procedures and methods of verification of performance or compliance.

6.2.8 Description of Part 3, Execution

6.2.8.1 Preparation

State site conditions and actions necessary for the proper installation of products into the Work.

6.2.8.2 Sequence

Describe product placement sequence.

6.2.8.3 Installation

State actions necessary for installation of products furnished under Part 2. Include separate provisions for each product with specific installation procedures and tolerances.

6.2.8.4 Post-installation testing

Define tests and inspections for installed or completed Work.

6.2.8.5 Repair

Define deficient Work and provide corrective actions for final acceptance.

6.2.8.6 Protection

List actions required to protect installed Work before acceptance.

6.2.9 Description of Notes to Specifier

Notes are appended to the specification and are not part of the specification. These notes are for the specifier and include general notes, foreword to checklists, references, and checklists. The general notes provide guidance on how to incorporate the ACI specification into Contract Documents. The foreword to the checklists explains how to modify the ACI specification in the Contract Documents for the project. There are two types of checklists: the mandatory requirements checklist and optional requirements checklist. The mandatory requirements checklist identifies information that is required to be included in the Contract Documents because there is no default requirement in the specification. The optional requirements checklist identifies alternative or optional additions to the default requirements. A default requirement is a limiting requirement that has been selected for the specification. Unless otherwise specified in the Contract Documents, default requirements are mandatory conditions of the specification. The optional requirements checklist provides guidance to the specifier in specifying alternative requirements. Checklists do not provide explanations for the requirements; instead, refer to ACI guides and reports for additional information.

To assist the specifier, checklists notes can include:

(a) Reference citations

(b) Recommended values

(c) Alternative products

(d) Alternative installation procedures

Refer to 6.2.9.4 for checklist format.

6.2.9.1 General notes, foreword to checklists, and list of references

ACI construction specifications shall include the following wording without modification except for insertion of title and number of the ACI specification. Paragraphs F4, F5, and F6 may be omitted if they do not apply.

NOTES TO SPECIFIER

General notes

G1. ACI Specification XXX is to be used by reference or incorporation in its entirety in the Project Specification. Do not copy individual sections, parts, articles, or paragraphs into the project specification because taking them out of context may change their meaning.

G2. If sections or parts of ACI Specification XXX are copied into the Project Specification or any other document, do not refer to them as an ACI specification, because the specification has been altered.

G3. A statement such as the following will serve to make ACI Specification XXX a part of the Project Specification:

“Work on (Project Title) shall conform to all requirements of ACI (Specification number with date suffix and title) published by the American Concrete Institute, Farmington Hills, Michigan, except as modified by these Contract Documents.”

G4. Each technical section of ACI Specification XXX is written in the three-part section format of the Construction Specifications Institute, as adapted for ACI requirements. The language is imperative and terse.

G5. If ACI Specification XXX is used with another ACI specification that contains overlapping provisions, identify which requirements are in conflict and state in the contract documents which requirements control.

Foreword to checklists

F1. This foreword is included for explanatory purposes only; it is not a part of ACI Specification XXX.

F2. ACI Specification XXX may be referenced by the specifier in the Project Specification for any building project, together with supplementary requirements for the specific project. Responsibilities for project participants must be defined in the Project Specification. ACI Specification XXX cannot and does not address responsibilities for any project participant other than the Contractor.

F3. Checklists do not form a part of ACI Specification XXX. Checklists assist the specifier in selecting and specifying project requirements in the Project Specification.

F4. The Mandatory Requirements Checklist indicates work requirements regarding specific qualities, procedures, materials, and performance criteria that are not defined in ACI Specification XXX. The specifier must include these requirements in the Project Specification.

F5. The Optional Requirements Checklist identifies specifier choices and alternatives. The checklist identifies the sections, parts, and articles of ACI Specification XXX and the action required or available to the specifier. The specifier should review each of the items in the checklist and make adjustments to the needs of a particular project by including those selected alternatives as mandatory requirements in the Project Specification.

F6. Cited references—Documents and publications that are referenced in the checklists of ACI Specification XXX are listed below. These references provide guidance to the specifier and are not considered to be part of ACI Specification XXX.

(Provide a list of the applicable references using the format in 8.3.)

6.2.9.2 Mandatory requirements checklists

Notes are provided in the mandatory requirements checklist if a product or installation procedure is required for construction within the scope of the specification but there is no default requirement in the specification. Minimize the number of items in the mandatory requirements checklist. It is acceptable to write a specification without a mandatory requirements checklist. The following shows an example of notes in a mandatory requirements checklist.

EXAMPLE
Mandatory Requirements Checklist
Section/Part/Article | Notes to Specifiers
4.2.2.8 Specified strength | Indicate the specified compressive strength of concrete fc′ for various portions of the Work. Sample language for Contract Documents: “The specified compressive strength of concrete, fc′, for all concrete in the Work is 4000 psi.”

Minimize the number of items in the mandatory requirements checklist. A specification with no mandatory notes is acceptable.

Items outside the scope of the specification, such as directions on how to write Contract Documents or project administrative requirements, cannot be included. The general notes provide guidance on how to incorporate the specification into the Contract Documents. Do not add a mandatory requirement for the scope statement that requires the specifier to specify the scope. Reminders to the designer of what to include on project drawings may be included in the checklist notes but are not appropriate in the specification text because the specification is not written to instruct the designer.

6.2.9.3 Optional requirements checklists

The specifier may want to require items either in place of or in addition to the default requirements in the cited reference specification. The optional requirements checklist can provide sample language that the specifier can use to invoke the optional requirement in the Contract Documents. Limited discussion or citations explaining circumstances when an option should be invoked may be included.

6.2.9.4 Checklist format

Use the following format for each item in the mandatory and optional requirements checklists. In the left column, provide the numbering of the referenced article and provide a brief description of the subject. In the right column include the following:

(a) Concise instruction to specifier

(b) Concise guidance to specifier (optional)

(c) References for additional guidance (optional)

(d) Sample language to invoke optional requirement (optional)

The following is an example of an entry in an optional requirements checklist.

EXAMPLE

Optional Requirements Checklist

Section/Part/Article | Notes to Specifiers

5.3.2.6

Joint preparation

If bond is required at construction joints, specify acceptable joint preparation. The following joint preparations are acceptable:

(1) Adhesive applied in accordance with the manufacturer’s recommendations

(2) Surface retarder in accordance with manufacturer’s recommendations

(3) Roughened surface that exposes the aggregate uniformly and does not leave laitance, loosened particles of aggregate, or damaged concrete at the surface

(4) Portland-cement grout of the same proportions as the mortar in the con-crete in an acceptable manner.

Sample language for Contract Documents:

At construction joints, roughen the sur-face that exposes the aggregate uniformly and does not leave laitance, loosened particles of aggregate, or damaged concrete at the surface. Al-ternatively, the specifier may allow Contractor to choose any of the four options.

Specifier may allow Contractor to choose any of the four options.

6.3—Language

6.3.1 Tolerances

Refer to ACI 117 unless it does not cover a required tolerance. Specify tolerances not covered and notify ACI Committee 117 of the need for additional tolerances.”

EXAMPLE

Tolerances for reinforcement location shall be in accordance with ACI 117.

6.3.2 Verb usage

Write ACI specifications in mandatory language. Where possible, use terse imperative language. Avoid passive tense. Do not provide a reason for the requirement.

6.3.3 Gender-specific language

Avoid using gender-specific terms if possible. Such terms can often be replaced by “operator” or “person.”

6.3.4 Subjective language

Use specific, objective language rather than vague, subjective descriptions. Do not use the following words or phrases:

adequate

all

any

appropriately

approximately

comprehensive

detailed

each

every

good

in a workmanlike manner (or other similar phrases)

immediately

nearly

rigorous

shall function as intended

to the satisfaction of the specifier

significantly

special

substantial

such

usual

6.3.5 Time-related requirements

Specify ending points for time-related requirements.

6.3.6 Qualitative requirements

Avoid qualitative requirements and refer to measurable parameters.

6.3.7 Repetition of items

Specify an item one time only. If needed again, refer to the item by its original provision number.

6.3.8 Jargon and slang

Do not use legal jargon. ACI specifications become legal documents by being referenced in Contract Documents. Write specifications with more emphasis toward effective communication than toward use of legal terms. Do not use such terms as “herewith,” “hereinafter,” “as per,” or “wherein.”

Likewise, do not use technical slang such as “rebar,” “pour concrete,” “wet concrete,” and “freeze/thaw.” Refer to 8.2.7 for additional examples of preferred terminology.

6.3.9 Approved

Do not use the word “approved” when referring to Architect/Engineer review of Contractor submittals. Use “accepted,” “reviewed,” or similar terms that do not relieve Contractor of obligations under contract documents.

6.3.10 Responsibilities

ACI specifications provide requirements that are performed by the Contractor. Therefore, it is not necessary to begin provisions with “The Contractor shall…” Refer to the Contractor only if necessary to avoid misinterpretation of responsibility.

6.3.11 Referral phrase

There are only two referral phrases permitted in ACI specifications.

When the referral phrase “as indicated in Contract Documents” is used in the provision, the specifier must include the provision requirements in the Contract Documents for the specification to be complete.

When the referral phrase “unless otherwise specified” is used in the provision, the specifier may include an alternative to the default requirement in the Contract Documents.

6.3.12 Compliance phrases

Use “conform to” if referring to compliance with materials specifications and “in accordance with” for compliance with test methods and practices.

6.3.13 Article use

“The,” “a,” and “an” are used to impart specificity to a noun. They are not required when the subject or object is known or has been previously identified. Such words that do not require an article before their use are: Architect/Engineer, Contractor, Contract Document, inspection agency, licensed design engineer, and Owner.

EXAMPLE

Use: “Testing agencies shall be accepted by Architect/Engineer.”

Instead of: “The testing agencies shall be accepted by the Architect/Engineer.”

6.3.14 Pronouns

The use of personal pronouns is discouraged.

6.3.15 Options

It is acceptable to use the verb “may” to indicate that the Contractor can exercise an option if prescribed conditions are satisfied. It is better, however, to rewrite the sentence to avoid using “may.” Use “either... or...” if the Contractor has limited, specified alternatives. Do not use “may” to indicate an alternative choice, because when “may” is used, the Contractor is not obligated to perform the actions.

6.3.16 Conditional phrases

Conditional phrases “if,” “when,” and “where,” are used in provisions if the action depends on whether a stated condition is satisfied. When so used, these words have the following meanings:

If—on condition that; in case that

When—at the time that; in the event that

Where—in whatever place

These meanings have subtle differences. For consistency, use “when” for cases that refer to time, use “where’ for cases that refer to position or situation, and use “if” for all other cases.

6.4—Referenced standards

6.4.1 Standards in specification text

Standards that are written in mandatory language and referenced in the specification are considered referenced standards, which are listed in Part 1 of a single-item specification and in Section 1 of a multi-item specification. Include the full title and year designation in the list of referenced standards. It is preferred to use the latest version of referenced standards unless there is a reason not to. Do not indicate the year of the standard where the standard is mentioned in the text of the specification. Organize referenced standards according to the standards-producing organization and list the organizations in alphabetical order.

EXAMPLE

1.4 Referenced standards

Standards of [insert organization abbreviations] cited in this Specification are listed by name and designation, including year.

1.4.1 American Concrete Institute

ACI 117-10—Specification for Tolerances for Concrete Construction and Materials

1.4.2 ASTM International

ASTM C39/C39M-09—Standard Test Method for Compressive Strength of Cylindrical Concrete Specimens

It is preferred that all cited standards be authored by a committee under a consensus process.

It is acceptable for an ACI specification to modify an ASTM specification for a specific requirement.

If an ACI specification refers to combined ASTM standards, include the following provision in the interpretation article: “Unless otherwise stated, the inch-pound system [or metric, whichever is applicable] of units is applicable to combined standards referenced in this specification.” Provisions should include the complete designation of a combined standard.

6.4.2 References in checklists

The cited references in the checklists are to be listed as the last item of the Foreword to Checklists using the format in 8.3.

6.5—Appendixes

Appendixes are allowed in specifications; however, they are considered nonmandatory and can only contain information-only material. They appear after the checklists.

PART 3—GUIDES AND REPORTS

CHAPTER 7—DEVELOPMENT OF GUIDES AND REPORTS

7.1—General

Technical committees may author ACI guides and reports.

7.2—Description of guides and reports

7.2.1 Guides

ACI guides present committee recommendations for analysis, design, specifying, selection, evaluation, testing, construction, or repair of concrete materials or structures. If the committee does not give recommendations, the document should not be titled as an ACI guide. ACI guides can be in the form of handbooks, manuals, and technical notes.

A guide can provide pertinent examples and case studies to explain covered concepts and indicate advantages and disadvantages of various alternatives.

ACI committees can write guides to assist the user to develop Project Specifications for a specific construction activity.

ACI guides are written in nonmandatory language. Mandatory language can be used in nonmandatory-language documents when quoting directly from or referring to provisions in a document that uses mandatory language or is suggesting requirements.

7.2.1.1 Handbooks and manuals

Handbooks provide information and guidance on how to apply design standards in practice and typically contain charts and tables to facilitate design of concrete structures. Charts, tables, and figures may also be used to illustrate the detailed steps in designing a concrete member or a structure. They may also include examples to illustrate specific design methods. Examples of handbooks include SP-17, ACI Design Handbook, and SP-4, Formwork for Concrete (which is individually authored but committee sponsored).

Manuals generally provide guidance and instructions to field personnel involved in different aspects of concrete construction. An example is SP-2, ACI Manual of Concrete Inspection.

7.2.1.2 Technical notes (TechNotes)

TechNotes are narrowly focused, single-topic guides, usually practice oriented. A TechNote presents specific direction on a particular issue, and may contain pictures, figures, tables, and numeric examples. TechNotes can cover topics such as design, construction, or repair methods, or can provide recommendations on a concrete technology. TechNotes are written in nonmandatory language. At TAC’s discretion, TechNotes can be published on the ACI website, as hard copy, and in the Manual of Concrete Practice (MCP). In addition, TechNotes may be published in Concrete International at the editor’s discretion. The committee is to maintain a TechNote in accordance with 7.3.2.

7.2.2 Reports

ACI reports provide information on concrete technology in the committee’s area of expertise. Reports may include recommended action but are not required to do so. Reports can cover topics such as research results, design or construction methods, or current knowledge on a particular concrete technology.

If there is insufficient knowledge to write a comprehensive ACI report, committees may publish Emerging Technology Reports.

ACI reports are written in nonmandatory language. Mandatory language can be used if quoting directly from or referring to provisions in a document that uses mandatory language.

7.2.2.1 Emerging Technology Report (ETR)

An ACI Emerging Technology Report provides information on emerging concrete technology in the committee’s area of expertise where there is insufficient knowledge to write a comprehensive ACI report. It is intended to introduce a new technology into practice by providing basic information to allow implementation and permit accumulation of performance histories. The document should include a statement of limitations and a discussion of research needed to provide the missing information. These documents are identified by the designation “Emerging Technology Report” on the front cover and title page, and by an introductory statement on the title page (14.2.4). The document shall have a maximum lifetime of 10 years from date of initial publication, by which time it must have either been withdrawn or revised and published as a report or guide.

To publish the document as a regular ACI report, the committee must letter ballot to remove the ETR designation from the next edition. When submitting the revised document for TAC review, the chair must include a written summary of the committee’s reasoning for removing the designation. TAC approval is needed to remove the ETR designation.

7.2.3 Errata

Errata are posted on the ACI website. When potential errors are discovered in an ACI guide or report, the committee chair has the authority to decide if a correction needs to be made and provides staff with the correction. The chair is not required to ballot the committee.

7.3—Development

7.3.1 New guides and reports

Committees must obtain TAC approval before beginning work on a new document. The proposal, sent to the Managing Director of Engineering, should indicate why it is needed and include a preliminary outline.

ACI guides and reports are developed in a four-step process:

1. Preparation of a new document or revision of an existing document.

2. Letter balloting of the draft document by the committee, according to the procedures of Chapter 3.

3. Submission of the committee-approved document for TAC review, according to the procedures of 7.4. There is no public discussion period for ACI guides and reports.

4. Revision of the document in response to TAC comments.

After a new document has been successfully balloted by the technical committee, the chair must submit the document for TAC review.

Once a document has been approved by TAC and the committee has responded adequately to TAC’s review comments, ACI publishes the document.

7.3.2 Existing guides and reports

Committees are expected to revise, reapprove, or withdraw a document within 8 years from its adoption date. The adoption date is the month and year of first publication. TAC may remove those documents from the MCP that have not been reapproved or revised within 8 years of the adoption date. In the case of an ITG document, the document is removed from the MCP after 5 years.

If the committee does not revise (7.3.2.2), recommend reapproval (7.3.2.1), or recommend withdrawal (7.3.2.3) of a document within the 8-year period, TAC may reapprove or withdraw it without committee action.

7.3.2.1 Reapproval

The committee may decide to reapprove a document because the information in an existing document, while not new, is still valid. The first reapproval of a document is for 5 years. The second and subsequent reapprovals (if any) are for 3 years. The committee is required to letter ballot the reapproval. Negative votes do not need to be resolved, but the ballot must still pass. The reapproval may include updating references and minor editorial improvements of notation, terminology, metrication, or other similar items. A reapproval must not include technical changes.

The committee must submit its recommendation for reapproval of the document to TAC for approval. The recommendation includes a letter ballot summary (3.5) and a statement that technological progress at this point does not require revision or that the document is currently being revised but the revision is not complete. Include a summary of the updates to the document. Generally, TAC reviews only the committee’s ballot summary and the summary of updates. A reapproval does not change the year of adoption but “Reapproved” with the year of reapproval is added to the document number.

7.3.2.2 Revision

The committee should revise a document when the information in the document needs to be updated. The committee must letter ballot revisions according to Chapter 3 and submit the document to TAC for review. Upon adoption of a revised document, the existing version is marked historical. (A document is made historical when it has been superseded by a revision.) The revised document’s number receives the new year of adoption.

7.3.2.3 Withdrawal

The committee should recommend withdrawal of a document when the committee determines that the information it contains is obsolete and should not be revised. A letter ballot of the committee is required. Negative votes do not need to be resolved, but the ballot must still pass. The recommendation for withdrawal should include a statement that, in the judgment of the committee, the document is no longer useful or amenable to updating. The committee’s recommendation and related ballot summary must be submitted to the Managing Director of Engineering for review by TAC.

Upon TAC’s approval of the recommendation, the document is not included in the next edition of the MCP. It may still be available for purchase from ACI as a historical document.

7.3.2.4 ITG guides and reports

After an ITG document is published, TAC will request an ACI committee consider the incorporation of the content of the ITG document into a new or existing committee document. Related technical committee(s) may have been identified during formation of the ITG as described in 1.4.1.2.

The technical committee should:

(a) Review and revise the content of the ITG document or incorporate the information into an existing committee document

(b) Ballot the revised content of the ITG document as soon as practicable because the ITG document only has a 5-year life in the MCP

7.3.3 Documents sponsored with other ACI technical committees

ACI committees may agree to cosponsor a document when the scope of the document overlaps their missions. Committees may request to jointly sponsor a document when at least 75 percent of voting members from each affected committee vote in favor of the proposed arrangement. The chair must forward the comments of negative voters to TAC. In such arrangements, one committee is the major sponsor and the others are minor sponsors.

The major sponsor committee is responsible to draft and ballot the document. Members from the minor sponsor committees may assist in the development of the draft. The minor sponsor committees will ballot the final draft of the document. Negative votes from both the major and minor sponsor committee must be resolved. At least 50 percent of voting members from the minor sponsor committees must vote in favor of the draft document before it is submitted to TAC. The chair must forward the comments of negative voters and their resolutions to TAC.

The document designation includes all sponsoring committees. The document’s roster includes only members of the major sponsor committee.

7.3.4 Restrictions on circulating drafts

Mark the draft “draft document, not for publication” and include date of the final draft. The chair may only circulate the drafts to individuals outside the committee, TAC, and ACI staff to obtain expert technical advice not available in the committee or to ensure that all interested parties are given an opportunity to express viewpoints.

Committee documents, at any stage of development, must not be released for publication other than to ACI or cosponsors of joint committees, except on approval of TAC. Similar restrictions apply to test data or unpublished technical information circulated in a committee.

Posting of draft documents on the committee’s ACI website is encouraged. Posting of draft documents on independent websites is not permitted because control, copyright, and document status are not secure.

7.3.5 Coordination of information

7.3.5.1 Technical committees

Coordination with other technical committees is an important part of processing documents. Some reasons for coordination with other committees are:

(a) To provide agreement for information that will be incorporated or referenced in another committee document

(b) To improve quality of the document through the input of another committee

(c) To minimize instances of documents with parallel or overlapping scopes

(d) To minimize technical conflicts between committee documents

If substantial difficulties arise between two committees, the matter can be referred to TAC.

Documents submitted for TAC review may be in conflict with or vary from existing ACI documents. The committees should identify conflicts between the submitted document and existing ACI documents and provide reasons for the differences, if applicable.

7.3.5.2 Construction Liaison Committee

Part of the ACI Board of Direction’s Construction Liaison Committee (CLC) mission is to review technical committee documents that deal with constructibility and economy. As part of the TAC review process, staff sends documents that contain sections on construction to CLC for review.

7.3.5.3 Terminology

The “ACI Concrete Terminology” (CT) contains all ACI-approved terms, and is available at http://concrete.org/Tools/ConcreteTerminology.aspx. Individuals may submit proposed CT changes to TAC.

TAC reviews each document’s definitions at the time of submission for TAC review (10.2.2).

7.3.6 Translation of ACI documents

Upon TAC approval, translation of an ACI document into a language other than English may be permitted and is considered an editorial change and no further balloting by the committee is required. The translated document is published with the translation disclaimer (14.2.5).

7.3.7 Guides and reports authored by ACI chapters

ACI chapters may publish their documents without TAC approval. They must, however, use a disclaimer stating that the document was prepared and reviewed by the chapter and has not been reviewed or approved by ACI. Chapter documents must only use chapter logos on their documents.

If a chapter wishes to use the ACI logo, the document must be processed through an ACI technical committee and receive a TAC review and approval.

7.4—Writing guides and reports

7.4.1 Format

Refer to Chapter 8 for format of a guide or a report.

7.4.2 Units

In accordance with ACI Board Policy, guides and reports shall be published in dual units (14.3). The primary units shall be stated in in.-lb followed by SI units in parentheses.

Soft unit conversion of a document may be considered editorial. No further balloting by the committee is required to approve the unit conversion. When hard unit conversions are developed, they must be balloted.

This dual-units requirement may be waived by TAC in exceptional circumstances. TAC approval to waive the requirements for dual units is required before submitting the document to TAC. The application must describe the circumstances supporting a waiver.

A committee may request a waiver for certain figures, tables, or examples because of the resulting complexity if dual units were incorporated. If a waiver is given for figures or tables, a unit conversion table must be provided. For numerical examples, comparable separate examples in each system of units must be provided.

For additional information on units, refer to Chapter 11.

7.4.3 Notation

Refer to Chapter 10 for information on notation.

7.4.4 Style

Refer to Chapter 9 for information on style.

7.4.5 Editorial review

The committee’s editorial subcommittee or task group should thoroughly edit a document before final committee letter ballot. When submitting the document to TAC, the chair should state that the editorial subcommittee has reviewed the document.

The editorial subcommittee should review for document structure, sentence structure, grammar, redundancy, spelling, and typographical errors. Because many people contribute to a document, it is essential that the subcommittee review the separate sections for consistency in style and format. The editorial subcommittee should be familiar with Chapters 8 and 9.

7.5—TAC review

7.5.1 Submission package

All materials required for submitting documents for TAC review shall be submitted to the Managing Director of Engineering at least 3 months before a TAC meeting. Submitting the document by the deadline does not guarantee placement in the next TAC document review cycle. TAC typically accepts the documents in the order received. With the submittal, the chair shall include:

(a) An electronic copy of the document in Microsoft Word

(b) Original artwork

(c) Statement of the type of document (7.2) being submitted

(d) A ballot summary of the final letter ballot(s) (3.5), including resolutions to all negatives

(e) A summary of revisions to the existing document in the case of a revision

The committee is encouraged to provide a list of at least three potential external reviewers for the document.

Documents prepared by joint committees may be subject to the review procedures of the sponsoring organizations. Coordinate with staff the required submissions to such organizations.

7.5.2 Staff editorial review

TAC has directed staff to perform an editorial review of each document that is submitted for TAC review. Staff reviews the document for grammatical errors, misspelled words, ambiguous statements, and checks the document for compliance with ACI style. All staff-recommended editorial changes are sent to the chair for approval. Once the chair and staff have agreed upon editorial items, staff submits the edited document to TAC for review.

7.5.3 TAC review

One of the most important functions of TAC is the review of technical committee documents. TAC reviews documents for:

(a) Technical content and correctness

(b) Potential conflicts, duplications, and overlaps with other ACI documents

(c) Compliance with ACI formats

(d) Clarity

The submitted document is sent to all TAC members and to selected external reviewers who are experts on the subject matter and who are not members of the committee submitting the document. ACI staff also forwards the document to committees that have guides or reports that may cover the subject matter in the document to help identify conflicts, duplications, and overlaps between committee documents. Reviewers are given 4 weeks to review the document and submit comments.

TAC will review the entire document, even if only one section has been revised because a revision of one section of the document may necessitate a change elsewhere in the document.

7.5.3.1 TAC review group

Each document is assigned to a TAC review group (RG) that is composed of a TAC member as review chief, two other TAC members as primary reviewers, and a staff liaison. All comments received from TAC members, external reviewers, Construction Liaison Committee (CLC), staff, and chairs of coordinating committees are compiled as TAC review comments and distributed to the RG by the review chief.

The TAC RG reviews all comments and meets with a committee representative, usually the chair, to discuss the TAC review comments. The review chief leads the discussion on TAC’s behalf.

7.5.3.2 Review comment classifications

Reviewers classify each of their comments as primary (P), editorial (E), or secondary (S) and also provide specific page and line number references for each comment, or label them as “Page 0” and “Line 0” for general (G) comments that apply to the entire document.

Primary (P) comments identify technical issues that the committee must address before publication of the document.

Editorial (E) comments identify editorial issues that the committee must address before publication of the document. The committee is expected to implement all E comments unless the committee agrees that the change is not an improvement or that it would change the intended meaning.

Secondary (S) comments identify technical or editorial issues that should be addressed either in this document or the next revision of the document.

General (G) comments identify issues general to the entire document that the committee must address before publication of the document.

7.5.4 TAC decision

After the RG meets with the committee representative, the RG makes a recommendation to TAC regarding the document. TAC considers the recommendation and makes one of the following decisions on the document:

(a) Document is approved for publication, contingent upon satisfactory response to TAC review comments in a timely manner

(b) Document is not approved for publication, and it is returned to the committee for revision, reballoting, and resubmission (commonly called 3R)

The committee is notified of TAC’s decision, and the official TAC review comments are sent to the committee for consideration.

7.5.4.1 Document approved

When the document is approved, the committee should act promptly to prepare a response to each TAC review comment.

7.5.4.2 Responding to TAC comments

The committee must document its response to each TAC review comment. The committee can agree with a P, E, or G comment and make an appropriate change to the document or disagree with reason. When the committee disagrees, a detailed reason statement for the disagreement must be documented.

The committee can agree with an S comment and make a change to the document, disagree (no documentation is required), or agree to take the issue up as new business.

Responses to TAC comments must be approved by the committee by either letter ballot or meeting ballot, regardless of whether or not the response resulted in a technical change to the document (Chapter 3). Include with the ballot the document with proposed changes resulting from the proposed responses to TAC comments (in strikeout/underline).

If a comment is strictly editorial and appropriate, the chair has the authority to implement the change, and no further action by the committee is required. If a voting member believes that the comment is not strictly editorial, or if there is doubt, the committee must ballot to approve the proposed response.

After the document has been revised in response to TAC review comments, the following shall be submitted to the Managing Director of Engineering:

(a) The revised document in Microsoft Word format, showing the committee’s changes using the strikeout/underline feature

(b) All original or revised artwork

(c) The comment form including the committee responses to the TAC review comments.

(d) A ballot summary on the responses to TAC review comments, including any related committee minutes that provide records of the resolution of negative votes and negative withdrawals

When compliance with TAC review comments is verified, the document is adopted. The adoption date is the same as the publishing date.

If a committee decides to abandon a document after TAC approval has been received, the committee is required to letter ballot this decision. The balloting summary of the decision to abandon the document must be submitted to ACI staff. This ballot is considered an administrative ballot and the negatives do not need to be resolved.

Technical committees must respond to TAC review comments within 2 years of the review, otherwise the TAC approval is withdrawn. In such case, the committee must resubmit the document for TAC review and respond to a new set of TAC review comments. In exceptional cases, TAC may extend the time frame for acceptance of the committee responses upon written request from the committee chair with detailed explanation of the reasons.

7.5.4.3 Document not approved

If the document is not approved by TAC, the committee is usually expected to revise, reballot, and resubmit (commonly called “3R”) the document to TAC. The decision not to approve is usually the result of major technical deficiencies in the document. Therefore, TAC expects a comprehensive effort by the committee before the document is resubmitted.

When a document is not approved, the TAC RG will indicate what they believe is necessary to revise the document. Although TAC expects the committee to address issues raised during the TAC review when revising the document, the committee is not expected to respond individually to each review comment.

7.6—Appeal processes

The adoption of committee documents in process or the content of published ACI committee documents may be appealed. Appeals of documents in process may be made on technical or procedural grounds. Appeals of published documents may be made only on technical grounds. Because appeals are normally heard at ACI conventions, all appeals must be submitted in writing to the Managing Director of Engineering at least 6 weeks before the convention for inclusion on the agenda of the hearing committee.

7.6.1 Guides and reports under development

A voting committee member has the right to appeal TAC on a committee document under development by the appellant’s committee. The appellant must submit an appeal package to the Managing Director of Engineering. If an appeal is upheld, the document shall not be processed further, and is returned to the committee with comments.

7.6.2 Published guides and reports

A current member of the Institute has the right to appeal the technical content of published ACI committee documents. The appellant must submit an appeal package to the Managing Director of Engineering. If a technical appeal is upheld, the originating committee should ballot a revision to address the issue raised by the appeal within the time limit established by TAC or the document will be withdrawn by TAC.

7.6.3 Technical grounds

TAC is the Institute’s final authority on all technical matters. If an appeal on technical grounds is made, an item is placed on the agenda for the next scheduled TAC meeting and those interested are invited to attend the meeting.

7.6.4 Procedural grounds

TAC is the Institute’s final authority on procedural matters pertaining to nonstandardized technical committee documents. If an appeal on procedural grounds is made, an item is placed on the agenda for the next scheduled TAC meeting and those interested are invited to attend the meeting.

CHAPTER 8—FORMAT AND LANGUAGE FOR GUIDES AND REPORTS

8.1—Format

8.1.1 Outline

Below is an example of an outline with the required sections for ACI guides and reports.

8.1.2 Description of required front matter

(a) Title—The title of the document appears prominently on the first page of the draft document. The title of the document should include either the word “guide” or “report,” depending on the document, and indicate the subject matter, for example, “Report on ….” or “Guide for…”

(b) Roster—All voting members (of the main committee and the subcommittee that developed the document) and consulting members at the time of the opening date of a document’s final letter ballot before submission for TAC review are listed on the roster published on the front page of the committee document. Associate members are not listed. When a committee reapproves a document, the committee roster published with the original document is retained, and the roster of the current committee is not shown.

The chair may list other individuals who contributed to the document and should receive recognition.

Place an appropriate note immediately below the roster. The acknowledgement note should not list specific contributions. An example of an appropriate note is: “Special acknowledgements to {list of individuals} for their contributions to this [report or guide].”

(c) Synopsis—A one- or two-paragraph synopsis should state the document’s scope and purpose, and should inform and spark interest without going into too much detail. Each synopsis is printed in Concrete International, and should therefore make sense when read independently of the document.

(d) Keywords—A list of items discussed in the document that aid users in retrieving material. The title, synopsis, and table of contents of the document are good sources for keywords. Approximately three to 10 keywords are required. The keywords should reflect the document’s subject matter without being too general. For example, avoid listing “concrete” or “water-cement ratio.” List keywords in alphabetical order and separate them with semicolons. Do not use multiple forms of the same word as keywords.

(e) Table of contents—A table of contents includes titles of chapters and sections. Do not include page numbers in the table of contents; page numbers are assigned by staff after final formatting of the document.

(f) References—Final Chapter; includes standards and cited references.

8.1.3 Description of chapters

Chapter 1—Introduction (1.1) and Scope (1.2)—provides the history, the scope of the document and context of the information, and may provide a brief description of each chapter in the document.

Chapter 2—Definitions and notation—list the notation used throughout document. Arrange in alphabetical order, with roman letters appearing first and Greek letters at the end. Upper-case letters should come before lower-case letters in the list. Define technical terms that are unique to the document. Refer to the “ACI Concrete Terminology” (CT) for general technical terms.

For documents with terms defined, add the following statement:

ACI provides a comprehensive list of definitions through an online resource, “ACI Concrete Terminology,” http://concrete.org/Tools/ConcreteTerminology.aspx. Definitions provided here complement that source.

For documents with no terms defined, add the following statement:

ACI provides a comprehensive list of definitions through an online resource, “ACI Concrete Terminology,” http://concrete.org/Tools/ConcreteTerminology.aspx.

Other chapters—present information in a logical order.

8.1.4 Description of back matter

Appendixes—Some documents use appendixes to present supplementary information such as long derivations, research data, or sample calculations. Use a separate appendix for each main purpose, lettered consecutively (Appendix A, Appendix B, etc.). Appendixes, if included, should follow the reference chapter. Appendixes should also be listed in the table of contents.

8.1.5 Numbering and titles

Chapters and sections should have titles. Items may or may not be titled, but number them consecutively following the decimal designation system. The numbering system should not exceed four levels.

8.2—Language

8.2.1 General principles

Technical writing must be precise and convey a single, specific meaning. Using multiple terms when referring to a single item or idea creates confusion, and can lead to misinterpretation of information. ACI requirements for technical writing include:

(a) Avoid words or phrases that have more than one meaning that can be applicable to the context of the document.

(b) Do not use slang expressions.

(c) If there is any doubt that a specific phrase or term can be confused with another and it must be used in the document, define the exact intended meaning at its first mention or in the definitions chapter.

(d) Use terminology and definitions from the CT unless there is a technical reason for using a different definition.

8.2.2 Clarity

ACI technical document language should not hedge or convey uncertainty, as this causes the document to lose credibility to the reader. Avoid beginning sentences with phrases such as “It is recommended that…,” “Committee XXX recommends that…,” or “It is suggested that...” It is understood that the document presents recommendations of the committee.

When using phrases such as “It has been observed that…” or “Research has shown that...,” the reader wonders, “Who observed? What research?” In these instances, identify the source or cite a reference.

8.2.3 Gender-specific language

Avoid using gender-specific terms, such as “he,” “she,” or “man,” when possible. Such terms can often be replaced by “operator” or “person.”

8.2.4 Vague language

Do not use vague adjectives or adverbs.

8.2.5 Conditional phrases (use of if, when, and where)

These conditional phrases are used in provisions where the action depends on whether a stated condition is satisfied. When so used, these words have the following meanings:

If—on condition that; in case that

When—at the time that; in the event that

Where—in whatever place or situation

These definitions have subtle differences. For consistency, use “when” for cases that refer to time, use “where” for cases that refer to position, and use “if” for all other cases.

8.2.6 Active versus passive voice

When possible, write in the active voice. This means that the subject of the sentence performs the verb of the sentence, which makes for more forceful and direct writing. The passive voice usually employs a form of the verb “to be.” When using the passive voice, the subject of the sentence receives the action of the verb.

8.2.7 Acceptable and unacceptable terminology

Certain terms and phrases should typically not be used in ACI documents. Some terms to be avoided are listed in the following along with their acceptable alternatives.

Avoid | Use
about | approximately
air-entraining agent | air-entraining admixture
below | the following
place concrete | cast concrete
chairman | chair
concrete block and cmu | concrete masonry unit
constructability | constructibility
control joint | contraction joint
cost (when referring to monetary cost) | price
e.g. | for example
epoxy (as a verb) | apply epoxy
form streaking | formstreaking
form work | formwork
freeze/thaw | freezing and thawing
freezing and thawing durability | resistance to freezing and thawing
furthermore | in addition (additionally)
ground-granulated blast-furnace slag | slag cement
high performance concrete | high-performance concrete
i.e. | that is
lateral force resisting system | lateral-force-resisting system
microsilica | silica fume
mix (noun) or mix design | mixture proportions
NPC | normal cement
PFA | fly ash
Portland cement | portland cement
pour concrete | place concrete
rebar | reinforcing bar (in some instances, reinforcement should be used)
referred to as | called
see | refer to
self compacting concrete | self-consolidating concrete
shearing stress | shear stress
since (if not referring to time) | because
slab(s)-on-grade | slab(s)-on-ground
stud shear reinforcement | shear stud reinforcement
superplasticizer | high-range water-reducing admixture
trial mix (trial mixes) | trial batch
water tightness | watertightness
water cementitious ratio or water-to-cementitious-material ratio | water-cementitious materials ratio
w/(c+m) water-cementitious material ratio | water-cementitious materials ratio (w/cm)
water reducer | water-reducing admixture
water to cement ratio | water-cement ratio (w/c)
wet or plastic concrete | fresh concrete

8.3—References

Cited references should be in the author/date format.

All references must be mentioned at least once in the document to be included as a reference. ACI does not publish bibliographies.

EXAMPLE

Chapter 10—References

ACI Committee documents and documents published by other organizations are listed first by document number, full title, and year of publication followed by authored documents listed al-phabetically. Include each element of the authored reference, including month and page num-ber(s) were applicable.

American Concrete Institute

ACI 212.3R-04—Chemical Admixtures for Concrete

American Society of Civil Engineers

ASCE/SEI 7-10—Minimum Design Loads of Buildings and Other Structures

ASTM International

ASTMC39/C39M-12 Standard Test Method for Compressive Strength of Cylindrical Concrete Specimens

Authored documents

Kosmatka, S. H.; Kerkhoff, B.; and Panarese, W. C., 2002, Design and Control of Concrete Mixtures, EB001, 14th edition, Portland Cement Association, Skokie, IL, 372 pp.

Mathur, R.; Lee, H.; and Orsolini, G., 1999, “Two-Level Design Spectrum for Highway Bridges,” Seismic Response of Concrete Bridges, SP-187, K. Krishnan, ed., American Concrete Institute, Farmington Hills, MI, pp. 345-360.

Cite references in the text as follows.

If possible, reference printed publications. For original content available only from electronic sources, however, include as much information as possible: author, title of page, title or owner of site, URL, and date that the site was accessed.

If there is no author, the owner of the site may be substituted for the author.

For electronic journals, follow the same format for paper journals, and add the URL.

Do not include bibliographies in ACI committee documents. Bibliographies list the references consulted in writing a document. References are only those sources that have been referenced in the document.

PART 4—STYLE

CHAPTER 9—ACI TECHNICAL WRITING STYLE

For writing style questions or issues not addressed in the TCM, refer to the latest edition of The Chicago Manual of Style. The primary units are stated in in.-lb followed by SI units in parentheses.

9.1—Equations

When a single equation is part of a provision/section or sentence, use a sentence fragment with a colon before the equation.

If several equations are part of a provision/section, use a full sentence to introduce the equations.

Place simple mathematical expressions in line with text.

9.1.1 Equation numbering

If an equation is referenced by another provision/section, including an equation in a table, it must have an identification number (XX) and requires the abbreviation Eq. The equation number is the same as the provision or section number. If a provision/section contains more than one equation, add a letter suffix to the number.

9.2—Figures

Figures require an italicized caption. The word “figure” must be abbreviated as “Fig.” followed by the provision number, an Em dash (—), and the caption. Place a period at the end of figure captions.

Figure numbers are the same as the provision or section number. If a provision or section refers to more than one figure, add a letter suffix to the figure number. Begin sentences with the full word “Figure” rather than the abbreviation “Fig.”

Transmit each figure as an individual file of the highest available quality. Figures that are embedded in the Word document are usually not of the best quality and are used by ACI Staff as a reference only with respect to the general position within the document. ACI Staff places all figures in their proper position before publication. All submitted figures should have high contrast and be easy to read. Adhere to the following guidelines when submitting graphics for documents.

For electronic photos:

(a) .eps, .tif., .jpg, or high-resolution (600 dpi) .pdf files are the preferred formats. Avoid .bmp or .gif files.

(b) Photos should be a minimum of 300 dpi and need to be at least 3.33 in. wide.

(c) If possible, submit photos and figures. Digital editions of the publication are published in color, and print editions are printed in black and white.

For drawings and line art:

(a) eps, .tif., .jpg, or high-resolution .pdf files are the preferred formats. Avoid .bmp or .gif files.

(b) Avoid using fill patterns, or shading, in figures as they do not reproduce well.

(c) Use only sans-serif fonts, such as Arial or Helvetica, for labels in drawings and graphics.

(d) Avoid using fine lines and small text that can become illegible when the figure is reduced for publication.

(e) Avoid using color as a distinction between lines in a graph or photograph, as the print editions will be printed in black and white.

For printed photographs:

(a) Original high-contrast photographs result in the highest-quality printed image.

(b) If photographs cannot be reproduced with suitable quality and contrast, staff will eliminate the image and revise the text accordingly.

Videos are allowed in electronic guides and reports. The committee must submit a video that can be embedded in an electronic document; URLs to videos are not allowed. A photo is required for the printed document.

9.3—Tables

A table title is at the top, the first letter of the title is capitalized, the remaining letters are lower case, and the table caption is boldfaced. Table numbers are the same as the provision or section number. If more than one table is in a provision or section, add a letter suffix to the table number. Footnotes in tables are mandatory information and are shown at the bottom of the table. Symbols used for table notes should follow this list: *, †, ‡, §, #, ||. The left-most column should contain the conditions and the right-most column should contain the result. If a table row needs to be referenced, assign a letter to that row.

Where practical, place a variable being defined on the left side of the expression.

Use column and row lines only as necessary for clarity. Do not use lines on sides of a table.

9.4—Lists

The first word in the list is capitalized, unless it is a number, symbol, or equation. Use a complete sentence followed by a colon to introduce a list; the list itself does not need punctuation or a conjunction, such as “and,” after the penultimate term.

When using lists:

(a) Lettered—Preferred identifier for a list

(b) Numbered—Permitted when sequential actions are required or if it is a section with a letter

(c) Bulleted—Don’t use bulleted lists

Mathematical expressions in a list don’t require an equation number and don’t have units because units are implied in the calculation.

EXAMPLE

Spacing of flexural reinforcement closest to the tension face in each direction shall not exceed the smallest of (a) through (d), where stress fs shall be calculated or taken as 2/3fy

Units are not provided for constants in equations if the intent of the calculation is clear. If a code uses a constant that has unusual units, provide an explanation in the commentary. Where a provision/section involves two or more items connected by the conjunctions “and” or “or,” the conjunction shall be interpreted as follows:

(a) “And” indicates that all of the items apply

(b) “Or” indicates that any one of the items applies

9.5—Grammar

9.5.1 Numbers

Within the body of text, always spell out numbers less than 10 unless accompanied by units of measurement or a decimal place. Use numerals for numbers 10 and higher.

Use commas to separate numbers greater than 9999.

Numerals should not be used to begin a sentence. When a sentence cannot be restructured to move the numeral elsewhere in the sentence, spell out the number.

9.5.2 Hyphens

Punctuate two or more compound adjectives with hyphens or commas.

Use hyphens between whole numbers and fractions that precede a unit abbreviation.

Do not use a hyphen for an adjective composed of a number and a unit.

Hyphenate the following commonly used industry terms:

(a) Post-tensioning

(b) Saturated surface-dry

(c) Strike-off

(d) High-range water-reducing admixture

9.5.3 Serial comma

The serial comma is used in ACI technical writing. Therefore, when listing three or more items that are separated by commas, a comma should precede the word “and” or “or” before the last item.

9.5.4 Footnotes

Footnotes should not be used in provisions or sections, but they may be used in tables and figures.

9.5.5 Parentheses and brackets

Don’t use parenthetical expressions.

9.5.6 Abbreviations

Define abbreviations or acronyms in the body of the document in each section the first time they are used.

9.5.7 Capitalization

Capitalize specific types, classes, or categories; any mention of a specific figure, table, or equation; and the names of ACI certification programs.

9.5.8 Per versus “/”

Typically, a slash (solidus) should be used between unit abbreviations when one unit is being measured per the other. The exceptions are units commonly expressed as acronyms, such as mph and psi.

9.5.9 And/or

Don’t use “a and/or b;” use “a, b, or both.”

CHAPTER 10—NOTATION AND DEFINITIONS

10.1—Notation

10.1.1 General

List all notation used in the document in Chapter 2. The notation description given in Chapter 2 must be consistent within the document. Refer to the notation guide on the ACI website.

10.1.2 Rules for making notation

Notation descriptions should be unique, brief, and provide the essence of the term. Follow these rules when making a symbol:

(a) Use Roman letters for dimensions, force, and temperature

(b) Use Greek uppercase letters for mathematics

(c) Use Greek lowercase letters for dimensionless terms

(d) Subscripts may be a single letter or an abbreviation

10.1.3 Format

When listing notation, uppercase notation precedes lowercase notation of the same letter. Roman letters precede Greek letters.

10.1.4 Notation use in text

The following notation is widely used and the descriptions should not be repeated in places other than Chapter 2:

As, Av, b, bw, d, db, h, fc′, fy, fyt, ℓd, ℓn, Mn, Mu, Nn, Nu, Pu, Pn, s, t, Tn, Tu, Vu, Vn, l, and f.

Other notation description is typically given on initial use within a section. For subsequent use of the notation, use only the notation symbol.

Notation should not begin a sentence.

Use “greater than” or “less than” in text and the symbols “>” and “<” in tables and equations.

10.2—Definitions

Definitions are listed in Chapter 2 of guides, reports, and codes in alphabetical order. List definitions in Part 1 of single-item specifications and Section 1 of multi-item specifications. Define technical terms that are unique to the document. Refer to Concrete Terminology (CT) for standard definitions. The committee should not prepare a definition for non-concrete-related terms that are defined in a dictionary or by another recognized authority.

The committee should prepare a definition for concrete-related terms that are important to understand the document.

The committee may prepare a definition for a non-concrete-related term that is important to understand the document and is not adequately defined in a dictionary, but such a term will usually not be included in the CT.

The committee may duplicate terms that are defined in the CT in a document if those terms are deemed important and necessary to understand that particular document.

Definitions included in a document are not required to exactly match the CT definition, because the CT definitions are written to be general, but a document’s use of the term may be narrower.

For documents with terms defined, add the following statement:

ACI provides a comprehensive list of definitions through an online resource, “ACI Concrete Terminology,” http://concrete.org/Tools/ConcreteTerminology.aspx. Definitions provided here complement that source.

For documents with no terms defined, add the following statement:

ACI provides a comprehensive list of definitions through an online resource, “ACI Concrete Terminology,” http://concrete.org/Tools/ConcreteTerminology.aspx.

10.2.1 ACI Concrete Terminology

“ACI Concrete Terminology” (CT) is an ACI standard that provides concrete-related definitions. It is published on the ACI website: http://concrete.org/Tools/ConcreteTerminology.aspx

10.2.2 Responsibility for definitions

ACI technical committees are responsible for defining specialized terms within their documents. The CT Task Group is responsible for terms in the CT.

10.2.2.1 CT Task Group

TAC forms a CT Task Group to review submitted definitions and make recommendations to TAC regarding changing the CT. The CT Task Group chair is a member of TAC, but the task group can include members outside of TAC.

10.2.2.2 Process for submitting terminology

When ACI committee reports and guides are submitted for TAC review and approval, the definitions are automatically reviewed by the CT Task Group. The review of these terms includes a comparison with the CT definitions. Individuals and committees may also directly suggest changes to the definitions in the CT by submitting them to the Managing Director of Engineering.

10.2.2.3 Revising the CT

The CT is open for public discussion once a year. The CT Task Group reviews the comments, ballots changes per the TCM, and makes recommendations to TAC.

10.2.2.4 Referencing the CT

The CT is a standard and can be referenced in ACI documents using the following format with the appropriate year.

ACI, 2014, “ACI Concrete Terminology,” American Concrete Institute, Farmington Hills, MI, 74 pp.

10.2.2.5 Publication of the CT

Upon Standards Board agreement that ACI’s procedures have been followed, the Standards Board releases the discussion and closure for publication in an ACI periodical, on the ACI website, or both, and recommends publishing the standard. Upon publication of the closure and any approved revisions, the standard is complete.

10.2.3 Format

ACI style is to mimic the dictionary, which includes the term and the definition. Unless the term is a proper noun, it is not capitalized. The term is in bold font.

Terms are usually defined using a single phrase; definitions requiring more than one phrase should have each phrase separated by a semi-colon.

Terms are listed alphabetically.

Verbs are stated in the infinitive rather than the participle, for example, the term to be defined is “abrade” not “abrading.”

Definitions are to be simple, explicit, and understandable to nonexperts, describing the essential characteristics of the term.

When a term has more than one definition, number each definition.

Do not include details such as how things are made, used, or measured.

Do not repeat the term defined.

Do not include lists because they are rarely all-inclusive.

Refrain from using qualitative adjectives, such as special or high. If a definition uses a qualitative adjective that may connote an uncertain property, such as special or high, define the qualitative adjective explicitly.

Refrain from using terms with adjectives that connote properties without a tolerance, such as waterproof, flat, or rigid.

CHAPTER 11—UNITS OF MEASUREMENT

11.1—Policy

ACI technical documents must adhere to the ACI policy on metrication given in 14.3. IEEE/ASTM SI 10 cited in the Board policy is available as a separate publication from ASTM International.

11.2—Inch-pound units

Abbreviated units only when preceded by a numeral. Do not add an “s” to the end of a unit abbreviation to make it plural.

Derived units are formed by combining base units, supplementary units, and other derived units according to the algebraic relations linking the corresponding quantities. Several examples of derived units are given in Table 11.2. Note that some of the derived units have been given special names.

11.3—SI units

“Metric” is a somewhat generic term, as there are a number of different metric systems in use worldwide. For example, many countries use kgf/cm2 instead of Pa for stress. The International System of Units (SI) is the metric system adopted in the United States. SI includes seven base and two supplementary units and a large number of derived units. Prefixes are used with the base units and derived units to indicate powers of 10.

Derived units are formed by combining base units, supplementary units, and other derived units according to the algebraic relations linking the corresponding quantities. Several examples of derived units are gi in Table 11.3. Note that some of the derived units have been given special names.

11.4—Hard versus soft conversion

“Soft” conversions are exact mathematical conversions, rounded to an appropriate number of significant digits. “Hard” conversions are measurements in one system converted to a standard dimension in the other system that would be used in design and construction.

The ACI Board policy statement requires ACI codes and specifications be published in two separate versions, one using hard-converted SI units and the other inch-pound units. Other ACI documents must be published using dual units. The primary units are stated in in.-lb followed by SI units in parentheses.

Except for the codes and specifications, conversions may be either hard or soft, as appropriate. Soft conversions are generally appropriate for reporting measured values such as test data or dimensions of existing structures. Hard conversions are appropriate for codes and specifications and for making recommendations, setting requirements, or discussing products that are available in that system of measurement. If manufacturers have elected to make only soft conversions of their products, use their soft-converted values to describe or reference the product.

11.4.1 Soft metric conversion

To make soft metric conversions, apply the conversion factor from IEEE/ASTM SI 10 (Table 11.6.1), then round to the number of significant digits that gives an accuracy equivalent to that of the inch-pound value. Show the resulting soft-converted value in parentheses following the inch-pound value.

(a) Make a soft metric conversion of the ASTM C39/C39M test result of 4030 psi.

Use the conversion factor of 1 psi = 6.894757 kPa:

4030 psi × 6.894757 kPa/psi = 27785.87071 kPa = 27.78587071 MPa

In ASTM C39/C39M, compressive strength is reported to the nearest 10 psi, which is approximately 70 kPa. Thus, it would be appropriate to report the strength to the nearest 0.1 MPa. You would show the soft conversion in your document as:

ASTM C39/C39M test result of 4030 psi (27.8 MPa)

(b) Make a soft conversion of a distance of 125 ft.

First, use the exact conversion of 0.3048 m = 1 ft:

125 ft × 0.3048 m/ft = 38.100 m

Assuming three figures are significant, that is, distance was reported to the nearest foot, you would show the soft conversion as “a distance of 125 ft (38.1 m).”

If, however, the distance of 125 ft was obtained by rounding to the nearest 5 ft so that the value could have been anywhere between 123 and 127 ft, only two significant figures are justified, and you would write the conversion as “a distance of 125 ft (38 m).” Refer to 11.6.3 for information on rounding.

If you do not know the precision of the measurement, make a reasonable estimate. Ideally the number of significant digits retained should be such that precision is neither sacrificed nor exaggerated in making the conversion. See the documents of ACI Committee 304 for an example of soft conversion.

11.4.2 Hard metric conversion

Apply the appropriate conversion factor from IEEE/ASTM SI 10 (Table 11.6.1) and then round to the standard dimension that would be used when design and construction are in the other system of units. Show the original value followed by the hard conversion separated by the word “or” or placed in brackets.

For hard conversion of bar spacing of 16 in., first multiply by the conversion factor:

16 in. × 25.4 mm/in. = 406.4 mm

The 406.4 mm value could be rounded to 410 mm, to have the same precision as the original 16 in. But for hard conversion, it would be more appropriate to use further rounding that reflects actual field practice: “bar spacing of 16 in. or 400 mm” or “bar spacing of 16 in. (400 mm).”

Using the word “or” indicates that 400 mm is an alternative to, but not necessarily an exact equivalent of 16 in. Always consider using actual dimensions of products and equipment that are available and manufactured to SI dimensions when making a hard metric conversion, and vice-versa when going from SI to inch-pound units. The exception is if comparing test results with a specification limit that is given as decimal percent.

All ACI documents containing both inch-pound and SI units, with one as a hard conversion of the other, shall include the following statement in the first chapter:

“The paired values stated in inch-pound and SI units are usually not exact equivalents. Therefore, each system is to be used independently of the other. Combining values from the two systems may result in nonconformance with this document [guide or report, as appropriate].”

11.5—Format for unit names and abbreviations

11.5.1 General

A unit name is its full, written name, such as kilogram or microgram. Its abbreviation is the letters used to shorten it, such as kg or µg.

When spelling out the full name of a unit, print the unit name in lower case, even those derived from a proper name, such as newton, kelvin, hertz, or pascal.

Use the plural of written unit names—“several kilograms.”

Use abbreviations in conjunction with numerals (the area is 10 m2); write out names if numerals are not used, such as “area is measured in square meters.”

Indicate the product of two or more units in abbreviated form by using a dot positioned above the line—kg·m·s–2.

Do not mix names and abbreviations—write N·m or newton meter, not N·meter or newton·m.

11.5.2 Percentages, decimals, and fractions

Spell out the word “percent.”

Don’t use percent on numbers that include decimals.

Don’t use numbers with exponents.

Don’t confuse “percentage point” with “percent.” Use “percentage point” where changes to values measured in “percent” are made.

Do not spell out fractions. Use numerals.

Fractions are common for measured distances in inch-pound units.

11.5.3 Degrees

Don’t abbreviate the word “degree.” When referring to Fahrenheit or Celsius, use the degree symbol (°), not the word “degree.” When referring to an angle, spell “degree.” Don’t add a space between the number and the degree symbol.

11.6—Conversion of units

Converting from one system of units to another requires two steps: multiplying or dividing by the appropriate conversion factor, and rounding off to an appropriate number of significant digits.

11.6.1 Conversion factors

Table 11.6.1 lists conversion factors for measurements commonly used in the concrete industry.

11.6.2 Significant digits

The most difficult part of conversions is selecting the appropriate number of significant digits to use after making a conversion. Given the number of digits in the conversion factors and that conversions are usually made on a calculator, it is possible to end up with impractical converted values. In all conversions, the number of significant digits retained should be such that accuracy is neither sacrificed nor exaggerated by the conversion process.

For example, consider a concrete with a 6 in. slump.

The original unit provides one significant digit of accuracy. Converting provides four significant digits, which implies greater accuracy. Provide one to two significant digits, as appropriate. Significant digits are any digits necessary to define a value or quantity. Generally, leading zeros are not significant; trailing zeros may or may not be significant.

11.6.3 Rounding

After considering the precision of a value, round the converted value so that the same level of precision is implied as in the original value.

If the inch-pound measurement is expressed as a combination of units, convert to the smaller unit and then multiply by the appropriate conversion factor. For example, convert 5 ft 6 in. to 66 in. before converting.

Do not round off either the unit or conversion factor before multiplying.

After multiplying by the conversion factor, round off to a number of significant digits to represent the accuracy of the original measurement.

After rounding off, move the decimal point as necessary to express the SI converted value using one of the preferred prefixes. The numerical value for SI dimensions should be between 1 and 999. For example, use 1.2 km, not 1200 m.

Going back to the example of 6 in. slump in 11.6.2, the implied precision of the measurement is ±0.5 in. or approximately ±10 mm. Therefore, the appropriate conversion of 6 in. slump is 150 mm slump.

11.6.4 Reinforcing bar designations

Converting reinforcing bar designations is complicated by the various schemes used to designate bar sizes and properties. The best approach is to fully describe the bars in terms of physical dimensions such as diameter or cross-sectional area rather than using a national designation. Also, different countries use different standards in which the tensile properties of the steel may differ from those in the United States. Report the properties of the steel used such that the reader can understand the reinforcement without detailed knowledge of a particular country’s design standard.

11.6.5 Degree of precision

In the context of this section, precision refers to the lowest common working limit for a measured quantity. For example, a measuring tape is commonly shown to 1/8 in.

It is not appropriate to report or require more precision in measurements than is appropriate for the values being discussed. Refer to Table 11.6.5 for recommended degrees of precision.

The values shown in Table 11.6.5 are recommended for:

(a) Reporting new research work

(b) Preparing Project Specifications

(c) Writing general technical papers

(d) Making recommendations regarding concrete practice

Note that the same degree of precision may not be appropriate for reporting measured values and for use in a specification.

11.6.6 Mass versus weight

Mass represents the amount of substance in an object and weight represents the gravitational force acting on the object. In the inch-pound system, the pound (lb) is used as both the unit of weight (or force) and as the unit of mass. In general, there is no need to make a distinction between mass and weight except when performing a dynamic structural analysis. In this case, the mass of the object has to be used in the calculations. The mass is obtained by dividing the weight in pounds by the gravitational acceleration g, which is 32.2 ft/s2. The resulting quantity has the unit slug.

In the SI system, kilogram is the unit of mass and newton is the unit of force. The weight of an object in newtons is obtained by multiplying the mass in kilograms by 9.81 m/s2, which is the gravitational acceleration in SI units.

When converting a quantity in units of pounds to the corresponding quantity in SI units, make sure that the correct conversion factor is used. For example, pounds of cement in a mixture represent the mass (amount) of cement and would be converted to kilograms by multiplying the number of pounds by 0.4545924. On the other hand, a dead load in pounds would be converted to newtons by multiplying the number of pounds by 4.448222.

11.6.7 Decimal point and implied tolerances

If numerical limits are given in a document, the tolerances should also be given. If tolerances are not stated explicitly, then tolerances are implied by the way the limit is written. For example, if a temperature is specified as 23°C, by the rules of rounding, any temperature between 22.5°C and 23.5°C will round to 23°C and satisfy this requirement. However, if the temperature is specified as 23.0°C, then the permitted range is from 22.95°C to 23.05°C. If a numerical limit is given as a whole number, the implied tolerance is ±0.5, if a limit is given to the nearest 0.1 the implied tolerance is ±0.05, and so forth. These principles need to be considered when using decimal points in numerical limits.

PART 5—SESSIONS AND VIDEO PRODUCTS

CHAPTER 12—CONVENTION SESSIONS AND RELATED PUBLICATIONS

12.1—Committee planning

Every 3 to 4 years, ACI technical committees should plan technical sessions at ACI conventions.

Presentation materials used during technical sessions at ACI conventions are to be high quality and are expected to report new or unpublished work that adds to the existing knowledge base. Presentations that promote the use of proprietary products without sufficient, objective, supporting data are generally not acceptable.

Depending on the subject and the number of presentations that can be generated, the committee may decide to plan a session, multiple sessions, or a symposium. The guidance in this chapter applies to sessions and symposia, referred to as sessions for simplicity.

A single session has a 2-hour duration. Requests for up to four sessions are common. Requests for five or more sessions will require persuasive reasons.

A symposium is a larger event and usually consists of at least four 2-hour sessions, two of which may run concurrently. The ACI website contains the necessary forms for requesting a technical session.

12.2—TAC approval

TAC uses a two-step process to approve technical sessions:

1. Preliminary approval of a session proposal, which requires submitting basic information about the proposed session, such as the name of the moderator, the general topic, and goals of the session.

2. Final approval of the session program, which requires submitting all final details about the session, including a list of all speakers and the titles and abstracts of their presentations.

TAC uses the following criteria when approving session requests:

(a) The request form indicates a strong justification for the session, including:

(i) A statement on the scope of the session and how it would benefit the attendees

(ii) How the speakers are selected

(iii) A description of the content of the session

(iv) An abstract for each presentation

(b) The scope and outcome are relevant to ACI’s mission, including:

(i) Presentation of new documents

(ii) Emerging technology

(iii) Awareness of an established technology

(c) The session is sponsored by more than one technical committee.

(d) The session topic is relevant to the convention theme.

A technical committee may seek to publish papers related to their sessions as an ACI Special Publication (SP).

12.2.1 Session moderator training

The session moderator and co-moderator are encouraged to review the online Session Moderator Training available on the ACI website.

12.3—Sponsorship of technical sessions at non-ACI conventions

Technical committees may sponsor technical sessions that are held outside ACI conventions. The technical content of the proposed session is to be consistent with the committee’s mission and there is to be no financial obligation by the committee or the Institute. The request shall be submitted to the SP and Session Coordinator.

TAC will consider a request to publish proceedings from a technical session held outside an ACI convention. Refer to 12.5.1 for details.

12.4—Convention session procedures

12.4.1 Initiating a session

A technical committee usually volunteers to either sponsor or cosponsor a technical session, but TAC may ask a committee to assume such an assignment. If appropriate, the committee should consider inviting other committees to cosponsor the session.

Session topics should relate to the convention theme if possible, but it is not required. Potential session topics may include presentations of new committee documents, new research findings, case histories, or timely topics that the committee determines will be of interest to convention attendees.

After deciding to sponsor a session, the committee selects a session moderator who will have overall responsibility for the session. A comoderator should also be selected, and a task group may be organized to assist in selecting session presentations.

12.4.2 Preliminary TAC approval

The preliminary technical session request form is completed by the committee chair or proposed session moderator and submitted to staff from the ACI website. The proposal should indicate to TAC that the committee is planning the session with a clear objective (200 to 300 words) and has chosen session topics that will be of widespread interest.

TAC reviews the session request and accepts it, declines it, or requests additional information before making a decision. When TAC approves a session, a time slot is reserved by staff at the requested convention. The session moderator will be notified of the TAC decision by staff. A call for papers (presentations) in Concrete International may be submitted online.

12.4.2.1 Deadlines for preliminary TAC approval

The committee must submit a preliminary technical session request form to TAC at least two conventions before the convention where the technical session will be held. Staff must receive the request at least 1 week before the TAC meeting.

If the committee plans to have a call for papers, more lead time is required. Refer to 12.4.5.1 for guidance on preparing a call for papers or presentations. Refer to the ACI website for technical session and SP deadlines.

12.4.3 Time allotted for presentations

Typically, each convention session consists of 2 hours with an appropriate number of 20-minute presentations, adequate time for floor discussion, and speaker introductions. Sessions with fewer than four presentations are discouraged and sessions with more than six presentations will not be approved. Session moderators are responsible for monitoring presentation times, discussions, and the timely conclusion of each presentation and the session.

TAC and the Convention Committee require that a timetable of speakers be published in the convention program and posted outside the session room. This allows for convention attendees to plan their time to attend specific presentations.

12.4.4 Sessions honoring prominent ACI members

The ACI Board of Direction approved a policy in 1991 for honoring prominent ACI members with sessions at conventions with the requirements that:

(a) The honored individual has made an outstanding contribution to ACI and the concrete industry.

(b) The Convention Committee has the responsibility of evaluating the honored individual’s contributions and approving this event.

(c) The request for sessions honoring prominent ACI members is reviewed for technical content and approved by TAC.

(d) The proposal for sessions and dinner honoring a prominent ACI member is submitted for consideration to the Convention Committee by TAC after approving the technical content.

(e) The sessions and dinner must be approved at least one convention in advance by the Convention Committee.

(f) The sessions and dinner cannot be held to conflict with the Opening Reception, the President’s Reception, or the Concrete Mixer.

Sessions honoring prominent ACI members should adequately reflect and represent their field of activity and may consist of either multiple sessions or a symposium and are titled accordingly:

(a) Session Honoring [Name of prominent ACI member], Part 1: [Title], Part 2: [Title], etc. Sessions usually consist of a minimum of two 2-hour sessions.

(b) Symposium Honoring [Name of prominent ACI member], Part 1: [Title], Part 2: [Title], Part 3: [Title], Part 4: [Title], etc. Symposia usually consist of a minimum of four 2-hour sessions.

12.4.5 Speakers

There are several sources to identify prospective speakers such as the committee itself, known authorities in the subject field, or a call for papers in Concrete International (CI).

12.4.5.1 Calls for papers

Calls for papers or presentations are published announcements in CI requesting people to submit abstracts for presentation at ACI conventions or other meetings. Calls for papers are initiated on the ACI website. Complete all fields of the form, including whether a manuscript is expected to be submitted if the abstract is selected. Issue the call for papers or presentations as soon as TAC approves the preliminary session request. The call should indicate the session objective and list examples of potential topics for presentation. Give the name of the person to whom the abstracts are to be sent along with the deadline for receipt of abstracts and the date for final papers (for SPs). (Abstracts should be sent to the moderator 8 months before the technical session.) Refer to a current issue of CI for examples of calls for papers.

A typical time schedule is:

Actions | Time (months) before the technical session
Submit preliminary request for session | 12
Submit preliminary request for companion session SP (optional) | 18
Initiate Call for Papers (presentations) at the ACI website. There is a 3-month lead time for publication of the notice in CI. | 16
A Call for Papers is published in three consecutive issues of CI. | 13 to 11
All abstracts should be received by the moderator(s) so that the committee can select final speakers. | 8

12.4.5.2 Selecting speakers

Contact prospective speakers early, but do not make definite arrangements until receiving preliminary TAC approval. At initial contact, speakers should have an idea of the presentation subject and possible title.

Prospective speakers should prepare an abstract (2000 to 300 words) of the presentation as soon as possible and submit it to the session moderator for the committee’s consideration.

The sponsoring committee should review the submitted abstracts with regard to the theme of the session. In selecting speakers, consider the quality of past presentations by prospective speakers, if such information is available. Avoid selecting speakers who have a history of failing to appear at previous conventions to make their presentations. Submit to the Event Services Department the names and addresses of speakers who are not ACI members so that they can receive registration forms. Encourage speakers to visit the ACI website for the latest convention information.

12.4.6.3 Notifying speakers

Upon selection by the sponsoring committee, notify speakers that they are on the tentative program, inform them of the allocated presentation time, and ask them to proceed with preparing their presentation.

If paper versions of the presentations are to be considered for session or symposium publication (SP), indicate the deadline for submission of manuscripts and approximate date for notification of acceptance. Also, advise the speakers that selection of a presentation for convention session does not guarantee publication of a paper and that manuscripts are reviewed in accordance with the ACI publication policy. The Event Services Department will send appropriate forms to each session moderator for distribution to the selected speakers.

ACI does not pay speakers’ expenses ir travel, or offer an honorarium. This is stated in the letter advising a speaker that the abstract has been selected for presentation.

Notify speakers who are not selected for the program. If an SP is planned and if the abstracts have merit, those submitting the abstracts may be asked to prepare papers to be considered for the SP with other papers developed from the technical session.

12.4.6 Final TAC approval

For final approval by TAC, submit all details of the technical session, including summary of the session to be published in the convention program (200 to 300 words), the name and contact information of the moderator(s) and of each speaker, titles of their presentations, and abstracts (200 to 300 words) for each presentation. The final session request form is completed online by the session moderator, who has completed the session moderator training, and submitted to staff. These forms can be found on the ACI website. TAC will make a final review to determine whether the session will be approved. If the session receives final approval, staff will notify the moderators and the committee chair. The information in the final approval form will be used in the preconvention program mailing, in CI, and other publicity. The sponsoring committee should arrange for appropriate local publicity, specialized publicity, and attendance from particular groups that might be interested in the session.

The committee may not alter the details of the session once final approval has been granted without the permission of TAC. Submit any requested changes to the SP and Session Coordinator.

12.4.6.1 Deadlines for final TAC approval

Sessions must be submitted for final TAC approval no later than the Friday after the end of the preceding convention. Failure to meet the deadline will postpone the TAC review and thus the session may be postponed or not approved.

12.4.7 Staff assistance

ACI Event Services staff will secure the necessary standard audio visual equipment for the session once staff is advised of the committee’s needs.

Staff sends copies of authors’ guides and guidelines for preparing slides to session moderators for distribution to the speakers.

12.4.8 Presentation materials

Quality slides are important to the overall quality of a presentation. TAC encourages speakers to prepare slides using Microsoft PowerPoint®. Presentations should be professional in appearance. Presenters should refrain from the use of brand names and specific product endorsement whenever possible. Small logos are acceptable.

12.5—Publication of session papers in an ACI Special Publication

The committee may wish to publish papers from convention sessions or a symposium in a Special Publication (SP). A minimum of 10 papers is recommended for an SP. ACI SPs are published in CD-ROM format. Individual authors are encouraged to submit their papers for consideration by an ACI periodical if a collection of papers as an SP is not planned. An SP may include papers from convention sessions, papers submitted but not presented, and other papers dealing with the same subject matter received by the Institute and approved by the committee for inclusion in the SP. Papers must be original unless otherwise approved by TAC.

Ideally, the SP should be available at the time of the technical session. This requires careful planning, coordination with the SP and Session Coordinator, and a rigid timetable for manuscript submissions and reviews. Technical session and SP deadlines are available on the ACI website.

Final manuscripts and all backup material must be submitted at least 3 months before the technical session to ensure that the SP will be available for sale at the convention. In many cases, however, the SP will be published after the technical session. In this case, final manuscripts and all backup material must be submitted to the SP and Session Coordinator within 2 years of the technical session.

Information on obtaining TAC preliminary and final approvals and preparing an SP can be found on the ACI website.

12.5.1 SP from conferences outside ACI conventions

TAC will consider requests to publish proceedings from technical sessions held at conferences outside an ACI convention, provided the following requirements are met:

(a) The conference must have formal cosponsorship by ACI

(b) The technical session must be associated with an ACI committee

(c) A financial agreement must be in place for publishing the SP

(d) ACI’s SP procedures must be followed on all papers

Cosponsorship by ACI requires the approval of the ACI Executive Vice President. Submit the request, along with a discussion of the financial implications for ACI to the SP and Session Coordinator.

12.5.2 SP honoring an individual

SPs honoring an individual can have a title and preface dedicated to the individual. The preface should be no more than 1 page (approximately 600 words). The preface should discuss the individual’s contribution to the concrete industry. All papers should be technical. Nontechnical papers are not allowed.

12.5.3 Preliminary TAC approval

When a decision is made to publish an SP, the committee should submit an online preliminary SP request form to the SP and Session Coordinator before proceeding with production of an SP. This request should:

(a) Identify the SP editor(s), including contact information

(b) Provide a brief overview of the proposed SP

(c) List proposed paper titles and authors, including their contact information (this requirement may be waived if a call for papers is planned to be issued in Concrete International)

(d) Provide a timetable leading to the publication of the SP

TAC approves or declines preliminary SP requests based on appropriateness of the subject matter and anticipated usefulness of the publication.

12.5.4 Preparation of papers

Information on the ACI website includes:

(a) Information for SP editors (processing information, initial and final approval requirements, initial and final paper submission checklists, calls for papers, review forms, and paper awards criteria)

(b) Information for SP paper authors (manuscript guidelines and copyright transfer form)

All SP papers, including figures, require dual units. SI (metric) or inch-pound units of measurement can be used as primary units. The secondary units must be provided in parentheses.

Some papers presented at a convention session might not be published. Experience shows that some oral presentations cannot be adapted to written format. After the SP editor selects presentations for the session or symposium publication, notify the presenters promptly that an SP is planned, and invite them to prepare a manuscript for review. Give authors a firm deadline for submission of manuscripts. If possible, provide original manuscripts before the actual presentation.

12.5.5 Review of papers

TAC generally delegates coordinating the reviews of SPs to the SP editor. The editor selects at least two qualified reviewers for each paper. Except in special cases approved by TAC before papers are reviewed, a reviewer must not review more than 25 percent of the papers for any SP or 10 papers, whichever is less.

The editor should provide the SP and Session Coordinator with a list of the reviewers and how many papers each reviewer has been assigned. When the SP editor has authored one of the papers, the editor shall submit that paper to the SP and Session Coordinator, who will assign anonymous reviewers.

Reviewers follow the criteria listed in the manuscript review forms available on the ACI website. Reviews should be returned to the editor within 30 days. At least two reviewers must recommend publication. If one of the two reviewers does not recommend publication, a third reviewer shall be assigned.

The editor provides authors with copies of anonymous review comments and instructions for submitting final manuscripts. Authors must address review comments in preparing their final manuscripts, and must provide an explanation to the editors why particular review comments were not incorporated into the final manuscript.

The editor is responsible for determining that the final manuscript addresses all review comments in a satisfactory manner. Final manuscripts for all papers, along with all reviews, a preface providing background information and a summary of the SP contents, and any other information requested are then submitted to ACI staff for final TAC approval.

12.5.6 Final TAC approval

For final TAC approval, the committee must submit a final SP request to the Managing Director of Engineering, including the completed SP, the table of contents, preface, all papers, the reviews for all papers with the reviewers’ names, and the copyright transfer forms. TAC reviews the final documentation and verifies that procedures have been followed. Following TAC approval, ACI staff prepares materials for publication of the SP.

CHAPTER 13—DEVELOPMENT OF VIDEO PRODUCTS

ACI technical committees may decide that, for a particular topic, the most effective means of communication is a video. The distribution of video products is a rapidly moving area of technology and it is anticipated that videos will be produced in a standard movie format for playback on computers. The movie files may be distributed through the ACI Concrete Knowledge Center, as part of a Special Publication published on a DVD, or by other methods approved by TAC.

Videos are to be professional quality and report information that adds to the existing knowledge base. Videos that describe proprietary products without sufficient, objective, supporting data are not acceptable.

The ACI logo and committee sponsorship should be visually shown at the beginning of the video and in ending credits.

13.1—Initial approval

The technical committee votes to approve the video concept in accordance with Chapter 3. The concept should include the scope and goals of the video.

After committee approval, the video concept is to be submitted to TAC.

13.2—Funding request

After TAC approves of the concept, and if the committee requests funds to create the video, the committee should contact the Managing Director of Engineering.

13.3—Secondary approval

The technical committee votes to approve a detailed description of the proposed video in accordance with 3.2. The details should include a story board and script.

After committee approval, the video description is to be submitted to TAC.

Upon TAC approval, Institute resources can be expended by authorized staff.

13.4—Final approval

After completion, the technical committee ballots to approve the video. A passing ballot requires 75 percent of voting members to vote affirmative, and negatives do not require resolution.

After committee approval, the video is submitted to TAC.

Upon TAC approval, the video is adopted. The adoption date is the month the video is initially available to the public. The video will be posted on the member side of the committee web page.

TAC will recommend a distribution method to ACI’s Executive Vice President.

13.5—Revision

The committee may not alter the video without TAC approval.

A revision of a video should follow the same process as the creation of a video; that is, initial approval, funding request (if needed), approval of detailed description of the revision, and final approval.

PART 6—POLICIES

CHAPTER 14—DOCUMENT-RELATED INSTITUTE POLICIES

14.1—Publication

14.1.1 Stand-alone document

All technical committee documents are published in electronic and hard copy formats, and are available for purchase.

14.1.2 ACI Manual of Concrete Practice

The ACI Manual of Concrete Practice (MCP) is published annually and contains a majority of ACI’s technical committee documents. TAC decides not to include an entire document in the MCP, a synopsis or notice is included in the MCP.

14.2—Legal and directional statements

Under certain conditions, ACI documents require introductory or disclaimer statements to be included when the documents are printed.

14.2.1 Disclaimer on first page of guides and reports

Nonmandatory language documents shall have the following statement on the first page:

“ACI Committee Reports, Guides, and Commentaries are intended for guidance in planning, designing, executing, and inspecting construction. This document is intended for the use of individuals who are competent to evaluate the significance and limitations of its content and recommendations and who will accept responsibility for the application of the information it contains. ACI disclaims any and all responsibility for the stated principles. The Institute shall not be liable for any loss or damage arising there from. Reference to this document shall not be made in contract documents. If items found in this document are desired by the Architect/Engineer to be a part of the contract documents, they shall be restated in mandatory language for incorporation by the Architect/Engineer.”

14.2.2 Disclaimer on inside front cover

All ACI documents shall have the following statement on the inside front cover:

“Copyright by the American Concrete Institute, Farmington Hills, MI. All rights reserved. This material may not be reproduced or copied, in whole or part, in any printed, mechanical, electronic, film, or other distribution and storage media, without the written consent of ACI.

“The technical committees responsible for ACI committee reports and standards strive to avoid ambiguities, omissions, and errors in these documents. In spite of these efforts, the users of ACI documents occasionally find information or requirements that may be subject to more than one interpretation or may be incomplete or incorrect. Users who have suggestions for the improvement of ACI documents are requested to contact ACI via the errata website at http://concrete.org/Publications/DocumentErrata.aspx. Proper use of this document includes periodically checking for errata at http://concrete.org/Publications/DocumentErrata.aspx for the most up-to-date revisions.

“ACI committee documents are intended for the use of individuals who are competent to evaluate the significance and limitations of its content and recommendations and who will accept responsibility for the application of the material it contains. Individuals who use this publication in any way assume all risk and accept total responsibility for the application and use of this information.

“All information in this publication is provided ‘as is’ without warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose or non-infringement.

“ACI and its members disclaim liability for damages of any kind, including any special, indirect, incidental, or consequential damages, including without limitation, lost revenues or lost profits, which may result from the use of this publication.

“It is the responsibility of the user of this document to comply with all applicable laws and regulations of any nature, and to establish environmental and/or health and safety practices appropriate to the specific circumstances involved with its use. ACI does not in any way represent, imply, or warrant that the information in this document complies with any or all laws, nor does it make any representations with regard to environmental and/or health and safety issues and the use of this document. The user must determine the applicability of all laws and regulatory limitations before applying the document and must comply with all applicable laws and regulations, including but not limited to, United States Occupational Safety and Health Administration (OSHA) health and safety standards.

“Participation by governmental representatives in the work of the American Concrete Institute and in the development of Institute standards does not constitute governmental endorsement of ACI or the standards that it develops.”

14.2.3 Statement describing ITG reports

The first page of Innovative Task Group (ITG) documents shall include the following statement:

“ACI encourages the development and appropriate use of innovative technologies through the publication of the Innovation Task Group Documents. These documents present information and recommendations based on available test data, technical reports, limited experience with field applications, and the opinions of committee members. The presented information and recommendations, and their basis, may not be as extensively developed and tested as those for more mature technologies. This document identifies areas in which information is believed to be less fully developed, and describes related research needs. The professional using this document should understand the limitations of this document and exercise judgment as to the appropriate application of this innovative technology.”

14.2.4 Statement describing Emerging Technology Reports

The first page of an ETR shall include the following statement:

“ACI encourages the development and appropriate use of new and emerging technologies through the publication of the Emerging Technology Reports. These documents present information and recommendations based on available test data, technical reports, limited experience with field applications, and the opinions of committee members. The presented information and recommendations, and their basis, may not be as extensively developed and tested as those for more mature technologies. This report identifies areas in which information is believed to be less fully developed, and describes related research needs. The professional using this document should understand the limitations of this document and exercise judgment as to the appropriate application of this emerging technology.”

14.2.5 Translation disclaimer

The first page of a translated document shall include the following statement:

“The official version of an ACI document is the English version. A translation of an ACI document is for the convenience of users. Care has been taken to ensure that the translation is correct; however, ACI does not guarantee its accuracy. Official interpretation of an ACI document shall be based only on the English version.”

14.2.6 Metric unit conversion disclaimer

The first page shall include the following statement:

“The official version of this ACI document uses inch-pound units. A conversion of an ACI document into SI units is for the convenience of users. Care has been taken to ensure that the conversion is correct; however, ACI does not guarantee its accuracy. Official interpretation of this ACI document shall be based only on the U.S. customary units.”

14.2.7 Patent disclaimer

Documents including patented items shall have the following statement on the first page:

“This ACI document contains requirements that can, at the time of the document’s adoption by ACI, be satisfied practicably only by use of a patented material, product, process, procedure, or apparatus. ACI does not endorse this technology. The selection of any design methodology or use of any patented technology is at the option of the user.”

14.2.8 Certification statement

Documents including certification shall have the following statement:

“The materials, processes, quality control measures, and inspections described in this document should be tested, monitored, or performed as applicable only by individuals holding the appropriate ACI Certification or equivalent.”

14.3—ACI metrication policy

The ACI Board of Direction approved the following policy on metrication:

The general policy of ACI shall be that all new and revised ACI codes and specifications shall be published in two separate versions, one using inch-pound units and one using hard-converted SI units. Exceptions to this policy will depend upon industry needs and TAC approval. All new and revised ACI standards and other publications shall use dual units. Nonarchival information, such as visual materials used at convention sessions, shall use units of measurements selected by the author. All conversions shall conform to the latest version of IEEE/ASTM SI 10, supplemented where applicable by ASTM E621. In hard conversions, due consideration shall be given to uniformity among Institute documents and to availability of metric products for concrete construction.

ACI Board Committees shall establish provisions to implement this policy.

TAC shall review and recommend revisions to this policy to the Board on an as-needed basis to meet the demand for metrication of ACI documents.

INDEX

A

ACI Concrete Terminology, 10.2

Submitting, 10.2.2.2

Referencing, 10.2.2.4

Revising, 10.2.2.3

ACI Foundation, 2.8.1

ACI membership, 1.6, 1.7, 1.8

Adoption, 4.2.2, 4.5.5, 7.3.2

Agenda, 2.3.5, 2.3.8

American National Standards Institute (ANSI), 4.1, 4.5.6

Appeals, 3.4.5, 4.6, 7.6

Committee document actions, 4.6, 7.6

Membership action, 1.7.8

Appendixes

Codes, 5.2.3

Reports, 8.1.4

Specifications, 6.5

Appointments, 1.7.2, 1.7.3, 1.7.5

Associate members, 1.6.2

ASTM International, 4.1.2.2, 4.1.2.3

Authored references, 8.3

B

Backmatter, 5.2.3

Balance of interests, 1.8

Balloting committee documents, Chapter 3

Abstention, 3.2.5.4

ACI 318 exception, 3.3.2

Adding new members, 1.7.2

Affirmative votes, 3.2.5.1

Affirmative votes with comments, 3.2.5.2

Analysis of results, 3.2.6, Fig. 3.2.1

Appeals, 3.4.5

Distribution, 3.2.4

Format, 3.2.2

Initiation, 3.2.2

Letter ballots, 3.1, 3.2

Meeting, 3.3

Negative votes, 3.4

- Appeals, 3.4.5

- Nonpersuasive, 3.4.3

- Persuasive, 3.4.4

- Resolution of, 3.2.5.3, 3.4, Fig. 3.4

- Unrelated, 3.4.2

- Withdrawal, 3.4.1

Negative votes with reason, 3.2.5.3

Nonvoting members, 3.2.5.6

Not returned, 3.2.5.5

Passage of items, 3.2.1, 3.3.1

Patented items, 3.2.8

Proxy, 3.1

Revising and reballoting, 3.2.6.2

Special procedures, 3.6

Subcommittee, 3.2.7

Summaries, 3.5

Time frame, 3.2.3

Updating, 3.2.6.1

Votes, 3.2.5

Voting methods and rules, 3.1

Biannual report, 2.4.6

Bibliographies, 8.3

Bulleted lists, 9.4

C

Certification, 6.2.6.5, 6.2.6.6, 14.2.8

Chairs, committee, 1.9.1

Appointment, 1.9.1.3

Candidates, 1.9.1.2

Qualifications, 1.9.1.1

Resignation, 1.9.1.5

Responsibilities, 1.9.1, 2.5

Term, 1.9.1.4

Voting, 3.2.5

Chapters, 7.3.7

Checklists, 6.1, 6.2.11

Format, 6.2.9.4

Optional, 6.2.9.3

Mandatory, 6.2.9.2

Classification of members, 1.6

Appeal, 1.7.8

Consultants, 1.8.4

General Interest, 1.8.3

Producer, 1.8.1

User, 1.8.2

Code cases, 4.1.1.2

Codes, Chapter 5

Code requirements, 4.1.1.1

Commentary, 5.5

Format, Chapter 5

Hard versus soft conversion, 11.4

Language, 5.3

Metrication policy, 14.3

Organization, 5.2

References, 5.4

Committees, Part I

Communication, 2.4

Discharge, 1.4.2.1, 1.4.3

Establish, 1.4.1

Expenses, 2.8

Goals, 2.2

Joint, 1.5, 1.7.3

Meetings, 2.3

Membership, 1.6, 1.7, 1.8

Mission, 2.1

Officers, 1.9

Organization, Chapter 1

Reorganization, 1.4.2

Subcommittees, 1.2.3

Conferences outside of ACI, 12.3

Consulting members, 1.6.3

Convention sessions, 2.2.3, Chapter 12

Call for papers, 12.4.5.1

Deadlines, 12.4.6.1

Final approval, 12.4.6

Honoring prominent ACI members, 12.4.4

Initiating a session, 12.4.1

Moderator training, 12.2.1

Preliminary approval, 12.4.2

Presentation materials, 12.4.8

Speakers, 12.4.5

Staff assistance, 12.4.7

Special publications, 12.5

- ACI awards, 2.6

- Final approval, 12.5.6

- Preliminary approval, 12.5.3

- Preparation of papers, 12.5.4

- Publication of session papers, 12.5

- Review of papers, 12.5.5

Conventions, Chapter 12

Conversion factors, 11.6.1

Coordination, 4.2.6, 7.3.5

Documents, 4.2.6.4, 4.2.6.5, 7.3.3, 7.3.5.1

Terminology, 4.2.6.8, 7.3.5.3

With other committees, 2.4.5, 4.2.6.4, 7.3.5.1

With construction liaison committee, 4.2.6.6, 7.3.5.2

Copyright, 3.2.8, 4.2.8, 14.2.7

D

Decimals, 11.5.2

Definitions

ACI Concrete Terminology, 7.3.5.3

Code chapters, 5.2.2

Description of chapters, 8.1.3

Format, 10.3

Guides and reports, 8.1.1

Multi-item specification, 6.2.6.3

Single-item specification, 6.2.1

Style, 10.2

TAC review, 4.2.6.8

Degree of precision, 11.6.5

Design standards, 4.1.1

Discharge committee membership, 1.4.2.1

Disclaimers and statements, Chapter 14

Certification, 14.2.8

Emerging Technology Report, 14.2.4

General, 14.2.2

ITG introductory, 14.2.3

Nonmandatory language document, 14.2.1

Patented items, 14.2.7

Translation, 14.2.5

Unit conversion, 14.2.6

Documents, Part 2, Part 3

Appeal, 4.6, 7.6

Approval, 4.5.6, 7.5.4.1

By chapters, 7.3.7

Closure, 4.5.3, 4.5.4

Comments, 3.2.5.2, 3.2.5.6, 4.4.4.2, 7.5.4.2

Coordinating, 2.4.5, 4.2.6, 4.2.6.4, 4.2.6.5, 4.2.6.6, 4.2.6.7, 4.2.6.8, 7.3.5

Copyright, 3.2.8, 4.2.8, 14.2.7

Date of adoption, 4.2.2, 4.5.5, 7.3.2

Development, 4.2, 7.3

Drafts, 4.2.5, 7.3.4

Not approved, 4.4.4.3, 7.5.4.3

Publication policy, 14.1

Reapproval, 4.2.2.1, 7.3.2.1

References, 5.4, 6.4, 8.3

Review, 4.2.4, 4.4, 4.4.2, 4.4.3, 7.5.3

Revisions, 4.2.2.2, 7.3.2.2

TAC review, 4.4, 7.5

- Appeal, 4.6, 7.6

- Approval, 4.4.4.1, 7.5.4.1

- Decision, 4.4.4, 7.5.4

- Review group, 4.4.3.1, 7.5.3.1

- Response to comments, 4.4.4.2, 7.5.4.2

Types, 4.1, 7.2

- Acceptance criteria, 4.1.1.3

- Code case, 4.1.1.2

- Code, 4.1.1.1

- Construction specification, 4.1.2.1

- Construction standard, 4.1.2

- Design standard, 4.1.1

- Design specification, 4.1.1.4

- Emerging Technology Report, 7.2.2.1

- Guide, 7.2.1

- Handbook and manual, 7.2.1.1

- Innovation task group, 1.3, 4.2.3, 7.3.2.4, 14.2.3

- Inspection services specification, 4.1.2.4

- Material specification, 4.1.2.2

- Provisional standard, 4.5.2.2

- Reference specification, 4.1.2.1, 4.1.2.2, 4.1.2.4, 4.1.2.5, Chapter 6

- Report, 7.2.2

- Standard, Chapter 4

- Special publication, 12.5

- Technical Notes (TechNotes), 7.2.1.2

- Test methods, 4.1.2.3

- Testing services specification, 4.1.2.5

Units of measurement, Chapter 11

Withdrawals, 4.2.2.3, 7.3.2.3

Documents not requiring standardization, Chapter 7

Emerging Technology Reports, 7.2.2.1

Guides, 7.2.1

Handbook and manuals, 7.2.1.1

Reports, 7.2.2

Technical Notes (TechNotes), 7.2.1.2

Documents requiring standardization, Chapter 4

Acceptance criteria, 4.1.1.3

Code cases, 4.1.1.2

Construction specification, 4.1.2.1

Construction standards, 4.1.2

Design specification, 4.1.1.4

Design standard, 4.1.1

Inspection services specification, 4.1.2.4

Materials specifications, 4.1.2.2

Reference specifications, 4.1.2.1, 4.1.2.2, 4.1.2.4, 4.1.2.5

Standards, 4.1.1, 4.1.2

Test methods, 4.1.2.3

Testing services specification, 4.1.2.5

E

Emerging Technology Reports, 7.2.2.1

Disclaimer, 14.2.3

Equations, 9.1

Expenses, 2.7.4

F

Figures, 9.2

Format

ACI Concrete Terminology, 10.2.2.4, 10.2.3

Author/date references, 5.5.3, 8.3

Codes, Chapter 5

Construction specifications, Chapter 6

Forward to checklists, 6.4.2

Guides and reports, Chapter 8

Letter ballot, 3.2.2

Mandatory Requirements checklists, 6.2.9.4

References, 5.4, 5.5.2, 6.2.6.4, 6.4, 8.3

Unit names and abbreviations, 11.5

Video, Chapter 13

Footnote, 9.5.4

Fractions, 11.5.2

Frontmatter

Codes, 5.2.1

Guides and reports, 8.1.2

Multi-item specification, 6.2.3

Single-item specification, 6.2.1

G

General disclaimer, 14.2.2

Grammar, 9.5

Abbreviations, 9.5.6

And/or, 9.5.9

Capitalization, 9.5.7

Footnotes, 9.5.4

Hyphens, 9.5.2

Numbers, 9.5.1

Parentheses and brackets, 9.5.5

Per versus “/”, 9.5.8

Serial comma, 9.5.3

Guides, Chapter 7

Disclaimer, 14.2.1

Emerging Technology Report (ETR), 7.2.2.1

Format, 8.1

Language, 8.2

- Acceptable/unacceptable terminology, 8.2.7

- Active versus passive voice, 8.2.6

- Clarity, 8.2.2

- Conditional phrases, 8.2.5

- Gender-specific, 8.2.3

- Gender principles, 8.2.1

- Vague, 8.2.4

References, 8.3

TechNotes, 7.2.1.2

Guides and reports, Part 3

Appeal processes, 7.6

Cosponsored, 7.3

Description, 7.2

Development, 7.3

- Coordination of information, 7.3.5

- Cosponsored documents, 7.3.3

- Draft document, 7.3.4

- Editorial subcommittee, 7.4.5

- Editorial review, 7.4.5, 7.5.2

- Existing, 7.3.2

- Guides and reports authored by ACI chapters, 7.3.7

- ITG, 7.3.2.4

- New guides and reports, 7.3.1

- Patented items, 3.2.8

- Reapproval, 7.3.2

- Revision, 7.3.2.2

- Translation of ACI documents, 7.3.6

- Updating existing documents, 7.3.2

- Withdrawal, 7.3.2.3

Errata, 7.2.3

Format and language, Chapter 8

TAC review process, 4.4, 7.5

- Appeal, 4.6, 7.6

- Developing guides and reports, 7.3

- Editorial review, 7.4.5

- Procedures, 4.2

- Session deadlines, 12.4.6.1

- Session requests, 12.4.2

- Staff editorial review, 7.5.2

- Submitting guides and reports, 7.5.1

- Submitting terminology, 10.2.2.2

- TAC decision, 7.5.4

- TAC review, 7.5.3

Writing, 7.4

- Format, 7.4.1

- Notation, 7.4.3

- Style, 7.4.4

- Units, 7.4.2

H

Handbooks and manuals, 7.2.1.1

Hard metric conversion, 11.4.2

I

Inch-pound units, 11.2

Innovation Task Groups (ITGs), 1.3, 1.4.1.2

Discharge, 1.4.3

Disclaimer, 14.2.3

Establish, 1.4.1.2

Membership, 1.6.1.5, 1.6.3.5

Intellectual property, 3.2.8, 4.2.8

J

Joint committees, 1.5.2, 1.6.2.5, 1.7.3

K

Keywords

Codes, 5.2.1

Guides and reports, 8.1.1, 8.1.2

Specifications, 6.2.3, 6.2.5

L

Language

Codes, Chapter 5

Construction specifications, Chapter 6

Guides and reports, Chapter 8

Liaison members, 1.1, 1.2.3, 1.2.3.3, 1.6.4

Lists, 9.4

M

Manual of Concrete Practice, 4.2.2, 14.1.2

Material specifications, 4.1.2.2, 4.1.2.3, 4.2

Meetings, 2.3

Agenda, 2.3.8

Closed, 2.3.6

Minutes, 2.3.9

Quorum, 2.3.2

Visitors, 2.3.7

Members, committee, 1.6, 1.7, 1.8, 1.9.5

Appeal, 1.7.8

Application, 1.7.1

Appointments, 1.6.1.5, 1.6.2.5, 1.6.3.5, 1.6.4.5, 1.7.2, 1.7.3, 1.7.5

Associate, 1.6.2, 1.7.1

Balance of interests, 1.8

Categories, 1.6

Chairs, 1.9.1, 2.3.1, 2.4, 2.5

Classification, 1.8

Consultants, 1.8.4

Consulting, 1.6.3.5, 1.8.4, 3.2.5.6

General interest, 1.8.3

Joint committees, 1.5.2, 1.7.3

Liaison, 1.2.3, 1.2.3.3, 1.6, 1.6.4, 4.2.6.6, 7.3.5.2

Not appointed, 1.7.2, 1.7.5

Officers, 1.9, 2.3.4, 2.4

Overlap, 1.4.1.1, 1.4.1.2, 1.7.4, 2.4.4, 4.2.6.2, 4.2.6.4, 4.2.6.5, 4.4.3, 7.3.3, 7.3.5, 7.5.3

Privileges, 1.6.1.3, 1.6.2.3, 1.6.3.3, 1.6.4.3

Producer, 1.8.1

Qualifications, 1.6.1.1, 1.6.2.1, 1.6.3.1, 1.6.4.1, 1.9.1.1

Questionnaire, 1.4.2.2, 2.4.7

Reappoint, 1.6.2.4, 1.6.4.4, 1.8.5, 1.9.1.3, 1.9.1.4

Requirements, 1.6.1.2, 1.6.2.2, 1.6.3.2, 1.6.4.2, 1.8

Resignation, 1.7.7

Restrictive, 1.7.5.1

Rosters, 1.8, 5.2.1, 6.2.5, 8.1.2

Secretary, 1.9.3

Subcommittees, 1.2, 1.2.1, 1.2.2, 1.2.3, 3.2.7

Task groups, 1.2.4, 1.3, 4.2.7

Termination, 1.7.6, 1.7.8, 1.8.5

Terms, 1.6.1.4, 1.6.2.4, 1.6.3.4, 1.6.4.4, 1.9.1.4

Turnover, 1.7.2

User, 1.8.2, 1.8.4

Vice chair, 1.9.2

Voting, 3.1, 3.2, 3.3, 3.4, 3.5

Metrication, Chapter 11, 14.3

Minutes, 2.3.8

Letter ballots, 3.2, 3.4

Post on website, 2.3.5, 2.3.9, 2.4.3

Privileges, 1.6.1.3, 1.6.2.3, 1.6.3.3, 1.6.4.3

Missions, 2.1, 2.4.5, 4.2.6.2, 4.2.6.5

Multi-item specification

Definitions, 10.2

Format, 6.2

Referenced standards, 6.4

N

Negative votes, 3.2.5.3, 3.4

Persuasive, 3.4.4

Nonpersuasive, 3.4.3

Resolution, 3.2.5.3, 3.4, 3.4.2, 3.4.4, 3.5

Unrelated, 3.4.2, 3.4.5

Withdrawal, 3.4.1

Nonmandatory language document disclaimer, 14.2.1, 14.2.2

Notation

Codes, 5.2.2

Guides and reports, 8.1.1

Style, Chapter 10

O

Officers, 1.9, 2.4.1

Organization and operation of technical committees, Part 1

Overlapping membership, 1.7.4

P

Patented items, 3.2.8, 4.2.8

Disclaimer, 14.2.7

Percentages, 11.5.2

Photographs, 9.2

Policies, ACI, Chapter 14

Publication, 14.1

Legal and directional, 14.2

Metrication, 14.3

Producer, 1.8.1

Provisional standard, 4.5.2.2

Public discussion, 4.2, 4.5

Publication

Balance of interest, 1.8

Circulating draft standards, 4.2.5

Emerging Technology Report, 7.2.2.1

Restrictions, 7.3.4

Revising, 4.2.2, 7.3.2.2

TAC review, 4.4.3, 7.5.3

Publications

Guides and reports, Part 3

Special Publication (SP), 2.2.3, 12.1, 12.4.5.3, 12.5

Standards, Part 2

Q

Qualifications, 1.6.1.1, 1.6.2.1, 1.6.3.1, 1.6.4.1, 1.9.1.1

Questionnaires, 2.4.7

Quorum, 2.3.2

R

Reapproval, 4.2.2.1

Reference specifications, 4.1.2.1, 4.1.2.2, 4.1.2.4, 4.1.2.5

Referenced standards

Codes, 5.2.2, 5.4.3

Construction specifications, 6.4

Multi-item specifications, 6.2.3

Single-item specifications, 6.2.1

Standards in specifications, 6.4.1

References, 5.4, 6.4, 8.3

ACI Concrete Terminology, 10.2.1, 10.2.2

Code, 5.2.2, 5.4.1, 5.5.2

Commentary, 5.5.2

Construction Specification, 6.1, 6.4

Foreward to Checklists, 6.2.9.1

Guides, 8.3

Notes to Specifiers, 6.2.9.1

Referenced standards, 6.4

Reports, 8.3

Reinforcing bar designations, 11.6.4

Reorganization, committee, 1.4, 1.4.2

Reports, Part 3

Development of, 7.3

Disclaimer, 14.2.1

Emerging Technology Report (ETR), 7.2.2.1

Format, 8.1

Language, 8.2

- Acceptable/unacceptable terminology, 8.2.7

- Active versus passive voice, 8.2.6

- Clarity, 8.2.2

- Conditional phrases, 8.2.5

- Gender-specific, 8.2.3

- Vague, 8.2.4

Resignations, 1.7.7

Revision, 4.2.2, 4.2.2.2, 7.3.2.2

Robert’s Rules of Order, 2.3.1

Roster

Cosponsored guides and reports, 7.3.3

Cosponsored standards, 4.2.6.5

Codes, 5.2.1

Guides and reports, 8.1.2

Letter ballot passage, 3.2.1

Specifications, 6.2

Subcommittees, 1.2.3

Rounding, 11.6.3

S

Secretary, 1.9.3

Seminars, educational, 2.2.4

SI units, 11.3

Significant digits, 11.6.2

Single-item specification

Definitions, 10.2

Format, 6.2

Referenced standards, 6.4

Soft metric conversion, 11.4.1

Specifications

Construction, 4.1.2.1

Design, 4.1.1.4

Format and language, Chapter 6

Inspection, 4.1.2.4

Materials, 4.1.2.2

Multi-item, 6.2.3

Reference, 4.1.2.1, 4.1.2.2, 4.1.2.4, 4.1.2.5

References, 6.4

- Checklists, 6.4.2

- Standards, 6.4.1

Single item, 6.2.1

Testing, 4.1.2.5

Sponsorship of technical sessions at non-ACI conventions, 12.3

Staff assistance, 2.9, 12.4.7

Staff review, 4.4.2, 7.5.2

Standardization procedures, 4.2

Standards board, 4.5

Style, Part 4

Conversions, 11.4

Definitions, 10.2

Dual units, 11.4

Editorial review, 4.2.4

Equations, 9.1

Figures, 9.2

Grammar, 9.5

Lists, 9.4

Notation, 10.1

Tables, 9.3

Technical writing, Chapter 9

Units of measurement, Chapter 11

Subcommittees, 1.2.3

Ballots, 1.2.3, 3.2.7

Designation, 1.2.1

Editorial, 1.2.3.1

Liaison, 1.2.3.3

Comparison with Task Groups, 1.2.2

Steering, 1.2.3.2

Symposium publications, 2.2.3, 12.3, 12.4, 12.5

Synopsis

Codes, 5.2.1

Guides and reports, 8.1.2

Specifications, 6.2.1, 6.2.3

T

Table of contents

Codes, 5.2.1

Guides and reports, 8.1.1

Specifications, 6.2.1, 6.2.3

Tables, 9.3

Task groups, 1.2.4

Technical activities committee (TAC), 1.1

American National Standards Institute (ANSI), 4.1, 4.5.6

Appeals, 3.4.5, 4.6, 7.6

Approval

- Chairs, 1.9.3, 1.9.4

- Circulating drafts, 4.2.5, 7.3.4

- Design standards, 4.1.1

- Committee closure, 4.5.3

- Convention sessions, 2.2.3, 12.2, 12.4.2, 12.4.2.1

- Develop new document, 2.2.1

- Discharge committees, 1.4.3

- Establish committees, 1.4.1

- Guides and reports, 7.3.1, 7.3.2

- ITG formation, 1.3

- Material specifications, 4.1.2.2

- Metrication, 14.3

- New standard, 4.2.1

- Outside publications and products, 2.2.5, 12.5.1, Chapter 13

- Remove ETR designation, 7.2.2.1

- Responding to TAC comments, 4.4.4.2, 7.5.4.2

- Session papers, 2.2.3, 12.4.2, 12.4.6, 12.5

- Speakers, 12.4.5.2, 12.4.6

- Terminology, 4.2.6.8

- Translation, 4.2.7, 7.3.6

- Units of measurement, 4.3.2, 7.4.2

- Withdrawal of document, 7.3.2.3

Biannual reports, 2.4.6

Correspondence, 2.4.3

TAC subcommittees

- Construction Standards Committee (TCSC), 1.1.2

- Design Standards Committee (TDSC), 1.1.1

- Repair and Rehabilitation Committee (TRRC), 1.1.3

Technical committee certificates, 2.7

Technical committee operation, Chapter 2

Technical notes (TechNotes), 7.2.1.2

Terms, membership, 1.6.1.4, 1.6.2.4, 1.6.3.4, 1.6.4.4, 1.9.1.4

Terms, language, 5.3, 6.3.2, 6.3.8, 8.2

Terminations, 1.7.2, 1.7.6, 1.7.8, 1.8.5

Terminology, 4.2.6.8, 6.2.6.3, 7.3.5.3, 8.2.7, 10.2

Test methods, 4.1.2.3, 4.2

Titles

Articles, 5.2.4

Codes, 5.2.1

Guides and reports, 8.1.2

Section and subsection, 5.2.5

Specifications, 6.2.1, 6.2.5

Translation disclaimer, 4.2.7, 7.3.6, 14.2.5

Translation of ACI documents, 4.2.7, 7.3.6

U

User, 1.8, 1.8.2, 1.8.3, 1.8.4

Units, 4.3.2, 7.4.2

Units of measurement, Chapter 11

Conversion of, 11.6

- Conversion factors, 11.6.1

- Decimal point and implied tolerances, 11.6.7

- Degree of precision, 11.6.5

- Mass versus weight, 11.6.6

- Reinforcing bar designations, 11.6.4

- Rounding, 11.6.3

- Significant digits, 11.6.2

Format for unit names and abbreviations, 11.5

- Percentages, decimals, fractions, 11.5.2

- Degrees, 11.5.3

Hard versus soft conversion, 11.4

Inch-pound, 11.2

SI, 11.3

V

Vice chair, 1.9.1.1, 1.9.2

Video products, Chapter 13

Votes, 1.6.1.3, 1.6.2.3, 1.6.3.3, 1.6.4.3, 2.3.4, 2.3.5, Chapter 3

Voting members, 1.2.3, 1.6.1, 3.1, 3.2.1, 3.2.5, 3.3, 3.4.2, 3.5, 4.2.6.5, 4.4.4.2, 7.3.3, 7.5.4.2

W

Withdrawals, 3.4.1, 4.2.2.3, 7.3.2.3

Writing style, Chapter 9

Equations, 9.1, 9.1.1

Figures, 9.2

Grammar, 9.5

- Abbreviations, 9.5.6

- And/or, 9.5.9

- Capitalization, 9.5.7

- Footnotes, 9.5.4

- Hyphens, 9.5.2

- Numbers, 9.5.1

- Parentheses and brackets, 9.5.5

- Serial comma, 9.5.3

- Per versus “/”, 9.5.8

Lists, 9.4

Tables, 9.3