ARTICLE Clipboard to Reach integration

ARTICLE Clipboard to Reach integration

Fixture data feed from Clipboard to Reach

Reach can connect and consume extra-curricular fixtures for students so that they appear as expected movements for students in Reach.

Clipboard Connection Procedure

  • School provides Reach with the API link to Clipboard (generated in Clipboard) so that Reach can connect to consume data about upcoming fixtures

  • Once connected, Reach will provide the school with a view of the data that is available for Reach to use.

Clipboard Data consumed by Reach

  • Teams - Reach creates a new student group for each team and this is populated dynamically by Clipboard on a per sync basis at whatever frequency the Clipboard to Reach sync is set. Students will move between groups according to their Clipboard team status.

  • Fixture Details - data fields that are relevant to Reach in fixture data from Clipboard are

    • Department - may be used to filter which fixtures are consumed by Reach

    • Activity type - may be used to filter which fixtures are consumed by Reach

    • Team involved

    • Opponent

    • Start date-time

    • End date-time

    • Location (eg: field)

    • Location address - GPS co-ordinates can be set for transport management

    • Location owner - may be used to identify home/away games for transport scheduling

    • Notes

What Reach does with data consumed from Clipboard

  • Student are placed in and maintained dynamically per data sync into their relevant teams

  • Team fixtures are known from the data and these create Fixture Events in Reach

  • Reach creates a Fixture sign out tile on the Kiosk SISO screen for each student to sign out to. No staff approval is required, it functions in the same way that a location sign out performs with Quickleave functionality.

  • School can require staff intervention on sign out if preferred (ie: staff required to sign students out)

  • School can assign Activity Types or Location Addresses to different sign out locations (ie: SISO to away game = Off Campus Sport, SISO to home game = On Campus Sport)

  • School can require staff intervention on return from fixture to boarding precinct (ie: staff member required for the return SISO)

  • Fixtures may be set to impact required meal counts

  • A table of fixtures is maintained by Reach which is a way to view aggregated data for any time period

  • Fixture locations can be mapped to a GPS position (like Reach locations) for display on the static Kiosk GPS Map view.

  • Fixtures can be identified as home or away and “Transport Required” lists can be generated automatically and maintained for transport scheduling.

  • Schools can use Reach K-Forms or Reach Lists to assist with managing transport lists.


Consideration for schools implementing Clipboard integration to Reach.

SISO to fixtures

When activated, Clipboard fixtures for students will appear in the student's SISO screen with a tile automatically generated for sign out.  


 

Open image-20240620-013139.png


It will not be necessary for students to create leave requests for sporting and other fixtures that Reach can gather from Clipboard.

However, we do need to implement any Sign Out controls if there are any for these fixtures. For example do students need to be signed out to Fixtures by staff or can they sign themself out? Do they need to see staff on return from fixture or can they sign themself back in?

Which fixtures?

  • Are there any types of Clipboard fixtures that you do not want to create a fixture sign out tile in Reach for?  

SISO to fixture rules

  • Is there a single sign out and return to house rule for all fixtures or will different types of fixtures require different sign out or return to house procedures? 

  • Do you want the same set of sign out and return to house rules for all students (house, year) or might student groups require different rules?

  • Is there a single Sign out location for all fixtures or will there be multiple SISO locations used for fixture types or destinations (eg: on or off campus, sport or extra-curricular).

  • Do you want fixtures visible to students in the Reach Mobile App, on Kiosk screens or BioPads or only on Staff screens?

Transport Required lists

  • Do you want Reach assistance with transport scheduling and management?

  • Do you want Reach to maintain a “Transport Required” list of students for fixtures that are off campus?

  • Do you want to use Reach k-Forms or Lists to dynamically maintain “Transport required” lists? (eg: allow students to update their own required transport status)

  • Do you want Reach assistance to manage and schedule your transport methods, assets and allocations (eg: school buses, parent transport, taxi bookings, self drive, public transport, etc)

Fixture to Approved Leave management

  • Will students be departing for Approved Leave events from Event Fixtures (eg: SISO to leave from Friday evening training, Saturday sport?)

  • Reach Confirmations can assist with this management

Rollcall results

  • Do you want rollcall status for boarding students collected in Clipboard to be consumed into the student record in Reach?