A flat-deductible field isn’t insurance.
Real insurance contracts have co-pay, percentage coverage, a maximum, and a per-term claim cap. None of that fits into a single deductible field. Manage1to1 models the policy the way your contract reads, applies the rules in the right order when the damage report comes in, and gives the tech in front of the family a number they can trust at the moment of the incident instead of in a reconciliation spreadsheet later.
The coverage model
Four variables, all of them needed.
Insurance contracts almost never reduce to a single deductible number, and pretending they do leaves the calculation to a spreadsheet that nobody is auditing. Manage1to1 models the actual policy variables separately, so the math at incident time matches the math in the contract.
- Co-pay: fixed dollar amount the client owes regardless of the underlying cost
- Coverage percentage: the share of cost the policy absorbs (80% of the repair, for example)
- Coverage maximum: a ceiling on what the policy will absorb per incident
- Max claims per term: limit on how many times a policy can be used in a policy year, with an Unlimited option
- Admin override flag for emergency claims that need to exceed the cap, recorded with the override
Why schools choose Manage1to1
Built for K-12. Not retrofitted from enterprise IT.
Coverage variables that match the contract
Co-pay, percentage, maximum, and claim cap as four distinct fields. What you enter on the policy is what gets applied on the incident.
The math runs while you’re looking at it
The family-vs-policy-vs-district split is calculated on the incident screen before the repair starts. No after-the-fact reconciliation.
Last year’s policy is still there
Each policy carries its own policy year, so historical claims stay attached to the rules that applied at the time. New rules roll forward without disturbing prior claims.
Reminders go before the lapse
Insurance Expiry Reminders email the family on a configurable cadence ahead of the policy end date. Coverage that ends shouldn’t be a surprise.
FAQ
Common questions.
- Not directly, and after thirteen years of K-12 work we’ve found you don’t need it to. You configure your district’s insurance program in Manage1to1 with its real-world coverage rules (co-pay, coverage percentage, coverage maximum, max claims per policy term), and the platform applies those rules per incident automatically. Worth Avenue, Securranty, a self-insured pool, or any other program, the tracking workflow is the same. What changes between vendors is the policy values you enter, not the workflow.
- The platform applies coverage percentage first, caps that absorbed amount at the coverage maximum if set, then adds the co-pay to the client’s share. The result is a per-incident breakdown showing what the policy pays, what the family owes, and what (if anything) the district is left holding. The calculation log backs it up at audit.
- A limit on how many times a single policy can be used within its policy term. Once the cap is reached, the option to apply that policy to a new incident is disabled on the incident screen. An admin-override flag (per policy) lets a supervisor bypass the cap for emergencies, and the override is recorded with the supervisor, timestamp, and reason. The cap resets automatically at the policy-year boundary.
- Yes. Each policy carries a policy-year label and historical claims stay attached to the policy version that covered them. When you roll out the new year’s policy with different co-pay or coverage rules, in-flight and historical claims under the old policy are unaffected. Audit trails reflect the rules that applied at the time of the incident.
- AppleCare+ is a hybrid (extended manufacturer warranty plus accidental damage with a co-pay) attached to a specific device serial. Manage1to1 tracks it as a separate coverage type from third-party insurance, synced device by device from Apple School Manager. The status surfaces on the incident screen alongside any third-party policy, so the tech sees both sources of coverage up front. When AppleCare+ ships a replacement, the new serial syncs back into the device record automatically.
- You configure the cadence as a comma-separated list of days before the policy end date. The default is 30,7 (one month and one week out). Some districts run a fuller cadence like 60,30,14,7,1 ahead of an annual renewal cycle. Reminders go to both the assigned user and any guardian on file. When the feature is first enabled, strict-equality matching and a sent-log prevent retroactive blast emails for already-expired coverage.
See what fits your district
Stop calculating insurance in a spreadsheet.
Tell us about your insurance program: the carrier (or that you self-insure), the co-pay and percentage rules, the claim cap. We’ll reply with a quote, a migration plan, and a sample calculation against a real incident so you can see the workflow against your real numbers.
- Quote tailored to your enrollment + SLA tier
- Migration plan from your current help-desk / asset tool
- Integration map for your MDM, SIS, and payment processor
- Honest answers — our team is all former K-12, we know what the product does and doesn’t do
Prefer the shared demo first? Try it at manage1to1.com/demo.