Reports and reporting are important parts of the program development and accountability process. In designing these processes, we attempt to collect information so that it can meet multiple reporting and accountability needs. To accomplish this process, we have developed two types of reports: data reports and narrative reports. The data reports are numerical measures of various types, and the narrative reports fill in the gaps. These reports are explained below.
Check the calendar for important Program Planning and Reporting Dates
Team Assignment Document (TAD)
The Team Assignment Document is a negotiated agreement between the team and its assigned administrator. The Team Assignment Document describes goals, objectives, and reporting indicators for each of the team’s major programs. The programs’ goals, objectives, and indicators are posted on the Web. Faculty use the team’s document to construct their respective Faculty Assignment Documents (FAD.)
The TADs use the logic model.For more information about working with the logic model, visit the University of Wisconsin Extension program development and evaluation page (http://www.uwex.edu/ces/pdande/evaluation/evallogicmodel.html). For a quick overview of the logic model, read the five-page Extension bulletin The Logic Model for Program Planning and Evaluation (PDF), a part of the Program Assessment Resources of the University of Idaho Extension Service.
Faculty Assignment Document (FAD)
The Faculty Assignment Document (MS Word) is a negotiated agreement between the faculty member and his or her Center Director and captures the essence of the faculty member's goals and responsibilities for that year. This annual document is significant for accountability issues and Promotion and Tenure (P&T) functions. For county faculty, the Faculty Assignment Document should reflect County Plan of Action goals and contain program goals, objectives, and indicators from the appropriate Team Assignment Documents.
The data reports collect numeric information for each of the major extension programs and their initiatives.
Program Indicator Reports
Program Indicator data will be collected on all major program initiatives. These program
indicators were determined by the program teams when they prepared their
plans of work. Extension agents and specialists will report data on all programs they
have worked with. This reporting process uses the Web and links into a database.
Individuals should report their data quarterly. The data
in these reports is extremely important for documenting our efforts. The Program
Indicator Reports, along with other program planning information, are used
to generate accountability documents identifying Extension's value and impacts.
Narrative reporting will provide program accomplishment and impact details. These reports may include some of the information submitted in the data reports, but should amplify the significant details. These reports should focus on program accomplishments and impacts. These narrative reports and their current due dates are found below.
Faculty Program Accomplishment report (individual reports)
The Faculty Program
Accomplishment Report reflects the faculty member's significant program
involvement and accomplishments for the year. These reports are to be submitted
at the end of the year in two ways: (1) as electronic copies e-mailed as separate
Word documents to Paul Becker and (2) as paper copies submitted as support documentation
in the appropriate sections of faculty members’ Promotion and Tenure files.
Those copies submitted to Paul Becker will be used to develop state and federal reports. See report
template for
additional information.
Team Program Accomplishment reports (team and
unit reports)
Team Program Accomplishment Reports summarize the statewide efforts by program
team members and other contributors to the team.
The collection of program indicators and narrative information is based on the
earlier work of the program teams. For more information and the template, see
the Impact Primer.
County Plans of Action (county document)
County Plans of Action
will record the significant program efforts planned by that county. The document
will be built primarily upon Program Team plans that have already been developed.
Counties can supplement these plans with program efforts that were not previously
developed by formal program teams. The Plan of Action should closely tie to
the Faculty Assignment Document goals.
Important Program Planning and Reporting Dates
| July 15, 2008 | Data due. Submit FY 2007-2008 Program Indicator Reports on the Web. (Third quarter report covering April 1 through June 30, 2008.) |
| Sept. 11, 2008 | Program team meetings (optional) at WVU Jackson's Mill to update 2008-2009 Program Indicator Report forms. |
| Sept. 17, 2008 | Requests for Proposals due: For Seed Grants for Research Projects, submit to Dave Cormier; for Competitive Funds for Team Activities, submit to Paul Becker. (Awards will be announced Oct. 13.) |
| Sept. 17 , 2008 | Draft Faculty Assignment Document (FAD) (individual) MS Word, due to program directors. |
| Sept. 17, 2008 | Indicator Report forms for 2008-2009 due. Program teams submit Program Indicator Report form changes for new year to Paul Becker. |
| Oct. 1, 2008 | Federal Fiscal Year 2008-2009 begins (October 1, 2008 - September 30, 2009). Begin reporting against new Program Indicators. |
| Oct. 1, 2008 | Interim Reports due: Seed Grants for Research and/or Competitive Funds for Team Activities interim reports due for those who received funds in Spring 2008. |
| Oct. 1, 2008 | ES-237 4-H Youth report due to Marsha Price. (County report.) |
| Oct. 15, 2008 | Data due. Submit FY 2007-2008 Program Indicator Reports on the Web. (Fourth quarter report covering July 1 through September 30, 2008. Year-end report. Please include any data not previously reported, covering October 1, 2007 through September 30, 2008.) |
| Nov. 26, 2008 | Team Program Accomplishment/Impact Statements due. By e-mail, send as MS Word file to program directors and Paul Becker. |
| Nov. 26, 2008 | Program Team Goals and Objectives (Team Assignment Document (TAD)) due. By e-mail, send as MS Word file to program directors and Paul Becker. |
| Dec. 17, 2008 | Final Faculty Assignment Document (FAD) MS Word, completed and signed by faculty and program directors.. |
| Dec. 17, 2008 | Faculty Program Accomplishment reports due (individual). By e-mail, send each report as a separate MS Word file to Paul Becker. |
| Dec. 17, 2008 | Faculty files close. Promotion and Tenure (P&T) files due to program directors. |
| Jan. 15, 2009 | Data due. Submit FY 2008-2009 Program Indicator Reports on the Web. (First quarter report covering October 1 through December 31, 2008.) |
| Feb. 13, 2009 | Requests for Proposals due: For Seed Grants for Research Projects, submit to Dave Cormier; for Competitive Funds for Team Activities, submit to Paul Becker. (Awards will be announced March 14, 2009.) |
| March 27, 2009 | Final reports due for those who received Seed Grants for Research and/or Competitive Funds for Team Activities in Spring 2008. |
| April 15, 2009 | Data due. Submit FY 2008-2009 Program Indicator Reports on the Web. (Second quarter report covering January 1 through March 31, 2009.) |
| May 15, 2009 | Written requests due from faculty members who want to be considered for promotion and/or tenure. Send letter requesting consideration for promotion and/or tenure to Program Unit Director. |
| March 28, 2009 | Program Accomplishment Reports submitted to CSREES |
| March 28, 2009 | 2010-2014 Plan of Work update submitted to CSREES |
