Requirements and Expectations

What is Required to Adopt FFNC?

As a low-resource solution, FFNC leverages tools NC community colleges already use. No installation of new software is required.

Technical Requirements:

  1. Microsoft Excel
  2. Entrinsik Informer
  3. Datatel/Colleague

To ensure that FFNC serves an institution well, college administrators decide how, when, and with whom to use the tool in a way that best supports the school’s needs.

Organizational Requirements:

  1. A purpose/desired outcome for using FFNC
  2. Support from high-level leadership to encourage the relevant departments to establish a process that will make FFNC function well at your institution

Expectations for Using FFNC

All FFNC colleges in the NC Community College System should plan to participate in the project evaluation for Finish First NC. This includes periodic sharing of aggregate data about the impact of FFNC on student completions and student success, information about how using FFNC shapes school practices, and baseline data.

Wake Tech has engaged the Belk Center for Community College Leadership at North Carolina State University to conduct an independent evaluation on the project impact. Researchers will connect with FFNC users to conduct the evaluation.

Users are requested to make the appropriate points-of-contact available to FFNC project staff as needed and are encouraged to reach out to project staff as needed for successful implementation of the data tool.

What FFNC Users Can Expect

After your institution’s site visit, and during implementation, FFNC users should plan to:

  1. Send feedback and impact data to FFNC project staff periodically
  2. Participate in FFNC webinars and training sessions
  3. Request technical or implementation support from FFNC project staff as needed
  4. Improve your institution’s FFNC processes as needed

The FFNC project team is here to help you with any implementation support. We can also connect you with other users across the state from institutions similar to your own to exchange best practices.