Trackers
Broad Goals
We worked with the following goals
- There should be minimal overhead for a teacher to report their work. Where possible derive data from other sources and reduce the work required from the teacher.
- Privacy of the data is very important. Visibility of the data and who approves what data has to reflect the roles within each project.
- Consolidated view of the data should reflect the progress against the goals of the project and will have to vary for each projects.
- Recognise and eliminate errors as early as possible. Common errors like duplicate reporting, reporting for a wrong school accidentally etc. Should all be caught and teachers warned before the data is submitted.
Good output tracking can enable informed choices in term of managing the programs. Further this also helps communicate clearly what is the default activity that the teacher is expected to do in the school on any given day. While we provide the flexibility for the teacher to alter what they do, it is important that they think about and understand what the default expectations are.
Explore and ACE
Amazon required us to report on the number of sessions done each month and therefore these two became the first projects where we started gathering the data. In the case of Explore, trainers report what activity they conducted for each session they did at the schools on each day. From this data we provide a dashboard that displays a summary of these session by activities or by weeks and teachers. The first display will help us understand which activities are more popular among the teachers and students. The second one will help us see how the program is progressing over the course of the year.
In the case of ACE, the government teachers report what session they did for their class for each session (which is typically once a week) and the Asha trainers also report when they visit a school to assist the government teacher. The dashboard for this display the progress of the sessions which will help us see if all the lessons are being taken and in order, where the Asha teachers visit occurred, if a lesson was taken out of order or repeated etc. We can also see the progress of the sessions by week which will help us spot schools that are lagging behind.
Computer Teachers
Our computer teachers visit primary and middle schools and teach all classes. Further they teach the CS curriculum for classes 1 to 8 as well as Maths, English and other subjects through a curated set of activities which build conceptual clarity. The CS curriculum has a sequence and therefore resembles the ACE reporting and the subject activities resembles the Explore reporting as these are a discrete set of activities that teachers choose from for each class.
Our computer teachers also do content work towards various lesson plans, mapping packages to the curriculum etc. These are being reported by not to the extent of tracking the progress in these works. We will eventually expand these trackers as well.
RTC, KaradiPath and Regular Teachers
At the RTC we are taking a slightly different route. The reporting at the school will be similar to ACE or the CS curriculum part of the Computer Teachers. However at the RTCs, each day students taking many different courses come at varying times. Therefore we felt it would be best for students to submit details at the end of each session on what course-lesson they did on that day and for how long.
KaradiPath teachers will report which session number in the KaradiPath curriculum they did for which batch of students. Regular teachers will also report which lesson they are teaching to which class for each period in the school timetable.
All these trackers are still being developed.
