Ontario POA case management: what your software actually needs to handle
Provincial Offences Act work has a specific shape: offence sections, set fines, demerit and CVOR points, disclosure and dispositions. Here is what software must model.
Provincial offence work looks simple from the outside. A client gets a ticket, you act on it, the matter resolves. In practice it has a specific structure that general-purpose legal software does not anticipate, and the gap between that structure and a generic matter record is where paralegal offices lose hours every week.
This article walks through what that structure is, so you can tell whether a system genuinely handles it.
Offences are data, not descriptions
The single biggest difference between software that understands this work and software that does not is whether an offence is a structured record or a sentence someone typed.
A properly modelled offence carries:
- The section of the Act or regulation it falls under
- The standard wording, so charge descriptions are consistent across your office
- The set fine, which you should not be looking up separately
- Demerit points, where they apply
- CVOR points, tracked separately, because commercial clients care about these specifically
- A suggested fee, so quoting is consistent between staff
When these are structured, quoting a new client takes seconds and is consistent regardless of who answers the phone. When they are free text, every member of staff keeps their own reference sheet, and those sheets drift out of date.
Victim fine surcharge should be calculated
The victim fine surcharge is a statutory addition that follows from the fine amount according to a defined scale. It is exactly the sort of thing software should compute and humans should not.
If a system expects you to type the surcharge in, that is a small but reliable source of error, and it compounds across every quote and every disposition letter your office produces.
Courts, prosecutors and officers are entities
Across a year your office deals with the same courts, the same prosecutors and many of the same officers repeatedly. These should be records you select, not names you retype.
The practical benefits show up immediately. Court addresses stay correct on generated documents. You can see every matter at a given court on a given date, which is what makes bulk scheduling and bulk document generation possible. And ICON court and offence codes, which link courts, officers, cases and disclosure together, stay consistent.
Disclosure is a workflow
Requesting Crown disclosure is not a single event. You request it, you wait, some of it arrives, you often request more, and you need to know at any moment which matters are waiting on what.
Software that handles this well lets you record the request, track what came back, request additional disclosure against the same matter, and see across your whole caseload which files are outstanding. Software that handles it badly gives you a checkbox labelled "disclosure received".
Court dates carry more than a date
A provincial offence matter typically passes through several kinds of appearance, and they are not interchangeable. Early resolution meetings, trials, sentencing, motions and enforcement steps all behave differently and generate different correspondence.
Treating them as typed appointments loses the ability to answer basic questions like which matters are at early resolution versus set for trial, and which ones need a notice of intention to appear filed.
Dispositions should produce the letter
Every matter ends somewhere: guilty, not guilty, withdrawn, stayed, dismissed, or resolved to a lesser charge. Recording that outcome should not be separate from telling the client about it.
When the disposition is structured, the disposition letter can be generated from it, with the right paragraphs for that outcome, the correct fine and surcharge, and the client and matter details filled in. When it is a note in a text box, someone writes the letter by hand, and the wording differs depending on who wrote it.
The supporting cast
Beyond the offence-specific structure, the same practice needs the ordinary spine of any legal software, and it needs to be joined up with the rest:
| Capability | What it needs to connect to |
|---|---|
| Client and file records | Your own file-numbering scheme, including office identifiers |
| Trust and general accounting | The matter, so payments and balances sit with the file |
| Document generation | The client, case, court and office record |
| Calendar | Court dates, with export so staff can see them in their own calendar |
| Conflicts check | Run before the file is opened, against existing clients and matters |
| Tasks and call history | The matter, so context is not lost between staff |
| Audit log | Everything, without exception |
What to ask in a demo
Rather than watching a scripted tour, ask the vendor to do these five things live:
- 1Open a speeding matter and show the set fine and demerit points coming from the offence record.
- 2Show the victim fine surcharge being calculated rather than entered.
- 3Show every matter at one court on one date, then generate notices of trial for all of them.
- 4Record a disposition and produce the client letter from it.
- 5Show a client’s trust ledger and how it reconciles.
Any system built for this work will handle all five without preamble. Anything that needs configuration first is telling you where the gaps are.
Common questions
- Does POA mean power of attorney in this context?
- No. In Ontario legal practice POA normally refers to the Provincial Offences Act, which covers traffic and provincial offence matters including Highway Traffic Act charges. Power of attorney is an unrelated area and uses the same abbreviation, which causes regular confusion when firms compare software.
- Why do CVOR points need to be tracked separately from demerit points?
- They apply to different things. Demerit points attach to an individual driver’s record, while CVOR points attach to a commercial vehicle operator’s record. A commercial client cares about both, and about them separately, so software that collapses them into one field cannot answer the questions those clients ask.
- What is an ICON code?
- It is the Ontario court and offence code used to identify courts and offences consistently. In case management software it is useful as a linking value across courts, officers, cases and disclosure records, which keeps references consistent rather than dependent on how someone typed a court name.
- Can generic legal practice management software handle POA work?
- It can hold the matters, but it typically does not model offence sections, set fines, demerit or CVOR points, or victim fine surcharge natively. Firms usually recreate these with custom fields, which works for a small caseload but makes bulk operations and consistent quoting difficult as volume grows.
Keep reading
Choosing an HTA Pro alternative: an evaluation guide for Ontario paralegals
A practical checklist for comparing HTA Pro alternatives, from provincial offence data models and trust accounting to migration support and your exit plan.
Read the guideDocument templates and bulk generation for a traffic practice
Retainers, notices, disclosure requests and disposition letters, filled from the file rather than retyped, and produced for a whole court date at once.
Read the guide