School-bus review

School-bus review

Then test the whole path. Check the phone, the service, each saved copy, and every person who can open it. Make a missing signal visible so silence is not mistaken for safety.

Write the promise in words a family can check. “Show the bus within ten minutes of this stop” is clearer than “improve travel.” It limits both the place and the time. Let the family see when sharing is on. Let them remove an old record without hunting through several screens.

Run the test with a child, a driver, a parent, and a support worker. Give each role only the view needed for its task. Try a late bus, a lost phone, and an account used by the wrong person. The result should protect people even when the day does not go to plan.

Keep a short review card beside the feature. It should state the job, people, place detail, start time, stop time, saved copies, and help route. A new team member can then see why each fact exists. If no one can explain a field, remove it from the plan.

Check the card when the service adds a map, report, partner, or new use. Ask the same family question again: would a reasonable person expect this? Give notice before the change, not after. Keep the old choice until the person makes a new one.

At the end of the bus trip, verify that live sharing stopped. At the end of the saved period, verify that old records are gone from the main service and its planned copies. Record the check so the promise is more than text on a screen.

Use five short questions during review. What job needs the place? Who needs to see it? How much detail is enough? When should sharing stop? What can the person do?

Answer with a real case. The bus alert needs a route area. It may need the next stop. It does not need every shop passed on the way. The driver needs traffic guidance. A parent needs the arrival window. A school worker may need a late-bus warning. Those are different views.

Now test control. Turn sharing on. Check the visible sign. Pause it. Check that new facts stop. Start it again. End the trip. Check that live access closes. Ask a support worker to repeat these steps.

Test an error next. Give the phone a wrong time. Remove its network link. Move it outside the route. Let its battery die. The screen must show doubt. It must not show an old place as current. Help must stay reachable.

Finally, inspect the record. Use a random trip name. Follow it through each planned store and copy. Check each access role. Remove the trip. Confirm the stated end state. Record any copy that needs more time and why.

These checks keep the design tied to a human promise. They also expose broad collection early. If the alert still works without an exact point, use less detail. If an old copy has no job, do not keep it. If a new partner needs data, run the review again before sharing.

Back to the chapter