*Note that because of procedural changes, these policies and procedures are currently under review. Questions should be directed to RUSA Executive Director, Jessica Hughes, email@example.com.
- 1 Chapter 4: Guidelines
- 1.1 Procedures for Guideline Creation
- 1.2 RUSA Board Review of Guidelines
- 1.3 Publication of Approved Guidelines
- 1.4 Seven-Year Review of Guidelines
- 1.5 Procedures for Guideline Revision
- 1.6 Sunsetting Guidelines
- 1.7 Appendices
- 1.7.1 Model Outline for RUSA Guidelines
- 1.7.2 Checklist for Creation or Revision of RUSA Guidelines
- 1.7.3 Supporting Documentation Checklist
1. 1 Procedures for Guideline Creation
The RUSA Standards and Guidelines Committee (abbreviated as S/G within this document), coordinates the development of all RUSA guidelines. ALA Bylaws permit only type-of-library divisions to adopt technical standards. RUSA, as a type-of-activity division, may write guidelines only. All guidelines are approved at the division level.
ALA Bylaws (http://www.ala.org/aboutala/governance/constitution/bylaws) in Article VI. Section 3.d. specify:
Type-of-activity divisions may develop and adopt technical standards as official ALA standards. Type-of-activity divisions may participate in the development of nontechnical standards by type-of library divisions but nontechnical standards may be adopted, or approved as official ALA standards, only by type-of-library divisions.
A RUSA unit or committee should complete the following tasks to submit a new guideline for approval:
- Identify the audience, define and agree on the need, and determine that the committee has the expertise and background to develop a guideline.
- Notify the RUSA Executive Director of the intent to develop a new guideline.
- Request that the chair of S/G appoint a liaison from the S/G Committee. The liaison should provide advice and guidance throughout the review process.
- Develop a quality draft for S/G review:
- Follow the content and formatting of 1.7.1 Model Outline for RUSA Guidelines.
- Consult 1.7.2 Checklist for Creation or Revision of RUSA Guidelines.
- Include the following: goal(s), structure, purpose, intended audience, type of guideline (service, performance, technical, or procedural), content and organization.
- Include 1.7.3 Supporting Documentation Checklist, documenting activity to date.
- Distribute the quality draft for comment. Copies should go to:
- section chair, if appropriate
- RUSA executive director
- RUSA Standards and Guidelines Committee chair
- If recommended by the S/G Committee:
- attend a meeting of the S/G Committee to discuss the draft and receive feedback about content, format, style, and other editorial matters. Then, review comments and incorporate necessary revisions.
- invite comments on the draft from RUSA membership and relevant committees/groups via email, electronic discussion lists, or public hearing at an ALA conference, as appropriate.
- Submit a revised draft to the S/G Committee. This process is iterative until the draft is in a satisfactory final state.
- If the S/G Committee approves the final draft, it will be forwarded to the chair of the appropriate RUSA section executive committee for section approval. The section chair will send written confirmation of approval or disapproval to the chair of the S/G Committee and to the originating unit or committee chair.
- If approved by the RUSA section, the S/G Committee chair will present the final draft, and the Supporting Documentation Checklist, to the RUSA executive director at least one month prior to the board meeting at which consideration by the RUSA Board is expected. The RUSA executive director will distribute it to the RUSA Board.
- If the S/G Committee finds the final draft unacceptable and an impasse is reached after discussion with the originating unit or committee, the S/G Committee will transmit its findings to the originating unit or committee, the RUSA section, and the RUSA Board for final review.
1. 2 RUSA Board Review of Guidelines
Upon approval by the originating unit or committee, the appropriate RUSA section executive committee, and the S/G Committee, the S/G Chair will notify the RUSA executive director that all have found the guideline acceptable and consistent with existing RUSA guidelines. If only minimal editing is required, approval notification may proceed. The RUSA Board may now formally act on it.
1. 3 Publication of Approved Guidelines
If approved by the RUSA Board, the RUSA executive director will submit the approved guideline to the editor(s) of RUSQ for publication. The executive director will also post the guideline on the RUSA Web site.
1.4 Seven-Year Review of Guidelines
RUSA Standards and Guidelines Committee will initiate a guideline review at seven year intervals after initial Board approval. Guideline review allows the opportunity for a guideline to be continued as is, revised, or sunsetted.
1.5 Procedures for Guideline Revision
Those working to revise a guideline should notify the RUSA Executive Director of their effort and follow 1.1 Procedures for Guideline Creation.
1.6 Sunsetting Guidelines
The seven-year guideline review may result in a recommendation to approve, as is, revise, or sunset the guideline. The S/G Committee also may recommend that the RUSA Board sunset any guideline that has not be reviewed by the end of the eighth year. A proposed guideline may be dropped if a final draft is not presented within three years.
1.7.1 Model Outline for RUSA Guidelines
Guidelines serve as an authoritative document offering suggested levels of performance or adequacy. They outline a recommended course of action. Unlike standards that carry the weight of a rule, guidelines describe measures to help libraries meet the requirements of a standard. Include in the introduction the purpose or objectives of the document, the need which justified development of the guideline, the scope, and the audience or group which the guideline serves.
Body of Document
Use short, declarative sentences. Avoid lengthy descriptive phrases. Avoid passive voice.
The format of the guideline should follow those recommended in the ALA Standards Manual. Number the sections in sequential order, with secondary ideas listed under general statements.
2.1 Qualifications of Professional and Support Staff
2.2 Staff Development
Each numbered section may have a header with a statement or paragraph(s) underneath, or may have a main section header with a numbered statement/paragraph underneath.
Example 1: Headers with statements/ paragraphs following
The goal of information service is to provide an end-product: the information sought by the user. Information service should not only meet but also anticipate user needs. It should encourage user awareness of the potential information resources that fulfill individual information needs.
The library should provide instruction in the effective use of its resources. Such instruction can range from the individual explanation, creation of guides in appropriate media to formal assistance through interpretive tours and group presentations.
Example 2: Main section header with numbered statements or paragraphs following
3.1 The library should arrange information services according to a coherent plan taking into account read accessibility to users.
Avoid detail beyond three numbered divisions (e.g. 1.1.2) to prevent making the document cumbersome and difficult to follow.
1.1 A RUSA guideline should incorporate benchmarks or yardsticks by which a particular library or information service, resources, or material may be judged.
1.1.2 The library should provide users with complete, accurate answers to their information queries regardless of the complexity of those queries.
1.1.3 The library should make service areas for information services highly visible and readily accessible to all users.
Included as appendices: definitions of special terms, a bibliography of relevant sources, recommended procedures, etc. These procedures may also refer to separately-published documents.
1.7.2 Checklist for Creation or Revision of RUSA Guidelines
Checklist for Creation or Revision of a RUSA Guideline http://www.ala.org/ala/mgrps/divs/rusa/about/policies/developingguidelines/checklist4guidelines.doc
1.7.3 Supporting Documentation Checklist
The following checklist of information must accompany a new or revised guideline when submitted to the RUSA Standards and Guidelines Committee for review. This checklist will travel with the guideline throughout the review to document proper completion of the process. The Supporting Documentation Checklist records:
- Originating unit or committee contact person
- A brief history of the guideline’s development, if the history is significant to understanding the guideline.
- Related guidelines and standards used to develop the guideline, if applicable.
- The ALA divisions, committees and units, individuals, and other interested parties consulted during the development of the guideline, if applicable.
- The dates when the guideline was submitted to:
- originating unit or committee for review
- S/G Committee for review
- appropriate RUSA section executive committee for review
- the RUSA Board for review (via the RUSA executive director)
- The dates when the guideline was approved or rejected by the:
- originating unit or committee
- S/G Committee
- appropriate RUSA section executive committee
- RUSA Board
Updated March, 2014