Empowering organizations to move forward with data.

Data Rollup optimizes the delivery and storage of reports, empowering schools, conferences, and unions with the ability to access reports immediately in PDF format and store them digitally.

The vision for NADE DataRollup was born out of a desire to continue to empower schools/conferences division-wide to choose SIS systems that meet their unique needs while complying with state and government reporting requirements. While requirements vary state to state, a selection of reports have become standard requirements for private, denominational or parochial schools. The reports include:

  • Opening Report
  • Closing Report
  • Record of Attendance (available for inspection upon request)
  • Cumulative Student Record
  • Report Cards
  • Academy Transcripts (not official until the school/union adds the seal and watermark)

Additionally, Data Rollup optimizes the delivery and storage of reports, removing the physical Bluebook and empowering schools, conferences, and divisions the ability to access reports immediately in PDF format and store them digitally.

Key Points:

  • Schools may print report cards directly from their Student Information System (SIS) for parents.
  • As the data in the Data Rollup database is the actual legal/official data, it is imperative that Data Rollup Report Cards are verified to be accurate.
  • The NAD is only concerned about the information being archived and ensuring that ALL of the information needed for an archive is imported into the system.

The Data Rollup SIS Data Transfer Specification document is available for SIS vendors.


  1. The data imported will never be modified
    • Data Rollup is a reporting tool, period. There is no way to alter imported data. Reports are generated from imported data only (now with the exception of optional data entry for opening and closing reports)
    • Imported data is not used for ANY other purpose than to run the reports built in Data Rollup. 
    • Only PDF reports can be saved from Data Rollup. Data cannot be exported in any other format, preventing import and manipulation of data in a third party application.
  2. Ensure that access to data is authorized based on student, teacher, school relationships
    • Imported data controls access based on a simple, effective dependency schema. In other words, if I am a teacher I am only able to see data from students associated to my classrooms. If I am a principal, I am only able to see data from students, whose teachers belong to my school. And, if I am a superintendent, I can only see data from students, who’s teacher belongs to a school that is in my conference.
    • Authorization to run reports is determined by Union Directors. Authorization to run a particular report, while governed by Union Directors, is managed by the User Manager, which is a separate NAD application. Users are assigned roles, typically based on employment. These roles provide access to specific set of reports.
    • Access to Data Rollup tool (authentication) is controlled by Conference Superintendents
    • Entrance to the Data Rollup tool is only gained by logging into the NAD Toolbox. This access is controlled by Conference Superintendents, who actively manage those users who are employed by the conference represented. At any time, a superintendent can remove access to reports by disabling a users account, ensuring data is secure in the instance a teacher may be terminated.

While the initial desire was focused on compliance with state requirements, the benefits of access to standardized reports for teachers, principals, conference superintendents, and union directors was obvious—immediate access to appropriately authorized data to assist in health and safety, student assessment and human resources. The application is built to honor pre-established rules of access to data in a digital world.


The User Manager hosts the user information. NAD Employee ID numbers are generated here and permissions are assigned.

The Student ID Manager provides the means for obtaining and tracking your Student IDs.

Data Rollup is the NAD reporting system used to create various reports such as Opening and Closing Reports, Report Cards, Cum Record Report, Education Directory, etc. It is tied directly into several SIS vendors and appplications including: Jupiter, RenWeb, eAdventist, and eCertification.

The Secure File area gives access to webinar archives, resource discount information, textbook order forms, and any other kind of information that is specifically negotiated or designated for our Adventist educators and students.

The eCertification app is the portal for certified educators to access their full status sheet – listing their certifications, endorsements, expirations, and recertification requirements.

  • Data Rollup/SIS Support Protocols for Schools
  1. Schools refer to the support information available to them to resolve errors and questions.
  2. If further assistance is needed, schools contact the Conference.
  3. Conferences may reach out directly to NADE Technology Support for assistance on behalf of school and conference questions/errors.

Dashboard User Guides

These are a great resource to help with Data Rollup, Educator and Student ID numbers, error solving, and much more.

Troubleshooting Versions of Reports
Major reports (Opening/Closing, etc.) have built-in troubleshooting versions of the report found on the report landing page in Data Rollup.  Please access the report in this way first to resolve any discrepancies in the report. Support Tickets should be submitted right from the Troubleshooting Version if you need help. Tickets are routed to the Conference.

Helpful Links


  • Jupiter
  • RenWeb


  1. Meet with NADOE Director of Technology & Support for an overview of Data Rollup.
  2. Review the Data Rollup SIS Data Transfer Specification document.
  3. Commit to a pilot program for at least one year with a minimum of three NAD SDA schools of various types and sizes.
  4. Commit to support our NAD SDA schools with customer support and programming for Data Rollup compatibility
  5. Update SIS when needed – in a timely fashion. (Updates are made in the specification document and SIS vendors notified.)