About

Why ConductKeeper exists

ConductKeeper started inside a real school’s discipline workflow: referrals on paper, follow-ups in inboxes, and positive behavior going unrecognized because celebrating it was one more manual job.

We built one system that treats discipline and PBIS as the same program — because a student’s story isn’t complete with only the referrals in it. The referral a teacher files in the hallway, the points that student earns back in class, the report the principal brings to the board: it’s all one record, and it should live in one place.

What we believe

• Behavior culture should be visible. If recognition lives in a portal nobody opens, it isn’t shaping anything. Put it on the hallway TV.
• Students should own their story. Every student can see their own record — points, badges, and referrals alike — and only their own.
• Families are part of the program. Guardian communication, consent opt-ins, and parent-friendly conduct reports are built in, not bolted on.
• Proof over promises. The results we share come from real schools measuring real outcomes. If we can’t back a claim, we don’t make it.

Who builds it

ConductKeeper is built by Myrnix LLC, a small team based in New Smyrna Beach, Florida, that answers its own support requests. When you ask a question, you’re talking to the people who write the product — questions go to an engineer, not a ticket queue.