1810-new_COMPS - DEV Grant Profile - User Guide

Charter Online Management and Performance System (COMPS)

Developer (DEV) Program

Grant Profile User Guide

Release 2.0, January 2024

Comps.ed.gov

Public Burden Statement

According to the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless such collection displays a valid OMB control number.  The valid OMB control number for this information collection is 18xx-xxxx.  Public reporting burden for this collection of information is estimated to average 8 hours per response, including time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information.  The obligation to respond to this collection is required to obtain or retain benefits (EDGAR, Section 75.720 and 80.40).  If you have any comments concerning the accuracy of the time estimate, suggestions for improving this individual collection, or if you have comments or concerns regarding the status of your individual form, application or survey, please contact Stephanie Jones, at stephanie.jones@ed.gov, directly.

1. Table of contents

2 Introduction 3

2.1 Overview 3

2.2 Purpose 3

3 User Access and Management 4

3.1 Overview 4

3.2 Instructions and Screenshots 4

4 Grant Profile 5

4.1 Overview 5

4.2 Reporting Steps 5

4.3 Instructions and Screenshots 6

4.3.1 Homepage 6

4.3.2 Assurances 7

4.3.3 Competition Priorities 8

4.3.4 Key Program Activities 9

4.3.5 Grant Objectives 10

4.3.6 Grant Objectives – Document Uploads 11

4.3.7 Grant Objectives – Lottery 17

4.3.8 Approved Budget 18

4.3.9 Approved Budget – Budget Narrative 20

4.3.10 Waiver Requests 22

4.3.11 Submit 23

2. Introduction

   1. Overview

This document provides a description of the executed tasks and associated screenshots that are used to describe the implementation and performance of CSP Grantees as part of the Charter School Programs (CSP) Data Collection, Risk Assessment, and Monitoring contract (GS-10F-0288W) and the Charter Online Management and Performance System (COMPS). Where applicable, this document provides explicit detail on the logic patterns of response options which show the full range of experiences Grantees may have as they use the system based on their responses as they go.

The Charter School Programs (CSP) grant program serves the purpose of Section 5201 of the Elementary and Secondary Education Act of 1965 (ESEA), which seeks to expand the number of high-quality charter schools and increase national understanding of the charter school model. Developers (DEV) are one of the key recipients of Federal CSP funds.

As CSP grant recipients, DEV Grantees have to follow certain Federal and U.S. Department of Education (ED) laws and regulations, as well as adhere to the project objectives and measures the grantee outlined in their grant applications, such as assurances, competitive priorities, key program activities, grant objectives, approved budget and waiver requests. As part of this requirement, CSP is requiring the Grantees enter key grant and project information at the time of award. This baseline information will be input once, and used to benchmark additional data/reporting that is required each Spring and fall as part of the APR and school/subgrant data collection requirements.

2. Purpose

The Charter Online Management and Performance System (COMPS) is a web-based application designed to assist ED in conducting compliance and performance monitoring activities for CSP Grantees. COMPS accumulates evidence of compliance and performance from Grantees, as well as provides the ability to capture previously reported data in a more secure and efficient manner. The vision is that COMPS will:

• Streamline the collection of data relating to the CSP monitoring of Developers using COMPS.

• Provide a comprehensive performance and knowledge management platform.

• Collect grant-recipient performance data, import budget data, perform analytics, automates key document and reporting workflows, and enables two-way communication between OESE and Grantees.

The Grant Profile is the baseline and foundation module for COMPS. Grantees are required to submit baseline information at the time of their award, such as assurances, competitive priorities, key program activities, grant objectives, approved budget and waiver requests. The Grant Profile module will only be filled out once by Grantees at the start of their grant award. The information continued in the module will be used in the School/Subgrant Data Collection Module and Annual performance Reports (APR) modules, which are covered in a separate user guide.

The purpose of this document is to outline the key tasks DEV Grantees undergo to complete the required activities in COMPS upon their initial grant award, using the Grant Profile module.

3. User Access and Management

   1. Overview

The User Access and Management module allows access, through an authentication process, to the system’s landing page for approved users. The system will provide a central web portal that delivers information, based on role, to DEV organizations. The portal permits users to see only the information that is appropriate for their roles. For example, a grantee project director would only be able to see data collection information regarding their grant. Users are able to navigate to a user access management page that allows them to edit their name and email address and change their password.

2. Instructions and Screenshots

1. Grantees will enter the COMPS system for the first time with their approved email and a temporary password.

2. Grantees will be able to click on their user profile to review their basic information, as depicted below.

3. From there, Grantees can edit portions of their user profile such as their username, name, phone number and job title, as depicted below.

4. Grant Profile

   1. Overview

The Grant Profile is a module for DEV Grantees to enter baseline grantee organization and grant award information. This information is submitted by DEV Grantees once, at the beginning of the grant. Grantees are required to submit baseline information at the time of their award, such as assurances, competitive priorities, key program activities, grant objectives, approved budget and waiver requests.

2. Reporting Steps

During the post-award process, the DEV Project Director and associated staff gain access to the COMPS system. The users then enter the Grant Profile at the start of their grant award. This module is intended to only be entered once during a grant lifecycle.

1. For a new grant award, ED will enter key information for a Grantee into their Grant Profile and activate the Grantee’s profile.

2. Grantees will be notified, enter COMPS and access the Grant Profile module.

3. Grantees will view a dashboard that lists their grant award(s).

4. Grantees will click edit to fill out the application Grant Profile sections (listed below).

5. Grantees will submit the form to ED and will be unable to edit the form (they can still view it).

6. ED will review the form for accuracy and completion and either accept it, or reactivate it to return to the grantee for corrections.

7. If reactivated, the grantee will make any corrections and resubmit.

8. This data entry is expected to only occur once, at the time of an initial award.

3. Instructions and Screenshots

   1. Homepage

1. Grantees will enter COMPS and click on the Grant Profile Module.

2. Grantees will see their associated award(s).

3. Grantees will see an “active” award record.

4. Grantees will click the action button to be able to view/edit.

2. Assurances

1. Grantees first will view and certify their cohort assurances by clicking on each checkbox.

2. Please note that the text in the screenshots to the right is illustrative. Assurances will be created in the Grant Profile by ED, and the specific language is dependent on the cohort each grantee is a part of.

3. 

   1. Next, Grantees will select their competition priorities included in their application.

   2. For each selected priority, they will provide a description on how they plan to address the priority.

   3. Please note that the text in the screenshots to the right is illustrative. Competition priorities will be created in the Grant Profile by ED, and the priorities depend on the grantee’s cohort.

   Competition Priorities

4. 

   1. Next, Grantees will enter their key program activities.

   2. DEV grantees will include their enrollment projections by grade level, and approved enrollment targets by grade level and budget period.

   3. Please note that some of the fields will auto calculate.

   Key Program Activities

5. Grant Objectives

1. Next, Grantees will enter their key program activities.

2. Grantees will enter their project objectives and associated performance measures. They will be able to add as many objectives and measures as needed.

3. This information will flow to their APR module.

4. After the grant objectives are input, grantees will then select the value type (Raw Number, Ratio, Percentage).

5. The grantee will then input the goal for each of their budget periods.

6. Grantees will repeat this step for each performance measure under each project objective.

7. Grantees are also able to edit and save.

6. 

   1. On the next grant objectives page, Grantees will upload their logic, management, board policies and manual, organizational chart, closure plan and transportation plan.

   Grant Objectives – Document Uploads

If Grantees select that their closure plans have not been developed, they are prompted to explain and provide a date of closure availability.

Underneath the closure plan, Grantees will upload their transportation plan.

If Grantee select that their transportation plans are not yet developed, they are prompted to explain and provide an availability date.

Once uploaded, Grantees will be able to see/access their files.

2. After uploading, they will be prompted to enter a question if they have an approved charter.

3. If they click yes, they are prompted to add the authorizer name, address, phone and dates for the charter application.

Underneath they fill in the following information.

4. Underneath, the grantee is prompted to answer if they have a contract.

5. If they click yes, the grantee will need to upload a contract, select a management organization type, and fill in specific information.

6. If they select EMO, thy will be prompted to link to a website.

7. Grantees can enter multiple contracts and repeat the data entry steps.

7. Grant Objectives – Lottery

1. On the next grant objectives page, Grantees will upload their lottery policy.

2. If they select yes, they will be prompted to upload their plan and respond to the questions outlined on the right.

3. If they do not have a lottery plan, they will not upload a plan, but do respond to the questions outlined in the screenshot below.

8. 

   1. Next, Grantees will select whether they are claiming indirect costs.

   Approved Budget

2. If they select yes, they are prompted to indicated which statement applies.

If Grantee select the first option, they are prompted to enter the indirect cost rate, dates the agreement covers, and then approving agency.

If Grantee select the third option, they are prompted to select the applicable options from the dropdown.

If Grantee select the fourth option, they are prompted to select the applicable options from the dropdown.

9. 

   1. Next, grantees will upload their approved budget narrative and click save and continue.

   Approved Budget – Budget Narrative

2. From there, grantees will review the components of their budget and for each component, enter the appropriate budget amount for across their budget periods.

10. Waiver Requests

1. Grantees will then enter any waiver requests.

2. If they click yes, they have to describe the request.

3. If the waiver has been officially approved, grantees are required to enter the date of approval.

4. Grantees are able to add additional waivers.

11. Submit

1. Grantees will then submit their Grant Profile to ED for review.

Office of Elementary and Secondary Education – COMPS – User Guide – Release 2.0