3
Warning: Cannot modify header information - headers already sent by (output started at /homepages/28/d670503062/htdocs/letsbeinventive/wp-config.php:1) in /homepages/28/d670503062/htdocs/letsbeinventive/wp-includes/rest-api/class-wp-rest-server.php on line 1768
Warning: Cannot modify header information - headers already sent by (output started at /homepages/28/d670503062/htdocs/letsbeinventive/wp-config.php:1) in /homepages/28/d670503062/htdocs/letsbeinventive/wp-includes/rest-api/class-wp-rest-server.php on line 1768
Warning: Cannot modify header information - headers already sent by (output started at /homepages/28/d670503062/htdocs/letsbeinventive/wp-config.php:1) in /homepages/28/d670503062/htdocs/letsbeinventive/wp-includes/rest-api/class-wp-rest-server.php on line 1768
Warning: Cannot modify header information - headers already sent by (output started at /homepages/28/d670503062/htdocs/letsbeinventive/wp-config.php:1) in /homepages/28/d670503062/htdocs/letsbeinventive/wp-includes/rest-api/class-wp-rest-server.php on line 1768
Warning: Cannot modify header information - headers already sent by (output started at /homepages/28/d670503062/htdocs/letsbeinventive/wp-config.php:1) in /homepages/28/d670503062/htdocs/letsbeinventive/wp-includes/rest-api/class-wp-rest-server.php on line 1768
Warning: Cannot modify header information - headers already sent by (output started at /homepages/28/d670503062/htdocs/letsbeinventive/wp-config.php:1) in /homepages/28/d670503062/htdocs/letsbeinventive/wp-includes/rest-api/class-wp-rest-server.php on line 1768
Warning: Cannot modify header information - headers already sent by (output started at /homepages/28/d670503062/htdocs/letsbeinventive/wp-config.php:1) in /homepages/28/d670503062/htdocs/letsbeinventive/wp-includes/rest-api/class-wp-rest-server.php on line 1768
Warning: Cannot modify header information - headers already sent by (output started at /homepages/28/d670503062/htdocs/letsbeinventive/wp-config.php:1) in /homepages/28/d670503062/htdocs/letsbeinventive/wp-includes/rest-api/class-wp-rest-server.php on line 1768
{"id":122,"date":"2015-05-10T13:49:17","date_gmt":"2015-05-10T12:49:17","guid":{"rendered":"http:\/\/www.letsbeinventive.co.uk\/?page_id=122"},"modified":"2016-04-05T16:37:25","modified_gmt":"2016-04-05T15:37:25","slug":"pupil-tracker","status":"publish","type":"page","link":"http:\/\/www.letsbeinventive.co.uk\/other-projects\/pupil-tracker\/","title":{"rendered":"Pupil Tracker"},"content":{"rendered":"
<\/p>\n
Features:<\/strong><\/p>\n One of the problems with schools is the sharing of information. In my role as a form tutor and a classroom teacher, one of my biggest frustrations was that I only had about 50% of the information about the child sat in front of me. I could easily access their academic grades, their attendance, and their behaviour record.<\/span><\/p>\n This didn’t help me to find out if a vulnerable child was receiving any mentoring. On a wider school level, it wasn’t easy for SLT to collate statists about student uptake and statistics of extra-curricular activities and interventions. Heads of department didn’t have a coherent overview of booster and intervention sessions that their staff were working hard to deliver.<\/span><\/p>\n With this in mind, I started developing the ‘Student Tracker’.<\/span><\/p>\n\n\t\t\n
\nSome of the information is available to staff members, some of the time.<\/span><\/p>\n
\nIt didn’t help me to find out if a student who was struggling reading exam questions was getting any extra help in English.
\nI had lost count of the amount of times I had meetings with parents and I couldn’t tell them if their child was attending booster sessions\u00a0or extra-curricular activities.<\/span><\/p>\n