Print Icon
 

You have received this because you are in Boarding


You may unsubscribe at the bottom of the page

These are some of the questions we get asked..

When we go to schools we ask if we can have the Director of Boarding, Director of IT and where possible the College Business Manager all in the same room.


This is what they ask...

  • We use "Database A" at school we don't want another database how can you connect to our system?

Our Response "In order to facilitate data exchange between REACH and your school’s database our preferred method is to access your school’s data via a Web Service or other dedicated API that has been provided by your school’s database software provider." READ MORE


  • With changes in the Privacy Act this year and your system being browser based, where is our data stored?

Our Response "The REACH Privacy Policy document was last updated on 4th April 2014. You can view and download the most recent version of the REACH Personal Data Privacy Policy here http://reachboarding.com/privacy

The REACH school administrator will always be alerted and provide the most recent revised copy of this document as the document is updated." READ MORE


  • Our Boarding Campus has several houses with each housemaster/mother responsible for their own house, can REACH accommodate all this or do we need multiple systems?

Our Response "REACH has been designed by those in boarding so we can take care of a single house system or multiple. As each user has a unique ID, a simple filter on your view allows you to see your students each and every time you login." WANT TO SEE HOW


  • This all looks great but what's the cost, why can't we just keep using what we have? (Love the Business Manager's)

Our Response "REACH has always been about inclusive not exclusive, this is why REACH is priced per boarder, we have schools with less than 50 boarders to more than 600 boarders, all saying the time they save, the efficiency of the system, knowing where their students are, has proven how valuable REACH is to them.  Just like you they all started with the free trial request and within a Term were on the system as a client school. Our unique Kitchen Widget keeps track of your catering requirements, every student that goes on approved leave reduces your meal count by one. Over 40,000 meal notifications through REACH ensures a quick return in investment." WANT TO SEE HOW

Signing out for Approved Leave

ABSA Annual 2014 Conference

See you there!!

At REACH we love to have a chat with our schools once they have had an opportunity to use REACH with their own data, it is great to hear how they are all going and most of all their feedback and recommendations!


If you haven't already heard any of our Podcasts take a look at our Blog Page or subscribe to our iTunes Podcast account.




Weekly Updates - Bugs/Fixes and a whole lot more

Change Log

Version 2.53 - 2014-05-11 - Happy Mothers Day!

  • Added Identifiers to Staff Details
  • Minor database clean up
  • Removed Boarder PIN validation check as it's no longer needed
  • Combined several SISO methods into a single workflow for better long term maintainability
  • Completely rebuilt the SISO process to improve peak load performance. This includes:
    • All Dashboards operate off of the same application page to prevent multiple page load calls
    • Metrics View:
      • Overview Graph is loaded from cached data
      • Meal Widget is loaded from live data
      • RLL is loaded from live data
      • Your Boarders Lists is loaded from cached data
      • Leave Request Summaries have been removed for now due to unresolved bugs
      • News is loaded from live data
    • Airport View:
      • Arrivals and Departures are loaded from cached data
      • Certain events will now force a cache update in the background
      • Arrival and Departure dialogs use buffering to allow for instant state updates
      • Bulk Location Changes use buffering
    • Kiosk View:
      • Boarder List is loaded from cached data
      • SISO Dialog is now apart of the Dashboard to prevent additional loading of a frequently used dialog
      • Locations are loaded from cached data
      • Location updates use buffering
      • Leave Request for SISO is loaded from cached data
      • Leave Request SISO uses buffering
      • PIN dialogs use cached data
      • PIN dialogs now support Mifare card scanning for PIN Identification
      • Mifare card scanning data is loaded from cached data
      • Staff Boarder Override PIN works for Boarder context only now
  • Filters are not working as yet (Your Boarders List and Kiosk View) though we anticipate this to be a rather quick fix

We thank you for your feedback and support. Best Practice is our goal for all our schools