K–12 EdTechB2B/Enterprise SaaS

Reducing risk during the highest-volume week in staff contracting

I helped districts move staff contracts off paper by designing contracts that hold every assignment a teacher has, and a safe way to send them.

  • Form design
  • Research synthesis
  • Information architecture
  • Product strategy
Contract Groups settings that send assignments combined in one document or as separate contracts, with a preview of the result.

The 30-second version

Problem

Districts couldn’t take their contracts off paper

Contracts held only one additional assignment, so districts with more built extra templates or mapped their own PDFs. They’d been asking for a fix since launch, and it had to ship before the next contracting season.

What I did

Built contracts around how districts actually write them

Analyzed 38 real contracts and found three assignment types that covered nearly everything. Designed a structured assignment table and a Contract Groups send flow with a live preview.

Outcome

34% more adoption, beating the 20% target

Support tickets about contract forms dropped 27% within six months, also past the 20% target set before the project.

01

Context

School districts issue contracts to their staff every year, and more of them were moving that process into Frontline Central. A single teacher’s agreement can cover a primary role, ongoing additional duties and supplemental assignments, each paid differently.

The Form Builder allowed only one additional assignment per contract. Districts with more built extra templates or mapped their own PDFs to work around it. They had been asking for better contract support since the product launched, and without it they couldn’t move their paper process online. The work had to ship before the next contracting season.

Role
Product Designer
Worked with
2 product managers, 1 engineering team
Research
38 real district contracts, existing customer research, post-launch feedback
Scope
Research synthesis, interface design, interaction design
02

Supporting multiple assignments

Earlier design decisions rested on assumptions about how districts structured their agreements. I analyzed 38 real contracts from districts across nine states, written in about 20 different template formats. Terminology and formatting varied, but three assignment types covered nearly everything: primary, secondary and supplemental. That let the product handle real-world complexity without encoding state-specific language.

Miro board of real district contracts grouped into contracts with tables and contracts with rich text, each assignment tagged P, S or Sup.
My Miro board: real district contracts grouped by layout, with each assignment tagged primary (P), secondary (S) or supplemental (Sup).

I sorted the assignments by how each one is paid, not by what districts called it. The same label could mean different things: Tulsa used “extra duty assignment” for both a year-round duty and a one-time summer stipend.

District terms from 9 states, such as permanent position, extra duty and stipend, grouped and mapped to three assignment types by how they are paid: primary (salary), secondary (paid throughout the year) and supplemental (paid once or split).
District labels mapped to three assignment types by how each is paid.

Product had planned to build this into the rich text editor with tokenized data. My wireframes showed it would put the burden of formatting on administrators, and engineering flagged the cost of customizing the editor, so I made the case for a structured table built on Form Builder patterns administrators already knew.

The redesigned form builder: a contract template with Primary assignment, Secondary assignments and Supplementals blocks, each filled from the employee record.
The redesigned form builder: primary, secondary and supplemental assignments as structured blocks.
03

A new decision at send

Supporting multiple assignments in one contract raised a question the product had never had to ask: should those assignments go out as one consolidated contract or as separate ones? The answer depends on state regulation and district policy, and errors at that stage are hard to reverse. A mistake could reach hundreds of employees at once.

I designed Contract Groups to make that decision explicit at the moment of sending. It asks two questions: who receives the contract, and how each assignment should be issued. Defaults guide administrators toward common patterns, and a live preview shows the resulting contract before it goes out. It uses the same three assignment types as creation, so the riskiest step builds on work administrators have already done.

Contract Groups send screen: recipients chosen by contract group, a Combined or Separate contract format, a choice per assignment type, and a preview of the resulting contracts.
Contract Groups: a choice for each assignment type, with a live preview of the resulting contract before sending.
04

Results & learnings

Within six months of release, adoption rose 34% and support tickets about contract forms dropped 27%, beating the 20% targets set before the project began.

The lesson I took is that adding a capability can also add a decision. Supporting multiple assignments was the request, and designing for what it changed at send is what made it safe to use.

Next case study · 02 Cutting support tickets by 90% for a mandatory account migration Read next