Bulk Actions — Nikki Piccini

Designing for Compliance: Pretest Infrastructure and Bulk Action Patterns at Scale

When Texas funding legislation tied CTE school allotments to student knowledge growth, iCEV's existing testing infrastructure became a compliance-critical system overnight. I redesigned the testing administration experience and developed a scalable bulk action pattern for districts managing hundreds of teachers and thousands of students through a permanent, irreversible workflow with real financial consequences attached to every action.

$290M

annual TIA funding pool districts were competing to qualify for

90%

minimum student completion rate required for TIA funding eligibility

150+

clicks required to enable tests for 30 students in the original workflow

Client

iCEV

Year

2024

Role

UX Strategist

Deliverables

UX Strategy · Interaction Design · Bulk Action Pattern · Permissions Architecture · Edge Case Design

Legislative Context

The External Catalyst

Texas's Teacher Incentive Allotment program, updated through HB 2 and aligned TEA guidelines, created direct financial incentives for schools that could demonstrate measurable student learning growth in CTE programs. Beginning in 2025-26, districts participating in TIA are required to administer valid pretests and posttests with a standardized administration window, secure handling protocols, and a minimum 90% completion rate among eligible students. TIA funds are distributed with 90% going directly to teacher compensation at the campus level.

The scale of what's at stake is significant. TEA awarded over $290 million in TIA funds for the 2023-24 school year alone, covering nearly 25,000 designated teachers across 481 school systems. Participation was projected to grow to approximately 600 districts for 2024-25, with increased allotment amounts across all designation tiers. For CTE programs specifically, 2024-25 represented one of the first data capture years under the updated guidelines, meaning the infrastructure being used to generate that data was entering its highest-stakes testing period at exactly the moment the requirements tightened.

iCEV explicitly positions their pretest/posttest feature as a TIA qualification tool — their platform promises Texas districts they can use iCEV to qualify for Teacher Incentive Allotment funding. The districts using iCEV to do that were collectively competing for a share of that $290M annual pool. The testing infrastructure I redesigned was the mechanism through which their qualification data would be generated and validated.

Legislative Context · Texas Teacher Incentive Allotment

What Was at Stake

Texas HB 2 and updated TEA guidelines tied CTE school funding directly to demonstrable student knowledge growth, measured through valid pretest and posttest scores with a minimum 90% completion rate. iCEV's testing infrastructure became the mechanism through which districts would qualify — or fail to qualify — for their share of $290M in annual state funding.

Annual TIA Pool

$290M

awarded by TEA for the 2023-24 school year across participating districts

Designated Teachers

25K+

across 481 school systems in 2023-24, growing to ~600 districts in 2024-25

Completion Threshold

90%

of eligible students must complete both tests — districts below this lose funding eligibility

Minimum Participation

90% of eligible students must complete both the pretest and posttest. Districts falling below this threshold lose funding eligibility.

Validity & Security

Assessments must have a standardized administration window, secure handling protocols, and alignment with CTE course standards.

iCEV's Position

iCEV explicitly positioned their platform as a TIA qualification tool for Texas's 1,200+ school districts.

The Design Implication

Every unresolved edge case was a potential compliance failure with direct funding consequences attached.

Source: Texas Education Agency · Teacher Incentive Allotment Guidebook · HB 2 & HB 120 legislative updates

The Problem

150 Clicks to Enable 30 Tests

The existing pretest and posttest workflow was built for individual, manual administration. To enable a test, a user had to navigate to the pre/posttest administration page, locate a course or student in an endless scroll list, click enable inline, and confirm each individual enablement through a modal. For a teacher or admin enabling tests for a class of 30 students, that was a minimum of 150 clicks — and every single one of those clicks was permanent. Once a test was enabled, it could not be undone.

At the scale of Houston ISD, with over 200,000 students, that math becomes functionally impossible. And the 90% completion threshold attached to TIA qualification meant that every unresolved edge case — late enrollments, mid-semester drops, absences during the testing window, roster errors — wasn't just an administrative inconvenience. It was a potential compliance failure with direct funding consequences.

The edge cases were abundant and specific. What happens when a student enrolls after the testing window opens? If a student drops mid-semester with a zero-value posttest score, do they drag down the class averages that determine a teacher's TIA designation? Who has the authority to make an override decision — the admin, the teacher, or neither? What constitutes a valid exemption versus a data integrity risk? Each of these happens regularly in any district of meaningful size, and the existing workflow had no designed answer for any of them.

Lo-fi prototype showing the tedious manual test enablement workflow

The original workflow — navigate, scroll, click enable, confirm modal, repeat. A minimum of 150 clicks to enable tests for 30 students.

Designing for Compliance: Pretest Infrastructure and Bulk Action Patterns at Scale

The External Catalyst

What Was at Stake

150 Clicks to Enable 30 Tests

Two Overlapping Problems, One Coherent Pattern

Macro Bulk Actions: Testing Administration

Cascading permissions architecture

The Exemption Date Solution

How the logic works