Define the task the public station serves
Imagine a village office providing a public computer where visitors can find published municipal information and download a blank form. The first visitor finishes, and the next person sits down. Staff should know how that new visit begins, what happens to the previous session, and who handles a station that fails to return to its intended starting state.
For Michigan township, village, and city teams, choose one public-facing station to review with its office owner and IT provider. List the permitted tasks, websites, downloads, and printing needs. Identify the staff contact who helps visitors and a covering employee for absences. Agree on the expected start screen and the process staff use when the station needs technical attention.
Have IT identify the actual public configuration
For a Windows station, Microsoft documents Assigned Access as a way to configure a kiosk or restricted user experience. Microsoft Edge also has dedicated kiosk experiences. Ask IT to identify the Windows configuration, browser mode, and account actually used by visitors. Have the technical team confirm which features are available for that device and its approved setup.
Have IT demonstrate what the visitor can open and how the station keeps staff accounts, applications, and working folders within their approved access arrangements. Compare that demonstration with the station's permitted tasks. Include the actual public websites and any approved printing or download step. Record unexpected navigation or account prompts so IT can resolve them before the office accepts the configuration.
Agree on session completion and file handling
Give visitors a clear completion instruction that matches the configured station. Have IT demonstrate the supported way to end a visit and explain the resulting browser and Windows behavior. Agree with the office owner how downloaded files and any printing should be handled. Put those expected outcomes in the review record so staff have a concrete result to check.
Microsoft's general Edge InPrivate guidance says downloads and favorites can still be saved. Its kiosk documentation describes additional configuration for deleting downloads when a kiosk instance closes. Have IT verify the effective file handling on this station alongside the browser-session behavior. Include approved download locations and any connected printer in the review, with the responsible provider checking their actual configuration.
Rehearse two visits with sample information
Schedule a planned check using an approved training page, harmless sample information, and a clearly identified test download. Have a staff member follow the first visitor's permitted workflow and end the session using the agreed instruction. Let IT direct the configuration and file checks. Keep the expected handling of the sample page, browser state, and test file visible in the test record.
Then have another staff member approach the station as the next visitor. Confirm the intended start screen and repeat an approved public task. Check the first test session's information and downloaded file against the outcomes agreed with IT. Document what was observed and any difference. Use those findings with IT's configuration and security review when deciding whether the station is ready for public use.
Test idle and interrupted-visit recovery
A visitor may leave without completing the normal end step. Agree with the office owner and IT how the station should handle inactivity and an interrupted visit. Microsoft's Edge kiosk guidance notes that its idle-timeout option closes the browser and that automatic restart needs a separate arrangement such as Assigned Access. Have IT demonstrate the actual return path on the configured device.
Rehearse the approved inactivity test with sample information and verify the next visitor's starting state. Include the office's planned response to a closed browser, restart, or other interruption that IT considers relevant. Confirm who notices an unusable station and which approved assistance staff can offer while it is reviewed. Record any recovery gap with an owner and a next action.
Keep the verified setup useful to staff
Keep a short operating note near the staff support process: the station's purpose, start screen, completion instruction, expected reset behavior, and known IT contact. Have the office owner decide who can authorize continued public use when a check fails. Staff need an agreed response and a way to report the problem through the municipality's established process.
Repeat the relevant sample checks after a browser or Windows configuration change, a new permitted website, or a change to download and printing arrangements. Close a support issue by verifying both the permitted visitor task and the return to the agreed starting state. Update the staff note and keep any unresolved limitation visible to the office owner and IT provider.
Keep this checklist with the station record
Review one public-facing computer with the office owner, supporting staff, and IT provider.
- Permitted tasks, public account, start screen, and staff contact.
- Verified Windows and browser configuration for the actual device.
- Session completion, download handling, and printing expectations.
- Two sample visits checked against the approved outcomes.
- Inactivity and interruption recovery demonstrated by IT.
- Assigned corrections, public-use decision, and updated staff instructions.
YOUR NEXT STEP
Review a public computer as a sequence of visitor sessions. Confirm the permitted task, session completion, file handling, and recovery behavior with IT, then use harmless sample visits to check the agreed outcomes.
Need a hand putting a plan in place? Explore our Managed IT services for Michigan municipalities or talk with our team.
