The final conferences are the last events of the site visit and may be the most challenging part. In these meetings the institutional efforts that went into the self-study and site visit preparation and the site visit team findings are brought together by the visiting team chair in an explanation of the suggestions, and recommendations that will be made to the Commission on Dental Accreditation (CODA).
There are usually two final conferences: one with administration directly responsible for the program and the other with institutional administration. During each of these conferences the site visit team findings are explained in detail to the institutional leader. As shown below attendance at the final conference may differ depending on the program(s) being evaluated.
Pre-Doctoral Dental Program
Conference #1
- Dean of the College
- Assistant and Associate Deans
- Site Visit Team
- CODA Staff
Conference #2
- University President
- Dean of the College (optional)
- Assistant and Associate Deans (optional)
- Site Visit Team
- CODA Staff
Allied Programs
Conference #1
- Program Director
- Faculty of the program (optional)
- Site Visit Team
Conference #2
- University President
- College President
- Dean of Allied Programs
- Program Director
- Faculty of the program (optional)
- Site Visit Team
Advanced Education Programs
Conference #1
- Program Director*
- Faculty of the program (optional)
- Site Visit Team
*and/or others at the program's discretion
Conference #2
- Institutional Representatives (CEO, CAO, Hospital Administrator, for example)
- Site Visit Team
Even if you are not participating in the final conference it is important for all Site Visitors to be knowledgeable about the process. This knowledge will help you write your section of the draft report.
A preparatory executive session is held just before the final conference. This is the time to review the report contents and to rehearse the presentation with team members who will be attending the final conference. Guidelines have been developed for each program type to help Site Visitors prepare for this important conference (Appendix 6.1).
General guidelines for the conferences include:
- Thank the hosts. Begin the session by thanking them for their participation in the Commission's voluntary accreditation process.
- Describe the protocol and process for the final conferences. The sequence of the final conference is reviewed with the attendees. They are provided verbally with a summary of the findings of the site visit team standard by standard. They are asked to delay questions until the entire report has been read. In addition, they are reminded that they cannot record the meeting, but they are encouraged to take notes. It is usually important to restate that the role of the visiting team members is to present the findings of the site visit team based upon accreditation standards.
- Move from the general to the specific. The conference begins with an overview of the report. The attendees are told how many suggestions and recommendations are contained in the report prior to beginning with a detailed account of each. (Review Unit 5 as a reminder of the details required in the final report. This detailed accounting is also included in the final conference.) It is not enough to tell the program administrators that the team will make a recommendation about an area such as the curriculum. The verbal report must spell out the specific deficiency and make a recommendation that is targeted to correcting the deficiency.
- Progress through the standards in numerical order. The Chair of the site visit team will begin by reading the first standard for which there are comments and stating whether there is a suggestion or recommendation. If there is a suggestion, it is usually read first, followed by recommendations.
- Be thorough. It is important that all of the recommendations in the final report are included in the presentation of the report during the final conferences. (The goal is not to give the program administrator(s) the "big picture" and fill in the specific recommendations after leaving the site.) The program director must be fully informed in detail of the findings before the conference is over.
- Answer questions but do not prolong the exchange. After the report has been completed there may be questions. Answers should be formulated in order to clarify issues for program or institutional representatives; however, they should not defend either the standard in question or the report. It is important that the responses be as accurate and succinct as possible. If there are concerns or defensive behaviors demonstrated by the institutional representatives, the chairman/staff representative of the site visit team should reiterate the role of the team (to find facts) and try to move to the conclusion of the conference.
- Summarize the sequence of events that will follow the site visit. The Chair should review the accreditation steps following the site visit.
- The preliminary draft report will be sent to the institution approximately 6-8 weeks after the site visit.
- The institution will have 30 days to respond. They are encouraged to look for and respond to factual inaccuracies or differences in perception, and to report progress made in implementing the recommendations since the site visit.
- The report and the institutional response will be considered by the Commission, and the accreditation status will be determined.
- The report and accreditation status will be sent to the institution within 30 days following the CODA meeting.
- Thank the institutional representatives again.
Additional Suggestions
In addition to the general guidelines in the preceding paragraphs, there are several other helpful suggestions that may be applied to the final conference:
- It is important to take an appropriate amount of time. The final conference is a critical part of the site visit. Rushing through it is an affront to those involved. It encourages a breakdown in communication and creates problems later if the institution receives a site visit report that contains suggestions and recommendations not discussed at the final conferences.
- It is sometimes important to reiterate the differences between recommendations and suggestions so that the institutional administrators are clear on the formal responses that are required.
- It is important to be complete and include all of the recommendations that will be in the final report. The program director must be informed in detail of the findings before the site visit is over. Encourage the program director to begin addressing recommendations before the written draft is received.
- Maintain a professional demeanor throughout the final conferences. The tone of the final conference should suit the message. Don’t make them laugh if the report is negative. If the recommendations are numerous and serious, the attendees should not smile as the recommendations are discussed. It may be tempting to reassure the institutional representatives, but it is better to deliver the final report in a manner that conveys the seriousness of the recommendations.
- Do not ask the program or institutional representatives to help write the report. The final conference must reflect the contents of the site visit team's final report. It is not appropriate to "do the program a favor" and ask them for information they would like to see in the report.
- Maintain control. The final conference is not a discussion or a debate; nor is it an opportunity to re-conduct the site visit. The report reader should do most of the talking. The institutional representatives can ask questions at the conclusion of the presentation, but disagreements over the standards or the site visit team’s findings should not be part of the final conference.