Shared Tablets in a Music Department: The Handback Checklist

A shared tablet can finish one lesson with a score open, headphones connected and a recording still uploading. The next learner needs a usable starting point without access to the previous learner’s account or files. That changeover deserves a written routine, just as the room’s keys and instruments do.

First, establish what “shared” means on this tablet

A normal iPad passed between students is different from Apple’s Shared iPad deployment. The latter requires supervision and a device-management service; named-user access uses organisation-issued Managed Apple Accounts. Ask IT which setup is actually in use before writing instructions for staff. Apple’s Shared iPad overview describes the requirements.

Managed Shared iPads can also offer a temporary Guest session. Ending that device session deletes its local data and browsing history. Confirm that required work has finished uploading before guest logout. Unsaved work is not waiting for the student when they return. Apple also warns that a temporary session can be accessed without a password while it is active, so it should not be left unattended with a learner signed into a website.

For an ordinary shared tablet, have the administrator specify the browser, permitted accounts and local-data cleanup. A restricted screen is not enough: Guided Access limits an iPad to one app, but does not create separate learner accounts inside that app.

These four places need separate attention. Checking one does not tell you the state of the others.

App session

Who is signed in to the practice tool, score reader or recorder? Use that service’s sign-out.

Browser

What remains in other tabs, saved passwords and website storage? Follow the approved browser cleanup.

Files

Are there exported PDFs, recordings or photos outside the app? Check the agreed local save locations.

Device user

Is this a managed learner or Guest session? Finish the correct device-level logout where one exists.

For our own platform, Practis sign-out ends the app session; it is not a device-cleanup command. Our check of the deployed sign-out implementation confirmed that it does not remove arbitrary local drafts or downloaded files. Pair it with your approved browser and device procedure. For decisions about who should have access in the first place, use the separate practice-data and student-privacy checklist.

Prepare the microphone, files and physical setup

Give each tablet an asset label and an agreed start page. Keep the instructions beside the charging station, with a staff contact for failures. Do not put a shared student password on that sheet. A department planning its wider workflow can discuss account needs through Practis for institutions; device administration still needs its own plan.

Check the microphone using a short, non-sensitive test. Browser permission and device restrictions can both affect access. In Safari on iPad, Apple documents Settings → Apps → Safari → Microphone; individual websites also have settings through Safari’s page menu. Use the department’s chosen permission policy instead of broadly allowing every website. See Apple’s Safari privacy and permission controls.

On an Android tablet using Chrome, start at Chrome → Settings → Site settings, or open the current site’s information and permissions. Google’s permission instructions describe the available controls. If a restriction comes from device management, ask the administrator; do not work around it with another account or browser.

Then check the actual lesson task. A microphone permission does not prove that the app can hear the intended instrument. Headphones, connected accessories, room noise and input selection may still matter. The note-detection troubleshooting steps help separate an input problem from a playing problem.

Use a stable stand with charging and headphone cables clear of the keyboard, pedals and walking route. Lower playback volume before a learner puts headphones on, then let them adjust it comfortably. Check text size, zoom and other accessibility settings with the learner. A standard starting setup should leave room for individual needs.

Finally, agree where finished work belongs. Staff should be able to distinguish a submitted recording from a local-only copy. Avoid collecting lesson files in a personal Apple or Google account that remains signed in for everyone.

Leave time for these six checks

Use the sheet below as a starting point, then fill in the exact cleanup and save locations approved for your devices. It is a normal changeover checklist, not a factory-reset procedure.

1. Save and verify. Finish the practice session or recording and confirm the expected work has reached its destination. A filename appearing in a local list does not establish that an upload completed. Allow extra time when Wi-Fi is unreliable.
2. Stop capture. End recording or microphone-following activity. Check the device’s microphone and camera indicators before closing the tool.
3. End the account session. Use the app or website’s sign-out, then close other signed-in lesson tabs. Decline prompts to save personal passwords on the shared tablet.
4. Run the approved cleanup. Follow the department’s browser or device-user instructions. Handle downloads, photos and any recovery folders separately. Staff should know which files are disposable local copies before deleting them.
5. Check the starting state. Reopen the agreed start page. The previous learner’s account and files must not be available to the next person. If they are, keep the tablet with staff.
6. Prepare the next lesson. Return volume to the agreed starting level, check the next learner’s accessibility needs, and reconnect charging where appropriate. Inspect the stand and cables; clean equipment only as its makers permit.

Be especially careful in the iPad Files app. Deleting an iCloud Drive file can delete it on other devices using that account. Deleted files normally remain in Recently Deleted for 30 days; deleting them there is permanent. Remove Download keeps the cloud copy, but it does not remove access through a still-signed-in cloud account. Apple explains these different file actions.

For a managed temporary Guest session, device logout handles the guest’s local data, but the save check still comes first. Apple’s Shared iPad security guidance explains why temporary-session work cannot rely on background syncing after logout.

Try the procedure with dummy work before students use it

Use two staff-approved test accounts and an unimportant PDF or recording. Do not borrow student logins for the trial. Have one staff member follow the written instructions while another observes where a decision or missing step causes hesitation.

Repeat after a browser, app or device-management change that affects the routine. Keep a short record of the device, date, person checking and unresolved issue, without student passwords or sensitive lesson notes.

A substitute teacher should also be able to carry out the procedure. Add the approved handback sheet and support contact to the department’s teaching handover materials, then run the first real changeover with staff present.