This week's permit-sandbox labs failed because two workstations lacked the city's GIS plug-in. How should the instructor use that evaluation result?
Select an answer to reveal the explanation.
Short Explanation
Lab notes are not a souvenir — they are next week's packing list. If the GIS plug-in was missing, put a check for it on the setup sheet before the next offering. Filing, blaming, or dumping labs does not close the loop.
Full Explanation
When this week’s permit-sandbox labs failed because two workstations lacked the city’s GIS plug-in, the instructor should change next week’s setup checklist so the GIS plug-in is verified before class starts. Evaluation results that identify preventable environment gaps should drive preparation improvements for the next municipal offering. Filing the notes but keeping the same checklist "for consistency" fails continuous improvement; consistency with a broken setup is not a virtue. Blaming the IT help desk in learner survey comments while leaving the checklist unchanged fails to convert evaluation into action the instructor controls. Canceling all future labs to lecture from slides forever fails the skill objective that required sandbox practice. Exam caveat: turn environment failures into checklist controls before the next class. Operational check: add a GIS plug-in verification line with owner and timestamp to the setup checklist, test two spare machines, confirm plug-ins load before learners arrive next week, and document that labs then support the permit objective. Keep the published objective visible on every rubric and report so raters do not drift into convenience metrics. Retain scored artifacts with the course file per city retention rules and brief only stakeholders with a need to know.