You are on page 1of 72

ACI

Technical Committee Manual


2004

Prepared by the

Technical Activities Committee


March 2004

American Concrete Institute


P. O. Box 9094
Farmington Hills, Michigan 48333-9094
ii ACI Technical Committee Manual — 2004

FOREWORD

This manual has been prepared by the Technical Activities Committee to guide the
operation of ACI technical committees.

The success of any committee effort depends largely on the administrative ability and
initiative of the chair. Chairs of ACI technical committees are chosen for their
demonstrated ability and knowledge in the field to be covered by the committee as well
as for their administrative skills. Many details of committee operations are left to their
judgment.

For uniformity of operation and for coordination of activities of the many ACI committees,
some mandatory regulations are necessary for compliance with approved policies for
the development of standards. These mandatory requirements for committee activities
are found throughout the manual. They are stated in the positive language of “shall” or
“must,” whereas suggestions are presented as “should” or “may.”

TAC is always looking for ways to


improve and streamline committee procedures.
Any comments are welcome.

American Concrete Institute


38800 Country Club Drive
Farmington Hills, Michigan 48221
telephone 248/848-3730
fax 248/848-3720
www.concrete.org
ACI Technical Committee Manual — 2004 iii

TABLE OF CONTENTS
Contents Page

ORGANIZING TECHNICAL COMMITTEES ............................................................................................................1


Chapter 1

1.1 Establishing Committees and Missions........... 1 1.6.6.3 Producer ...............................................................5


1.2 TAC Contact Member......................................... 1 1.6.6.4 User Interest .........................................................5
1.6.6.5 User .....................................................................5
1.3 Organizing the Committee ................................ 1 1.6.6.6 General Interest ....................................................5
1.3.1 Subcommittees and Task Groups ........................ 1 1.6.6.7 Consultants ...........................................................5
1.3.1.1 Subcommittee Designation .................................. 1 1.6.6.8 Balance of Interests ..............................................5
1.3.1.2 Editorial Subcommittee ........................................ 1 1.6.6.9 Annual Review ......................................................5
1.3.1.3 Control Group or Steering Subcommittee ............ 1
1.7 Committee Reorganization.................................5
1.4 Technical Committee Membership ................... 2 1.7.1 Reorganization with Discharge of Members .........5
1.4.1 Committee Officers .............................................. 2 1.7.2 Reorganization with Retention of Members ..........5
1.4.1.1 Chairs .............................................................. 2
1.4.1.2 Vice Chairs........................................................... 2 1.8 Membership Terminations .................................6
1.4.1.3 Secretaries........................................................... 2 1.8.1 Membership Termination to Achieve Balance.......6
1.4.2 Committee Members............................................ 2 1.8.2 Appeal of Membership Termination ..................... 6
1.4.2.1 Voting Members ................................................... 2
1.4.2.2 Associate Members.............................................. 3 1.9 Resignations .......................................................6
1.4.2.3 Consulting Members ............................................ 3
1.4.2.4 Associate and Consulting Members Privileges .... 3 1.10 Joint Committees................................................6
1.4.2.5 Liaison Members.................................................. 3
1.4.2.6 Subcommittee Members ...................................... 3 1.11 TAC Subcommittees...........................................6
1.11.1 TAC Metrication Committee (TMC).......................6
1.5 Appointments..................................................... 3 1.11.2 TAC Repair and Rehabilitation Committee
1.5.1 Appointment Not Approved .................................. 4 (TRRC) ...............................................................6
1.5.2 Appeal to TAC...................................................... 4 1.11.3 TAC Specifications Committee (TSC)...................6
1.11.4 TAC Technology Transfer Committee (TTTC) ......6
1.6 Selection of Voting Members............................ 4
1.6.1 Qualifications ....................................................... 4 1.12 Innovation Task Groups (ITG)............................7
1.6.2 Voting Member Meeting Requirements................ 4 1.12.1 Requesting an ITG ...............................................7
1.6.3 Geographical Distribution of Committee 1.12.2 TTTC Review ........................................................7
Members .............................................................. 4 1.12.3 ITG Formation.......................................................7
1.6.4 Variety of Member Experience............................. 4 1.12.4 ITG Updates..........................................................7
1.6.5 Overlapping Membership ..................................... 4
1.6.6 Classification of Committee Members and 1.13 Technical Committee Certificates .....................7
Committee Balance.............................................. 4 1.13.1 Voting Member Certificates...................................7
1.6.6.1 Classifications ...................................................... 4 1.13.2 Chair Certificates ..................................................7
1.6.6.2 Producer Interest.................................................. 5 1.13.3 Outstanding Service by Committee Members.......7

OPERATING TECHNICAL COMMITTEES..............................................................................................................8


Chapter 2

2.1 Fulfilling the Mission ......................................... 8 2.4 Distributing Correspondence ............................9


2.4.1 Correspondence within a Committee ....................9
2.2 Goals ................................................................... 8 2.4.2 Correspondence between Committees.................9
2.2.1 Create a New Standard........................................ 8 2.4.3 Correspondence to TAC and ACI Headquarters...9
2.2.2 Create a New Report or Guide............................. 8
2.2.3 Update Existing Documents................................. 8 2.5 Coordination with Other Committees .............10
2.2.4 Sponsor Convention Sessions and Related 2.6 Annual Report of Committee Activities ..........10
Publications.......................................................... 8 2.7 Questionnaires................................................. 10
2.2.5 Sponsor Individually Authored Papers ................. 8 2.8 Staff Assistance ................................................10
2.2.6 Develop Seminars................................................ 8 2.9 Technical Committee Expenses .....................10
2.10 Special Funds....................................................10
2.3 Committee Meetings .......................................... 8 2.11 Concrete Research and Education
2.3.1 Closed Meetings .................................................. 8 Foundation (ConREF).......................................10
2.3.2 Visitors ................................................................. 8 2.12 Sponsorship of Technical Sessions at non-
2.3.3 Agenda................................................................. 9 ACI Conferences ...............................................10
2.3.4 Minutes ................................................................ 9 2.13 Workshop for Technical Committee Chairs....11
2.3.5 Quorum ................................................................ 9

Table of Contents
March 2004
iv ACI Technical Committee Manual — 2004

Contents Page

COMMITTEE DOCUMENTS ..................................................................................................................................11


Chapter 3

3.1 General Procedure ........................................... 12 3.5 Board Policies ...................................................16


3.1.1 Units of Measurement in Documents ................. 12 3.5.1 Policy on Performance Specifications.................16
3.5.2 Policy on ACI Certification Programs ..................16
3.2 Types of Documents........................................ 12 3.5.3 Policy on High-Performance Concrete................16
3.2.1 Documents Requiring Standardization............... 12 3.5.4 Policy on Units of Measurement .........................17
3.2.1.1 Codes................................................................. 13
3.2.1.2 Code Cases ....................................................... 13 3.6 Circulating Draft Documents ...........................17
3.2.1.3 Reference Specifications ................................... 13
3.2.1.4 Provisional Specifications and Test Methods..... 14 3.7 Coordination Procedures.................................17
3.2.1.5 Commentaries.................................................... 14 3.7.1 Coordination with Other Technical Committees ..17
3.2.1.6 Standardized Reports and Guides ..................... 14 3.7.2 Coordination with the TAC Specifications
3.2.1.7 Guide Specifications .......................................... 14 Committee (TSC) ................................................18
3.2.2 Documents Not Requiring Standardization ........ 14 3.7.3 Coordination with the Construction Liaison
3.2.2.1 Guides................................................................ 14 Committee (CLC) ................................................18
3.2.2.2 Reports .............................................................. 14
3.2.2.3 Bibliographies .................................................... 14 3.8 Technical Documents not Authored by ACI
3.2.2.4 Handbooks and Manuals ................................... 15 Technical Committees......................................18
3.2.2.5 Emerging Technology Series ............................. 15 3.8.1 Technical Documents Authored by ACI
Chapters .............................................................18
3.3 Preparation of Committee Documents........... 16
3.3.1 Organization of Material ..................................... 16 3.9 Introductory and Disclaimer Statements ........18
3.3.2 References......................................................... 16 3.9.1 ITG Introductory Statements ...............................18
3.3.2.1 References within Specifications ....................... 16 3.9.2 Emerging Technology Introductory Statement ...18
3.3.2.2 Reference to Patented Items ............................. 16 3.9.3 Patented Items ...................................................19
3.9.3.1 Introductory Statement........................................19
3.4 Editorial Review ............................................... 16 3.9.3.2 Disclaimer Statement..........................................19
3.9.4 Disclaimer of Government Endorsement ............19

BALLOTING COMMITTEE DOCUMENTS ............................................................................................................20


Chapter 4

4.1 Types of Voting Methods ................................ 20 4.5.3 Related: Nonpersuasive......................................22


4.1.1 Letter Ballot........................................................ 20 4.5.4 Related: Persuasive............................................22
4.1.2 Meeting Ballot .................................................... 20 4.5.4.1 Persuasive: Editorial Change..............................23
4.1.3 No-Protest Consent............................................ 20 4.6.4.2 Persuasive: Substantive Change ........................23

4.2 Letter Ballots .................................................... 20 4.6 Affirmative Votes with Comments...................24


4.2.1 Committee Letter Ballot...................................... 20 4.7 Interim and Progress Committee Ballots........24
4.2.2 Subcommittee Letter Ballot ................................ 20 4.8 Special Ballot Procedures................................24
4.2.3 ITG Review and Letter Ballot ............................. 20 4.9 Proxy Votes .......................................................24

4.3 Letter Ballot Procedures ................................. 20 4.10 Procedure for Reapproval of Committee
4.3.1 Initiating a Letter Ballot....................................... 20 Documents ........................................................24
4.3.2 Letter Ballot Content .......................................... 20 4.10.1 Purpose .............................................................24
4.3.3 Letter Ballot Format............................................ 20 4.10.2 Initiation .............................................................24
4.3.4 Letter Ballot Time Frame.................................... 21 4.10.3 Responsibility......................................................24
4.3.5 Letter Ballot Distribution ..................................... 21 4.10.4 Format .............................................................24
4.3.6 Letter Ballot Negative Votes............................... 21 4.10.5 Passage .............................................................24
4.3.7 Letter Ballot Summary........................................ 21 4.10.6 Completion..........................................................24
4.3.8 Analysis of Letter Ballot Results......................... 21
Fig. 4.1Analyzing Ballot Results and Passing of
4.4 Passage of a Letter Ballot Item....................... 21 Ballot Item .......................................................25
Fig. 4.2Resolution of Negative Votes ..........................26
4.5 Resolution of Negative Votes ......................... 22 Fig. 4.3Negative Vote Found Persuasive ....................27
4.5.1 Withdrawn .......................................................... 22 Fig. 4.4Affirmative with Comment................................28
4.5.2 Unrelated ........................................................... 22

Table of Contents
March 2004
ACI Technical Committee Manual — 2004 v
Contents Page

Chapter 5 PROCESSING COMMITTEE DOCUMENTS ........................................................................................................28

5.1 Submitting Documents for TAC Review ....... 29 5.5.6.1 Code Case ..........................................................32
5.5.6.2 Provisional Specification or Test Method ............32
5.2 Review of Documents...................................... 29 5.5.6.3 Code or Reference Specification ........................32
5.2.1 Review Comment Classifications ....................... 29 5.5.6.4 Other Standardized Documents..........................32
5.2.1.1 General and Specific Comments........................ 29 5.5.7 Response to Public Discussion...........................33
5.2.1.2 Primary Comment (P) ........................................ 29 5.5.7.1 Expedited Standardization ..................................33
5.2.1.3 Secondary Comment (S).................................... 29 5.5.7.2 Normal Standardization.......................................33
5.2.1.4 Editorial Comment (E)........................................ 30 5.5.8 Document Publication .........................................33
5.2.1.5 Editorial Comment (M) ....................................... 30 5.5.9 American National Standards Institute ................33
5.2.2 TAC Review Procedure...................................... 30 5.5.10 Appeals ...............................................................33
5.2.2.1 TAC Review Group ............................................ 30 5.5.10.1 Appeal of Standardized Documents ..................33
5.2.2.2 Review Comments ............................................. 30 5.5.10.2 Appeal of Nonstandardized Documents ............33

5.3 TAC Decision.................................................... 30 5.6 Publication for Public Review..........................33


5.3.1 Document Approval............................................ 30 5.7 Details of Public Discussion and Committee
5.3.2 Document not Approved .................................... 31 Closure...............................................................34
5.3.3 Appeal of TAC Decision on Document............... 31
5.8 Final Publication ...............................................34
5.4 Types of Standardization Procedures............ 31 5.8.1 Separate Publications .........................................34
5.4.1 Normal Standardization...................................... 31 5.8.2 ACI Manual of Concrete Practice........................34
5.4.2 Expedited Standardization ................................. 31
5.4.3 Provisional Standardization................................ 31 5.9 Publication of Joint Committee Documents...34
5.4.4 Procedure for Documents not Requiring 5.10 Updating Existing Documents .........................34
Standardization .................................................. 31 5.10.1 Committee Documents .......................................34
5.10.1.1 Revision.............................................................35
5.5 ACI Document Adoption and Publishing 5.10.1.2 Reapproval ........................................................35
Procedures ....................................................... 31 5.10.1.3 Withdrawal.........................................................35
5.5.1 Document Types ................................................ 31 5.10.2 ITG Documents...................................................35
5.5.2 Document Origination ........................................ 32
5.5.3 TAC Review ....................................................... 32 Fig 5.1 ACI Document Adoption and Publishing
5.5.4 TAC Approval..................................................... 32 Procedures .........................................................36
5.5.5 Standards Board Review ................................... 32 Fig.5.2 Procedure for Document Development by
5.5.6 Standardization Procedures ............................... 32 Innovation Task Groups ......................................37

CONVENTION SESSIONS AND RELATED PUBLICATIONS ..............................................................................38


Chapter 6

6.1 Introduction ...................................................... 38 6.2.6.3 Notifying Speakers..............................................40


6.2.7 Final TAC Approval.............................................40
6.2 Convention Session Timetables..................... 38 6.2.8 Headquarters Assistance....................................40
6.2.1 Committee Deadlines......................................... 38 6.2.9 Review of Presentation Materials........................40
6.2.1.1 Preliminary Approval of Session with a Call for 6.2.10 Presentation Summaries.....................................41
Papers or Presentations..................................... 38
6.2.1.2 Preliminary Approval of Session without a Call 6.3 Publication of Session Papers.........................41
for Papers or Presentations ............................... 38 6.3.1 SP Preliminary TAC Approval .............................41
6.2.1.3 Final Approval of Session .................................. 38 6.3.2 Preparation of Papers .........................................41
6.2.1.4 Timetable of Presentations ................................ 38 6.3.3 Review of Papers................................................41
6.2.2 Initiating a Session............................................. 38 6.3.4 Final TAC Approval.............................................42
6.2.3 Preparing a Proposal for TAC Approval ............. 39
6.2.4 Preliminary TAC Approval.................................. 39 6.4 Discussion.........................................................42
6.2.4.1 Sessions Honoring Prominent ACI Members..... 39
6.2.5 Session Moderators ........................................... 39 6.5 ACI Awards........................................................42
6.2.6 Speakers............................................................ 39
6.2.6.1 Call for Papers or Presentations ........................ 39 Fig 6.1 Timetable for Developing Technical Sessions
6.2.6.2 Selecting Speakers ............................................ 40 for ACI Conventions...........................................43

Table of Contents
March 2004
vi ACI Technical Committee Manual — 2004

Contents Page

Appendix A Sample Committee Forms and Guides ....................................................................................................... 44

1.4.1.1.a Suggested Successors For Technical 4.1.3.b Sample No-Protest Consent Confirmation..... 53
Committee Chairs ......................................... 45 4.3.7 Letter Ballot Summary ................................... 54
1.4.1.1.b Guidelines for Selecting ACI Technical 4.10.4 Sample Committee Letter Ballot for
Committee Chairs .......................................... 46 Reapproval ................................................... 55
1.4.2 ACI Committee Applicant’s Data Sheet ......... 47 6.2.3 Guidance on Requesting Convention
1.7.2 Committee Membership Questionnaire ......... 48 Sessions ........................................................ 56
2.6.a Annual Report of ACI Committee Activities ... 49 6.2.4 Preliminary Approval – Convention Session
2.6.b Annual Report – Page 2 ................................ 50 Request Form ................................................ 57
4.1.1 Sample Committee Letter Ballot .................... 51 6.2.7 Final Approval – Convention Session Request
4.1.3.a Sample No-Protest Consent Notice............... 52 Form ............................................................. 58

Appendix B Committee Web Sites ...................................................................................................................................59

B.1 Purpose............................................................. 59 B.2.8 Example Draft Copyright Notice..........................59


B.2.9 Example Draft Disclaimer Statement ..................60
B.2 Institute Policy on Development and Use of
Websites by Committees and Chapters......... 59 B.3 Registration, Security, and Login ....................60
B.2.1 ACI Website ....................................................... 59 B.4 Navigating the Committee Sites ......................60
B.2.2 Web Pages ........................................................ 59 B.4.1 Directory .............................................................60
B.2.2.1 Technical Credibility ........................................... 59 B.4.2 Committee Search Screen..................................60
B.2.2.2 Independence from Commercial and Political B.4.3 Join Committee ...................................................60
Influence ........................................................... 59 B.4.4 Standardization Actions ......................................60
B.2.2.3 Individual Respect and Privacy .......................... 59 B.4.5 Forms & Documents ...........................................60
B.2.2.4 Accountability ..................................................... 59
B.2.2.5 Document Copyright .......................................... 59 B.5 Committee Home Page.....................................60
B.2.2.6 Draft Copyright and Disclaimer .......................... 59 B.5.1 Membership ........................................................60
B.2.3 Meeting Agenda ................................................. 59 B.5.2 Document Library................................................61
B.2.4 Public Comment................................................. 59 B.5.3 Meetings .............................................................61
B.2.5 ACI Chapters...................................................... 59 B.5.4 Call for Papers ....................................................61
B.2.6 ACI Website Maintenance.................................. 59 B.5.5 Agenda and Approved Minutes...........................61
B.2.7 Example Document Copyright Notice ................ 59 B.5.6 Forums .............................................................61

Index .......................................................................................................................................................................................... 62

Table of Contents
March 2004
ACI Technical Committee Manual — 2004 1

CHAPTER 1 Organizing the Committee


1.3

ORGANIZING TECHNICAL COMMITTEES The chair is responsible for organizing the committee to
accomplish its mission and goals (2.2). This may deter-
mine the size of the committee. Several factors should be
Establishing Committees and Missions
1.1 considered: scope of the mission (2.1), balance of inter-
ests (1.6.6.8), geographical location of the committee
On March 23, 1994, the ACI Board of Direction passed members (1.6.3), and the currently assigned task. For new
the following motion: committees, the chair may initially appoint three to five
key voting members who could help identify other pro-
“[that] Board committees be delegated the authority to spective committee members.
administer the committees under their jurisdiction in-
cluding establishing new committees, developing or re- Large committees may require a vice chair (1.4.1.2), a
vising mission statements, and discharging committees secretary (1.4.1.3), subcommittees (1.3.1), task groups,
that are no longer needed to further ACI’s activities, pro- and a steering subcommittee or control group (1.3.1.3).
vided that these actions are in accordance with Board ap-
proved policies.” Subcommittees and Task Groups
1.3.1

Based on this policy, the ACI Technical Activities Subcommittees may be desirable when a committee can
Committee (TAC) establishes ACI technical committees subdivide its activities into parts that can be worked on
to meet the needs of the concrete industry. These commit- simultaneously. Task groups should be used if the work is
tees are assigned specific missions relating to improve- of limited scope and will last for a short period. This mat-
ment of the design, construction, manufacture, use, and ter is at the discretion of the chair.
maintenance of concrete structures and products. Actions Members of subcommittees and task groups must be
of all committees are subject to the review and approval members of the main committee. In special cases, with
of TAC. TAC permission, subcommittee members may be ap-
pointed from outside the main committee (1.4.2.6).
ACI technical committees may be established as joint
committees with other organizations. Joint committees Subcommittee Designation
1.3.1.1
(1.10) are to operate under the rules of the ACI Technical
Committee Manual unless a formal Memorandum of Un- Use of alphabetical designations for subcommittees
derstanding modifies the rules. The Board of Direction helps to avoid confusion between subcommittee and
initiates formal communication with other organizations, document numbers. For example, 318-A is a 318 sub-
particularly with those outside the United States, through committee.
the President, or, on behalf of the Board of Direction, by
the Institute Executive Vice President.
Editorial Subcommittee
1.3.1.2
When the committee is authorized, TAC establishes the Each committee should have an editorial subcommittee
committee’s mission (2.1). Changes in mission and scope to edit (3.4) all documents before final committee letter
may be proposed by the committee and shall be referred ballot. Having an editorial subcommittee allows the full
to TAC for approval. committee to devote more time and effort to technical
work and ensures a uniform, readable document. The edi-
Committees that are inactive, ineffective, or have com- torial subcommittee should use the ACI Style Manual as a
pleted their assignments may be discharged or reorgan- primary resource.
ized by TAC (1.7).
The chair appoints the subcommittee, which may con-
TAC Contact Member
1.2 sist of an individual or a small group with editorial ex-
perience.
Each member of TAC is assigned liaison responsibili-
ties with several technical committees and is designated 1.3.1.3 Control Group or Steering Subcommit-
as the TAC Contact Member. These assignments are tee
made to keep TAC abreast of the activities of the various A steering subcommittee or control group may be de-
committees. Technical committee chairs should keep the sirable in a large committee to assist the chair and help to
designated TAC Contact Members fully aware of com- produce committee action between full committee meet-
mittee activities and progress and should feel free to con- ings. All important actions of the control group are sub-
tact them for advice or information (2.4.3). ject to approval of the full committee.

Chapter 1 – Organizing Technical Committees


March 2004
2 ACI Technical Committee Manual — 2004

Technical Committee Membership


1.4 Committee Chairs. (These forms are included with the
Annual Report form – See 2.6.) TAC considers these
The technical committee documents of the American names when selecting or reappointing chairs. TAC may
Concrete Institute represent the consensus of the commit- interview the proposed candidates during the selection
tee, achieved by the process described in this manual, and process.
are valued and respected by the concrete community.
Vice Chairs
1.4.1.2
Technical committee members are expected to: The chair may wish to appoint a vice chair. Appoint-
ment does not imply that the vice chair will become the
1. Hold the safety, health, and welfare of the public as next chair. TAC requests and considers the advice of
their top priority. chairs when appointing their successors, but chair ap-
2. Be truthful in presenting information and data during pointments are TAC’s responsibility.
discussions, debates, and ballots concerning technical
issues. 1.4.1.3Secretaries
3. Act in a professional manner. A secretary can assist the committee by recording, pre-
4. Conduct themselves in a manner that will bring credit paring, and distributing minutes of meetings (2.3.4), bal-
to the Institute. lots (4.1), and correspondence. Appointment of a secre-
tary is at the chair’s discretion. To expedite the flow of
Committee members shall not state that they are official committee work, a person employed at the same place as
representatives of an ACI committee unless authorized by the chair may perform the committee secretarial duties
TAC nor state they are official representatives of the In- and should be appointed as a “nonvoting” secretary.
stitute unless authorized by the Board of Direction.
1.4.2Committee Members
Committee Officers
1.4.1 ACI technical committees have five categories of mem-
bers:
1.4.1.1Chairs • Voting members (1.4.2.1);
The success of a committee depends on the chair’s ad- • Associate members (1.4.2.2, 1.4.2.4);
ministrative ability and initiative. TAC appoints chairs for • Consulting members (1.4.2.3, 1.4.2.4);
specific two-year terms, which usually expire at the end • Liaison members (1.4.2.5);
of an ACI spring convention. Chairs must be members of • Subcommittee members (1.4.2.6).
the Institute. Chairs are voting members of the committee.
Technical committee members are volunteers who offer
Appointment and reappointment of technical committee their services to ACI and specific technical committees.
chairs are among TAC’s most critical responsibilities. Each prospective member, regardless of membership
Many factors affect the selection of chairs and there are category, is to submit an Applicant’s Data Sheet to the
no inflexible rules, but serious attention is given to: Managing Director of Engineering (Appendix 1.4.2 - ACI
• Rotating the chairs among all qualified committee Committee Applicant’s Data Sheet).
members to keep committee output vigorous. Un-
usual circumstances are required to justify reap- The chair is to notify the Managing Director of Engi-
pointment of a chair beyond six years; neering of all membership actions to be taken: appoint-
• Not having an individual chair more than one ACI ments (regardless of category), resignations, terminations,
technical committee at a time, because being a chair or changes of membership status. These actions become
requires a significant amount of effort; official when headquarters acts on the chair’s recommen-
• Assuring participation of all segments of the concrete dations.
industry in committee activities.
With the exception of associate members, ACI mem-
Active and well-organized committees always have bership is not required for technical committee service but
ongoing projects and can undergo normal leadership tran- is desirable; committee members are encouraged to join
sitions without disrupting vital committee activities. the Institute.
Chairs are responsible for having a number of individuals
prepared to assume the committee leadership at all times. 1.4.2.1 Voting Members
Each year, chairs are asked to list at least three possible Voting members are appointed because of their per-
replacements, in order of preference, with specific ratings sonal knowledge and expertise and not on the basis of
in various categories. (See Appendix 1.4.1.1.a, Suggested affiliation. A member’s employment, however, is consid-
Successors for Technical Committee Chairs, and Appen- ered in achieving balance of interests (1.6.6.8) and may
dix 1.4.1.1.b, Guidelines for Selecting ACI Technical determine membership classification and voting rights.

Chapter 1 – Organizing Technical Committees


March 2004
ACI Technical Committee Manual — 2004 3

Voting members are expected to vote on all committee • May express negative viewpoints, with reasons, on
ballots (4.1) and have the right of the floor at all meetings letter ballot items (4.1). These negative viewpoints
(2.3). Voting members are required to participate actively are not counted in the vote tally, do not affect the
in committee work by contributing technical information, outcome of a ballot item, and do not have to be re-
by promptly returning committee ballots and replying to solved (4.3.5), but must be distributed to the commit-
correspondence, and by attending committee meetings on tee for consideration;
a regular basis (1.6.2). Some committees may have spe- • Are not considered in determining the balance of vot-
cial attendance requirements. ing interests (1.6.6.8).

1.4.2.2Associate Members 1.4.2.5Liaison Members


Associate membership is an Institute membership bene- Liaison members represent related organizations and
fit. An associate member has the right to participate in function to exchange information and receive copies of all
committee activities, but does not vote and is not required committee correspondence. They are not expected to ac-
to attend committee meetings. A person applying for tively participate in committee affairs and do not vote
committee membership may be appointed or retained in (4.3.5). In the event they do participate, they should be
this membership category when balance of interests appointed to the appropriate membership classification.
(1.6.6.8) is affected or if a committee document is being
balloted (1.5.1, 4.1). Upon application, ACI members are 1.4.2.6Subcommittee Members
appointed as an associate member to a maximum of three For committees with broad responsibilities, such as
technical committees. Student and junior members are not Committees 318 and 301, TAC permits the establishment
to be appointed to more than one committee. of permanent, formal subcommittees (1.3.1) to address
different aspects of the committee’s work. Committees
On code-writing committees, the chair must approve all must receive TAC permission to have this type of struc-
appointments, including associate members. With TAC ture. Note that this structure is different from the informal
approval, the chair may elect to have no associate mem- subcommittees or task groups assigned by the chair to
bers. carry out short-term tasks for the committee. TAC ap-
proval is not required for any committee to create infor-
Associate membership terms are for four years. See mal subcommittees.
1.4.2.4 for associate member privileges. When the term
expires, the chair should evaluate the person’s actual par- Voting members of formal subcommittees may include
ticipation and based on that, may: members of the main committee, nonmembers chosen for
• Transfer to voting or consulting member status; their special expertise, and representatives of other ACI
• Reappoint as associate member for another four committees. Subcommittee members who are not voting
years; or members of the main committee participate and vote
• Terminate committee membership. (4.2.2) on the subcommittee level but do not vote on main
committee items.
When individuals drop their ACI memberships, their
technical committee associate memberships are also ter- Appointments
1.5
minated.
Chairs should add new members on a regular basis and
1.4.2.3Consulting Members remove inactive members. Effective committees should
A consulting member is one whose membership is de- have sufficient turnover so that new ideas are constantly
sired because of a special expertise or a long-time brought in. With TAC approval, chairs of code-writing
association with the committee or its work. A consulting committees may limit the turnover of voting and sub-
member does not vote and is not required to attend meet- committee members (1.4.2.6) on their committees during
ings regularly or participate by correspondence. See each code cycle.
1.4.2.4 for consulting member privileges.
After reviewing an Applicant’s Data Sheet (Appendix
1.4.2.4Associate and Consulting Members 1.4.2), the chair should send the original to the Managing
Privileges Director of Engineering with an appointment recommen-
• Regularly receive minutes (2.3.4), information on dation and keep a copy for the committee files.
items being balloted (4.1), and correspondence dis-
tributed to committee members (2.4.1); ACI headquarters sends the formal appointment letter.
• Have the privilege of the floor at committee meetings Committee members, other than associate members
(2.3), but can not vote; (1.4.2.2), are appointed for unspecified terms.

Chapter 1 – Organizing Technical Committees


March 2004
4 ACI Technical Committee Manual — 2004

1.5.1 Appointment Not Approved contribute to the work of the committee may not be able
The chair may reject an application for voting member- to attend at least one meeting per year. The chair may
ship for various reasons, including lack of qualifications waive meeting attendance requirements under special
(1.6.1), not able to attend committee meetings (1.6.2), circumstances provided a voting member contributes to
committee balance (1.6.6.8), timing of a critical ballot the work of the committee.
(4.2), or committee size. Adding voting members just
before conducting a critical letter ballot is not advisable Meeting schedule conflicts are difficult to avoid be-
because new voting members may not have knowledge of cause of the number of ACI committees and the varied
past committee discussions. Appointment as a nonvoting interest of the voting members. Before granting voting
associate member (1.4.2.2) may be appropriate until the member status to an applicant who already serves on three
situation should change. or more other ACI committees, the chair should make
sure that he or she will be able to attend meetings and
1.5.2 Appeal to TAC participate actively in the work of the committee. If an
The applicant has the right to appeal to TAC if the ap- applicant cannot attend these meetings, other membership
plication for membership is not approved or not acted on categories may be desirable.
in a reasonable amount of time. The person submits the
appeal to the Managing Director of Engineering. The 1.6.3Geographical Distribution of Committee
committee’s TAC Contact Member (1.2) reviews the ap- Members
peal and recommends action to TAC. The person may ACI is an international organization and committee
attend the TAC meeting where the appeal is to be consid- documents should reflect practices that are broadly appli-
ered. cable. Wide geographical distribution of committee mem-
bers guards against publication of documents that are re-
Selection of Voting Members
1.6 stricted to local practices only.

1.6.1Qualifications 1.6.4Variety of Member Experience


Voting members must be able to complete objectives Every committee should take the opportunity to intro-
related to the committee mission (1.1). They need the duce new people to ACI committee work. ACI often at-
training, knowledge, experience, time, and facilities to tracts structural engineers and materials specialists.
perform the work. Committees are encouraged to expand expertise and par-
ticipation by including architects, specifiers, contractors,
In general, committee membership is open to all quali- younger members, and those outside the mainstream of
fied individuals. There are instances, however, where ACI activity.
voting members are selected on the basis of specific ex-
pertise required to complete the committee's work. TAC 1.6.5Overlapping Membership
grants the chairs of Committees 318 and 530 the right to The chair should review the missions (1.1) of closely
limit the number of voting members and subcommittee related committees and develop overlapping membership
members on their committee. where desirable, because cross-representation aids coor-
dination (2.5, 3.7). Sometimes it is necessary to use capa-
ACI Committee 318 is an example of a committee with ble voting members in multiple committee assignments.
selective membership. Such a committee may establish Voting membership on more than three technical commit-
subcommittees to broaden the base of input to the com- tees, however, is generally discouraged.
mittee's work (1.4.2.6).
Classification of Committee Members and
1.6.6
1.6.2 Voting Member Meeting Requirements Committee Balance
Committees generally hold their meetings (2.3) at ACI
spring and fall conventions. At meetings, members arrive 1.6.6.1Classifications
at consensus on major issues including resolution of nega- A voting member of a committee that prepares or has
tive votes on letter ballots, solve problems, plan future jurisdiction over documents requiring standardization
activities, and accomplish much of their work. (3.2.1) shall be classified by the chair as Producer, User,
or General Interest. Classification of committee members
A sufficient number of voting members must attend by organizational interest is needed to ensure fairness and
committee meetings to be able to resolve negative votes balance among affected interests. Such classification can
on letter ballots in accordance with Section 4.5. Thus a be different on different committees. Classification shall
voting member is required to participate by attending be related to the mission (1.1) of the committee. Members
committee meetings on a regular basis (1.4.2.1). It is rec- may appeal their classification to the committee chair and
ognized, however, that some members who wish to ultimately to TAC.

Chapter 1 – Organizing Technical Committees


March 2004
ACI Technical Committee Manual — 2004 5

1.6.6.2Producer Interest section, but should have broad-based membership to en-


A Producer Interest is an organization, trade associa- sure balanced coverage of the subject. Balance of interests
tion, or individual that produces, markets, or sells materi- is not required in subcommittees (1.4.2.6), but the mem-
als, products, or systems covered in the committee’s mis- bership should ensure balanced coverage of the subject.
sion.
Annual Review
1.6.6.9
1.6.6.3 Producer Each committee that prepares or has jurisdiction over
A voting member who is affiliated with a producer in- documents requiring standardization shall carry out an
terest shall be classified as a Producer. annual review of membership and include a summary of
voting member classification in the Annual Report (2.6,
User Interest
1.6.6.4 Appendix 2.6).
A User Interest is an organization that purchases or uses
materials, products, or systems covered in the commit- Committee Reorganization
1.7
tee’s mission.
From time to time, it may be necessary for TAC to re-
1.6.6.5 User organize (1.1) technical committees. The reasons for re-
A voting member who is affiliated with a User Interest organization of the committee may include:
shall be classified as a User, provided that the member • The committee has completed its assigned mission
could not also be classified as a Producer. For example, a and only a small committee is needed to maintain
design engineer who is a member of a committee writing committee documents;
a design guide would be classified as a User, but would be • The mission or direction of the committee has
classified as General Interest on a committee dealing with changed sufficiently to require reorganization; or
concrete materials. • The reorganization of the committee is needed to ac-
complish the assigned mission.
General Interest
1.6.6.6 • A code-writing committee is beginning a new code
A voting member who is not classified as Producer or cycle.
User shall be classified as General Interest: for example,
an employee of a government agency or a university. Upon reorganization, TAC may decide to appoint a new
chair and discharge all members or to appoint a new chair
1.6.6.7Consultants who is responsible for reviewing current membership.
A consultant retained by a Producer Interest or by a
User Interest under an indefinite continuous arrangement 1.7.1Reorganization with Discharge of
that includes membership on an ACI committee shall be Members
classified Producer or User, respectively. Consultants If TAC discharges the committee membership upon
representing themselves or affiliated with an employer not appointment of a new chair, all committee members are
classified as a Producer or User shall be classified as Gen- notified of the reasons for the discharge and given an ex-
eral Interest. planation of future plans. Former committee members
have the opportunity to apply for reappointment to the
1.6.6.8Balance of Interests committee.
Balance of interests on a committee that prepares or has
jurisdiction over documents requiring standardization 1.7.2Reorganization with Retention of Mem-
(3.2.1) requires that: bers
If the present membership is to be retained, subject to
• The combined number of voting members classified review, the chair must:
as User (1.6.6.5) and General Interest (1.6.6.6) shall • Review the activity of the committee members and
equal or exceed the number of voting members clas- recommend changing the classification to a nonvot-
sified as Producer (1.6.6.3); and ing status (1.4.2.4) of those who have not demon-
• Each Producer Interest (1.6.6.2) shall have no more strated adequate activity; or terminating the commit-
than one voting member. tee membership (1.8)
• Review the overall committee composition and rec-
Balance of interests is required for the committee to ommend addition or deletion of committee members
ballot any action. Committees seeking exceptions to the to ensure balance of interests (1.6.6.8) and to main-
requirements of this section can request consideration by tain a reasonable size to accomplish tasks (1.5.1).
TAC. Committees preparing documents that do not re- • The chair is urged to add new committee members
quire standardization (3.2.2), such as guides and reports, who are knowledgeable in the committee’s field and
are not required to conform to the requirements of this who can provide vitality to the committee (1.5).

Chapter 1 – Organizing Technical Committees


March 2004
6 ACI Technical Committee Manual — 2004

The chair may request a written statement from com- 1.8.2 Appeal of Membership Termination
mittee members stating they wish to continue to serve. If Any voting member may appeal a membership termina-
an affirmative response is not received in a reasonable tion decision to TAC. The discharged member can send
time (two months), the chair can consider it a lack of in- an appeal to the Managing Director of Engineering and
terest and notify the Managing Director of Engineering to can appear in person at the TAC meeting where the ap-
terminate (1.8) that individual’s committee membership. peal is being considered.
A questionnaire may be used to ask the committee
members if they wish to continue as active members, Resignations
1.9
change their membership status, or resign (Appendix
1.7.2 - Committee Membership Questionnaire). Committee members resign by notifying the chair and
the Managing Director of Engineering of such intent.
Headquarters sends an official letter confirming the resig-
Membership Terminations
1.8
nation.
The chair should periodically review the voting mem-
bers’ performance of regularly attending meetings, an- Joint Committees
1.10
swering correspondence, and especially of returning letter
ballots. Inactive voting members should be contacted and Appointment of committee members to committees
encouraged to become more active or consider becoming joint with other organizations, such as the American Soci-
an associate or consulting member of the committee. Be- ety of Civil Engineers (ASCE), the American Society of
cause of ACI’s stringent voting requirements (4.4), voting Mechanical Engineers (ASME), and The Masonry Soci-
members who do not return ballots may stop a committee ety (TMS), generally follow ACI guidelines (1.1, 2.4.3,
from successfully balloting a document. Failure of a vot- 3.6, 5.1, 5.9).
ing member to meet the requirements may result in termi-
nation of membership. TAC Subcommittees
1.11

If a voting member does not meet the requirements, the TAC subcommittees are established to assist TAC (1.1)
chair should write to the Managing Director of Engineer- in its oversight responsibility. Actions of TAC subcom-
ing to recommend a change in membership category or mittees are subject to review and approval by TAC.
membership termination. Changes to the membership
make room for willing and active voting members. The 1.11.1 TAC Metrication Committee (TMC)
chair is encouraged to discuss the situation with the TAC TMC is to develop, guide, and assist technical commit-
Contact Member (1.2) before making such a recommen- tees to carry out ACI metrication policy (3.1.1, 3.5.4).
dation since committee members may view the member-
ship termination as an extreme step. 1.11.2TAC Repair and Rehabilitation Commit-
tee (TRRC)
The chair may want to use the membership question- TRRC is to advise TAC on:
naire to help assess committee members’ interest. Voting • ACI’s goals, objectives, and prominence in repair and
members can evaluate their actual participation and may rehabilitation (to include evaluation, maintenance
request change in committee membership status (Appen- and protection);
dix 1.7.2 - Committee Membership Questionnaire). • Existing or potential conflicts or duplications of
committee efforts, and means for resolving these
1.8.1Membership Termination to Achieve Bal- situations;
ance • Other issues as requested.
In order to achieve balance (1.6.6.8), the chair may de-
cide to terminate voting memberships or change them to 1.11.3TAC Specifications Committee (TSC)
nonvoting classifications. This is done only after the chair TSC is to assist technical committees in preparing and
has shown that a substantial effort has been made to ob- maintaining specifications (3.2.1.3) in the correct format
tain balance by adding new voting members. and language, and manage specification development by
the Institute (3.7.2).
When a change of employment produces a change in
classification (1.6.6.1) and this results in an imbalance in 1.11.4TAC Technology Transfer Committee
voting interests, a voting membership can be terminated. (TTTC)
Reappointment can be considered when balance is TTTC is to accelerate the transfer of new technology to
achieved and if the person requests reappointment. the concrete construction community (1.12).

Chapter 1 – Organizing Technical Committees


March 2004
ACI Technical Committee Manual — 2004 7

Innovation Task Groups (ITG)


1.12 document(s) to be produced, and a tentative time
schedule for the effort.
An Innovation Task Group (ITG) is appointed by TTTC
• The ITG’s membership consists of at least one mem-
(1.11.5). The role of an ITG is to evaluate new technology
ber of TTTC, who serves as the chair, and at least
and, if appropriate, transfer that technology into standard-
four experts in the field. Those experts may include
ized ACI documents. An ITG operates as an ACI techni-
members of the CIAS panel that appraised the tech-
cal committee, except as otherwise indicated, and has a
nology. The ITG membership shall conform to the
limited mission and life. The process for document
balance requirements of Section 1.6.6.8.
development by an ITG is given in 1.12.1 through 1.12.4
• The TTTC should identify, as early as possible, the
(Fig. 5.2).
technical committee that agrees to maintain the docu-
1.12.1Requesting an ITG ment once the work of the ITG is complete. The
An interested party submits a request for document TTTC chair should appoint members of that technical
development through the ITG process to the TAC Tech- committee to the ITG, and should encourage coordi-
nology Transfer Committee and the Managing Director of nation between the ITG and that committee as the
Engineering. The request identifies the new technology; document is developed, balloted, and standardized.
describes its advantages over existing technology; sum- • To facilitate development of the document, an inter-
marizes its state of development, testing, and evaluation; ested party can provide funding, via ACI, to support
and identifies the type of standardized document to be meetings of the ITG, or can provide honoraria for the
produced by the ITG (test method, guide, or specifica- principal drafters of the document, or both. If such
tion). The request may include a report by the Concrete outside funding is not available, the TTTC chair may
Innovation Appraisal Service (CIAS) if the interested request funding from ACI to support such costs.
party has obtained such a report.
ITG Updates
1.12.4
1.12.2TTTC Review The chair of the ITG is expected to report to TTTC re-
The TTTC chair appoints a task group to review the garding the progress of the ITG at each ACI convention,
request and recommends whether an ITG should be ap- and more frequently if requested by TTTC.
pointed. No one who has a direct economic interest in the
outcome of the ITG evaluation shall participate in the task 1.13Technical Committee Certificates
group. The task group’s report shall address the following ACI provides the following types of certificates for
questions: technical committee participation.
• Will a document on the new technology fit within
ACI’s general mission; 1.13.1 Voting Member Certificates
• Does the new technology provide advantages over As official recognition of appointment of a voting
existing technology; member, the Institute sends a certificate along with the
• Are there competing technologies; official appointment letter.
• Do technical papers or research reports adequately
document the new technology; 1.13.2 Chair Certificates
• Is the new technology mature enough to proceed with On behalf of TAC, the Institute sends a certificate of
the development of an ACI document; and appreciation to outgoing technical committee chairs. The
• Does the task group recommend formation of an certificate recognizes the contributions of the person for
ITG? chairing a specific committee and the years of service.

If the task group does not recommend formation of an 1.13.3Outstanding Service by Committee
ITG, the TTTC shall inform both the submitting party and Members
TAC of the decision and supply a brief report. The committee chair may issue an certificate to a com-
mittee member who has performed outstanding service,
1.12.3ITG Formation such as:
If formation is recommended by the task group and • Extraordinary effort in the production or revision of a
approved by TTTC, TAC approval must be obtained be- committee document;
fore the TTTC chair appoints an ITG to evaluate the new • Leadership and administrative skills in organizing
technology and prepare a draft document. When TTTC and conducting a successful technical session.
forms an ITG, the formation and the ITG’s mission shall
The chair shall obtain TAC Contact Member approval
be publicized to the ACI membership by an announce-
before recommending the certificate. The certificates will
ment in Concrete International.
be provided by ACI upon recommendation of the commit-
• The ITG’s charge includes a general description of tee chair. The committee chair and the TAC Contact
the technology to be evaluated, the standardized Member shall sign it.

Chapter 1 – Organizing Technical Committees


March 2004
8 ACI Technical Committee Manual — 2004

CHAPTER 2 seminars or workshops in the committee’s area of


expertise. This includes suggesting qualified seminar
OPERATING TECHNICAL COMMITTEES topics, speakers, pertinent topics, or appropriate visual
aids. The Educational Activities Committee (EAC)
Fulfilling the Mission
2.1 reviews, approves, and manages all new ACI seminar
topics.
The main purpose of ACI technical committees is to
make knowledge in the assigned fields available through Committee Meetings
2.3
publication. TAC gives the chair considerable authority to
accomplish the committee mission (1.3) Chairs are responsible for calling committee meetings
and must give members adequate notice, typically one
In all committee work, whether standardization is month. ACI headquarters provides convention meeting
required or not (3.2.1), the protection of the public and the rooms request forms to chairs, requesting return by a
interests of the ultimate consumer must dominate. certain date. See Appendix B on how to request meeting
room from the committee’s web page.
Goals
2.2
If the chair cannot conduct the meeting, an alternate is
Each committee should annually prepare and review to be selected so the committee work can continue
specific goals that support the committee mission (1.1). uninterrupted. The committee members and ACI
The chair submits the committee goals in the annual headquarters must be notified in advance if a scheduled
report (2.6), which are published in the ACI Committees meeting must be canceled.
booklet. Any or all of the following goals may be
included: All technical committee meetings (except closed
meetings) are open to visitors. The chair is encouraged to
Create a New Standard
2.2.1 give a brief introduction of the committee work and
Prepare a proposed code, specification, or other periodically summarize progress during the meeting.
document which, when adopted by the ACI procedures,
becomes an Institute standard. (3.2.1). Committee chairs are to exercise control to ensure
orderly discussion at meetings. This is particularly
Create a New Report or Guide
2.2.2 important in large committees. The use of Robert’s Rules
Prepare a committee report or guide that discusses and is advised. A booklet summarizing Robert’s Rules can be
summarizes pertinent information (3.2.2). obtained from the Managing Director of Engineering.

If the committee is to hold a meeting away from an ACI


Update Existing Documents
2.2.3
convention, the chair is to notify the Managing Director
Maintain, update, and revise ACI documents that fall
of Engineering at least three months in advance so a
within the committee’s mission (5.10).
notice of the meeting time and place can be published in
Concrete International.
2.2.4Sponsor Convention Sessions and
Related Publications
2.3.1Closed Meetings
Sponsor symposia or sessions at ACI conventions with
A closed committee meeting is permitted if the chair
possible related publication in an Institute periodical or as
states that the matter under consideration is administrative
an ACI Special Publication (SP). The development of
rather than technical. Discussion of technical matters in a
these sessions is explained in detail in Chapter 6.
closed meeting is out of order. For a closed meeting, the
chair makes the usual arrangements through the
2.2.5Sponsor Individually Authored Papers
Convention Department for the meeting room but is
Sponsor the preparation, presentation, and publication
solely responsible for notifying members of the meeting.
of technical papers authored by individuals who may be
Closed meetings are not listed in the convention program.
committee members. Encourage research necessary as a
basis for such papers or to support the committee’s
Visitors
2.3.2
mission. (See 2.11)
Visitors are encouraged to attend the meetings because
Develop Seminars
2.2.6
committee work is of interest to Institute members. The
Technical committees may, in cooperation with
chair should keep the visitors in mind without interfering
educational committees and ACI chapters, develop
with committee work.

Chapter 2 – Operating Technical Committees


March 2004
ACI Technical Committee Manual — 2004 9

2.3.3  Agenda Correspondence within a Committee


2.4.1

The chair should prepare the agenda in advance of the Correspondence containing proposals, critiques, or new
meeting and provide copies to all committee members and data should be sent to the entire committee. When one
the committee’s TAC Contact Member (1.2). Extra copies committee member writes to another, it is desirable to
should be available at the meeting for committee send copies to all committee members so they can keep
members and visitors and one should be posted outside abreast of developments and be able to contribute to the
the meeting room, if possible. See Appendix B for work. This also allows the members to be up-to-date be-
instructions on how to post agenda on the committee’s fore meetings so that committee discussions are more
Web page. effective.

Minutes
2.3.4 Correspondence within a subcommittee (1.3.1) should
be sent to the main committee officers so that they are
Minutes must be prepared to record important aware of the work and are better able to coordinate the
deliberations, resolution of negatives, and decisions of total committee effort.
committee and subcommittee meetings. Minutes provide
a continuing record of committee work and help prevent Correspondence between Committees
2.4.2
repeated discussion of the same subject.
Correspondence between committees is usually
In addition to recording motions and voting results, the between the chairs, with copies to the Managing Director
minutes should include the names of the committee of Engineering. If committee members correspond, copies
members and visitors attending the meeting and the should be sent to the chairs of the respective committees.
voting members not present. Minutes should be circulated
promptly to the entire committee for information and Correspondence
2.4.3 to TAC and ACI
guidance and particularly to ensure completeness and Headquarters
accuracy. Minutes should always be approved at the next
committee meeting or by correspondence. Copies of all The committee files at ACI headquarters are the
minutes shall be sent to the TAC Chair, TAC Contact “Official Files.” Originals or legible copies of all
Member, and to the Managing Director of Engineering important correspondence, agenda and minutes,
(2.4.3). See Appendix B for instructions on how to post membership lists, complete records of ballots (4.2), and
minutes on the committee’s Web page. resolution of negative votes (4.5) must be sent to the
Managing Director of Engineering.
Quorum
2.3.5
Copies of important correspondence must be sent to the
A quorum for conducting business at a committee TAC Chair, TAC Contact Members (1.2), and the
meeting consists of 40% of the voting members. This is Managing Director of Engineering. These three names
the minimum number of voting members required to should be placed at the bottom of the committee roster to
resolve negative votes on committee letter ballots (4.5). receive copies of correspondence. They are not committee
With one exception, the content of technical documents is members and do not vote or return ballots unless they
finalized by a full committee letter ballot (4.2.1). were officially appointed to the committee. Copies of
draft documents should be sent to the TAC Contact
Distributing Correspondence
2.4 Members at the time of mailing to committee members.

Because committees usually meet twice a year (1.6.2, The ACI President and staff, other than the Managing
2.3), effective circulation of correspondence is vital to Director of Engineering, do not need copies of correspon-
committee activity and progress. To ensure timely dence unless it relates to matters between committees or
completion of committee work, concise correspondence broad aspects of Institute policy.
with prompt attention and reply by members is necessary.
If a committee is joint with another organization (1.10),
Committee chairs and secretaries are encouraged to use such as ASCE, ASME, or TMS, additional distribution
faxes and electronic mail to speed committee may be required.
communication.

Chapter 2 – Operating Technical Committees


March 2004
10 ACI Technical Committee Manual — 2004

Coordination with Other Committees


2.5 Technical Committee Expenses
2.9

Committee missions are often closely related and the The Managing Director of Engineering can honor
work of one committee may affect or overlap with vouchers from a committee chair, or a person authorized
another. To avoid conflicting information in ACI by the chair, for postage and reproduction expenses
documents (1.6.5, 3.7.1), chairs must be aware of their incurred in committee work, and supply stationery and
committee’s work in relation to other technical envelopes upon request. The Institute does not assume
committees. other committee expenses unless the Board of Direction
specifically provides prior authorization.
Annual Report of Committee Activities
2.6
Special Funds
2.10
Each chair must submit an annual report of committee
activity (Appendix 2.6 — Annual Report Form) that Requests for project funding by ACI technical
provides information on committee progress on goals committees to governmental agencies and other organi-
(2.2) and balance of interests (1.6.6.8). Annually, zations shall be reviewed by staff and submitted to TAC
headquarters sends forms to the chairs and sends copies of for approval before submission to the funding agency.
the completed forms to the TAC Contact Members (1.2). TAC determines who will contact the funding agency. A
Guide for Applying for Government Agency Grant for
Annual reports are due at headquarters before the Committee Activity is available from headquarters.
spring convention. When a committee chair fails to
submit an annual report, staff notifies TAC. TAC studies When the Board of Direction has authorized the
the possibility of future progress and may make changes solicitation of special committee funds, they shall be
in organization or personnel to make the committee more deposited to the Institute’s account, through the Institute’s
effective (1.8). Executive Vice President. The funds shall be disbursed on
vouchers signed by the chair of the committee for whose
Questionnaires
2.7 work the fund was created.

Chairs may find it useful to gather information by using Concrete Research and Education
2.11
questionnaires. These should be carefully designed to Foundation (ConREF)
elicit meaningful responses. A copy should be sent to the
Managing Director of Engineering as well as a summary The Concrete Research and Education Foundation
of the results or other appropriate information. The (ConREF) requests that each ACI committee chair
summary should be sent to the committee and all respond- identify areas of research related to the committee’s work.
ents. These research areas will be considered by ConREF’s
research council and used as a guide to direct funding.
Staff Assistance
2.8 Therefore, the committee annual report (2.6, Appendix
2.6) should list high-priority research topics that, if
Although the ACI engineering staff is not large enough funded, would assist the committee in completing its
to provide a liaison for each committee, staff can assist as mission.
coordinators. By being informed of committee activities,
staff can help with each committee’s assigned goals (2.2)
Sponsorship of Technical Sessions at
2.12
and keep it from infringing on the work of other
non-ACI Conferences
committees.
Technical committees may sponsor technical sessions
The quickest way to get material, such as drafts or
held at non-ACI conferences. The technical content of the
memos, to committee members is to communicate
proposed session is to be consistent with the committee’s
directly. The chair may request staff assistance for
mission and there is to be no financial obligation by the
technical, editorial, and secretarial tasks. When requested,
committee or the Institute.
headquarters can provide a chair with clerical help.
The request shall be submitted to the Managing
Anything sent to staff for processing must be
Director of Engineering for TAC consideration. The
accompanied by instructions. Any material received at
approved request will then be forwarded to the ACI
headquarters without instructions is regarded as an
Executive Vice President.
information copy and, after the contents are noted, is
placed in the committee file.

Chapter 2 – Operating Technical Committees


March 2004
ACI Technical Committee Manual — 2004 11

Workshop for Technical Committee Chairs


2.13 The technical committee chairs are encouraged to
attend these workshops and are expected to attend at least
At each ACI convention, TAC presents a Workshop for one workshop a year. If the chair is unable to attend a
Technical Committee Chairs. These workshops are workshop, the chair is to name an alternate so the
designed to allow the committee chairs to meet and committee can be represented at each workshop. Only one
interact with their TAC contacts, to find out what is person should represent the committee. At the spring
expected of them as chairs, to hear about new meeting, the incoming chairs will also be invited to
developments, and to ask questions. attend.

Chapter 2 – Operating Technical Committees


March 2004
12 ACI Technical Committee Manual — 2004

CHAPTER 3 Units of Measurement in Documents


3.1.1

COMMITTEE DOCUMENTS In accordance with ACI Board Policy (3.5.4), all docu-
ments, including revisions to existing documents, shall be
prepared and published in one of the following three ways
General Procedure
3.1 (1.11.2):

The principal purpose of ACI is to disseminate informa- • A document with dual units, SI (metric) and in.-lb;
tion pertaining to concrete and concrete products. Consis- • A document with only SI units;
tent with this purpose, documents are prepared by estab- • Two documents, one with SI units and the other with
lished committees and published by ACI. The documents in.-lb units.
generally cover design and construction.
With the permission of TAC, this policy may be
Committees obtain information on specific subjects, waived in exceptional circumstances. The committee
correlating results of field experience, laboratory research, must apply to TAC for approval to waive the require-
and knowledge gained from experience in design, con- ments for SI units before submittal of the document to
struction, and manufacture. Information also comes from TAC. The application must describe the exceptional cir-
a comprehensive review of literature, personal experience cumstances supporting the application.
of committee members, and contact with authorities in the
field of the committee mission. The committee condenses An example of an exceptional circumstance is that
these reviews of current thinking into standardized docu- because masonry units are not produced in standard SI
ments, reports, guides, special publications, or other sizes and there is no worldwide industry need for the
documents. TAC recommends to the Executive Vice Masonry Code with arbitrary SI units, the Masonry
President the publication modes judged most appropriate Code is exempt.
for specific documents.
A committee may request from TAC that certain fig-
Documents are developed in a three-step process: ures, tables, or examples not have dual units, because of
• Preparation of a new document or revision of an ex- the resulting complexity if dual units were incorporated.
isting document; If an exemption is given for a figure or table, a conver-
• Letter balloting (4.2) of the draft document by the sion table must be provided. For numeric examples, a
committee; and comparable example in the alternative systems of units
• Submission of the committee-approved document for must be provided. If a document contains several nu-
TAC review (5.1). merical examples, a representative number shall be pre-
sented in both systems of units.
This chapter describes the types of documents and gives
general guidance on the preparation of documents. De- IEEE/ASTM SI 10 provides guidance on proper use
tailed information on the format and style for preparing of SI units and is available as a separate publication
and revising ACI documents is contained in the ACI Style from ASTM headquarters. See Section 5 of the ACI
Manual and the ACI Specification Manual. Chapter 4 Style Manual for guidance on making conversions to SI
presents document balloting requirements. Chapter 5 pre- units.
sents requirements for submitting the completed docu-
ment to TAC and subsequent processing. Types of Documents
3.2

It is not the intent of ACI to duplicate published work. Throughout the TCM, the term “document” is used to
Where satisfactory consensus standards exist for material cover all committee works, published or being developed
specifications and test methods, such as the American or revised, such as codes, reference and guide specifica-
Society of Testing and Materials (ASTM), those standards tions, reports, and guides. All documents are developed
should be referenced in ACI documents. through ACI’s consensus procedures.
Committee documents are classified as those requiring
As part of their participation in committee activities,
and those not requiring standardization.
ACI committee members contribute to the committee’s
work products, including written works. All work prod-
Documents Requiring Standardization
3.2.1
ucts of ACI committees belongs to ACI. By participating
in committees, ACI committee members acknowledge
Standardization is the most rigorous consensus process
that the rights to such work products, including any copy-
used by ACI. It ensures the widest input and high overall
right, reside with ACI.

Chapter 3 – Committee Documents


March 2004
ACI Technical Committee Manual — 2004 13

quality assurance for a document. The ACI standardiza- They must be worded in explicit, mandatory language
tion process is approved by the American National Stan- so that there is only one possible legal interpretation. Be-
dards Institute (ANSI) and is given in Chapter 5. Docu- cause the entire code (including appendices, synopses,
ments can be identified as ACI standards; however, the and footnotes) is a legal document, codes shall cite only
word “Standard” will not appear in the title although the mandatory-language documents. Additional references to
phrase “An ACI Standard” will appear on the cover of the guides, reports, papers, and research results can be made
document. in a separate commentary (3.2.1.5).

Standardized documents may be written using options An ACI code shall not have the effect of requiring pro-
(a), (b), or (c): prietary items or methods (3.3.2.2), and shall not state that
its provisions shall govern when in conflict with a refer-
(a) Nonmandatory language where the document is encing code or body.
providing recommendations; or
(b) Mandatory language where the document is A technical committee intending to develop a new code
providing compulsory requirements; or must request TAC approval before beginning to work on
(c) Both nonmandatory and mandatory language. the document. The request shall indicate the scope of the
code and why it is needed.
If option (c) is used, the nonmandatory language por-
tion of the document must be separated from the manda- Code Cases
3.2.1.2
tory portion. This can be achieved with a commentary,
appendix, series of notes per ASTM style, or different A code case clarifies an existing code or provides new
typeface. For example: provisions for situations not covered by an existing code.
Specific requirements in code language provide rules for
The minimum concrete cover shall be 2 in. additions or alternatives not covered by an existing code.
(mandatory portion). Code cases ensure that such clarifications or provisions
Increased cover may be required (nonmanda- are given general distribution.
tory portion).
The Managing Director of Engineering considers code
The method of delineation for mandatory and case requests, and if accepted, a processing fee is charged.
nonmandatory portions of the document must be defined Individuals requesting an official code case must do so in
clearly in the preface. writing. The Managing Director of Engineering acts as a
liaison between the individual and the appropriate com-
Documents written using options (b) and (c) can be mittee and is responsible for submitting requests to the
referenced by model codes or by authorities having juris- committee. The code case will be published in an ACI
diction over local building codes, or they can be refer- periodical within six months of the date of approval. (See
enced in Project Specifications. 5.5.6.1 for approval process.)

If the document does not provide compulsory require- A code case applies only to the designated edition of a
ments, the committee should use option (a). In addition, code (for example, ACI 318-02) and not to other editions.
reports and guides can become ACI standards using op-
tion (a). Reference Specifications
3.2.1.3

Documents in the categories defined in the following Reference specifications are written to be referenced as
sections are intended to be produced and maintained with part of a contract between an owner and a builder and
periodic revision as ACI standards (5.4, 5.5). must be worded in explicit, mandatory language subject
to only one possible interpretation.
Once a document has completed the ACI standardiza-
tion process, committees may request TAC permission to ACI reference specifications must conform to the re-
submit the standard to ANSI for adoption. quirements of the ACI Specification Manual.
A technical committee proposing to develop a new ref-
3.2.1.1Codes erence specification must obtain TAC approval before
ACI codes are written to be adopted by governmental beginning to work on the document. The proposal shall
or regulatory bodies for the regulation of design and con- indicate the scope of the specification and why it is
struction of concrete or masonry structures. ACI codes are needed. Titles of reference specifications should clearly
intended to provide minimum requirements for concrete indicate that they pertain to construction. For guide speci-
or masonry structures to safeguard the public safety, fications, see 3.2.1.7.
health, and general welfare.

Chapter 3 – Committee Documents


March 2004
14 ACI Technical Committee Manual — 2004

3.2.1.4Provisional Specifications and Test 3.2.1.7Guide Specifications


Methods A guide specification presents direction on a subject in
Provisional specifications and test methods provide general terms. Various characteristics, procedures, and
interim guidance to expedite development and updating of alternatives with advantages and disadvantages are given.
codes or specifications. After publication, they are to con- It is not a reference specification and shall not be incorpo-
tinue to be processed (5.5.6.2) through the Normal Stan- rated into the Contract Documents by reference; however,
dardization Procedure. They are worded in explicit, man- it directs the Architect/Engineer as to what must be in-
datory language and subject to only one possible interpre- cluded in Project Specifications. The document shall be
tation. They can be referenced by other codes or prepared in a specification and commentary format with
specifications. the recommended mandatory language portion clearly
delineated from the commentary portion.
The committee is to follow the ACI Specification Man-
ual format for preparing provisional specifications, and A technical committee proposing to develop a new
follow the ASTM Form and Style Manual format for pre- guide specification must obtain TAC approval before be-
paring provisional test methods. If a provisional test ginning to work on the document. The proposal shall in-
method falls within the scope of an ASTM subcommittee, dicate the scope of the specification and why it is needed.
it should be presented to that subcommittee for adoption Titles of guide specifications should clearly indicate that
as an ASTM test method. they pertain to construction.

3.2.2Documents Not Requiring Standardization


A technical committee proposing to develop a Provi-
Technical committees may author or sponsor any of the
sional Specification or Test Method must obtain TAC
following types of ACI documents that do not require
approval before beginning to work on the document. The
standardization:
proposal shall indicate the scope of the Provisional Speci-
fication or Test Method and why it is needed.
3.2.2.1Guides
ACI guides present direction for the analysis, design,
3.2.1.5Commentaries construction, selection or testing of concrete materials or
ACI commentaries complement codes (3.2.1.1) and structures. Guides make committee consensus recommen-
specifications (3.2.1.3), and often provide supporting dations on best practice in the covered area. If the com-
documentation for provisions of the codes or specifica- mittee does not give recommended actions, the document
tions. They are organized to parallel the section number- should not be titled as an ACI guide.
ing in the codes or specifications; however, all sections in
A guide can provide pertinent examples and case stud-
the codes or specifications do not require corresponding
ies to explain covered concepts, as well as indicate advan-
sections in the commentaries.
tages and disadvantages of various alternatives. As with
all nonstandardized ACI documents, guide language shall
A commentary is written in nonmandatory language
be nonmandatory. See “Guide for Measuring, Mixing,
and can reference documents that are written in nonman-
Transporting, and Placing Concrete (ACI 304R)” as an
datory language. Commentaries may offer alternatives for
example.
satisfying specific provisions in the codes or specifica-
tions, and may refer to patented items (3.3.2.2) that can be
used to meet the intent of a specific provision. Because 3.2.2.2Reports
they are written in nonmandatory language, commentaries ACI reports supply consensus information on concrete
cannot be referenced by codes and specifications. 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,
3.2.1.6Standardized Reports and Guides
design or construction methods, or current knowledge on
Standardized reports and guides present recommended
a particular concrete technology. As with all nonstandard-
or mandatory methods and materials to be used in plan-
ized ACI documents, report language shall be nonmanda-
ning, design, execution, or inspection of construction, and
tory. See “Design, Manufacture, and Installation of Con-
in preparing project specifications.
crete Piles (ACI 543R)” as an example.
Committees that develop reports and guides, and want
to have their documents subjected to public consensus 3.2.2.3Bibliographies
review, must follow the ACI Document Adoption and Committees should not include bibliographies in com-
Publishing Procedures (5.5). mittee documents.

Chapter 3 – Committee Documents


March 2004
ACI Technical Committee Manual — 2004 15

3.2.2.4Handbooks and Manuals 3.3.2References


Handbooks and manuals are practice-oriented and serve Committee documents should reference existing stan-
as reference documents for design professionals and field dardized documents or reports instead of duplicating their
personnel. text. See the ACI Style Manual for details on references
within documents.
Handbooks are design aids and typically contain charts
and tables to facilitate design of concrete structures. They When the committee document is revised or updated
may also include examples to illustrate specific design (5.10), references should also be updated. When updating
methods. Examples of handbooks include SP-17, ACI references such ASTM test methods or specifications, the
Design Handbook, and SP-4, Formwork for Concrete committee should make sure that the document’s text is in
(which is individually authored but committee spon- accord with the revised reference. The committee’s edito-
sored). rial subcommittee (1.3.2, 3.4) should compare the text
with the references. If there is a discrepancy, it should be
Manuals generally provide guidance and instructions to brought to the attention of the full committee for action.
field personnel involved in different aspects of concrete
construction. An example is SP-2, ACI Manual of Con- 3.3.2.1References within Specifications
crete Inspection. For handling references in guide and reference specifi-
cations, see the ACI Specification Manual.
Emerging Technology Series
3.2.2.5
3.3.2.2 Reference to Patented Items
This type of document deals with an emerging technol- ACI codes and specifications shall not refer directly to
ogy for which there is insufficient knowledge to write a a particular patent or proprietary technology by use of
comprehensive ACI document. It is intended to introduce trademarks or trade names. If a code or specification re-
a new technology into practice by providing basic infor- quirement can only be satisfied practicably by use of a
mation to allow implementation and permit accumulation patented material, product, process, procedure, or appara-
of performance histories. The document should include a tus, full and apparent disclosure of the controlling patent
statement of limitations (3.9.2) and a discussion of re- shall be made within the commentary of the code or the
search needed to provide the missing information. These optional requirements checklist of the specification.
documents are identified by the letters ETS in their
designation; for example, ACI 300.ETS. The document ACI code and specification requirements shall not man-
shall have a limited lifetime of ten years, after which it is date the use of patented items, but they may allow
either to be withdrawn or written as one of the regular patented technology as a possible solution. During the
type of ACI documents. See 3.9.2 for the required balloting (4.2) of such a code or specification require-
introductory statement. ment, the committee shall be informed on the ballot that
the ballot item involves the potential use of a patented
technology. See 3.9.3.2 for disclaimer note on patented
Preparation of Committee Documents
3.3
technology.
Sometimes the simplest, quickest, and most direct ap- The following example illustrates how a hypothetical
proach is for a qualified individual, such as the chair, to patented item could be referenced in the commentary of
prepare the first draft. Individuals can be called upon to an ACI code.
add to the draft where needed. The draft is submitted to
the entire committee for review, comment, and revision. Code Commentary
Participation by all members generally produces the best
results. After the committee approves the document by a 11.5.5 The following 11.5.5 (d) The Jiffy Plate
letter ballot (4.2.1), the document is the consensus of the types of steel rein- System®, covered by U.S.
committee. High quality editorial and technical treatment forcement are permit- Patent 52356xx, is an ex-
of a subject is expected (1.3.1.2, 3.4). ted: ample of a product that may
be used to meet this re-
See the ACI Style Manual for details on preparation of (a) deformed bars, quirement. ACI does not
committee documents for TAC review. See TCM Section (b) structural shapes, endorse this technology or
5.1 for the procedure to submit documents for TAC re- (c) rods with enlarged warrant that the use of this
view. heads, or technology will meet code
(d) cut plate steel with requirements. The selection
Organization of Material
3.3.1 enlarged ends of any design methodology
See the ACI Style Manual For details on organizing or use of any patented tech-
material within a document. nology is at the option of
the user.

Chapter 3 – Committee Documents


March 2004
16 ACI Technical Committee Manual — 2004

Editorial Review
3.4
Policy on ACI Certification Programs
3.5.2
Before final committee letter ballot (4.2.1), a document
In November 1997, the ACI Board of Direction en-
must be edited thoroughly by the committee’s editorial
dorsed incorporating ACI certification requirements into
subcommittee (1.3.1.2). When submitting the document to
all appropriate ACI committee documents, including
TAC (5.1), the chair must state that the editorial subcom-
standardized documents. The intent of this policy is to
mittee has completed its task.
improve the quality of concrete construction; it is not in-
Editorial changes may be made at any time without tended to force attendance at ACI sponsored certification
requirement of letter ballot except as a result of a negative programs.
vote (4.1.3, 4.5, 4.1), in which case confirmation by the
committee is required. Editorial changes are of two types: Wording in technical committee documents regarding
requirements or recommendations for certification must
• Those that introduce no change in technical content, allow for alternative means of certification, if such are
but correct editorial style, change nontechnical in- available. For example, appropriate wording could be:
formation or reduce ambiguity; and “Field testing of concrete shall be done by an individual
• Those that correct typographical errors in substance who has obtained certification as an ACI Concrete Field
(essential information that could be misused). Testing Technician, Grade I, or equivalent.” Reviewers of
all ACI technical committee documents are specifically
The editorial subcommittee (1.3.1.2) should review for instructed to identify any appropriate areas in the docu-
document structure, sentence structure, grammar, redun- ment being reviewed where requirements or recommenda-
dancy, spelling, and typographical errors. Because many tions for certification could be included.
people contribute to a document, it is essential that the
subcommittee review the separate sections for consistency ACI certification is currently available in the following
in style and format. See the ACI Style Manual for guid- areas:
ance on style, grammar, and format.
• Concrete Field Testing Technician, Grade I
Before a document is submitted to TAC for review, it
• Concrete Laboratory Testing Technician, Grade I
also must undergo an editorial review by staff. To allow
• Concrete Laboratory Testing Technician, Grade II
staff sufficient time to conduct the review and make nec- • Concrete Construction Special Inspector & Inspector
essary changes, documents shall be submitted to the Man- In-Training
aging Director of Engineering at least three months be- • Concrete Flatwork Finisher/Technician
fore the next scheduled TAC meeting. • Concrete Transportation Construction Inspector &
Staff sends the editorially revised document to the com- Inspector In-Training
mittee chair for approval and permission to submit to • Concrete Strength Testing Technician
TAC for review. • Field Aggregate Testing Technician
• Laboratory Aggregate Testing Technician
• Tilt-Up Supervisor/Technician
Board Policies
3.5 • Shotcrete Nozzelman – Dry Mix
The ACI Board of Direction has established the follow- • Shotcrete Nozzelman – Wet Mix
ing specific policies that can affect technical documents: • Canadian Standards Association (CSA) Based Con-
crete Field Testing Technician – Grade I
• Canadian Standards Association (CSA) Based Con-
3.5.1Policy on Performance Specifications crete Construction Special Inspector & Inspector In-
Where possible, performance rather than prescriptive Training
standards should be used. In ACI committee documents,
the requirements for concrete mixtures should be stated Additional information on the ACI certification pro-
by enumerating limits on properties of the freshly mixed grams may be obtained from ACI headquarters or the
and hardened concrete such as slump, air content, density, chair of the ACI Certification Programs Committee.
potential quality of paste (by a limit on water-cementi-
tious materials ratio), and strength. The requirements may Policy on High-Performance Concrete
3.5.3
be stated by limits on proportions of ingredients and other
such limitations as may be required by the work. When ACI technical committees should draft documents so as
the latter procedure is used, the document shall also in- to not inhibit or preclude the use of high-performance
clude an alternative procedure that permits concrete hav- concrete.
ing equivalent specified properties.

Chapter 3 – Committee Documents


March 2004
ACI Technical Committee Manual — 2004 17

Policy on Units of Measurement


3.5.4 Posting of draft documents on the committee’s ACI
Web site is encouraged (Appendix B). Circulation of draft
The American Concrete Institute (ACI) supports con- documents on independent web sites is not permitted
version to and increased use of the International System since control, copyright, and status of the document are
of Units (SI) (1.11.2). To promote and facilitate the use of not secure.
SI in concrete design and construction, the following
timetable is adopted: Coordination Procedures
3.7

Effective January 1, 2000, the general policy of ACI Coordination


3.7.1 with Other Technical
shall be that all new and revised ACI codes shall be pub- Committees
lished in two separate versions, one using inch-pound
units and one using hard-converted SI units. Exceptions Coordination with other technical committees is an im-
to this policy will depend upon industry needs and TAC portant part of processing documents (1.6.5, 2.5). It helps
approval. prevent conflicts and overlaps between committee docu-
ments. Some reasons for coordination with other commit-
Also effective January 1, 2000, all new and revised ACI tees might be:
specifications, standards, other publications, and visual
materials used in convention technical sessions or else- • Information developed is incorporated or referenced
where shall use either dual units or SI units only. Specifi- in documents of other committees;
cations may be published in two separate versions as ap- • The committee depends on the work input of another
proved by TAC. committee;
• Various committees may develop documents with
All conversions shall conform to the latest version of parallel or overlapping subjects.
IEEE/ASTM SI 10, supplemented where applicable by
ASTM E 621. In making hard conversions, due considera- A copy of the draft shall be sent to the chairs of related
tion shall be given to uniformity among Institute docu- committees at the time of letter ballot (4.2), with a request
ments and to availability of metric products for concrete to review and comment on overlapping subjects. When
construction. the document is submitted to TAC for review (5.1), the
chair is to provide a report of the committees that partici-
ACI Board Committees shall establish provisions to pated in the review.
implement this policy.
If a document contains definitions, a glossary, or new
TAC shall review and recommend revisions to this pol- symbols, it shall be sent to Committee 116, Terminology
icy to the Board on an as-needed basis to meet the de- and Notation, for review. If a document contains con-
mand for metrication of ACI documents. struction tolerances, it shall be sent to Committee 117,
Tolerances, for review.
Circulating Draft Documents
3.6
The reviewing technical committees do not have a vote
A committee document may undergo significant but can make constructive comments. If substantial diffi-
changes in technical content and format before final culties arise between two committees, the matter is re-
committee and TAC approvals. Therefore, drafts should ferred to TAC for arbitration.
be marked clearly “draft document, not for publication.”
The chair may approve circulating the draft outside the New and revised documents are not to be held back
committee, TAC, and ACI headquarters. This should be because of conflict with or variation from existing ACI
done only to obtain expert technical advice not available documents. Variances from information in existing ACI
in the committee or to ensure that all interested parties are documents, however, must be substantiated.
given an opportunity to express viewpoints when
developing an ACI standard. See 3.7.1 for coordinating Committees should be aware of documents published in
with other committees. the ACI Manual of Concrete Practice and should keep
abreast of papers and committee documents published in
Committee documents, at any stage of development, the ACI Journals and Concrete International. The chair or
must not be released for publication other than to the In- designated voting member should examine each published
stitute or cosponsors of joint committees (1.10), except on committee document for possible conflict with the
approval of TAC. Similar restrictions apply to test data or committee’s work.
unpublished technical information circulated in a commit-
tee.

Chapter 3 – Committee Documents


March 2004
18 ACI Technical Committee Manual — 2004

Coordination with the TAC Specifications


3.7.2
Introductory and Disclaimer Statements
3.9
Committee (TSC)
Under certain conditions, ACI documents require intro-
A committee proposing to develop a specification
ductory or disclaimer statements to be included when the
(3.2.1.3, 3.2.1.7) shall submit a statement of objectives
documents are printed.
and an outline to the Managing Director of Engineering
for TAC review. TSC (1.11.4) evaluates the proposal and
submits recommendations to TAC. ITG Introductory Statements
3.9.1
In the introduction to each Innovation Task Group
If TAC approves the proposal, TSC appoints one of its (ITG) document, statements describing the ITG process,
members as a liaison member to the proposing committee. whether any technology described is patented or other-
Also, the committee should appoint one of its members to wise proprietary, and an acknowledgement of funding
be an associate member of TSC. The TSC liaison member must be given.
is to be added to the committee’s list to receive corre-
spondence so TSC will be aware of the committee’s pro- • Statement describing the ITG process:
gress. If necessary, the liaison should give the committee ACI created a committee category called Innova-
recommendations on specification language and format. tion Task Groups (ITGs) as a mechanism to acceler-
Committees are to follow the ACI Specification Manual ate the standardization of new technology that has
when preparing specifications. been properly evaluated and documented. Any party
may submit to the TAC Technology Transfer Com-
TSC reviews the proposed specification at the time of mittee a technology for ITG consideration. When
committee letter ballot (4.2). After letter ballot approval formation is approved by TAC, ITGs have the spe-
and consideration of TSC comments, the committee shall cific mission of creating a proposed standardized
submit the specification, the TSC comments, and the document (subject to ACI consensus balloting proce-
committee’s response to TAC for review (5.1). dures), submitting it for the normal ACI document
review process, then submitting it for public review
TAC considers the TSC comments regarding format
for normal standardization.
and style. TAC makes the final decision about all docu-
ments.
• Statement regarding the funding of the ITG
(if appropriate):
Coordination with the Construction
3.7.3
To facilitate the development of this document,
Liaison Committee (CLC)
funds have been provided by [XXXX]. These funds
were made available to pay for a portion of the travel
Part of the Board of Direction’s Construction Liaison
and meeting expenses of the ITG, as well as possible
Committee (CLC) mission is to review any technical
honoraria to members of the ITG.
committee document that deals with constructability and
economy. Staff sends those documents that contain items
on construction to CLC for review, and the CLC com- Emerging Technology Introductory State-
3.9.2
ments are to be considered. These comments shall be re- ment
turned to the Managing Director of Engineering. The cover page of emerging technology documents
(See 3.2.2.5) shall include the following statement:
Technical Documents Not Authored by ACI
3.8 ACI encourages the development and appropriate use
Technical Committees of new and emerging technologies through the publication
of the Emerging Technology Series. This series presents
Technical Documents Authored by ACI
3.8.1 information and recommendations based on available test
Chapters data, technical reports, limited experience with field ap-
plications, and the opinions of committee members.
ACI chapters may publish their material freely without
The presented information and recommendations, and
TAC approval. However, they must use a disclaimer stat-
their bases, may be less fully developed and tested than
ing that the document was prepared and reviewed by the
those for more mature technologies. This report identifies
chapter and had not been reviewed or approved by ACI
areas in which information is believed to be less fully
International. Chapter documents must only use chapter
developed, and describes related research needs. The pro-
logos on their documents.
fessional using this document should understand the limi-
If a chapter wishes to use the ACI International logo, tations of this document and exercise judgment as to the
the document is to be processed through an existing ACI appropriate application of this emerging technology.
technical committee and receive a TAC review.

Chapter 3 – Committee Documents


March 2004
ACI Technical Committee Manual — 2004 19

Patented Items
3.9.3 3.9.3.2Disclaimer Statement
Any reference to a patented technology (See 3.3.2.2)
shall include the following note:
Introductory Statement
3.9.3.1
ACI does not endorse this technology or warrant that
Include the following statement regarding patented the use of this technology will meet code requirements.
items, if appropriate (See 3.3.2.2): The selection of any design methodology or use of any
patented technology is at the option of the user.
This ACI document contains requirements that can, at
the time of the document’s adoption by ACI, be satisfied
Disclaimer of Government Endorsement
3.9.4
practicably only by use of a patented material, product,
Participation by governmental representatives in the
process, procedure, or apparatus. During the document
work of the American Concrete Institute and in the de-
preparation and balloting, the committee and TAC were
velopment of Institute standards does not constitute gov-
informed in writing that the document under considera-
ernmental endorsement of ACI or the standards that it
tion involves the potential use of patented technology.
develops.

Chapter 3 – Committee Documents


March 2004
20 ACI Technical Committee Manual — 2004

CHAPTER 4 for resolving negative votes (4.5) allow differing opinions


to be addressed without stopping progress on a document.
BALLOTING COMMITTEE DOCUMENTS
Following the final letter ballot and resolution of all
negatives, the committee chair shall submit the document
4.1 Types of Voting Methods for TAC review (5.1).

Three types of voting methods are used in the prepara- 4.2.2Subcommittee Letter Ballot
tion of committee documents: Committees that have subcommittees as described in
1.4.2.6 shall establish procedures for subcommittee letter
4.1.1 Letter Ballot ballots. There is no requirement that negatives on sub-
Issued by the chair and voted on by the members, it is committee ballots be resolved in the same manner as
an official written action to determine if an item has con- negatives on committee ballots. The general objective is
sensus. A letter ballot (See Appendix 4.1.1) can be used to seek consensus within the subcommittee and ensure
to initiate action on new business or resolve negative that reasons for negative votes on subcommittee ballots
votes from a previous letter ballot. are forwarded to the full committee.

4.1.2 Meeting Ballot ITG Review and Letter Ballot


4.2.3
A motion called for at a meeting and voted on by the When an ITG document is drafted (1.12.3), the ITG
members at that meeting. A meeting ballot is an official subjects it to letter ballot:
action to determine if a proposed resolution of a negative • The ITG chair recommends three outside reviewers
vote from a previous letter ballot item has the consensus for approval by the TTTC chair. After approval by
of the committee (4.5). the TTTC chair, the TAC Contact Member appoints
three outside reviewers. These outside reviewers shall
No-Protest Consent
4.1.3 represent a wide range of interests outside the ITG
A notification to the committee membership (See Ap- and they shall have no direct economic interest in the
pendix 4.1.3.a) to confirm changes to documents that are outcome of the ITG evaluation or document devel-
made to: opment. The three outside reviewers are designated
as voters by the TTTC chair and are chosen to pro-
• Satisfy negative voters (4.5), vide broad input. Up to three additional nonvoting
reviewers may be selected, and act in the capacity of
• Address TAC review comments (5.3.1), or
outside reviewers (5.2). The task of the nonvoting re-
• Approve a closure statement (5.7).
viewers is to provide detailed technical review of the
document.
The lack of response by voting members is taken as
• The document is balloted by the members of the ITG
agreement with the changes. After 30 days, the review
and the three voting outside reviewers, following the
period is over, and the chair must notify the committee of
letter balloting procedures (4.3 through 4.5).
the results of the no-protest consent (See Appendix
4.1.3.b). • The ITG approved document is submitted to TAC for
review and approval (5.1).
Letter Ballots
4.2
Letter Ballot Procedures
4.3
Letter ballots are used to provide a record of actions Initiating a Letter Ballot
4.3.1
approved by the committee or by a subcommittee. A committee chair can initiate a letter ballot or a voting
member can call for a ballot through a motion at a com-
4.2.1Committee Letter Ballot mittee meeting. A simple majority of voting members
A committee letter ballot (See Appendix 4.1.1) is re- present at the meeting is required to pass such a motion.
quired for approval of new documents, for reapprovals or
withdrawals, and for revisions other than those resulting Letter Ballot Content
4.3.2
from comments on letter ballots. A letter ballot may be issued on a complete document,
on independent parts of a document, or on a revision of a
Letter ballots are a formal means for all committee document. (See 4.7 for interim and progress ballots.)
members to express their views. Efforts should be made
to resolve differences before submitting a document to Letter Ballot Format
4.3.3
letter ballot. Instances where the opinions of one or two Letter ballots should generally follow the sample in
voting members differ from those of the majority should Appendix 4.1.1 - Sample Committee Letter Ballot, and
not be allowed to unduly delay the document. Procedures must include all of the information in the sample.

Chapter 4 – Balloting Committee Documents


March 2004
ACI Technical Committee Manual — 2004 21

Letter Ballot Time Frame


4.3.4 4.3.8 Analysis of Letter Ballot Results
Once a ballot has closed (4.3.4) and the summary
The ballot must contain a closing date and the name of (4.3.7) is prepared, the committee chair must determine
the person to whom ballots are to be returned. The closing whether an item has passed according to ACI procedures.
date normally should not be less than 30 days after the The chair may decide that a prohibitive number of nega-
date of mailing. TAC Contact Member approval is neces- tives has been received, and rather than resolve the nega-
sary to obtain a shorter balloting period. The voting mem- tives individually, the committee needs to rewrite and
bers may be canvassed by telephone or other electronic reballot the document. See Fig. 4.1, Analyzing Ballot
means. The closing date may be extended if needed to Results and Passing of Ballot Item.
obtain the required affirmative ballots for passage of an
item (4.4). Negative votes received during the extended Passage of a Letter Ballot Item
4.4
voting period shall be included in the ballot analysis
(4.3.8). Passage of a document or item requires a letter ballot
(4.2) on the document and resolution of any negative
Letter Ballot Distribution
4.3.5 votes (4.5) by letter ballot or by meeting ballot. Passage
of a letter ballot requires that the number of affirmative
All members eligible to vote shall be sent a letter ballot. votes be at least that given by the 1/2 and 2/3 rules:
Associate, Consulting, and Liaison members shall be sent
the item being balloted for comment. Nonvoting members
may express negative viewpoints, with reasons, on letter The 1/2 At least 1/2 of the voting members vote
Rule affirmatively.
ballot items (1.4.2.4). These negative viewpoints are not
counted in the final ballot tally, do not affect the outcome The 2/3 At least 2/3 of the yes and no votes cast be
of a ballot item, do not have to be resolved (4.5), but must Rule affirmative.
be distributed to the committee for consideration. Copies
of the item being balloted and the letter ballot shall be In some cases, the resolution of a negative vote
sent to the TAC Chair, TAC Contact Member, and Man- changes the vote to an affirmative vote. This can result in
aging Director of Engineering. passage of an item or document that had initially failed
(See Example 5).
Letter Ballot Negative Votes
4.3.6
Letter Ballot Item Passing
Example 1
A negative vote on a letter ballot must be explained in
writing to receive committee consideration (4.5). The On one letter ballot for a 33-member committee, 24
voter should provide alternative wording that would sat- ballots are returned. There are 20 yes votes, 2 no votes,
isfy the voter’s concerns. Resolution or disposition of and 2 abstentions. More than 1/2 of the voting members
every negative vote with comments on a letter ballot must voted affirmatively, and more than 2/3 of the yes and no
be documented (5.1). votes cast were affirmative, so the ballot meets the 1/2
Rule and the 2/3 Rule. Once the negative votes are re-
If the negative voter does not supply a reason for the solved (4.5), the ballot item will pass.
negative vote, it is recorded as a negative without com-
ment. A negative vote without comment is counted as an  Letter Ballot Item Not Passing
Example 2
abstention when determining if a ballot passes and the
negative vote does not need to be resolved in accordance On another letter ballot of the same 33-member com-
with the procedures of 4.5. mittee, 22 ballots are returned. There are 16 yes votes, 4
no votes, and 2 abstentions. The ballot item fails because
Letter Ballot Summary
4.3.7 it does not meet the 1/2 Rule  at least 17 of the eligible
voters needed to vote affirmatively.
A ballot summary (See Appendix 4.3.7) shall be com-
pleted and sent to the Managing Director of Engineering Letter Ballot Item Not Passing
Example 3
for each letter ballot. For standardized documents, a copy
of each voting member’s ballot from the final ballot shall On another letter ballot of the same 33-member com-
be sent with the ballot summary. A ballot summary allows mittee, 30 ballots are returned. There are 17 yes votes, 10
a complete ballot history to be maintained at headquarters no votes, and 3 abstentions. The ballot item meets the 1/2
during a document’s formation, even if the committee’s Rule, but fails because it does not meet the 2/3 Rule. Of
personnel should change. The ballot summary includes a the 27 yes and no votes cast, at least 18 needed to be af-
list of voting members at the time of the final ballot. firmative.

Chapter 4 – Balloting Committee Documents


March 2004
22 ACI Technical Committee Manual — 2004

Resolution of Negative Votes


4.5 4.5.2 Unrelated
The stated reason for the negative vote may be unre-
ACI consensus procedures require that the committee lated to the item being balloted. In either a letter ballot or
must resolve all negative votes from voting members ei- a meeting ballot, affirmative votes from at least 2/3 of the
ther by letter ballot (4.1.1) or by meeting ballot (4.1.2). affirmative and negative votes are required to find an item
Each negative vote must be accompanied by a reason. unrelated (2/3 rule). Note that neither the 1/2 rule nor the
40% rule (4.5.3) apply to a ballot to find a negative vote
A negative vote can be resolved in the following ways: unrelated. Negative votes on a ballot to find a reason un-
related do not have to be resolved. If the negative vote is
• The voter can withdraw the negative vote (4.5.1); found unrelated, it is recorded in the minutes as an absten-
• The reason for the negative vote is unrelated to the tion.
balloted item (4.5.2);
• The reason for the negative vote is related to the bal- 4.5.3Related: Nonpersuasive
loted item, but nonpersuasive to the committee The committee may disagree with the reason given for
(4.5.3); a related negative vote. In this case, the committee must
• The reason for the negative vote is related to the bal- find the voter nonpersuasive by meeting ballot or by letter
loted item, persuasive to the committee, and is satis- ballot. Negative votes on these ballots do not need to be
fied by an editorial change to the item balloted resolved.
(4.5.4.1);
• The reason for the negative vote is related to the bal- To be able to find negative votes nonpersuasive by let-
loted item, persuasive to the committee, and is satis- ter ballot, it is necessary to meet both the 1/2 and 2/3 rules
fied by a substantive change to the item balloted (4.5).
(4.5.4.2). To be able to find negative votes nonpersuasive by
meeting ballot, it is necessary to meet the 40% rule and
The resolution of all negative votes (either at meetings the 2/3 rule:
or between meetings) must be recorded in the minutes
(2.3.4) of the meeting. The no-protest consent (4.1.3) ap- 40% At least 40% of the voting members vote
plies to any change to the document made at a meeting to Rule affirmatively. (Applies to meeting ballots)
satisfy persuasive negative votes. A protest from a com-
mittee member will be handled as new business. This new The 2/3 At least 2/3 of the affirmative and negative
business item is to be recorded in the committee minutes Rule votes cast be affirmative.
as new business and is to be carried on the agenda until
The 40% rule does not apply to ACI Committee 318
resolved. The resolution is to be documented in the min-
and ACI Committee 530; they will resolve negatives us-
utes.
ing ½ rule.
A member whose negative vote is found unrelated or
When the 40% rule is used, the member whose negative
nonpersuasive must be notified in writing of the right to
vote was found nonpersuasive by meeting ballot shall be
appeal in accordance with 5.5.10. A note in the minutes is
notified of the right to invoke a letter ballot. When the
considered sufficient notice of this right.
chair receives such a request, the results of the meeting
ballot are voided, and a full committee letter ballot must
Figure 4.2 provides an overview of the process for re-
be conducted to resolve the negative vote. Note that no
solving negative votes. Note that the sections do not have
such right exists if more than 50% of the voting members
to be followed in sequence; rather, they represent differ-
vote affirmatively.
ent ways to resolve a negative vote.
When a negative vote is found to be nonpersuasive,
Withdrawn
4.5.1 report in the meeting minutes that the negative was found
nonpersuasive, give the vote count, and the committee’s
The voter may be willing to withdraw the negative vote.
reasons for the finding.
Many negative votes are the result of a misunderstanding
or misinterpretation of the document being balloted. If the
Related: Persuasive
4.5.4
negative vote is withdrawn, record the vote as affirmative
The committee may, by letter or meeting ballot, find the
or abstention in accordance with the voter’s wishes.
reason for the negative vote persuasive. In this case, de-
Changes to a vote can be done by the voter either at a
termine if resolution of a persuasive negative vote re-
committee meeting or in writing and must be recorded in
quires an editorial or substantive change. Editorial
the meeting minutes.

Chapter 4 – Balloting Committee Documents


March 2004
ACI Technical Committee Manual — 2004 23

changes are defined in 3.4. Determination of whether a Example 5Changing Votes on a Letter Ballot
proposed change is editorial or substantive is sometimes a by Resolving Negatives
judgment call on the part of the chair. If there is reason-
able doubt or if there is an objection by a voting member, The same 33-member committee letter ballots another
the proposal must be treated as a substantive change item and 22 ballots are returned. The votes are 15 affirma-
(4.5.4.2). tive, 3 negative, and 4 abstentions. They need 17 affirma-
tive votes, so this ballot initially fails because it does not
4.5.4.1Persuasive: Editorial Change meet the 1/2 Rule of eligible voters (4.4). Rather than
A negative voter may be satisfied with an editorial reballoting the item, the chair hopes to resolve the nega-
change. In this case, change the document and report in tives to pass the ballot.
the minutes that, after an editorial change, the voter
agreed to change the vote to an affirmative. The negative At the committee meeting with 18 members present,
is now recorded as an affirmative. See Fig. 4.3, Flowchart one negative is found unrelated (4.5.2) by a vote of 12
for Negative Vote Found Persuasive. affirmative, 2 negative, and 4 abstentions (affirmative
votes from 40% of the eligible voting members are not
4.5.4.2Persuasive: Substantive Change required). The negative vote is recorded as an abstention
The committee may find the reason for the negative (4.5.2).
vote persuasive, and a substantive change to the document
is required. The change must be approved by a letter bal- The chair rules that the second negative is persuasive
lot or a meeting ballot. and can be resolved by an editorial change. No committee
member objects. The negative voter is present and agrees
When approving the substantive change by letter ballot, to withdraw the negative and vote affirmative. The
the 1/2 rule and the 2/3 rule must be met. Negative votes change is made and the negative vote is recorded as an
must be resolved. affirmative vote (4.5.4.1) bringing the total to 16 affirma-
tive votes.
When approving the substantive change by meeting
ballot, the 40% rule and the 2/3 rule must be met. Nega- The majority of members present agree that the third
tive votes must be resolved. The 40% rule does not apply negative is persuasive and the recommended change is
to ACI Committee 318 and ACI Committee 530; they will substantive. The meeting ballot to make the change re-
resolve negatives using ½ rule. sults in 17 affirmative votes and 1 negative vote. Another
meeting ballot is needed to find this latest negative vote
If the ballot taken on the substantive change is unani- nonpersuasive. It succeeds with 17 affirmative and 1
mous, including an affirmative vote from the voter who negative votes. Therefore, the third negative vote on the
cast the original negative, the original negative is re- original letter ballot is still recorded as a negative vote,
corded as an affirmative. since the ballot to make the change was not passed unani-
mously (4.5.4.2).
Example 4  Resolving Negative Votes from a
Letter Ballot at a Meeting The letter ballot results are 16 affirmative votes, 1 nega-
On one letter ballot for a 33-member committee, 22 tive, and 5 abstentions. The letter ballot needed 17 af-
ballots are returned. The votes are 16 affirmative, 4 nega- firmative votes; therefore, it still fails and the item must
tive, and 2 abstentions. They need 17 affirmative votes, so be letter balloted again, presumably after revisions.
the ballot initially fails because it does not meet the 1/2
Rule of eligible voters (4.4). Example 6 Persuasive Negative Votes
At a committee meeting with 18 members present, three On one letter ballot for a 20-member committee, 19
of the negative votes are deemed editorial and persuasive ballots are returned. There are 18 affirmative votes, 1
(4.5.4.1) and the voters agree to change their votes. The negative vote (Smith), and 0 abstentions. The ballot
three votes are now recorded as affirmatives, bringing the passes, but the negative vote must be resolved.
total votes to 19 affirmative, 1 negative, and 2 absten-
tions. The original letter ballot now passes by satisfying At their next meeting with 18 members present, the
both the 1/2 Rule and the 2/3 Rule. majority of members agree that the reason for the nega-
The remaining negative vote is found nonpersuasive by tive is persuasive and the recommended change is sub-
a 16 to 2 vote (4.5.3), thus satisfying both the 40% rule stantive. There is a meeting ballot to adopt Smith’s rec-
and the 2/3 rule. ommended change.

Chapter 4 – Balloting Committee Documents


March 2004
24 ACI Technical Committee Manual — 2004

As given in 4.5.4.2, by a total of 17 affirmative votes 4.7Interim and Progress Committee Ballots
and 1 negative vote (Johnson) the meeting ballot passes;
however, Johnson’s negative vote must be resolved. John- When committee documents are divided into chapters
son states his reasons for voting negative; he agrees a or sections, interim and progress committee ballots can be
change must be made but argues for a different change. used to bring out objections and crystallize opinions. A
The committee finds him persuasive with 17 affirmative letter ballot on the completed document or on each part of
votes and 1 negative vote (Lee). The committee must now the document must be taken before submission to TAC.
find Lee nonpersuasive (4.5.3), which they do with a vote For meeting the submittal procedures of 5.1, a letter ballot
of 17 affirmatives and 1 negative (Lee). on the entire document is preferable.

Johnson’s change is incorporated, and the original Special Ballot Procedures


4.8
negative vote by Smith is now resolved. The meeting bal-
lot results and the changes incorporated must be recorded Special ballot and operating procedures have been ap-
in the committee’s minutes. proved for Joint ACI-ASME Committee 359. Copies of
the TAC approved procedures can be obtained from
headquarters.
Example 7Difference Between A Meeting Ballot
And A Letter Ballot
Proxy Votes
4.9
On one letter ballot for a 33-member committee, 22 Proxy voting is not allowed.
ballots are returned. The votes are 20 affirmative, 1 nega-
tive, 2 abstentions, and 10 unreturned ballots. The letter Procedure for Reapproval of Committee
4.10
ballot passes because it meets the 1/2 and 2/3 Rules. Documents

At the following committee meeting with 18 members Purpose


4.10.1
present, the committee conducts a meeting ballot to find Reapproval of a committee document is appropriate
the negative vote nonpersuasive (4.5.3). The meeting bal- where the committee is preparing a substantive revision to
lot results in 15 affirmative and 3 negative votes. While an existing document, but wishes to keep the existing
the 15 affirmative votes would not have passed a letter document available in the Manual of Concrete Practice,
ballot (1/2 rule), a meeting ballot only requires 40% of the or where an existing report continues to be valid.
33-member committee (33 x 0.4 = 14) to vote affirma- 4.10.2Initiation
tively (4.5.3). The negative vote is resolved, and the bal- A committee chair can initiate a letter ballot to reap-
loting on this item is complete. The chair must inform the prove a committee document.
negative voters of their right to invoke a letter ballot.
4.10.3Responsibility
Affirmative Votes with Comments
4.6 The ACI Engineering Department, upon request, will
issue reapproval letter ballots (See Appendix 4.10.4) on
The ACI letter ballot form (See Appendix 4.1.1) allows behalf of the chair. Tallying votes and providing a ballot
for affirmative votes with editorial comment. Many times, summary, however, are the responsibility of the chair.
a voting committee member makes comments that are
beyond editorial. These comments need to be resolved by
Format
4.10.4
the committee as if they were negative votes.
Reapproval letter ballots should generally follow the
sample in Appendix 4.10.4. The committee chair shall
If the recommended change is editorial and appropriate,
provide justification for the need for the reapproval.
the committee chair should make the change and no fur-
ther action is required.
4.10.5 Passage
The 1/2 and 2/3 Rules defined in 4.4 apply to reap-
If the recommended change is substantive or if there is
provals. Negative votes must be accompanied by a reason
doubt, the vote is recorded as a negative. The vote must
and resolved in accordance with 4.5. At the close of the
be resolved in accordance with 4.5. See Fig. 4.4 for flow-
ballot, send the ballot summary (Appendix 4.3.7) to the
chart for Affirmative with Comment. A voter may agree
Managing Director of Engineering.
to withdraw the comment and negative vote on the condi-
tion that the committee takes it up as new business. This
new business item is to be recorded in the committee Completion
4.10.6
Headquarters submits the ballot summary to TAC for
minutes as new business and is to be carried on the
review. Reapproval of the document is finished when the
agenda until resolved. The resolution is to be documented
TAC approval of ballot results is completed.
in the minutes.

Chapter 4 – Balloting Committee Documents


March 2004
ACI Technical Committee Manual — 2004 25

Analyzing Letter Ballot Results (4.3.8)


And Passing of Ballot Item

Develop and Letter


Ballot Document

Prepare Ballot
Summary

NO Pass 1/2 Rule? YES

Resolve Negative YES Pass 2/3 Rule? NO


Votes or Reballot

Resolve Negative
Votes or Reballot?

Attempt to Resolve Rewrite and


Negative Votes (4.5) Reballot

Rewrite and Attempt to Resolve


Reballot Negative Votes (4.5)

Resolve Negative
Rewrite and NO Votes and Editorial
Reballot
Comments (4.5)

YES

Document Resolution
of Negative Votes

Notify Committee of Changes


(30 Day No-Protest Consent)

Ballot Passes

Figure 4.1 – Analyzing Letter Ballot Results and Passing of Ballot Items

Chapter 4 – Balloting Committee Documents


March 2004
26 ACI Technical Committee Manual — 2004

Resolution of Negative Votes (4.5)

Resolution of
Negative Votes

Determine
NO Withdraw Negative? Record as Affirmative
whether YES
Unrelated (4.5.2) (4.5.1) or Abstention

Unrelated (4.5.2) Negative Resolved -


Pass 2/3 Rule? YES
Record as Abstention Report to Committee

NO

Related – Is it
Nonpersuasive?
(4.5.3)

Pass Applicable
YES Negative Resolved -
Rules? (4.5.3)* Nonpersuasive (4.5.3)
Report to Committee

NO

Persuasive (4.5.4)
(Figure 4.3)

*If the negative is to be resolved by a letter ballot, the 1/2 Rule and 2/3 Rule must be met. If
the negative is resolved by a meeting ballot, the 40% Rule and 2/3 Rule must be met. The
40% rule does not apply to ACI Committee 318 and ACI Committee 530; they will resolve
negatives using ½ rule.

Figure 4.2 – Resolution of Negative Votes

Chapter 4 – Balloting Committee Documents


March 2004
ACI Technical Committee Manual — 2004 27

Negative Vote Found Persuasive (4.5.4)

Negative Vote
Found Persuasive
4.5.3

Editorial or Substantive
Editorial (4.5.4.1) Change Required? Substantive (4.5.4.2)
(4.6.4)

To Approve -
Make Change – Pass Applicable Rules
Record as (4.5.4.2)*
Affirmative Resolve Negatives

If Unanimous, including
original negative voter,
Negative Resolved – Record as Affirmative
Report to Committee

Negative Resolved –
Report to Committee

*If the negative is to be resolved by a letter ballot, the 1/2 Rule and 2/3 Rule must be met. If
the negative is resolved by a meeting ballot, the 40% Rule and 2/3 Rule must be met. The
40% rule does not apply to ACI Committee 318 and ACI Committee 530; they will resolve
negatives using ½ rule.

Figure 4.3 – Negative Vote Found Persuasive

Chapter 4 – Balloting Committee Documents


March 2004
28 ACI Technical Committee Manual — 2004

Affirmative with Comment (4.6)

Affirmative with
Comment (4.6)

Editorial or Substantive
Editorial Change Required? Substantive
(4.5.4)

Make Change Does the Voter


YES withdraw the NO
Comment?

Report to Committee
Take up as New Record as Negative
Business – Keep Resolve According to
On Agenda Until 4.5.4
Resolved

Figure 4.4 – Affirmative with Comment

Chapter 4 – Balloting Committee Documents


March 2004
ACI Technical Committee Manual — 2004 29

CHAPTER 5 A document submitted to ACI headquarters for publica-


tion is sent to TAC and one or more outside reviewers.
PROCESSING COMMITTEE DOCUMENTS ACI staff selects outside reviewers for their expertise on
the subject matter.

Submitting Documents for TAC Review


5.1 ACI staff also determines if committee coordination is
completed (3.7). If further coordination is needed, staff
All required materials for submitting documents for forwards the document to the relevant committees.
TAC review shall be sent to the Managing Director of
Engineering at least three months before a TAC meeting Reviewers classify each of their comments, as ex-
for procedural review, editorial review (3.4), and forward- plained in 5.2.1.
ing to TAC (see Checklist for Submittal of Documents to
TAC for Review in the ACI Style Manual). Review Comment Classifications
5.2.1

All documents prepared or sponsored by joint commit- 5.2.1.1General and Specific Comments
tees (1.10) are subject to the review procedures of both Reviewers indicate whether comments are general or
organizations and should be submitted to both organiza- specific, and provide the page and line number reference
tions. for specific comments. General comments are applicable
to the entire document or many places in a document.
With the submittal, the chair shall include: Reviewers are strongly encouraged to avoid providing
• A hard copy of the document; repeated specific comments where a general comment has
• An electronic copy of the document; been provided. A specific comment applies to a particular
• The results of the committee’s coordinating action element of the document. General and specific comments
(3.7) with related committees; are classified further as primary, secondary, or editorial:
• Known conflicts with documents of other ACI com-
mittees with an explanation of the conflicts (3.7.1); Primary Comment (P)
5.2.1.2
• State what type of document (3.2) is being submitted
and if the committee desires to have the document P comments identify primary technical issues, such as:
standardized (3.2.1);
• A ballot summary (4.3.7) of the final letter ballot; • Errors;
• For all negative votes (4.5) received on the final • Omissions;
committee letter ballot that were voted nonpersua- • Conflicts;
sive: • Serious deficiencies; and
• Statements prepared by the voters giving specific • Missing tables, figures, or other information;
reasons for voting negatively (4.5.3);
• The committee’s reason for finding a negative P comments must suggest a means of resolution.
vote nonpersuasive;
The committee must consider the comment and take
• A ballot summary of the vote of the committee
action. Usually, the committee either accepts the com-
to find the negative vote nonpersuasive, includ-
ment as stated and makes the change, or disagrees with
ing the number of affirmative and negative votes,
the comment and provides a rationale for disagreement. In
plus the total number of voting members in the
some cases, the committee disagrees with the comment as
committee (4.3.7); and
stated, but realizes that the text of the document has been
• The change that was made and ballot results for
misinterpreted, and makes editorial changes to clarify the
any substantive change (4.5.4).
text. The committee must provide a written rationale if the
TAC comment is not incorporated.
Review of Documents
5.2
One of the most important functions of TAC is the re- Secondary Comment (S)
5.2.1.3
view of technical committee documents. TAC reviews
documents for: S comments identify secondary technical or editorial
issues where the committee has latitude, such as:
• Technical correctness;
• Conflicts with other ACI documents; • Suggestions for technical or editorial improvement;
• Compliance with ACI formats, as in the case of • Questions that require committee attention do not re-
specifications; and quire a written answer; and
• Clarity of expression. • Comments that do not suggest a means of resolution.

Chapter 5 – Processing Committee Documents


March 2004
30 ACI Technical Committee Manual —2004

The committee is expected to consider and take action, 5.2.2.2Review Comments


but the committee need not document the response. Fol- The assigned TAC review group (5.2.2.1) considers the
lowing this definition, the TAC review group can change review comments at a meeting. The technical committee
a P comment submitted by a reviewer to an S if a means chair is invited to attend the review meeting. During its
of resolution is not provided by the reviewer (similar to evaluation of the comments, the review group should
changing a negative to an abstention if no reason state- eliminate duplicate comments and delete incorrect state-
ment and proposed change are provided). ments. The review group recommends to TAC whether
the document should be approved without comment, ap-
Editorial Comment (E)
5.2.1.4 proved with comments, or returned to the technical com-
mittee for revision, reballot, and resubmission.
E comments identify a specific or general editorial is-
sues that the committee must correct before publication of TAC Decision
5.3
the document, such as:
TAC considers the review group’s recommendation and
acts on the document (5.5.3). After TAC action, the
• Style and grammar corrections (the ACI Style Man-
comments (5.2.2.1) approved by the TAC review group
ual);
become official TAC comments. Staff notifies the com-
• Repetitive issues;
mittee of the TAC action and sends the TAC comments to
• Inconsistency; the committee for consideration.
• Missing reference information; and
• Reference format. 5.3.1Document Approved
If the document is approved with comments, the com-
When the comment is a suggestion or simply reinforces mittee shall act promptly to:
a reviewer’s preferences (such as “when in doubt, leave • Prepare a response to each Primary Comment
the comma out”), the comment is classified S, not E. (5.2.1.2); and,
Compliance with editorial comments is expected unless
• Prepare a response to each Editorial Comment
the meaning would be incorrectly changed if the comment
(5.2.1.4), if the committee disagrees with the editorial
was followed. Committees are expected to document the
change.
handling of E comments only where they take exception
to the comments. Changes made to the document in response to TAC
comments shall be sent in written form to the members of
Editorial Comment (M)
5.2.1.5 the committee, who shall be given no fewer than 30 days
to respond to those changes. If a voting member objects
M comments are a special case of the E comment that to a change, the objection shall be treated as a negative
are so obvious that they can be passed on to the commit- vote and resolved in accordance with 4.5. Otherwise, the
tee without action by the entire review group, and they do changes shall be considered accepted (No-protest consent,
not require discussion by the committee, such as: 4.1.3).

• Punctuation errors; After the document has been revised in response to


• Spelling or typographical errors; TAC comments and accepted by the committee member-
• Transposed words; and ship, the following shall be submitted to the Managing
• Tense agreement. Director of Engineering:
• The revised document in electronic format and a final
TAC Review Procedure
5.2.2 printed copy, including original artwork;
• The committee response to the TAC comments
5.2.2.1TAC Review Group (5.2.1); and
Each submitted document is assigned a TAC review • A report on the resolutions of all committee objec-
group. The review group has a review chief for each tions to the changes (5.2.1.2).
document being reviewed. All comments received from
TAC members, outside reviewers, TSC (3.7.2), CLC On behalf of TAC, staff checks the document for
(3.7.3), staff, and chairs of related committees are given compliance with the TAC comments. If the committee
to the TAC review chief for compilation. Once compiled, disagrees with a primary comment, a technical reason for
they are distributed to the review group. noncompliance must accompany the document.

Chapter 5 – Processing Committee Documents


March 2004
ACI Technical Committee Manual — 2004 31

5.3.2Document Not Approved Other standardized documents follow only certain sec-
If the document is not approved, but TAC considers tions of the ACI Document Adoption and Publishing Pro-
publication desirable, the committee is expected to revise, cedures. Code cases follow 5.5.1 through 5.5.5, and
reballot, and resubmit the document to TAC. The decision 5.5.6.1. Provisional specifications and test methods follow
not to approve is usually the result of major structural or 5.5.1 through 5.5.5, and then 5.5.6.2.
technical deficiencies in the document. Therefore, TAC
expects a comprehensive effort by the committee before Concrete International publishes the status of docu-
the document is resubmitted. When a document is not ments that are being processed through the standardiza-
approved, the committee receives the following guidance tion procedures.
from the TAC review group (5.2.2.1):
• General guidance on what the TAC review group be- Normal Standardization
5.4.1
lieves is necessary to improve the document; New documents or major revisions to existing docu-
• A set of primary comments (5.2.1.2) compiled by the ments must address public comments through Normal
review group. These comments represent technical Standardization, given in 5.5.7.2.
problems that the reviewers have identified in the
document. Although TAC expects the committee to Expedited Standardization
5.4.2
address these comments during revision of the docu-
ment, there is no requirement to respond individually To expedite a minor revision, reapproval, or withdrawal
to each of these comments. The committee should be of an existing ACI standard, the ACI Document Adoption
aware that the TAC review group might not evaluate and Publishing Procedures (5.5) allow for a quicker
all of the review comments once it becomes evident method of addressing public comments, given in 5.5.7.1.
that the document should not be approved. Further, This can reduce the time to publication by as much as six
simply addressing the primary comments is usually months. Minor revisions to standards include minor
not enough to upgrade the document to an acceptable changes, correction of errors, and updating of reference
condition; standards.
• The committee may also receive additional com-
ments with or without TAC classification and a Provisional Standardization
5.4.3
marked-up copy of the document containing editorial
corrections. These items are provided for the com- TAC must give approval before a committee can use
mittee’s use in revising the document for resubmis- the ACI provisional standardization procedure (3.2.1.4,
sion. 5.5.6.2). The request must be submitted to the Managing
• Conflicting comments may occur in these reviews Director of Engineering and must have a reason state-
and may be symptomatic of reviewer difficulties un- ment, including the expected expiration date.
derstanding the committee intent.
Procedure for Documents Not Requiring
5.4.4
5.3.3 Appeal of TAC Decision on Document Standardization
Any committee chair or other interested committee
members who wish to discuss or appeal previously trans- Documents not requiring standardization, such as re-
mitted TAC comments and actions on their committee ports and guides, follow 5.5.1 through 5.5.4 and 5.5.9 of
document should notify the Managing Director of Engi- the ACI Document Adoption and Publishing Procedures.
neering. An item is placed on the agenda for the next If the committee desires a report or guide to become a
scheduled TAC meeting and those interested are invited standardized document, follow the process for the appli-
to attend the meeting. cable type of standardization.

Types of Standardization Procedures


5.4 ACI Document Adoption and Publishing
5.5
Procedures
The ACI Document Adoption and Publishing Proce-
dures (5.5) include the procedures for processing a stan- Document Types
5.5.1
dardized document.
The ACI Document Adoption and Publishing Proce-
Because they must adhere to ACI’s national consensus dures apply to the adoption of any new or revised ACI
adoption procedures, codes and reference specifications technical committee document. A new or revised docu-
follow the complete ACI Document Adoption and Pub- ment is referred to as a “proposed document” until it is
lishing Procedures, 5.5.1 through 5.5.9, excluding the officially adopted.
provisions specific to other types of documents.

Chapter 5 – Processing Committee Documents


March 2004
32 ACI Technical Committee Manual —2004

5.5.2Document Origination Provisional Specification or Test Method


5.5.6.2
A proposed document originates in a technical commit-
tee. If a technical committee desires to develop a new A provisional specification or test method (3.2.1.4)
code or reference specification, the Technical Activities becomes effective upon Standards Board approval and is
Committee (TAC) must give approval. A technical com- published by ACI as a separate document. ACI staff and
mittee preparing any proposed document shall conduct its the chair of the originating committee shall expedite pub-
activities in accordance with the written procedures in the lication of the provisional standardized document, with a
Technical Committee Manual for achieving balanced goal to print within 90 days following Standards Board
membership, proper voting, and considering and resolving approval. Immediately after becoming effective, the
negative votes. document shall continue being processed through the
normal standardization procedure for codes and reference
TAC Review
5.5.3 specifications, starting with 5.5.6.3.
When the technical committee has approved a proposed
document, the proposed document shall be given a review Upon TAC approval (5.3.1), TAC establishes an expira-
by TAC. TAC reviews proposed documents for: tion date for the provisional specification or test method.
To prevent a provisional specification or test method from
• Technical correctness; expiring, the code and reference specification standardiza-
• Conflicts with other ACI documents; tion procedures must be completed. Upon completion of
• Compliance with ACI formats, as in the case of the standardization procedures, the term “provisional” is
specifications; and removed from the title of the document. Any standardized
• Clarity of expression. document referencing the provisional specification or test
method is unaffected by the transition from provisional to
TAC Approval
5.5.4 standardized document, but the reference must be updated
TAC may approve the submitted proposed document in the next revision. Provisional documents shall not be
without comments, approve the proposed document with reapproved.
comments, or require the rewriting and reballoting of the
proposed document by the technical committee. (5.3.2) If the originating committee does not pursue the stan-
dardization procedures of 5.5.7 or it is delayed beyond the
When TAC approves a proposed document that does established expiration date, TAC may decide to give the
not require standardization, the process skips to 5.5.10. provisional specification or test method report status. A
For a proposed document that requires standardization, provisional specification can be developed by one com-
the process continues in 5.5.5. mittee (originating technical committee or ITG) and later
transferred to another committee for processing in accor-
dance with 5.5.7. A provisional test method should be
Standards Board Review
5.5.5
transferred to the appropriate ASTM subcommittee, if it
When TAC approves a proposed document requiring
exists, when appropriate.
standardization, the balloting history shall be given pro-
cedural review by the ACI Standards Board. If ACI’s
procedures have not been followed, the Standards Board Code or Reference Specification
5.5.6.3
will return the proposed document to TAC with com-
ments. The code, reference specification, the revision, or an
announcement is published for public review and is open
for discussion for three months (5.6). Institute members
5.5.6Standardization Procedures
and the public may suggest revisions to the proposed
When the Standards Board has confirmed that Institute
document. The standardization procedure for the pro-
procedures were followed, procedure 5.5.6.1, 5.5.6.2,
posed document continues in 5.5.7.
5.5.6.3, or 5.5.6.4 is followed as appropriate.
Other Standardized Documents
5.5.6.4
5.5.6.1Code Case
A code case (3.2.1.2) becomes effective upon Standards
An announcement of the availability of the document
Board approval and a notice of the approval shall be pub-
for public review is published in an ACI periodical. The
lished with a number for each code case and the effective
document is available and open for discussion for three
date. A code case shall apply only to the designated edi-
months. Institute members and the public may suggest
tion of a code and shall not apply to other editions of the
revisions to the proposed document. The standardization
code. The standardization of the code case is complete.
procedure for the proposed document continues in 5.5.7.

Chapter 5 – Processing Committee Documents


March 2004
ACI Technical Committee Manual — 2004 33

Response to Public Discussion


5.5.7 5.5.10Appeals
Any person may appeal the adoption of committee
ACI allows for two procedures for responding to public documents in process or provisions of existing committee
discussion and suggested revisions to proposed docu- documents. Appeals may be made on technical or proce-
ments: Normal Standardization and Expedited Standardi- dural grounds. Since appeals are normally heard at ACI
zation. Expedited Standardization can only be used for a conventions, all appeals must be submitted in writing to
reapproval, withdrawal, or minor revision to an existing ACI headquarters at least six weeks before the convention
standardized document. for inclusion on the agenda of the hearing committee or
Standards Board.
Expedited Standardization
5.5.7.1
The technical committee will review all comments and 5.5.10.1 Appeal of Standardized Documents
suggested revisions to the proposed document. The pro- Appeals relating to standardized documents shall be
posed document shall be adopted by ACI unless: heard by TAC in the case of technical appeals, or by the
Standards Board in the case of procedural appeals. The
• Substantive objections not previously considered by Standards Board reviews TAC actions on all appeals. The
the committee are received; or Board of Direction hears the appeals of decisions of the
• The Institute receives objections of any kind from 50 Standards Board. All such appeals shall be heard as ex-
or more members during the public comment period. peditiously as possible considering normal meeting sched-
ules.
If either occurs, the proposed document is processed by
the Normal Standardization; otherwise, the standardiza- If an appeal of approval of a document in process is
tion procedure is complete and document publication con- sustained, the document shall be processed no further. If
tinues in 5.5.9. an appeal of an existing standardized document is sus-
tained, the document shall be corrected within a time limit
5.5.7.2Normal Standardization established by the Standards Board or shall be rescinded.
The technical committee will review all comments and The Standards Board shall return the document to the
suggested revisions to the proposed document received by originating committee through TAC for correction if the
the Institute during the public comment period. The tech- appeal is technical in nature or to the step in the stan-
nical committee chair will then write and issue a closure dardization procedure where the error occurred if it is
statement to the technical committee for a 30 day review procedural in nature.
period (5.7).
5.5.10.2 Appeal of Nonstandardized Documents
TAC will review the public comments, any amend- Appeals relating to nonstandardized documents shall be
ments, and the closure statement. If TAC agrees with the heard by TAC. The Board of Direction hears the appeals
technical committee revisions and closure statement, the of decisions of TAC. All such appeals shall be heard as
proposed closure is forwarded to the Standards Board. If expeditiously as possible considering normal meeting
TAC does not agree, the proposed closure is returned to schedules.
the technical committee with comments.
If an appeal of adoption of a document in process is
sustained, the document is processed no further. If an ap-
Document Publication
5.5.8 peal of an existing document is sustained, the existing
document shall be corrected within a time limit estab-
The Standards Board may either allow the publication lished by the TAC or shall be rescinded. TAC shall return
of any revisions and the closure statement, or return them the document to the originating committee for correction
to TAC. Upon publication of the closure statement and if the appeal is technical in nature or to the step in the
any revisions, the standardization of the document is com- procedure where the error occurred if it is procedural in
plete (5.8). nature.

 American National Standards Institute


5.5.9 Publication for Public Review
5.6

The new or revised document is published by ACI. Proposed standardized documents approved by the
Upon committee request and subsequent TAC approval, a Standards Board are published to allow for public review
standardized document may be referred to the American and comment (5.5.6.4). Publication is in an ACI periodi-
National Standards Institute (ANSI) for processing and cal or on the ACI Web site, or both. TAC recommends
adoption as an American National Standard. the mode of publication when the document is reviewed
and approved (5.2.2).

Chapter 5 – Processing Committee Documents


March 2004
34 ACI Technical Committee Manual —2004

If the proposed standardized document is to be pub- 5.8.1Separate Publications


lished only on the ACI Web site, a notice will be pub- All committee documents are published in a separate
lished in an ACI periodical that summarizes the major final format and are available to the public (5.5.8).
changes of a revised document or the scope of a new
document. The notice will also provide instructions on 5.8.2ACI Manual of Concrete Practice
how to access the document on the ACI Web site or how The ACI Manual of Concrete Practice (MCP) is a set of
to obtain a hard copy. A hard copy of proposed standard- bound volumes, published annually, that contains the ma-
ized documents will be made available at a nominal jority of ACI’s technical committee documents. If a
charge. document is not included in its entirety in the MCP be-
cause of a limited or specialized audience or because it is
Details of Public Discussion and Committee
5.7 too large, a synopsis or notice is inserted in the MCP to
Closure alert the reader of its availability. All documents are in-
cluded in the electronic version of the MCP.
Public discussion of committee documents (5.5.6.3,
5.5.6.4) closes three months after publication or an- Proposed documents that have been published in a peri-
nouncement of availability. Because of time constraints, it odical but have not yet been adopted may be placed in the
is usually necessary for the chair or a small subcommittee next edition of the MCP. They are distinguished from the
to prepare the closure. The closure should answer ques- adopted documents having gray edges on the pages. This
tions raised in public discussion, where possible. Ques- allows the Institute to present the most current informa-
tions beyond the scope of the committee document, dis- tion as soon as possible, as long as the proposed docu-
cussions of points considered and rejected by committee ments are clearly distinguished from the Institute-
action, and questions that are too complex to consider approved documents. Even though the Institute has not
within the allotted time, need not be answered. In these officially adopted these documents, ACI’s intensive re-
cases, an acknowledgment, a short explanation, and pro- view procedures have been followed before publication in
posed committee actions under new business are appro- a periodical. When the document is adopted, it is placed
priate. Any proposed revisions to the committee docu- in the next edition of the MCP without the gray edges.
ment are subject to approval by TAC.
5.9Publication of Joint Committee Documents
After the closure is prepared, the committee chair shall
send the written discussion and closure to the Managing Documents developed by joint committees (1.10) and
Director of Engineering and to each voting member of the released for publication by TAC are published by ACI
committee with instructions to voting members that lack unless some other mutually satisfactory arrangement has
of objection to the chair and ACI headquarters within 30 been approved. A joint sponsor of a document released
days is considered evidence of consensus on the closure. for ACI publication is advised by ACI headquarters of the
Publication schedules may require that the committee- release and the proposed date of publication and queried
approved closure be received by ACI no more than two as to interest in publication.
months after the discussion period ends. Therefore, the
chair or subcommittee may have less than 30 days to pre- Updating Existing Documents
5.10
pare a closure before distributing it to the committee for
their 30-day review. (No-protest consent, 4.1) 5.10.1Committee Documents
Committees must consider revision, reapproval, or
Final Publication
5.8 withdrawal of documents within four years from the ef-
fective date of the document. TAC may drop those docu-
After all of the above procedures have been completed ments from the ACI Manual of Concrete Practice that
and all approvals have been obtained, the documents be- have not been reapproved or revised within five years of
come official Institute publications (5.5.8). All standard- the effective date.
ized documents are given the year the standardization
procedure is completed and the standard is adopted, re- Before submittal to TAC, recommendations for revi-
gardless of whether the document is new, a major revi- sion, reapproval, or withdrawal must be approved by
sion, or a minor revision. Nonstandardized documents are committee letter ballot (4.2). A recommendation to reap-
assigned the year that compliance with TAC comments is prove (4.10) should be accompanied by a statement pro-
completed and verified by ACI staff. A footnote is added vided by the committee chair that explains why a reap-
to indicate the nature of the revision. If the document is proval is appropriate. The recommendation for with-
reapproved, the year remains the same, and the year of drawal should include a statement that, in the judgment of
reapproval is added, for example, XXX.3R-96 (Reap- the committee, the document is no longer useful or ame-
proved 2002). nable to updating.

Chapter 5 – Processing Committee Documents


March 2004
ACI Technical Committee Manual — 2004 35

TAC recommends reviewing a document and updating The committee is to submit the reapproval of the docu-
the references rather than reapproving (4.10) an old docu- ment to TAC for approval. The recommendation to reap-
ment without changes. prove should include a statement that technological pro-
gress at this point does not require revision or that the
If a standardized document is not reapproved or with-
document is currently being revised but is not yet ready.
drawn because of inaction on the part of the committee, or
A summary of the updates to the document should be
if it fails to receive the required ballot results (4.10.5),
included at the beginning of the submittal. Generally,
TAC shall act and, by majority vote, recommend reap-
TAC reviews only the committee’s ballot summary. A
proval or withdrawal.
reapproval does not change the year of publication.
Standardized documents are processed in accordance
with standardization procedures. Notice of actions taken Withdrawal
5.10.1.3
appears in an ACI periodical.
The committee should recommend withdrawal of a
5.10.1.1Revision document when the committee determines that the infor-
The committee should revise a document when the mation contained in the existing version is obsolete and
information contained in the document needs to be should not be revised. A letter ballot of the committee is
updated. The committee must ballot revisions according required (4.2.1). The recommendation to TAC for with-
drawal should include a statement that, in the judgment of
to Chapter 4 and submit the document to TAC for review the committee, the document is no longer useful or ame-
according to Chapter 5. TAC will review the entire nable to updating.
document, even if only one section has been revised.
If TAC decides to withdraw a document, the document
When the committee desires to publish new information
will no longer be included in the ACI Manual of Concrete
without revising the existing document, the committee is Practice. It may still be available for purchase from ACI
encouraged to develop a separate document. Supplements as a historical document.
to existing documents are not allowed.
Upon adoption of a revised document, the existing ver- ITG Documents
5.10.2
sion is automatically withdrawn and no action is required
of the committee. Upon completion of the normal standardization process,
responsibility for the document is transferred to an ACI
5.10.1.2Reapproval technical committee, following the recommendation of
The committee may decide to reapprove a document TTTC and TAC, and the ITG is discharged.
because the information in an existing document is still
valid. The committee is required to letter ballot the reap- If an ACI technical committee does not adopt the
proval (4.2.1). Part of the reapproval may include updat- document within five years from the date of its approval
ing references and minor editorial improvements of nota- by the Standards Board, it is withdrawn from the MCP,
tion, terminology, or other similar items. A reapproval and the ITG is discharged.
may not include substantive changes.

Chapter 5 – Processing Committee Documents


March 2004
36 ACI Technical Committee Manual —2004

ACI Document Adoption and Publishing Procedures ‡


(5.5)

Committee Approves
Final Draft of Document

Committee Approved TAC REVIEW Not Approved


Response with Comments (5.5.3) Rewrite, Reballot, Resubmit

Headquarters Approved Documents not Requiring


Review Standardization
(5.5.4)

Return to TAC
with Comments
STANDARDS BOARD REVIEW
(5.5.5)
TAC Response

Approved

Codes or Reference Other Standardized Provisional Specifications Code Cases


Specifications Documents or Test Methods (5.5.6.1)
(5.5.6.3) (5.5.6.4) (5.5.6.2)

Document Published Notice that Document is


for Public Review Open for Public Review

Expedited Standardization
(5.5.7.1)
Public Discussion Period
Normal Standardization
Committee Prepares Closure and
any Amendments (5.5.7.2)

Return to Committee
with Comments TAC and
STANDARDS BOARD
REVIEW
Committee Response

Publish Closure and ACI Publishes Document


Any Amendments

Possible options Required actions


‡ Not every possible option is shown. See 5.5 for complete procedures.

Figure 5.1 – ACI Document Adoption and Publishing Procedures ‡


Chapter 5 – Processing Committee Documents
March 2004
ACI Technical Committee Manual — 2004 37

Procedure for Document Development by Innovation Task Groups


(1.12)

Request for document development submitted to TTTC


Task Group appointed

Task Group recommends formation of ITG No

Yes Report to TAC & submitting party

Formation of ITG approved by TTTC No

Yes

Formation of ITG approved by TAC No Report to submitting party

Yes

ITG appointed: Chair from TTTC plus at least 4 experts Funding to support ITG:

Yes Interested party provides funds through ACI

Identify home committee No

Yes Funds provided by ACI

No

Yes ITG works on volunteer basis

ITG evaluates technology and drafts document

ITG Chair recommends 3 outside voting reviewers for TTTC


Chair approval; TAC Contact Member appoints reviewers
Document revised
Document successfully balloted by ITG No
and voting reviewers (4.2.3)

Yes

Document approved by TAC No

Yes

Document approved by Standards Board No

Yes
If provisional standard, print
Document submitted for public review to complete normal
standardization (Figure 5.1)

Document assigned to ACI technical committee No


Document printed in MCP for 5 years

Yes

ITG discharged Document withdrawn and ITG discharged

Figure 5.2 – Procedure for Document Development by Innovation Task Groups


Chapter 5 – Processing Committee Documents
March 2004
38 ACI Technical Committee Manual — 2004

CHAPTER 6 Preliminary Approval of Session with a


6.2.1.1
Call for Papers or Presentations
CONVENTION SESSIONS AND RELATED At least 20 months before the technical session, com-
PUBLICATIONS mittee submits to TAC the initial proposal for a technical
session. See 6.2.6.1 for guidance on preparing a Call for
Papers or Presentations. The proposal shall include a draft
Introduction
6.1 of the call for papers or presentations.

ACI technical committees are encouraged by TAC to Preliminary Approval of Session


6.2.1.2
take an active part in sponsoring technical sessions at ACI Without a Call for Papers or Presentations
conventions, and in publishing papers related to those
At least 13 months before the technical session, com-
sessions. TAC is responsible for the quality of all techni-
mittee submits to TAC the initial proposal for a technical
cal sessions at ACI conventions, and approves these ses-
session.
sions in accordance with the two-step process described
below. This chapter serves to assist committees in orga-
Final Approval of Session
6.2.1.3
nizing these sessions and help toward possible publication
of session papers. At least 8 months before the technical session, com-
mittee submits to TAC the final program for the technical
Presentations during technical sessions at ACI conven- session. (6.2.7)
tions are to be of the same quality as that of papers pub-
lished in ACI periodicals. Presentation materials used are Timetable of Presentations
6.2.1.4
to be of high quality and are expected to report new or
unpublished work that adds to the existing knowledge Convention sessions run for three hours normally with
base. Presentations that promote the use of proprietary six 20-minute presentations, leaving adequate time for
products without sufficient, objective, supporting data are discussion from the floor. Six talks can be presented if
generally not acceptable. Manuscripts that are to be con- each speaker’s time is limited and the moderators keep
sidered for publication by ACI are subjected to the same control of the session and discussion.
review process as are manuscripts submitted for publica-
tion in an ACI periodical. TAC and the Convention Committee require that a
timetable of speakers be published in the convention pro-
Special conferences, symposia, or seminars not in con- gram and posted at the door of the session room. This
junction with ACI conventions have special requirements allows for convention attendees to plan their time to hear
and are not covered in this chapter. specific talks.

Convention Session Timetables


6.2 Initiating a Session
6.2.2
A technical committee usually volunteers to sponsor a
Figure 6.1 summarizes the timetables for developing session, but TAC may request that a committee assume
technical sessions that include a Call for Papers or Presen- such an assignment. TAC may form an ad hoc committee
tations and sessions without a Call for Papers or Presenta- to organize a specific session. Where appropriate, the
tions. Additional explanations of the timetable and ap- committee should consider inviting other committees to
proval process are given below. cosponsor the session.

6.2.1Committee Deadlines Session topics should relate to the convention theme,


TAC uses a two-step process to approve technical ses- but this is not an absolute requirement. Potential session
sions: topics may include presentations of new committee
• Preliminary approval of a proposal for a session; and. documents; new research findings, case histories, or other
• Final approval of the session program. timely topics that the committee feels will be of interest to
convention attendees.
These approvals are granted at TAC meetings during
the fall and spring ACI conventions. Therefore, the com- After deciding to sponsor a session, the committee se-
mittee needs to submit session proposals and final pro- lects a session moderator who will have overall responsi-
grams to the Managing Director of Engineering at least bility for the session (6.2.5). A co-moderator should also
one month before ACI conventions. Approximate dead-
be selected, and a subcommittee may be organized to as-
lines for planning technical sessions are given in 6.2.1.1
sist in selecting session presentations.
through 6.2.1.4.

Chapter 6 – Convention Sessions and Related Publications


March 2004
ACI Technical Committee Manual — 2004 39

Preparing a Session Proposal for TAC


6.2.3 conventions before their scheduled technical session.
Approval These training sessions are held during each convention.
The committee chair or session moderator should make TAC will not grant final approval of the technical session
the preliminary proposal as complete as possible. See if this requirement is not fulfilled (6.2.7).
Requesting Convention Sessions (Appendix 6.2.3) for
guidance on the information to be included in the prelimi- 6.2.6 Speakers
nary proposal and Technical Session Request Form (Ap- There are several sources of prospective speakers such
pendix 6.2.4) and. A copy of the session request form can as the committee itself, known authorities in the subject
be obtained from the ACI Web site (See Appendix B). field, or a “Call for Papers or Presentations.”

The session request form should be sent to headquarters 6.2.6.1Call for Papers or Presentations
in accordance with the timetable in 6.2.1.1 and in Fig. 6.1. Calls for Papers or Presentations are published an-
The proposal should indicate to TAC that the committee nouncements in Concrete International requesting people
has given advance thought and planning to the session to submit abstracts for presentation (6.2.1.4) at ACI con-
objective and has chosen proposed session topics that will ventions or other meetings. The “call” should state explic-
be of widespread interest. Generally, sessions are pro- itly whether a manuscript is expected to be submitted if
posed for one or two half-day time sessions (3 hours the abstract is selected. Potential speakers can obtain a file
each). Proposals for sessions to cover more than two time of the recommended abstract format from the ACI Web
slots will require persuasive reasons attached to the re- site (See Appendix B).
quest form.
Timing is critical to obtain the best results from the
6.2.4Preliminary TAC Approval notices. The following gives a timetable of actions needed
TAC reviews the preliminary session proposal (See when a Call for Papers or Presentations is used to select
Appendix 6.2.4) and accepts it, rejects it, or requests addi- speakers:
tional information before making a decision. When TAC
approves a session, the requested time slot(s) is reserved • 16 months or more before the technical session:
at either a spring or fall convention. The session modera- Submit notice of Call for Papers or Presentations to
tor will be notified of this preliminary approval or rejec- the Managing Director of Engineering. There is a
tion by headquarters. If the session receives preliminary three-month lead-time until publication in Concrete
approval, the session moderator should submit a Call for International.
Papers or Presentations (6.2.6.1) or begin final selection • 11 to 13 months before the technical session: Staff
of speakers (6.2.6.2). will publish a notice in three consecutive issues of
Concrete International.
6.2.4.1Sessions Honoring Prominent ACI • Eight months before the technical session: All ab-
Members stracts should be received so that final speakers can
The ACI Board of Direction approved a policy in 1991 be selected. Pertinent information should be sent to
for honoring prominent ACI members with sessions at the Managing Director of Engineering for TAC final
conventions with the requirements that: approval (6.2.7) at the spring or fall TAC meeting be-
• The individual has made an outstanding contribution fore when the session is to be held. This is also nec-
to the Institute and the concrete industry; essary for advance publicity and mailings.
• The Convention Committee has the responsibility of
evaluating the individual’s contributions and approv- This is a minimum time schedule. The session modera-
ing this event; tor has little time between the last (third) published notice
• The proposals for sessions and dinners to honor an in CI and mailing the information to headquarters.
ACI member should be submitted for consideration
to the Convention Committee by a Board committee; The Call for Papers or Presentations should be issued as
• The sessions and dinners be approved at least one soon as TAC gives preliminary approval (6.2.4) for the
convention in advance by the Convention Commit- session. The “call” should indicate the objective of the
tee; and session and list examples of potential topics for presenta-
• The sessions and dinners cannot be held to conflict tion. The name of the person to whom the abstracts are to
with the Opening Reception, the President’s Recep-
be sent should be given along with the deadline for receipt
tion, or the Concrete Mixer.
of abstracts and the date of speaker notification (6.2.6.3).
Refer to a current issue of Concrete International for the
6.2.5Session Moderators format to be used. (See Appendix B, Item B.5.4, for in-
The session moderator and co-moderator are required to
structions on submitting a “Call for Papers or Presenta-
attend a training session at least one but preferably two
tions” for inclusion on the committee’s Web page.)

Chapter 6 – Convention Sessions and Related Publications


March 2004
40 ACI Technical Committee Manual — 2004

Selecting Speakers
6.2.6.2  Final TAC Approval
6.2.7
Prospective speakers should be contacted early, but no Final approvals of technical sessions are given at the
definite arrangements should be made until preliminary spring or fall TAC meeting before the convention when
TAC approval has been obtained (6.2.4). At the initial the session is scheduled. The session moderators should
contact, the speakers should have an idea of the presenta- send final programs to the Managing Director of Engi-
tion subject and possible title. neering no later than one month before the spring or fall
TAC meeting for final approval (See Appendix 6.2.7). It
Prospective speakers should prepare an abstract of the can also be obtained from the ACI Web site. Include titles
presentation as soon as possible and submit it to the ses- of sessions and of all talks, the names, and affiliations of
sion moderator for the committee’s consideration. the speakers and co-authors, the names of the co-
moderators and when they attended the mandatory train-
The sponsoring committee should review the submitted ing session, and whether a symposium volume is planned
abstracts subject matter with regard to the theme of the (6.3).
session and especially for oral presentation. In selecting
speakers, consider the quality of past presentations by Once all information regarding a technical session has
prospective speakers, if such information is available. been submitted, TAC will make a final review to deter-
Avoid selecting speakers who have a history of failing to mine whether the session will be approved. Failure to
appear at previous conventions to make their presenta- submit the required information one month before the
tions. TAC meeting will be grounds for TAC withholding final
approval of the session. TAC may grant a conditional
Notifying Speakers
6.2.6.3 approval provided the committee submits missing infor-
mation within three weeks after the TAC meeting. Ses-
Upon selection by the sponsoring committee, the sions not receiving final approval by TAC at the meeting
speakers should be notified that they are on the tentative preceding the convention of the scheduled session will be
program, be informed of the allocated presentation time, removed from the convention schedule and the sponsor-
and be asked to proceed with preparing their presentation. ing committee will be notified.
If paper versions of the presentations are to be consid- If the session receives final approval, the committee
ered for publication (6.3), indicate the deadline for sub- will be notified. The information in the final plan will be
mission of manuscripts and approximate date for notifica- used in the preconvention program mailing, write-ups in
tion of acceptance. Also advise the speakers that selection Concrete International, and other publicity. The sponsor-
of a talk for convention presentation does not guarantee ing committee should arrange for appropriate local pub-
publication of a paper and that manuscripts are subject to licity, specialized publicity, and attendance from particu-
ACI review as any other technical paper (6.3.3). The lar groups that might be interested in the session.
Convention Department will send appropriate forms to
each session moderator for distribution to the selected
Headquarters Assistance
6.2.8
speakers.
ACI staff will secure the necessary standard projection
It should be made clear that ACI does not pay speaker’s equipment for the session once headquarters is advised of
expenses, travel, or offer an honorarium. This should be the committee’s needs. In addition, the session modera-
stated in the “Call for Papers or Presentations,” in the tors need to work out the logistics for obtaining copies of
invitation to submit abstracts, or in the letter advising the the speaker’s computer files so that they can be installed
speaker that the abstract has been selected for presenta- on the computer before the session.
tion. The names and addresses of speakers who are not
ACI members should be submitted to the Convention Headquarters sends copies of authors’ guides and
Department so that they can be sent registration forms. guidelines for preparing slides to session moderators for
They should also be encouraged to visit the ACI Web site distribution to the speakers.
for convention information.
6.2.9Review of Presentation Materials
Speakers not selected for the program should be so ad- Quality slides are important to the overall quality of a
vised. If a symposium volume is planned and if the ab- presentation. TAC encourages speakers to prepare slides
stracts have merit, those submitting the abstracts could be using commercial presentation software (such as Power-
asked to prepare papers to be considered for publication Point). Slides are strongly preferred over overhead trans-
with other papers developing from the session. parencies because of the added skill required to make
effective presentations with transparencies.

Chapter 6 – Convention Sessions and Related Publications


March 2004
ACI Technical Committee Manual — 2004 41

• Identify the volume editor(s);


The session moderator should arrange for review of the
slides at least one month before the convention. Speakers • Provide a brief overview of the proposed special
who do not submit review copies should have their slides publication;
reviewed before the session. This review can be carried • List proposed paper titles and authors; and
out at a prearranged time during the convention using the • Provide a timetable leading to the publication of the
speaker ready room. Illegible slides should not be permit- volume.
ted to be shown.
TAC makes the decision for preliminary approval based
6.2.10 Presentation Summaries on the appropriateness of the subject matter and the an-
Speakers are expected to prepare a written summary of ticipated usefulness of the publication.
their presentation for distribution at the session. The ses-
sion moderator should inform the speakers how many Preparation of Papers
6.3.2
copies of the summaries to bring to the session; typically
at least 50 copies are needed. These summaries can range If the request receives preliminary approval, a package
from a single page to a complete paper, and they should of information necessary for preparation and review of
provide information for contacting the speaker or co- papers will be sent to the editor(s). This will include re-
authors. quirements for preparing the manuscript, figures, and
photographs, and copyright information.
Publication of Session Papers
6.3
Some papers presented at a convention might not be
The committee may wish to publish papers from a con- published. Experience shows that some oral presentations
vention session or symposium. Papers may be published cannot be adapted to written format. After the committee
in a special publication, called a symposium volume, or in selects presentations for the session or symposium, the
one of the ACI periodicals. Individual authors should be presenters should be notified promptly that a written vol-
encouraged to submit their papers for consideration by an ume is planned, and be invited to prepare a manuscript for
ACI periodical if a collection of papers is not planned. A review. Authors should be given a firm deadline for sub-
symposium volume may include papers based on conven- mission of manuscripts. Where possible, original manu-
tion presentations, papers submitted, but not presented, scripts should be provided before the actual presentation.
and possibly papers dealing with the same subject matter
received by the Institute and approved by the committee Session papers considered for Institute publication must
for inclusion in the special publication. meet the criteria outlined in the ACI Authors Guide, ex-
cept that papers selected for a symposium volumes may
The ideal situation is to have the symposium volume some times exceed page limits applicable to ACI periodi-
available at the time of the technical session. This re- cals.
quires careful planning, coordination with the Managing
Director of Engineering, and a rigid timetable for manu- Review of Papers
6.3.3
script submissions and reviews.
TAC generally delegates review of symposium papers
The final manuscripts and all backup material (6.3.3) to the technical committee. The editor selects at least two
have to be submitted at least three months before the reviewers for each paper. Where possible, reviewers
technical session to ensure that the symposium volume should be qualified individuals who are not authors of
will be available for sale at the convention. In most cases, other papers being considered for inclusion in the sympo-
however, the symposium volume will be published after sium volume. Except in special cases approved by TAC
the technical session. In this case, final manuscripts and before papers are reviewed, a reviewer should not review
all backup material must be returned to the Managing more than two papers for any symposium volume. At
Director of Engineering within two years of the technical least one-third of the total reviews should be done by out-
session. side reviewers (nonauthors).

SP Preliminary TAC Approval


6.3.1 As soon as reviewers are assigned, the editor should
When a decision is made to publish a symposium vol- provide the Managing Director of Engineering with a list
ume, the committee must submit a request for preliminary of the reviewers and how many papers each reviewer has
TAC approval to the Managing Director of Engineering been assigned. When the SP editor has authored one of
before proceeding with production of a symposium vol- the papers, the editor shall submit that paper to the Man-
ume. This request should: aging Director of Engineering, who will assign reviewers.

Chapter 6 – Convention Sessions and Related Publications


March 2004
42 ACI Technical Committee Manual — 2004

Reviewers follow the criteria listed in the manuscript 6.3.4Final TAC Approval
review forms provided by ACI headquarters. Reviews After receiving final manuscripts, reviewing documen-
should be returned to the editor within 30 days. At least tation, and determining that procedures have been fol-
two reviewers must recommend publication. If one of the lowed, ACI staff requests final approval of the sympo-
two reviewers does not recommend publication, a third sium volume by TAC. TAC typically reviews the table of
reviewer shall be appointed to break the tie. contents, preface, and list of reviewers and number of
papers reviewed by each. Following TAC approval, ACI
The editor provides authors with copies of anonymous staff prepares materials for final publication.
review comments and instructions for submitting final
manuscripts. Authors must consider review comments in 6.4Discussion
preparing their final manuscripts, and must provide an All material published by ACI is open to public discus-
explanation to the editors why particular review com- sion. A special notice is printed in the flyleaf page of a
ments were not incorporated into the final manuscript. symposium volume that reminds readers about discussion,
lists the closing date for discussion, and also the issues of
The editor is responsible for determining that all review the ACI Journal in which discussion and authors closures
comments have been addressed in a satisfactory manner will appear. When written discussion based on the oral
in the final manuscript. Final manuscripts for all papers, presentation is available before publication of the sympo-
along with review forms, a preface that provides back- sium volume, it appears in the volume along with the pa-
ground information and a summary of the symposium per.
volume contents, and any other information requested are
then returned to ACI headquarters. One or two late papers 6.5ACI Awards
should not delay publication of a symposium volume. All original papers published by ACI, including those
in symposium volumes, are eligible to be considered for
an award under the rules established by the Board of Di-
rection and the Awards Committee.

Chapter 6 – Convention Sessions and Related Publications


March 2004
ACI Technical Committee Manual — 2004 43

Timetable for Developing Technical Sessions for ACI Conventions


(See 6.2)

Sessions with Call for Papers or Presentations


(See 6.2.1.1)

Technical 20 months before session:


Committee Submit preliminary request form (6.2.3; Appendix 6.2.4)

18 months before session: TAC/


Obtain preliminary approval at TAC meeting (6.2.4) Staff

Technical 16 months before session:


Committee Submit Call for Papers or Presentations (6.2.6.1)

11 - 13 months before session: TAC/


Call for Papers or Presentations published in CI Staff

Technical 8 months before session:


Committee Select presentations (6.2.6.2), and Submit final program
for TAC approval (6.2.7and Appendix 6.2.7)

6 months before session: TAC/


Obtain final approval at TAC meeting (6.2.7) Staff

Convention where session is to be presented

Sessions without Call for Papers or Presentations


(See 6.2.1.2)

Technical 20 months before session:


Committee Submit preliminary request form (6.2.3; Appendix 6.2.4)

18 months before session: TAC/


Obtain preliminary approval at TAC meeting (6.2.4) Staff

Technical 8 months before session:


Committee Select presentations (6.2.6.2), and Submit final program
for TAC approval (6.2.7; Appendix 6.2.7)

6 months before session: TAC/


Obtain final approval at TAC meeting (6.2.7) Staff

Convention where session is to be presented

Figure 6.1 – Timetable for Developing Technical Sessions for ACI Conventions

Chapter 6 – Convention Sessions and Related Publications


March 2004
44 ACI Technical Committee Manual – 2004

Appendix A

Sample Committee Forms

and

Guides

Appendix A – Sample Committee Forms and Guides


March 2004
ACI Technical Committee Manual — 2004 45

Suggested Successors For Technical Committee Chairs


Please list specific ratings for at least three possible successors. TAC considers these nominees when selecting committee
chairs. Please complete this section even if your term does not end next year, in the event you should have to relinquish the
chair early.

Ratings of Committee Members as Potential Chairs

Adminis- Time Technical


trative and Knowl- Meeting Personal
Suggested Candidates Skills Support edge Skills Attributes Total

Maximum Rating 5 4 4 4 3 20

List Three Candidates:

"Guidelines for Selecting ACI Technical Committee Chairs" is on the back of this form. The guidelines define what is needed for
a person to chair a technical committee. The rating system listed above is parallel to these guidelines and should help you with
your recommendations.

Service as vice chair, subcommittee chair, or secretary of the committee and an occasional chance to conduct part of a
committee meeting is considered good training for potential chairs.

Please send to:


Patricia A. Levicki Name________________________________________________
Technical Committee Coordinator
ACI International Chair ACI Committee
P. O. Box 9094
Farmington Hills, MI 48333-9094 Date ________________________________________________
Phone - 248/848-3723/Fax - 248/848-3720
E-mail – pat.levicki@concrete.org

This information is CONFIDENTIAL and is restricted to the


Committee Chair, the Technical Activities Committee and ACI staff

Appendix 1.4.1.1.a - Committee Chairs Form


March 2004
46 ACI Technical Committee Manual — 2004

Guidelines for Selecting


ACI Technical Committee Chairs

What makes a good committee The Technical Committee


chair? Manual states:

= Administrative Skills = TAC Responsibility


To administer the committee, the person should: be orga- Appointments and reappointments of chairs are
nized; be able to delegate; follow-through with assign- among TAC's most critical responsibilities. TAC
ments; handle paperwork well; set realistic goals and meet requests and considers the advice of the current
chairs. However, TAC has total authority when
them; meet established deadlines; and motivate the com-
selecting technical committee chairs.
mittee members.

= Time and Support = Administrative


The person should be able to attend all the committee The success of a committee may depend on the chair's
meetings; have access to some type of office facilities administrative ability and initiative. Active and well
(word processor, secretarial, etc.); employer support of the organized committees will always have ongoing
committee activities; but most of all, have sufficient time to projects and can undergo normal leadership transi-
work on the committee activities. tions without disrupting committee activities.

= Terms
= Technical Knowledge Terms are for two or three years, which usually expire
Chairing a committee requires a good technical grasp of the at the ACI spring convention. Unusual circumstances
committee's field and the ability to effectively communicate are required to justify reappointments beyond six
this knowledge verbally and in writing. years.

= ACI Membership
Chairs must be members of the Institute.
= Meeting Skills
When chairing a meeting the person should be able to: = Candidates
focus in on the discussion and summarize the findings; Chairs should be rotated among all qualified com-
prevent lengthy discussions; be decisive; communicate mittee members and should be balanced so that no
one segment of the concrete industry should dominate
objectives to the committee; and most of all, effectively
the committee activities.
manage the meeting from beginning to end.
A person should chair only one committee at a time,
= Personal Attributes since a significant amount of effort and time is
Personal attributes should include: initiative; integrity; required to chair a committee.
honesty; fairness; and good judgment.
Chairs should have individuals prepared to assume
the committee leadership at all times.

Appendix 1.4.1.1.b – Guidelines for Selecting Committee Chairs


March 2004
ACI Technical Committee Manual — 2004 47

ACI COMMITTEE APPLICANT’S DATA SHEET


A voting member of an Institute technical or educational committee is expected to contribute technical information,
return ballots promptly, comment on draft reports, and attend committee meetings on a regular basis.
Committee
Number & Title

Member Class Voting Member Associate Member-requires ACI Membership


Name

Job Title

Employer
Mailing
Address

Phone/Fax Telephone: Fax:

Main Business E-mail:


What contributions can you make to the work of this ACI committee?

Brief statement of experience related to the work of this committee.

Background and accomplishments in construction, design, education, or other fields.

Inventions, publications, innovations, or types of construction experience.

Service on ACI committees and technical committees of other organizations.

ACI Member Number ________________ ACI membership is not required for voting membership but is desirable.

_________________________________________ ____________________________________________
Signature Date
Return this form to: ACI International, P. O. Box 9094, Farmington Hills, MI 48333
(Use additional sheets if needed) Form revised 03/02 PAL

Appendix 1.4.2 - ACI Committee Applicant’s Data Sheet


March 2004
48 ACI Technical Committee Manual— 2004

COMMITTEE MEMBERSHIP QUESTIONNAIRE

(Date of Mailing) Please Return By (30 days from mailing date)

ACI Committee (Committee Number)

(Committee Title)

I wish to retain my status as a voting member and intend to actively participate in ACI
Committee (Insert committee number).

I wish to be transferred to Associate Membership of ACI Committee (number).


My ACI membership number is ___________.

I wish to resign my membership on ACI Committee (number).

Please update my mailing address.

COMMENTS:

(Where italics are in parenthesis, add appropriate information.)

RETURN TO: __________________________


Signature
(Insert name and address and contact ______________________________
Name (typed or printed)
numbers) ________________________ ______________________________
Address
________________________________ ______________________________

________________________________ ______________________________

________________________________ ______________________________
Telephone/Fax
______________________________
E-mail
______________________________
Date

Appendix 1.7.2 - Committee Membership Questionnaire


March 2004
ACI Technical Committee Manual — 2004 49

Annual Report of ACI Committee Activities


Committee ______ - ______________________________________________________________________

Chair ____________________________________________________Date ______________________

1. List your progress on goals (including technical sessions) published in the current ACI Committees booklet:

2. List your goals for the upcoming year to be published in the next ACI Committees booklet. (TCM 2.2)

3. List documents you expect to submit to TAC for review in the next 12 months.

4. Report progress on preparing responses to TAC review comments (if applicable).

5. List any liaisons or conflicts with other committees in ACI or other organizations, any educational programs for
seminars, and any new technology to be featured in Concrete International.

Please return to: Patricia A. Levicki, Technical Committee Coordinator, ACI International, P. O. Box 9094, Farmington Hills, MI 48333-9094
Phone -248/848-3723 + Fax - 248/848-3720 + E-mail – pat.levicki@concrete.org

Appendix 2.6a - Annual Report of ACI Committee Activities


March 2004
50 ACI Technical Committee Manual — 2004

Annual Report of ACI Committee Activities


Page 2

Date _____________Chair ______________________________________________Committee _________

6. Balance of Interests (TCM 1.6.6.8)

Each committee that prepares or has jurisdiction over documents requiring standardization shall carry out an
annual review of membership and include in the Annual Report a summary of voting member classification.

The combined number of voting members classified as User and General Interest shall equal or exceed the
number of voting members classified as Producer; and each Producer Interest shall have no more than one
voting member.

If your committee prepares documents requiring standardization, please use this space for your membership
summary. See TCM Item 1.6.6 for complete information.

Sample: Total = 30 members

Users = 10 members
General = 6 members
Producer = 14 members

16 $ 14 = Balanced
SUMMARY OF VOTING MEMBER
CLASSIFICATION:

7. List one or two high-priority research topics that would assist your committee. (TCM 2.11)

Please return to: Patricia A. Levicki, Technical Committee Coordinator, ACI International, P. O. Box 9094, Farmington Hills, MI 48333-9094
Phone -248/848-3723 + Fax - 248/848-3720 + E-mail – pat.levicki@concrete.org

Appendix 2.6b - Annual Report of ACI Committee Activities


March 2004
ACI Technical Committee Manual — 2004 51

Sample Committee Letter Ballot

(Date of Mailing) Please Return By (not less than 30 days from mailing date)

ACI Committee (Committee Number) Letter Ballot

(Title of item being balloted. For example, Proposed Revisions to "Building Code Requirements for
Reinforced Concrete (ACI 318-02)" reported by ACI Committee 318)

I approve the above (insert one of the following: document, revision, reapproval, withdrawal).

* I approve, with editorial comment, the above (insert one of the following: document, revision,
reapproval, withdrawal).

** I do not approve the above (insert one of the following: document, revision, reapproval,
withdrawal).

I abstain.

COMMENTS:

(Where italics are in parenthesis, add appropriate information.)

*This approval should not be contingent upon committee adoption of the editorial comments.
**Negative votes must be accompanied by a statement of reason and should also have suggested changes, which if adopted, would
satisfy the objection.

(Votes of associate and consulting members are not counted in the official tally; however, their comments will be considered.)

RETURN TO: __________________________


Signature
(Insert name and address and contact ______________________________
Name (typed or printed)
numbers) _______________________ ______________________________
Date
_______________________________

_______________________________

Appendix 4.1.1 – Sample Committee Letter Ballot


March 2004
52 ACI Technical Committee Manual — 2004

Sample No-Protest Consent Notice

(Date of Mailing)

ACI Committee (Committee Number) No-Protest Consent Notice

(Subject that is being sent for No-Protest Consent)

This notice is to inform you that changes were made to the document (Why the changes were made being made
- for example: to satisfy negative voters; to address TAC review comments; or to approve a closure statement).

If you are a voting member and disagree with these changes you must inform me in writing by (not less than
30 days from mailing date). The changes you object to will then be letter balloted. If I do not hear from you, it
is assumed that you agree with the attached changes.

(Where italics are in parenthesis, add appropriate information.)

RETURN TO: __________________________


Signature
(Insert name and address and contact ______________________________
Name (typed or printed)
numbers) _______________________ ______________________________
Date
_______________________________

_______________________________

Appendix 4.1.3a – No-Protest Consent Notice


March 2004
ACI Technical Committee Manual — 2004 53

Sample No-Protest Consent Confirmation

(Date of Mailing – After 30-day period closes)

ACI Committee (Committee Number) No-Protest Consent Confirmation

(Title of document that is being changed)

This is to notify you that the no-protest consent notice sent to you on (Date of Original Mailing) did not receive any
protests to the changes made to the document (Why the changes were made being made - for example: to satisfy
negative voters; to address TAC review comments; or to approve a closure statement).

This is to notify you that this item passes.

(Where italics are in parenthesis, add appropriate information.)

RETURN TO: __________________________


Signature
(Insert name and address and contact ______________________________
Name (typed or printed)
numbers) _______________________ ______________________________
Date
_______________________________

_______________________________

Appendix 4.1.3b – No-Protest Consent Confirmation


March 2004
54 ACI Technical Committee Manual — 2004

Letter Ballot Summary


Committee

Document

Section(s) Balloted

Date Ballot Was Mailed Date Ballot Was Canvassed

Ballot Count

Number of Eligible Voters __________

Yes ____________ No ___________ Abstain ____________ Not Returned _____________

Names of voting members:

Names of negative voters and reasons:


(Attach copies of negative ballots)

Names of abstaining voters:

Names of eligible voters not returning ballots:

Send this summary to: ________________________________________________


Todd R. Watson Signature
Manager of Technical Documents
P. O. Box 9094 ________________________________________________
Farmington Hills, MI 48333-9094 Name
Phone - 248/848-3728/Fax – 248/848-3720
E-mail – todd.watson@concrete.org ________________________________________________
Date

Appendix 4.3.7 – Letter Ballot Summary


March 2004
ACI Technical Committee Manual — 2004 55

Sample Committee Letter Ballot


Reapproval of Committee Document

(Date of Mailing) Please Return By (not less than 30 days from mailing date)

ACI Committee (Committee Number) Ballot

(Title of item being balloted - for example,


Proposed Reapproval of "Corrosion of Metals in Concrete” (ACI 222R-96)"
reported by ACI Committee 222)

Reason for Reapproval: (Insert reason for the reapproval)

I accept the proposed reapproval.

I do not accept the proposed reapproval (provide reason).

I abstain.

Note: A vote to not accept the proposed reapproval is a vote to withdraw the current document from
the Manual of Concrete Practice.

COMMENTS:

(Where italics are in parenthesis, add appropriate information.)

(Votes of associate and consulting members are not counted in the official tally; however, their comments will be
considered.)

RETURN TO: __________________________


Signature
(Insert name and address and contact ______________________________
Name (typed or printed)
numbers) _______________________ ______________________________
Date

_______________________________

_______________________________

Appendix 4.10.4 - Sample Committee Letter Ballot for Reapproval


March 2004
56 ACI Technical Committee Manual — 2004

Guidance on Requesting Convention Sessions

!Number of half-day sessions


TAC reviews proposals for technical sessions at ACI $ One or two sessions are typical.
conventions and recommends sessions to the Convention $ Two sessions will be approved on preliminary submittal
Committee for final approval. TAC requires committees to only if plan is persuasive.
provide detailed information when requesting a convention $ TAC may approve only one session and ask for
session. Forms (Appendix 6.2.4 and 6.2.7) are provided so additional information or make suggestions.
the committees can assemble and present the needed
information to TAC. The forms are also available in the !Theme session
“Forms & Documents” section on the Committees web
page. $ Topics should relate to theme, but it is not required.
$ Avoid repetitive sessions on the same topic.
Chapter 6 of the TCM should be reviewed before
submitting a request to TAC. When evaluating a !Objective/synopsis
committee’s request for a session, TAC considers and
$ What is the committee trying to do?
weighs the following points:
$ Is the session on a committee document?
$ Will it help the committee attract new members?
!Person and Committee(s) Sponsoring Session !Probable topics/authors
$ Have a single point of contact for overall session issues. $ TAC looks for evidence of advance thought and
$ Considers the committee's recent sessions for quality, planning. Do the probable/desired topics reinforce the
attendance, etc. objective of the session?
$ Coordination and cooperation among committees is $ Based on the topics, TAC may suggest coordination or
encouraged and expected. cosponsorship to the committee.
$ A cosponsor is not needed but communication is $ Not trying to be obstructive.
desirable. $ Have balance between invited and offered papers.
!Session Moderator $ What topics - general?
$ Are the topics consistent with the objectives?
$ Consider previous sessions handled by moderator. $ Helps judge breadth of interest?
$ Contact information is important for timely
!Is this a dedicated symposium
communication with the Convention Department.
$ No moderator, no session. $ See policy statement or contact Convention
!Convention (date) requested Department.

$ Is there enough time to organize the session (6.2)? !Select speakers/call for papers
$ Is there space available at the convention?
$ Is there time for call for papers?
$ Have similar session topics already been requested?
$ If so, it shows open process.
!Title of proposed session $ Blend of both is best.
$ All selected speakers may not present breadth of
$ Does it fit the committee mission? subject.
$ Does it fit the convention theme (not mandatory, but a
plus)? !Symposium volume planned
$ Is it a topic of widespread interest?
$ Who is the likely audience? $ Is there time?
$ Has effort on sessions detracted from other committee $ Committee track record?
progress? $ Is there demand (marketability is a staff decision)?

Appendix 6.2.3 –Guidance on Requesting Convention Sessions


March 2004
ACI Technical Committee Manual — 2004 57

PRELIMINARY APPROVAL – CONVENTION SESSION REQUEST FORM

The following information is required for preliminary TAC approval of technical sessions.
(See Chapter 6 of the TCM for the approval process.)
Person submitting request and contact information:

Sponsoring committee(s):

Requested convention and day/time preference:

Session Moderator(s) and contact information:

Title of session:

Number of requested half-day sessions (6 papers per session) 1 2 3* 4*


*Provide justification on separate page for more than two sessions. (TCM 6.2.3)
Anticipated size of audience < 50 50 – 100 > 100

Would the session be appropriate as a theme session for the requested convention? Yes No
Objective/synopsis of session. Include who should attend and what are the benefits. (100 words or less). This will be
printed in the Convention Preview:

Probable topics and potential speakers (if known):

Will you select speakers (TCM 6.2.6.2)? Will you have a Call for Papers or Presentations (TCM 6.2.6.1)?
(After TAC preliminary approval, submit Call for Papers or Presentations to the Managing Director of Engineering.)

Has moderator taken a Session Moderator Orientation Workshop? Yes No If not, TAC may not approve session.

Submit to the Managing Director of Engineering 20 months before planned convention. Use additional sheets if needed.

Appendix 6.2.4 - Preliminary Approval – Convention Session Request Form


March 2004
58 ACI Technical Committee Manual — 2004

FINAL APPROVAL – CONVENTION SESSION REQUEST FORM


The following information is required for final TAC approval of technical sessions. Submit one form for each half-day
session. Submit this form to the Managing Director of Engineering no later than one month before the spring or fall TAC
meeting before the convention when the session is scheduled. (See 6.2.7 and Figure 6.1 of TCM.)
Sponsoring Committee and Chair:

Requested convention and day/time preference:

Session Moderator(s) and contact information. Introduction: Yes No Length _____Min.

Title of session:

Number of requested half-day sessions (6 papers per session) 1 2 3* 4*


*Provide justification on separate page for more than two sessions. (TCM 6.2.3)
Anticipated size of audience < 50 50 – 100 > 100

When did (will) the session co-moderators attend a training session?


Objective/synopsis of session. Include who should attend and what are the benefits. (100 words or less). This will be
printed in the Convention Preview:

Title of Presentation #1:


Presenter/contact information:
Co-authors and affiliations:
Title of Presentation #2:
Presenter/contact information:
Co-authors and affiliations:
Title of Presentation #3:
Presenter/contact information:
Co-authors and affiliations:
Title of Presentation #4:
Presenter/contact information:
Co-authors and affiliations:
Title of Presentation #5:
Presenter/contact information:
Co-authors and affiliations:
Title of Presentation #6:
Presenter/contact information:
Co-authors and affiliations:

Submit to the Managing Director of Engineering 8 months before planned convention. Use additional sheets if needed.

Appendix 6.2.7 - Final Approval – Convention Session Request Form


March 2004
ACI Technical Committee Manual — 2004 59

Appendix B B.2.2.4Accountability
Text or graphic references to any outside organization,
COMMITTEE WEB SITES or links to internet locations associated with any outside
organization, may be included only if their inclusion
Purpose
B.1 would not obfuscate or confuse the identity of the organi-
zation(s) responsible and accountable for the information
ACI committee sites have been built online on the ACI presented or referenced.
Website (www.concrete.org) and are accessible by select-
ing Committees from the ACI home page. A committee B.2.2.5Document Copyright
may use its Web page to post meeting agenda, meeting An approved ACI document or document excerpt may
minutes, and calls for papers or presentations. In addition, be included only if each page includes a copyright notice
a committee may post draft documents for review and equivalent to the example provided below. A document,
revision online. According to Institute policy (B.2), some photograph, graphic element, or other material from a
areas of the committee sites are restricted to members of source other than ACI may be included only if ACI has
the committee and its oversight committee. received explicit permission from its copyright holder,
and each page or appearance includes prominent identifi-
Institute Policy on Development and Use of
B.2 cation of its source.
Websites by Committees and Chapters
Approved by the ACI Board of Direction, April 25, 2002. B.2.2.6Draft Copyright and Disclaimer
A draft ACI document may be included only if each
B.2.1 ACI Website page includes a draft copyright notice equivalent to the
ACI intellectual property (including knowledge prod- example provided below, and the first page additionally
ucts under development) may be made available on the includes a draft disclaimer equivalent to the example pro-
Internet only on the ACI Website. vided below.

B.2.2Web Pages B.2.3Meeting Agenda


ACI strongly encourages committees and chapters to ACI will post meeting agenda on the ACI Website for
develop and maintain Web pages for inclusion on the ACI public access.
Website. Such material will conform to the following
principles: B.2.4Public Comment
All ACI documents released for public comment will be
B.2.2.1 Technical Credibility posted on the ACI Website during the comment period.
Documents, committee minutes, and other materials
under development or otherwise not approved for general B.2.5 ACI Chapters
release may be included only if access to them is securely ACI Chapters may establish websites that are inde-
limited to the appropriate development or review popula- pendent of the ACI Website. Such websites may not con-
tion in accordance with ACI procedures tain ACI intellectual property, but may provide links to
the ACI Website as appropriate. ACI may provide links
B.2.2.2 Independence from Commercial and from the ACI Website to a chapter website only if the
Political Influence chapter website meets the requirements of item 2 above.
Text or graphic references to commercial or political
organizations, or links to Internet locations associated B.2.6  ACI Website Maintenance
with such organizations, may be included only if their The ACI staff, with guidance and direction provided by
inclusion would not represent or imply inappropriate in- the ACI committee(s) so authorized by the Board, is re-
fluence by such organizations upon ACI technical infor- sponsible for managing and maintaining the content, or-
mation and activities. ganization, and format of the ACI Website, including all
links.
Individual Respect and Privacy
B.2.2.3
Material that personally criticizes an individual, or that Example Document Copyright Notice
B.2.7
includes personal or private information about an individ- Copyright © 2002 American Concrete Institute
ual (e-mail address, phone number, etc.), may be made
available to a particular audience (committee members  Example Draft Copyright Notice
B.2.8
only, ACI members only, all public, etc.) only with the
explicit permission of the individual for release to such Copyright © 2002 American Concrete Institute
audience. DRAFT – Not for Publication or Reference

Appendix B – Committee Web Sites


March 2004
60 ACI Technical Committee Manual — 2004

Example Draft Disclaimer Statement


B.2.9 B.4.4 Standardization Actions
The Standardization Actions site is available to the pub-
This document is under development and is not ap- lic. Clicking Standardization Actions displays a page that
proved for publication or reference. The American Con- lists documents that are available for public comment.
crete Institute assumes no responsibility for the applica- These documents are being processed through ACI's
tion of the information contained in this document or con- ANSI-approved standardization procedures and are not
sequences arising from its application. yet official ACI standards.

Registration, Security, and Login


B.3 To comment on a document, scroll down the list of pro-
posed documents. Double-click on the document you
To access committee Web sites, it is necessary to regis- wish to review, and the text is brought up in a .pdf (read-
ter on the ACI Web site and validate your ACI and com- only) file format. You must have an Adobe Reader to
mittee membership against the ACI database. Committee access the file. Directions are given on how to submit
files are updated by ACI on a weekly basis. your comments for committee consideration. The public
discussion period is listed for each document.
To register online, click the Register or Login buttons
on the ACI home page. Use ACI2000 as the ACI Regis- B.4.5Forms & Documents
tration Code and then enter your ACI member number. ACI committee forms and manuals are available to
Follow the online instructions and once registered, access committee members. Clicking Forms & Documents
privileges are granted to the user. The registration process brings up a page that lists three committee manuals: ACI
places information on your computer that identifies you to Technical Committee Manual, ACI Style Manual, and ACI
the ACI system. Therefore, you must register from every Specification Manual, in .pdf files (read-only) that need
computer that you will use to access the technical com- an Acrobat Reader program. Although you may not edit
mittee Web pages. the manuals, you may print them.

If you have forgotten your username or password, both Various committee forms are also available to the com-
the Register and Login pages have a place for you to click mittee members. They are in MS Word format and may
to have ACI immediately e-mail the information back to be downloaded to your system to be modified and used.
you. The “TAC Review Deadlines” chart is available for easy
reference.
Navigating the Committee Sites
B.4
Committee Home Page
B.5
After registering online, select Committees from the
ACI home page. Five options are available: Directory, After selecting a committee, through the directory list
Search, Join, Standardization Actions, and Forms & or search function, the committee’s home page is dis-
Documents played. Available to the public, this page includes the
committee’s mission, goals, and activities as provided
B.4.1Directory from the ACI database. Seven options are available from
The directory is available to the public. Clicking the the committee’s home page.
Directory button displays a list of the ACI committees. • Home (Committee)—open to the public;
Users can browse this list and select the committee of • Membership—restricted to that committee’s mem-
interest. Selecting a committee displays that committee’s bers and its oversight committees;
home page with its mission, goals, and activities. • Document Library—restricted to that committee’s
members and its oversight committees;
B.4.2Committee Search Screen • Meetings—open to the public;
The search function is available to the public. It • Call for Papers —open to the public;
searches the text on the committee home pages and pro- • Agenda and Approved Minutes—open to the public;
vides a results list. Clicking a committee name on the • Forums— restricted to that committee’s members
results list displays that committee’s home page with its and its oversight committees.
mission, goals, and activities.
B.5.1 Membership
B.4.3 Join Committee Access to the membership page is restricted to ACI
Clicking Join displays an online committee member- committee members. The committee membership roster
ship application that can be filled in and submitted elec- includes complete contact information and e-mail links,
tronically to ACI headquarters.

Appendix B – Committee Web Sites


March 2004
ACI Technical Committee Manual — 2004 61

when available. Members are requested to notify ACI of The Search Events Calendar will search for special
any address or contact number updates. The committee committee meetings. Clicking on the meeting displays a
members are generally listed according to category of screen providing more information about the meeting. If
membership, as follows: Officers, Voting Members, Con- an agenda is available, it can be viewed by clicking the
sulting Members, and Associate members. ACI headquar- Meeting Agenda option under More Information. Regu-
ters updates the committee membership rosters weekly. larly scheduled committee meetings held at ACI conven-
tions are listed on the Convention Web Page under the
Clicking the E-Mail Selected Members option brings numerical committee listings, which is available to the
up an e-mail function page. E-mails may be sent to all or public.
a selected number of members, who are alphabetically
listed in a selection box. There are also boxes for entering Committee Officers may click on the Convention
the subject and the body of the message and a button to Meeting Request Form to submit a meeting request form
send the message. for the upcoming convention. This electronic submittal is
forwarded directly to the Convention Department for in-
B.5.2Document Library clusion in the proposed meeting schedule.
This page includes the committee’s published docu-
ments, draft documents, forums for discussion, meeting Call for Papers
B.5.4
agenda, and unapproved minutes. Access to the document
library is restricted to members of the committee. Clicking the Call for Papers button retrieves all the
calls for papers for the committee that are listed in ACI
Posting material on the committee’s Web site may be Events Calendar. Selecting an item on the list provides a
handled in several ways. Committee officers may upload screen for specific information and contacts. New calls
and maintain the committee documents. Or word- for papers can be added directly to the web site by click-
processing files may be sent by e-mail to ACI’s Manager ing on “Add to the Calendar.”
of Technical Documents at webpost@concrete.org for
conversion to .pdf files (read only) posting on the com-  Agenda and Approved Minutes
B.5.5
mittee’s Web page.
Clicking this button retrieves all agenda and all minutes
If the committee submits a draft document, a forum will approved by the committee. Approved agenda are avail-
automatically be set up for online discussions of the docu- able to the public and approved minutes are available to
ment. ACI members.

Requests for building the committee’s document library Forums


B.5.6
or adding the committee’s published documents to the
document library should also be submitted to the Manager Access to the forums section is restricted to committee
of Technical Documents. members and the oversight committee. The forums are to
be used by the membership for online discussions regard-
B.5.3Meetings ing various documents, issues, and other items under con-
When the Meetings button is clicked from the commit- sideration by the committee.
tee’s home page, two choices are presented.

Appendix B – Committee Web Sites


March 2004
62 ACI Technical Committee Manual — 2004

INDEX

ACI document adoption and publishing procedures, - Unrelated, 4.5.2


5.5, Fig. 5.1 - Withdrawn, 45.1, 4.5.4
Agenda, 2.3.3, 2.4.3, B2.7, B5.5 - No-Protest Consent, 4.1.3
American National Standards Institute (ANSI) - Nonvoting members, 1.4.2.4, 1.4.2.5, 4.3.5
- Approval, 3.2.1, 3.2.1.6, 5.5.9 - Passage of item, 4.4
American Society of Civil Engineers (ASCE), 1.10 - Procedures, 4.3, 4.5
American Society of Mechanical Engineers (ASME), - Progress, 4.7
1.10 - Proxy, 4.9
American Society of Testing and Materials (ASTM) - Reapproval, 4.10, Appendix 4.10.4
3.1, 3.2.1, 3.2.1.4, 3.5.4, 5.5.6.2 - Rules, 4.4
Annual report, 1.6.6.9, 2.2, 2.6, 2.11 - Special procedures, 4.8
Appeals - Subcommittee, 1.4.2.6, 4.2.2
- Membership classifications, 1.6.6.1 - Summary, 4.3.7, 5.1, Appendix 4.3.7,
- Nonstandardized document, 5.5.10, 5.5.10.2 - Time frame, 4.3.4
- Not appointed to committee, 1.5.2 - Types, 4.1
- Standardized document, 5.5.10, 5.5.10.1 - Letter, 4.1.1, 4,2, 4.2.1, 4.2.2
- TAC action on committee document, 5.3.3 - Meeting, 4.1.2
- Termination, 1.8.2 - No-protest consent, 4.1.3, 4.5, 5.3.1, 5.7, Appendices
- Vote found nonpersuasive, 4.6, 5.5.10 4.1.3a, 4.1.3b
Applicant’s Data Sheet, 1.4.2, 1.5, Appendix 1.4.2 - Voting members, 1.4.2.1, 1.8, 4.3.5
Appointments, 1.3, 1.4.1.1, 1.5, 1.5.1, 1.5.2, 1.7.1, 1.8.1
Associate members, 1.4.2, 1.4.2.2, 1.4.2.4, 1.6.3 Bibliographies, 3.2.2.3
Board of Direction
Balance, 1.6.6, 1.6.6.8 - Appeals
- Annual Review, 1.6.6.9 - Standards Board, 5.5.10.1
- Associate members, 1.4.2.2,1.4.2.4 - TAC, 5.5.10.1, 5.5.10.2
- Classification, 1.6.6.1 - Authorizes, 1.1, 2.9, 2.10
- Exceptions, 1.6.6.8 - Policies, 3.5
- Organizing committees, 1.3 - Certification programs, 3.5.2
- Reorganization, 1.7.2 - Sessions honoring prominent members, 6.2.4.1
- Terminate to achieve balance, 1.8.1 - High-performance concrete, 3.5.3
- Voting members, 1.4.2.1, 1.5.1, 1.6.6.1 - Performance specifications, 3.5.1
Balloting committee documents, Chapter 4 - TAC authority, 1.1
- Abstention, 4.3.6, 4.5.1, 4.5.2 - Units of Measurement, 3.5.4
- Adding new members, 1.4.2.2, 1.5.6 -
- Affirmative votes with comments, 4.6, Fig. 4.4 Certificates, 1.13, 1.13.1, 1.13.2, 1.13.3
- Analysis of results, 4.3.8, Fig. 4.1 Certification programs, 3.5.2
- Associate members, 1.4.2.2, 1.4.2.4 Chairs, Committee, 1.4.1.1
- Balance of Interests, 1.6.6.8 - Accomplish mission, 2.1
- Consulting members, 1.4.2.4 - Appoint, 1.4.1.1, 1.7, 1.7.1, 1.8.1
- Distribution, 4.3.5 - Certificates, 1.13.2
- Format, 4.3.3, Appendices 4.1.1, 4.10.7 - Circulate draft documents, 3.6
- Interim, 4.8 - Reappoint, 1.4.1.1
- ITG, 4.2.3 - Responsibilities
- Letter, 4.1, 4.2, 4.2.1, 4.2.2, 4.3, 4.3.1, 4.3.2 - Annual reports, 2.6
- Meeting, 4.1.2 - Coordinate with other committees, 1.6.5, 2.5
- Negative Votes, 4.3.6 - Call meetings, 2.3
- Appeal, 4.5, 5.5.10 - Determine passage of ballot item, 4.4, Fig. 4.1
- Disposition, 4.3.6 - Memberships, 1.3.1.2, 1.4.2, 1.5, 1.7.2, 1.8, 1.8.1
- Explained in writing, 4.3.6 - Organize committee, 1.3
- Nonpersuasive, 4.5.3 - Submit documents, 5.1
- Persuasive, 4.5.4, 4.5.4.1, 4.5.4.2, Fig. 4.3 - Verify editorial subcommittee work , 3.4
- Resolution of, 4.2.1, 4.3.6, 4.5, Fig. 4.2 - Successors, 1.4.1.1, Appendices 1.4.1.1a , 1.4.1.1b
- Workshop, 2.13

Index
March 2004
ACI Technical Committee Manual — 2004 63

INDEX

Chapters, 3.8.1 - Review of presentation materials, 6.2.3, 6.2.4, 6.2.9


Classification of members, 1.6.6, 1.6.6.1, 1.8.1 - Session Request Form, Appendices 6.2.3, 6.2.4, 6.2.7
- Appeal classification, 1.6.6.1 - Speakers, 6.2.6, 6.2.6.1, 6.2.6.2, 6.2.6.3
- Classification, 1.6.6.1 - Symposium volumes, 6.3
- Consultants, 1.6.6.7 - ACI awards, 6.5
- General interest, 1.6.6.6 - Discussion, 6.4
- Producer, 1.6.6.2, 1.6.6.3 - Final approval, 6.3.4
- User, 1.6.6.4, 1.6.6.5 - Preliminary approval, 6.3.1
Codes, 3.2.1.1, 5.5.6.1, 5.5.6.3 - Preparation of papers, 6.3.2
- Associate membership, 1.4.2.2 - Review of papers, 6.3.3
- Cases, 3.2.1.2 - TAC approval, 6.2.1.1, 6.2.1.2, 6.2.1.3, 6.2.3, 6.2.4,
- Patented Items, 3.2.1.1, 3.3.2.2 6.2.7, 6.3.1, 6.3.4
Commentaries, 3.2.1.1, 3.2.1.5 - Timetables, 6.2, 6.2.1, 6.2.1.1, 6.2.1.2, 6.2.6.1, Fig. 6.1
- Patented Items, 3.3.2.2 - Training session, 6.2.5
Committees, Chapter 1 Conventions
- Balance, 1.6.6 - Meetings at, 2.3
- Chairs, 1.4.1.1 - Technical sessions, 2.2.4, Chapter 6
- Discharge, 1.1, 1.7, 1.7.1 Coordination, 2.5, 3.7
- Expenses, 2.9 - Documents, 5.1
- Joint, 1.1, 1.10 - With other committees, 1.6.5, 2.5, 3.7.1
- Limit membership, 1.6.1 - With TAC Specifications Committee, 3.7.2
- Meetings, 2.3 - With Construction Liaison Committee, 3.7.3
- Membership, 1.4
- Missions, 1.1, 1.3, 1.7, 2.1 Copyright, 3.1, 3.6, 6.3.2
- Officers, 1.4.1
- Organizing, 1.3 Discharge committee membership, 1.1, 1.7, 1.7.1
- Reorganization, 1.7, 1.7.1 Disclaimer statement, 3.9, 3.9.3.2, 3.9.4
- Subcommittees, 1.3.1 Distribution
Concrete Innovation Appraisal Service (CAIS), 1.12.1, - Agenda, 2.3.3
1.12.3 - Correspondence, 1.4.2.4, 1.4.2.5, 2.4, 2.4.1, 2.4.2, 2.4.3
Concrete International, 1.12.3, 2.3, 3.2.1.3, 3.7.1, 5.4, - Documents, 3.7
6.2.6.1, 6.2.7 - Geographic, 1.6.3
Concrete Research and Education Foundation, - Minutes 2.3.4
(ConREF), 2.6, 2.11 Documents, Chapter 3, Chapter 5
Consensus, 3.3, 4.2.2, 4.6, 5.4, 5.7 - Appeal, 5.3.3, 5.5.10, 5.5.10.1, 5.5.10.2
Consultants, 1.6.6.7 - Approved, 5.3.1, 5.5.4
Consulting members, 1.4.2.3, 1.4.2.4 - Chapters, 3.8.1
- Geographical distribution, 1.6.3 - Circulating, 3.6
- Membership, 1.4.2 - Closure, 5.5.7.2, 5.5.8, 5.7
Control group, 1.3.1.3 - Comments, 5.2.2.2, 5.5.7, 5.5.7.1, 5.5.7.2, 5.6
Convention committee, 6.2.1.4, 6.2.4.1, 6.2.6.3 - Coordinating, 3.7, 3.7.1, 3.7.2, 3.7.3, 5.1, 5.2
Convention sessions and related publications, 2.2.4, - Copyright, 3.1, 3.6, 6.3.2
Chapter 6, 6.1, Fig. 6.1 - Date of adoption, 5.8
- Call for papers, 6.2, 6.2.1.1, 6.2.4, 6.2.6, 6.2.6.1 - Disclaimer of government endorsement, 3.9.4
- Deadlines, 6.2.1 - Discussion, 5.5.6.3, 5.5.6.4, 5.7
- Final approval, 6.2.1.3, 6.2.5, 6.2.7, Appendix 6.2.7 - General procedure, 3.1
- Headquarters assistance, 6.2.8 - Joint committees, 3.6, 5.1
- Honoring prominent ACI members, 6.2.4.1 - New standard, 2.2.1, 3.2.1
- Initiating a session, 6.2.2, 6.2.3 - Not approved, 5.3.2
- Moderators, 6.2.2, 6.2.3, 6.2.4, 6.2.5 - Not authored by technical committee, 3.8
- Preliminary approval, 6.2.1, 6.2.1.1, 6.2.1.2, 6.2.4, - Not requiring standardization, 2.2.2, 3.2.2
Appendix 6.2.4 - Organization of material, 3.3.1
- Presentations, 6.1, 6.2.1.4, 6.2.10 - Origination, 5.5.2
- Proposal, 6.2.3, Appendices 6.2.3, 6.2.4 - Outside Reviewers, 5.2, 5.2.2.1
- Publication of session papers, 6.3 - Preparation, 3.3

Index
March 2004
64 ACI Technical Committee Manual — 2004

INDEX

- Procedures, document adoption and publishing, 5.4, 5.5, - Code cases, 3.2.1.2, 5.4, 5.5.6.1
5.5.1, 5.5.2, 5.5.3, 5.5.4, 5.5.5, 5.5.6, 5.5.6.1, 5.5.6.2, - Codes, 3.2.1.1, 5.4, 5.5.6.3
5.5.6.3, 5.5.6.4, Fig. 5.1 - Date of adoption, 5.8
- Processing, Chapter 5 - Discussion, 5.5.6.3, 5.5.6.4
- Publication, 5.5.8, 5.6, 5.8 - Guide specifications, 3.2.1.7
- Reapproval, 4.2.1, 4.10, 5.4.2, 5.5.7, 5.10, 5.10.1, - New standardized documents, 2.2.1
5.10.1.2, Appendix 4.10.4 - Procedures, 5.4, 5.5.4, 5.5.6, Fig.5.1
- References, 3.1, 3.3.2, 3.3.2.1 - Reference specifications, 3.2.1.3, 5.4, 5.5.6.3
- Requiring standardization, 1.6.6.8, 2.2.1, 3.2.1 - Provisional specifications and test methods, 3.2.1.4,
- Review, 3.4, 5.1, 5.2, 5.6, 5.7 5.4, 5.5.6.2
- Revisions, 4.2.1, 5.4.2, 5.5.7, 5.10.1, 5.10.1.1 - Standardized Reports and Guides, 3.2.1.6
- Separate publications, 5.8.1
- Submit for TAC Review, 5.1 Editorial
- TAC Review, 5.2, 5.2.2, 5.5.3 - Changes, 3.4, 4.5.4.1
- Appeal, 5.3.3 - Comments, 5.2.1.4, 5.2.1.5
- Approval, 5.2.2.2, 5.3.1, 5.5.4 - Review, 3.4, 5.1
- Comments, 5.2, 5.2.1, 5.2.2.2 - Subcommittee, 1.3.1.2
- Decision, 5.3, 5.3.1, 5.3.2 Educational Activities Committee (EAC), 2.2.6
- Editorial (E), 5.2.1.4, Emerging technology series, 3.2.2.5, 3.9.2
- Editorial (M), 5.2.1.5 Ethics, 1.4
- General or Specific, 5.2.1.1
- Primary (P), 5.2.1.2 Expenses, 2.9
- Secondary (S), 5.2.1.3
- Group, 5.2.2.1 General interest, 1.6.6.6
- Types, 3.2, 5.1, 5.5.1 Geographical distribution, 1.3.3, 1.6.3
- Bibliographies, 3.2.2.3 Goals, committee, 2.2, 2.6
- Code cases, 3.2.1.2, 5.5.6.1 Guide specifications, 3.2.1.7
- Codes, 3.2.1.1, 5.4, 5.5.6.1, 5.5.6.3 Guides, 3.2.2.1, 5.4.4
- Commentaries, 3.2.1.5
- Emerging technology series, 3.2.2.5, 3.9.2 Handbooks and manuals, 3.2.2.4
- Guide specifications, 3.2.1.7 High-performance concrete, 3.5.3
- Guides, 2.2.2, 3.2.2.1
- Handbook and manuals, 3.2.2.4 Individually authored papers, 2.2.6
- Innovation task group, 1.12, 3.9.1, 5.4.2 Innovation Task Groups (ITG), 1.12, Fig. 5.2
- Provisional specifications and test methods, 3.2.1.4, - Formation, 1.12.3
5.4, 5.5.6.2 - Introductory statement, 3.9.1
- Reference specifications, 3.2.1.3, 5.4 - Letter ballot, 4.2.3
- Reports, 2.2.2, 3.2.2.2 - Requesting, 1.12.1
- Standardized reports and guides, 3.2.1.6 - TTTC review, 1.12.2
- Symposium volumes, 2.2.4, 6.3 - Updates, 1.12.4, 5.10.2
- Units of measurement, 3.5.4
- Updating, 2.2.3, 5.10, 5.10.1, 5.10.2 Institute membership, 1.4.1.1, 1.4.2, 1.4.2.2
- Withdrawals, 4.2.1, 5.4.2, 5.5.7, 5.10, 5.10.1.3 Joint committees, 1.1, 1.10, 2.4.3, 3.6, 5.1, 5.9
Documents, not requiring standardization, 3.2.2, 5.4.4
- Appeal, 5.5.10.2 Liaison members, 1.4.2, 1.4.2.5
- Balance of interests, 1.6.6.8
- Commentaries, 3.2.1.5 Manual of Concrete Practice, 3.3.1, 3.7.1, 4.11.1, 5.8.2,
- Date of adoption, 5.8 5.10.1, 5.10.7
- Emerging technology series, 3.2.2.5 Meetings, 1.6.2, 2.3
- Guides, 3.2.2.1, 5.4.4 - Agenda, 2.3.3
- Handbook and manuals, 3.2.2.4 - Attendance, 1.4.2.1, 1.4.2.2, 1.4.2.4, 1.6.2, 1.6.3, 1.8
- Procedures, 5.4.4, 5.5.4 - Closed, 2.3.1
- Reports, 2.2.2, 3.2.2.2, 5.4.4 - Members, 1.4.2.1, 1.4.2.2, 1.4.2.3, 1.4.2.4
Documents, requiring standardization, 3.2.1, 5.5.6.4 - Minutes, 2.3.4
- Appeal, 5.5.10.1 - Quorum, 2.3.5
- Balance of interests, 1.6.6, 1.6.6.1, 1.6.6.8 - Visitors, 2.3.2

Index
March 2004
ACI Technical Committee Manual — 2004 65

INDEX

Members, committee, 1.4, 1.4.2 - Withdrawn, 4.5.1


- Annual Review, 1.6.6.9 New Business, 4.1.1, 4.5, 4.6, Fig. 4.4
- Appeal to TAC, 1.5.2, 1.8.2
- Appointments, 1.3, 1.4, 1.5 Officers, 1.4.1
- Associate, 1.4.2, 1.4.2.2, 1.4.2.4 Operating technical committees, Chapter 2,
- Balance of interests, 1.4.2.1, 1.8.2 Organizing technical committees, Chapter 1, 1.1, 1.3
- Certificates, 1.13.1, 1.13.3 Overlapping membership, 1.6.6
- Chairs, 1.4.1.1
- Change membership status, 1.6.2, 1.7.2, 1.8, 1.8.1 Patented items, 3.2.1.5, 3.3.2.2, 3.9.3, 3.9.3.1, 3.9.3.2
- Classification, 1.6.6, 1.6.6.1 Performance specifications, 3.5.1
- Consulting, 1.4.2, 1.4.2.3, 1.4.2.4 Producer, 1.6.6.2, 1.6.6.3
- Discharge, 1.7, 1.7.1 Proprietary items, 3.3.2.2
- Geographical distribution, 1.6.3 Provisional specifications and test methods, 3.2.1.4,
- Joint with other organizations, 1.10 5.4, 5.4.3, 5.5.6.2
- Liaison, 1.4.2, 1.4.2.5 Public review, 5.6, 5.7
- Multiple, 1.6.2, 1.6.5 Publications available
- Officers, 1.4.1 - ACI Authors Guide, 6.3.2
- Official actions, 1.4.2 - ACI Committees Booklet, 2.2
- Outstanding, 1.13.3 - ACI Specification Manual, 3.1, 3.2.1.3, 3.2.1.4, 3.3.2.1,
- Overlapping, 1.6.5 3.7.2,
- Qualifications, 1.5.1, 1.6.1, 1.6.2 - ACI Style Manual, 1.3.1.2, 3.1, 3.1.1, 3.3, 3.3.1, 3.3.2,
- Questionnaire, 1.7.2, 1.8, Appendix 1.7.2 3.4, 5.1, 5.2.1.4
- Reappoint, 1.4.2.2, 1.7.1, 1.8.1 - The a-b-c’s of Parliamentary Procedure, 2.3
- Rejected, 1.5.1 - A Guide for Applying for Government Agency Grant for
- Resignation, 1.7.2, 1.9 Committee Activity, 2.10
- Retain, 1.7.2
- Review activity, 1.7.2, 1.8, Qualifications, 1.5.1, 1.6.1, 1.6.2
- Secretary, 1.3, 1.4.1.3, Questionnaires, 1.7.2, 1.8, 2.7, Appendix 1.7.2
- Selection, 1.6 Quorum, 2.3.5
- Steering subcommittee, 1.3, 1.3.1.3
- Subcommittees, 1.3, 1.3.1, 1.3.1.2, 1.3.1.3, 1.4.2.6 Reappointments, 1.4.1.1, 1.4.2.2, 1.7.1, 1.8.1
- Task groups, 1.3, 1.3.1 Reapprovals, 4.10, 5.10.1.2
- Terminate, 1.7.2, 1.8, 1.8.1, 1.8.2 - Completion, 4.10.6
- Turnover, 1.5 - Format, 4.10.4
- Variety of Experience, 1.6.4 - Initiation, 4.10.2
- Vice chairs, 1.3, 1.4.1.2, - Passage, 4.10.5
- Voting, 1.4.2, 1.4.2.1, 1.6, 1.6.2, 1.8, 1.9 - Purpose, 4.10.1
Metrication, 1.11.2, 3.1.1, 3.5.4 - Responsibility, 4.10.3
Minutes, 2.3.4 Reference specifications, 3.2.1.3, 5.5.6.3
- Associate-consulting members, 1.4.2.4 References, 3.2, 3.3.2, 3.3.2.1
- Post on web site, Appendix B Reorganization, committee, 1.7, 1.7.1, 1.7.2
- Record Reports, 2.2.2, 3.2.2.2
- Ballot results, 4.5 Research, 2.11
- Members present, 2.3.4 Resignations, 1.9
- Resolution of negatives, 4.5 Revisions, 5.10.1.1
- Visitors, 2.3.4
Missions, 1.1, 1.3, 1.6.1, 1.6.6.1, 2.1 Secretaries, 1.3, 1.4.1.3
Multiple committee memberships, 1.6.2, 1.6.5 Seminars, educational, 2.2.6
Special funds, 2.10
Negative votes, 4.3.6, 4.5, 5.1 Specifications
- Persuasive, 4.5.4 - Committee, 1.114
- Editorial, 4.5.4.1 - Guide, 3.2.1.7
- Substantive, 4.5.4.2 - Manual, 3.1, 3.2.1.3, 3.2.1.4, 3.3.2.1, 3.7.2
- Related, nonpersuasive, 4.5.3 - Metrication, 3.5.4
- Resolution, 2.3.5, 4.5 - Provisional and Test Methods, 3.2.1.4, 5.5.6.2
- Unrelated, 4.5.2 - Reference, 3.2.1.3, 5.5.6.3

Index
March 2004
66 ACI Technical Committee Manual — 2004

INDEX

Sponsor Non-ACI Conferences, 2.12 - Discharge committees, 1.1


Staff assistance, 2.8 - Establish committees, 1.1
Standardization, 3.2.1 - Guide specification, 3.2.1.7
- Procedure, 5.4, 5.4.1, 5.4.2, 5.4.3, 5.4.4, 5.5, 5.5.6, - ITG formation, 1.12.3
- Expedited, 5.4.2, 5.5.7, 5.5.7.1 - Limit voting members, 1.6.1
- Normal, 5.4.1.1, 5.5.7.2 - Metrication, 3.1.1, 3.5.4
Standardized reports and guides, 3.2.1.6, 5.5.6.4 - Missions, 1.1
Standards board, 5.5, 5.5.7.2, 5.5.8, 5.5.10, 5.5.10.1, - Provisional or test methods, 3.2.1.4
5.6, Fig. 5.2 - Reapproval, 4.11.6
Subcommittees, 1.3, 1.3.1, 1.4.2.6, 1.6.1 - Reference specifications, 3.2.1.3, 3.7.2, 5.5.2
- Ballots, 4.2.2 - Reorganize, 1.7
- Balance of interest, 1.6.6.8 - Special Funds, 2.10
- Designation, 1.3.1.1 - Subcommittees, 1.3.1, 1.4.2.6
- Distributing correspondence, 2.4.1 TAC contact member, 1.2, 1.5.2, 1.8, 1.11, 1.13.3, 2.3.3,
- Editorial, 1.3.1.2, 3.3.2 2.3.4, 2.4.3, 2.6, 4.3.4, 4.3.5
- Steering, 1.3, 1.3.1.3 TAC Subcommittees, 1.11
- TAC, 1.11, 1.11.1, 1.11.2, 1.11.3, 1.11.4, 1.11.5 - High-Performance Concrete (THPC), 1.11.1, 3.5.3
- Voting, 1.4.2.6, 4.2.2 - Metrication (TMC), 1.11.2, 3.5.4
Symposium volumes, 2.2.4, 6.3, 6.3.1, 6.3.2, 6.3.3, 6.3.4, - Repair and Rehabilitation (TRRC), 1.11.3
6.4, 6.5 - Specifications (TSC), 1.11.4, 3.7.2
- Technology Transfer (TTTC), 1.11.5, 1.12, 1.12.1,
TAC, 1.1 1.12.2, 1.12.3, 1.12.4
- Annual reports not received, 2.6, Task groups, 1.3, 1.3.1, 1.4.2.6, 1.12.2
- Appeals, 1.5.2, 1.6.6.1, 1.8.2, 5.3.3, 5.5.10 Terms, 1.4.1.1, 1.4.2.2, 1.5
- Arbitration, 3.7.1 Terminations, 1.8
- Comments, 5.1, 5.2.2.2 - Appeal, 1.8.2
- Reconsider balance of interests, 1.6.6.8 - Associates, 1.4.2.2
- Recommend reapproval or withdrawal, 5.10.1 - Discharge, 1.7, 1.7.1
- Review of documents, 5.1, 5.2, 5.5.3 - Lack of interest, 1.7.2
- Comments, 5.2.1, 5.2.2.2, 5.5.7.2 - Resignations, 1.7.2, 1.9
- Coordination, 3.7.1, 3.7.2, 3.7.3 - To achieve balance, 1.8.1
- Decision, 5.3 The Masonry Society (TMS), 1.10
- Editorial review, 3.4 Trade Associations, 1.6.6.2
- General Procedure, 3.1
- Group, 5.2.2.1 User, 1.6.6.4, 1.6.6.5
- Preparation of committee documents, 3.3 Units of measurement, 3.1.1
- Procedure, 5.2.2
- Reapproval of committee documents, 4.10, 5.10.1 Vice chairs, 1.3, 1.4.1.2
- Submitting, 5.1 Voting members, 1.4.2, 1.4.2.1, 1.6, 1.6.1, 1.6.2, 1.6.3,
TAC approval 1.6.4, 1.6.5, 1.6.6.8, 1.6.6.9, 1.8, 1.13.1
- Chairs, 1.4.1.1, 1.4.1.2
- Circulating drafts, 3.6 Web sites, ACI, Appendix B
- Codes, 3.2.1.1, 5.5.2 Withdrawals, 4.2.1, 5.4.2, 5.5, 5.10, 5.10.1.3
- Convention sessions, 6.1, 6.2.1.1, 6.2.1.2, 6.2.1.3 Work product, 3.1
Workshop, Chair, 2.13

Compiled and edited by


Patricia A. Levicki

Index
March 2004

You might also like