Checklist Protocol for Safe AV Route Testing Near Schools in Punggol

Digital opportunity (v4): School Zone AV Testing Safety Checklist Target users: AV testing teams, safety officers, and local transport authorities responsible for overseeing autonomous vehicle operations near schools in Punggol or similar urban areas. How it would work: Develop a paper or digital checklist for AV route testing teams to complete before and during tests near schools. The checklist would cover time-of-day restrictions, school schedules, pedestrian crossing monitoring, emergency stop procedures, and communication with local authorities. Teams would use the checklist to document compliance and flag any incidents or near misses. First version: First version: A printed checklist template (A4 sheet) distributed to AV testing teams operating in Punggol, with fields for date, time, location, school proximity, pre-test safety checks, and incident reporting. The trial would involve one AV operator and one supervisor over a two-week period on routes passing within 500m of a school. Alternatives to investigate: Review existing AV safety protocols from other cities or companies, and compare with local LTA guidelines. Investigate if digital logging or real-time monitoring tools are already in use for similar purposes. Difference to test: Test whether the checklist increases the rate of documented pre-test safety checks and reduces unreported near misses compared to previous practice (baseline: no formal checklist). Source evidence of a capability or need: The Land Transport Authority said the vehicle involved was testing a new route in preparation for Grab's enhanced on-demand travel service in Punggol. Possible uses and limits: There is a clear need for improved safety protocols during AV testing near schools, as highlighted by the recent near miss. The checklist offers a practical, low-cost way to address this gap, but actual adoption and effectiveness must be tested. Potential users and optional payers: Unverified analysis, not established facts; confirm before acting. No established paying customer; this is a non-commercial safety tool for community and operator benefit. Competitors and alternatives to check: Unverified analysis, not established facts; confirm before acting. Alternatives may include existing digital AV safety protocols, LTA guidelines, or proprietary company checklists. These should be reviewed for overlap and gaps. Optional legal business model: Proposed hypothesis; revenue may never occur. No monetization required; this is a community safety protocol. No commercial hypothesis established. Skills and time to test: Skills: AV operations, basic safety training, checklist design. Time: 1 day to draft checklist, 2 hours for operator training, 2 weeks for pilot. Geographic availability and limits: Unverified analysis, not established facts; confirm before acting. Punggol, as reported in the source. Actual AV testing locations and school proximity must be verified locally. Legal and platform constraints to verify: Unverified analysis, not established facts; confirm before acting. Local privacy, transport safety, and data handling rules must be checked. No legal advice given; compliance with LTA and school policies required. Current prices and platform terms: Unverified analysis, not established facts; confirm before acting. Printing and training costs are unknown/not checked. No pricing or commercial terms reported. Age, payments and eligibility checks: MLAIEL requires age 16 or older; external eligibility and payments are unverified. MLAIEL minimum user age is 16. No external payments or age restrictions apply; external service requirements unverified. Smallest low-cost validation test: Draft and use the checklist for one week with one AV operator on a single school-adjacent route, then review compliance and operator feedback. Human responsibilities: AV operators and supervisors complete the checklist before and during each test run; supervisors review and collect completed checklists for compliance and incident analysis. AI contribution and limits: No AI required for the checklist itself; optional: future analysis of incident data for trends if digital logs are used. For this version, AI is not needed. Data and access needed: Access to AV test schedules, school locations and times, and incident/near miss reports. Consent from AV operators and relevant authorities to collect and review checklist data. Source-supported setting and capacity: The Land Transport Authority said the vehicle involved was testing a new route in preparation for Grab's enhanced on-demand travel service in Punggol. Ordered steps and owners: 1. Draft checklist with input from AV operators and local authorities. 2. Print and distribute to AV teams. 3. Train operators on use. 4. Collect completed checklists after each test run. 5. Review compliance and incident data after two weeks. Minimum resources and dependencies: Existing AV operator teams, printed paper, pens, and access to AV test schedules and school location data. Supervisor time for training and review. Costs and affordability unknowns: Actual costs for printing, training, and supervision are unknown and require local quotes; no reported amounts. How a newcomer can help: AV operators fill out checklists (5 minutes per run); supervisors collect and review (30 minutes per week). A beginner could assist with checklist distribution and collection under supervision. Pilot and success criteria: Proposed pilot target: At least 90% of AV test runs near schools have a completed checklist over two weeks (baseline: 0%). Measure compliance by counting completed checklists vs. total eligible test runs. Assess for any reported incidents or near misses during the period. Risks and safeguards: Operator non-compliance, checklist fatigue, incomplete or inaccurate reporting, and potential for checklist to be seen as a bureaucratic burden. Legal or privacy issues if incident data is sensitive. When to stop or change direction: If fewer than 50% of eligible test runs use the checklist, or if a serious incident occurs during the pilot, pause and review the protocol.