A 311 intake flow must capture checkbox selections and handwritten regions on scanned service forms. What should extraction target?

A 311 intake flow on scanned service forms must extract checkbox selections and handwritten regions because those areas carry the resident’s actual request. Checkboxes encode categories of work; handwriting adds addresses, access notes, and free-text details that printed headers do not contain. Targeting only the table cells with checkbox layouts on the scanned municipal service forms, not whether each box is marked or what was written, captures the grid structure every form already shares and tells the system nothing about which category this particular resident actually selected. Targeting only key-value pairs for handwritten entries on the scanned municipal service forms, with no extraction of checkbox selections, misses the marked categories entirely and fails when free-form scribble has no clear keys, keeping pixels unusable for structured intake systems. Targeting only handwritten styles and checkbox labels on the scanned municipal service forms, ignoring actual mark presence and handwritten region content, misses the selections and scribble that define the service request and under-specifies the ticket. Exam caveat: municipal scanned-form intake extraction targets checkboxes and handwritten regions—not table cells with checkbox layouts, key-value pairs for handwritten entries, or handwritten styles and checkbox labels alone. Operational check: define extraction regions for checkbox groups and handwriting boxes; evaluate on real 311 scans with mixed mark styles and incomplete forms; map outputs to intake fields; confirm incomplete forms fail validation before tickets auto-create in the municipal work system. Capture mark presence versus absence explicitly for each checkbox group so unchecked municipal options are not inferred as selected during ticket creation.