Student Behavior Contract Template
A behaviour contract is a written agreement between a student, a teacher and usually a family: one specific behaviour, what it looks like when it happens, how it is tracked, and what follows.
It works when it is narrow and it fails when it is comprehensive. A contract naming six behaviours is a list of complaints with signatures at the bottom, and students read it as exactly that.
It also is not a punishment, and the framing matters more than any clause. A contract presented as a consequence has already lost the participation that makes it work.
Pick one behaviour, and make it countable
The target must be something two people watching the same lesson would count identically. "Being disruptive" fails that test; "calling out without raising a hand" passes it.
Frame it as the behaviour you want rather than the one you are removing. "Raises a hand and waits to be called on" gives the student something to do; "stops calling out" gives them something to stop, which is much harder to practise and impossible to praise.
Choose the behaviour that unlocks the most, not the one that annoys you most. Often a single entry-and-settle target improves everything downstream, because a lesson that starts badly is difficult to recover regardless of what the contract says about the middle of it.
The parts of the contract
The review date is the part most often left blank and the part that determines whether the contract is still alive in a month. Without one, nobody ever formally decides that it worked, and it simply stops.
| Section | What it contains |
|---|---|
| Target | One behaviour, in observable terms, phrased positively |
| Looks like | Two or three concrete examples the student helped write |
| Tracking | Who records it, how, and how often — per period is usual |
| Goal | The threshold that counts as success, starting near current performance |
| Earned | What follows success — specific, soon, and genuinely wanted |
| Review | A named date, no more than two weeks out |
| Signatures | Student, teacher, family where appropriate |
Example behaviour contract
Student: Devon R. Teacher: Ms. Okonkwo. Class: Period 2 English. Start date: March 3. Review: March 14.
Goal: Devon will raise his hand and wait to be called on before speaking during whole-class discussion.
What this looks like: hand up and quiet while waiting; if the wait is long, hand stays up rather than the comment coming out; if he forgets, one reminder is enough and the next contribution is by hand.
What this is not: Devon is not being asked to talk less. His contributions are good and the class benefits from them. This is about the order they arrive in.
Tracking: Ms. Okonkwo marks a tally on the card at the end of each period — one point for each discussion segment with no call-outs. Three segments per period, so nine points per day possible.
Goal: 7 of 9 points per day. Devon is currently averaging 4.
Earned: at 7+ for four consecutive days, Devon chooses a class job for the following week and Ms. Okonkwo calls home with the news.
If a day goes badly: the day ends and the next one starts at zero. No day carries over.
Signed: Devon R. · Ms. Okonkwo · A. Ramirez (parent).
The student names, scores and incidents in this example are invented composites. Nothing here describes a real child.
Set the first goal where the student already nearly is
The most common design error is setting the target at where you want the student to end up. A contract requiring a jump from four to nine produces failure on day one and disengagement by day three.
Start just above current performance — if they average four, the goal is five or six. Success early is what makes the contract feel like something the student can win, and a contract nobody can win is worse than none, because it teaches that trying changes nothing.
Raise the bar only after a run of success, and tell the student in advance that it will rise. A goal that moves without warning reads as the adults changing the rules, which is precisely the perception this document exists to counter.
Why contracts fade
- The tracking took too long, so it stopped being done daily and then stopped entirely.
- The reward was too distant. A week is a long time; for younger students a day is often the ceiling.
- The review date was never set, so no one ever declared it finished or extended.
- The student was not part of writing it, so it reads as something done to them.
- It named too much, giving no clear signal about what to actually do differently.
- It ran alongside no change in the classroom, leaving the student to solve a problem the room was creating.
Ending it well
A contract that works should end, and ending it deliberately is part of the design. Fade the tracking first — daily to every other day to weekly — then stop, with the student knowing why.
Mark the ending explicitly. A student who has held a target for three weeks should be told plainly that they no longer need the card and why, because otherwise the disappearance of the tracking reads as the adults losing interest.
If it did not work, say so and change something rather than extending it unchanged. Extending a failed contract is how a document intended to build agency becomes a standing record of not meeting a target — which is the opposite of what it was for.
Frequently asked questions
One observable target behaviour, concrete examples of what it looks like, who tracks it and how, a goal set just above current performance, what is earned, a review date within two weeks, and signatures.
One. A contract naming several reads as a list of complaints, gives no clear signal about what to change, and is the single most common reason these fail.
Two weeks to a review, extended or faded from there. Anything longer without a formal check-in stops being tracked, and an untracked contract has already ended.
Yes, particularly the "what this looks like" examples. A contract written entirely by adults is something done to a student; one they helped write is an agreement, and the difference shows in whether it is honoured.