Court Clerk Operations
Prepare court clerk closeout, sentencing, and disposition packets by cross-referencing local hearing documents with the Court Operations Portal REST API. This skill covers the common reconciliation, financial, and form-entry patterns used by deputy clerks across criminal, traffic, and post-sentencing workflows.
Workflow
Every task follows the same sequence:
- Read every local payload file in the task's payloads directory, plus the answer template when one is provided.
- Call the portal to retrieve authoritative records for each target case, citation, or petition.
- Cross-reference local documents against portal records. Resolve every conflict using the reconciliation rules below.
- Compute financial amounts from portal fee schedules and payment policies, never from stale local worksheets.
- Build the output JSON conforming to the answer template, using the ordering, enum, date, and currency precision rules it specifies.
Portal API
All endpoints are GET requests to TASK_ENV_BASE_URL. No authentication.
| Endpoint |
Returns |
/api/jurisdictions |
Court metadata, jurisdiction codes, policy references |
/api/cases |
Case records: defendant, DOB, counsel type, status, disposition date |
/api/charges |
Charge records: offense, plea, disposition, fines, jail, probation, departure |
/api/docket-entries |
Docket history: filing, hearing, disposition, financial, and clerk-note entries |
/api/citations |
Traffic citation records: violation code, speed, disposition, payment plan status |
/api/fee-schedules |
Fee amounts by jurisdiction, effective date, and fee type (court_cost, assessment, user_fee) |
/api/payment-policies |
Installment plan rules: monthly band, first-due offset, account fee, restitution priority |
/api/forms |
Form metadata: required fields, placeholder instructions, revision dates |
/api/financial-petitions |
Payment petition records: balances, income, obligations, requested amounts |
/api/search |
Multi-entity search by case number, citation number, or name |
Query pattern: Use /api/search?q=<case_number> first to get a result set spanning cases, docket entries, charges, and citations in one call. Then call individual endpoints for fee schedules (/api/fee-schedules), payment policies (/api/payment-policies), and forms (/api/forms) which are not searchable by case number. For fee schedules, filter client-side by jurisdiction_code and effective_date -- use the schedule with the latest effective_date that is not past its end_date and is on or before the disposition date.
Full endpoint field descriptions are in references/portal_endpoints.md. Load it when a field's meaning is unclear.
Detailed reconciliation decision trees and fee applicability tables are in references/reconciliation_rules.md. Load it for complex conflicts that go beyond the summaries below.
Reconciliation Rules
Identity conflicts
When defendant name or DOB differs between local worksheets and portal records:
- Prefer the portal CMS record (
source_system = AOC-CMS or VACMS) over the finance queue or worksheet.
- If a hearing note or corroborating memo explicitly corrects the portal record, use that correction and cite the source as the resolution.
- When DOB is genuinely missing from all sources, use "TBD from case file" and flag the identity action as
use_placeholder_verify.
Counsel classification
counsel_type in /api/cases is the authoritative record. But the attorney_label_raw field can be misleading: "APD" may mean appointed private counsel, not public defender.
- When a hearing note or corroborating memo says defense counsel is appointed private (county-paid, not the PD office), classify as
appointed_private regardless of the raw label.
- Public Defender User Fee applies only when counsel is classified as
public_defender. Never apply it to appointed_private, retained, or unknown.
Case status and disposition
- Before posting any financial entry, confirm the case has a signed final order. Cases that are
deferred, continued, or pending must not receive sentencing financial entries.
- A draft worksheet showing "disposed" does not override a docket note that says the final order was not signed. If the status is genuinely pending, the closeout action is
hold_unsigned_order or exclude_pending.
- Use the disposition date from portal
/api/cases or the hearing notes, not the audit memo date.
Departure status
- Determine departure from the judge's actual pronouncement in the hearing notes, not from legacy worksheet labels.
- If the judge said "top of the range" or "no departure," the departure status is
no_departure or none.
- For misdemeanors where departure isn't evaluated, use
not_evaluated_misdemeanor.
- For pending cases with no final order, use
not_entered_pending.
Fee schedule conflicts
- A fee schedule is current when its
effective_date is on or before the disposition date and its end_date is null or after the disposition date.
- A fee schedule is stale when its
end_date predates the disposition date.
- Always use the current schedule amount. Flag stale amounts found in local worksheets as audit issues.
- Check
mandatory: if true, the fee applies regardless of what the worksheet says. If false, check the notes field for applicability conditions (e.g., PD user fee only for public defender cases).
Financial Computation
Fee calculation
- Start from
/api/fee-schedules filtered to the case's jurisdiction.
- For each fee with
effective_date <= disposition date and (end_date is null or end_date >= disposition date):
- Include if
mandatory is true, or if the fee's notes and statute support it for this case.
- Use the portal amount, not any local worksheet amount.
- Court cost is always mandatory for disposed criminal cases. Its amount varies by jurisdiction.
- Assessment fees (drug, crime lab) apply only when the conviction charge triggers them (controlled substance -> drug assessment and/or crime lab fee).
- PD user fee applies only when
counsel_type is public_defender and the case is disposed.
- Fines come from the charge record (
/api/charges) or hearing notes, not from fee schedules.
Payment plan math
When building an installment schedule from a total balance and monthly payment:
full_payment_count = floor(total_due / monthly_payment)
final_payment_amount = total_due - (full_payment_count * monthly_payment)
total_installments = full_payment_count + (1 if final_payment_amount > 0 else 0)
- If
final_payment_amount is 0, the schedule has full_payment_count equal installments.
- If
final_payment_amount > 0, the last installment is the reduced amount.
- First due date: add
first_due_days from the payment policy to the disposition date. If the policy notes specify a calendar convention (e.g., "15th of next month"), use that.
- Return-to-court date: add
return_to_court_offset_days from the policy to the final due date.
- Down payment: use
down_payment_required from the policy. Subtract from total before computing installments when nonzero.
- Monthly payment must fall within
[min_monthly, max_monthly] from the policy. When the requested amount from a petition falls within this band and is supported by the budget, approve it.
Payment application order
Follow the payment policy's restitution_priority:
- "Restitution before fines and costs" -> apply payments to restitution balance first, then fines/costs.
- "Restitution before discretionary fines" -> same ordering.
- "Not applicable" -> apply to fines/costs only (no restitution involved).
Budget supportability
When a petition provides income and obligations:
monthly_disposable_income = monthly_income - total_monthly_obligations
- If
monthly_disposable_income >= requested_monthly_payment and the requested amount is within [min_monthly, max_monthly]: supportable or supported_by_budget.
- If the requested amount is below
min_monthly: below_policy_minimum.
- If the requested amount exceeds
max_monthly: above_policy_maximum.
- If
monthly_disposable_income < min_monthly: unsupported_by_budget.
Placeholder Rules
Use the exact string "TBD from case file" for any field that is required by a form but missing from all available sources (portal, local payloads, hearing notes):
- SSN, driver's license number, mailing address, residence address, phone number
- Probation officer name, probation office location
- Any party detail not in the case file
Never invent these values. The form's placeholder_instruction from /api/forms confirms which fields get this treatment.
Exclusion Rules
Exclude the following from financial postings and register totals unless the portal record or current policy directly supports them:
- Account management fees when
account_fee in the payment policy is 0.00
- Collection fees, late payment fees, returned check fees, DMV fees when no triggering event (default, late payment, returned check, DMV referral) is recorded
- Traffic school fees not ordered in the hearing
- Restitution when no restitution order exists
- Court-appointed attorney fees, court reporter fees absent a specific order
- Stale fee schedule amounts -- always use current effective schedule
When excluding, include each item in the excluded_charges or excluded_financial_items array with its reason_code from the answer template enums.
Output Conventions
- Dates: ISO 8601
YYYY-MM-DD. Date-times: YYYY-MM-DDTHH:MM:SS.
- Currency: Numbers to two decimal places (e.g.,
150.00 not 150).
- Null values: Use JSON
null for genuinely absent dates (e.g., no disposition date for pending cases). Never use empty strings for dates or currency.
- Sorting: Follow the ordering rules in the answer template. When none specified, sort by case number or citation number ascending.
- Enums: Use the exact enum values from the answer template. Never substitute free text when an enum value exists.
Anti-Patterns
- Do not post financial entries for pending, deferred, or continued cases that lack a signed final order.
- Do not carry forward fees or amounts from outdated worksheets or stale schedules.
- Do not add fees (account-management, collection, late, DMV, restitution, copy, certification) unless directly supported by the current portal fee schedule, payment policy, or a specific court order.
- Do not invent identifiers, addresses, phone numbers, or contact details.
- Do not use the audit memo date as the disposition date.
- Do not treat an
APD label as public defender without checking corroborating sources.
- Do not include markdown or commentary in the JSON output; return only the JSON object.
1---2name: court-clerk-43description: Court clerk closeout, sentencing, and disposition packet preparation. Use when the task involves reconciling case records through a Court Operations Portal API to produce audit findings, case dispositions, fee reconciliation, docket entries, register totals, payment plans, probation referrals, license orders, or financial-field packets from local hearing notes, audit memos, finance extracts, petition summaries, or sentencing intake facts. Covers criminal sentencing closeouts, traffic violation payment plans, post-sentencing field packets (CC-1375/CC-1379), and criminal disposition batch registers.4metadata:5 source: https://skillmd.com/skills/prism-shadow/court-clerk-46---78# Court Clerk Operations910Prepare court clerk closeout, sentencing, and disposition packets by cross-referencing local hearing documents with the Court Operations Portal REST API. This skill covers the common reconciliation, financial, and form-entry patterns used by deputy clerks across criminal, traffic, and post-sentencing workflows.1112## Workflow1314Every task follows the same sequence:15161. Read every local payload file in the task's payloads directory, plus the answer template when one is provided.172. Call the portal to retrieve authoritative records for each target case, citation, or petition.183. Cross-reference local documents against portal records. Resolve every conflict using the reconciliation rules below.194. Compute financial amounts from portal fee schedules and payment policies, never from stale local worksheets.205. Build the output JSON conforming to the answer template, using the ordering, enum, date, and currency precision rules it specifies.2122## Portal API2324All endpoints are GET requests to `TASK_ENV_BASE_URL`. No authentication.2526| Endpoint | Returns |27|---|---|28| `/api/jurisdictions` | Court metadata, jurisdiction codes, policy references |29| `/api/cases` | Case records: defendant, DOB, counsel type, status, disposition date |30| `/api/charges` | Charge records: offense, plea, disposition, fines, jail, probation, departure |31| `/api/docket-entries` | Docket history: filing, hearing, disposition, financial, and clerk-note entries |32| `/api/citations` | Traffic citation records: violation code, speed, disposition, payment plan status |33| `/api/fee-schedules` | Fee amounts by jurisdiction, effective date, and fee type (court_cost, assessment, user_fee) |34| `/api/payment-policies` | Installment plan rules: monthly band, first-due offset, account fee, restitution priority |35| `/api/forms` | Form metadata: required fields, placeholder instructions, revision dates |36| `/api/financial-petitions` | Payment petition records: balances, income, obligations, requested amounts |37| `/api/search` | Multi-entity search by case number, citation number, or name |3839**Query pattern:** Use `/api/search?q=<case_number>` first to get a result set spanning cases, docket entries, charges, and citations in one call. Then call individual endpoints for fee schedules (`/api/fee-schedules`), payment policies (`/api/payment-policies`), and forms (`/api/forms`) which are not searchable by case number. For fee schedules, filter client-side by `jurisdiction_code` and `effective_date` -- use the schedule with the latest `effective_date` that is not past its `end_date` and is on or before the disposition date.4041Full endpoint field descriptions are in [references/portal_endpoints.md](references/portal_endpoints.md). Load it when a field's meaning is unclear.4243Detailed reconciliation decision trees and fee applicability tables are in [references/reconciliation_rules.md](references/reconciliation_rules.md). Load it for complex conflicts that go beyond the summaries below.4445## Reconciliation Rules4647### Identity conflicts4849When defendant name or DOB differs between local worksheets and portal records:50- **Prefer the portal CMS record** (`source_system` = `AOC-CMS` or `VACMS`) over the finance queue or worksheet.51- If a hearing note or corroborating memo explicitly corrects the portal record, use that correction and cite the source as the resolution.52- When DOB is genuinely missing from all sources, use "TBD from case file" and flag the identity action as `use_placeholder_verify`.5354### Counsel classification5556- `counsel_type` in `/api/cases` is the authoritative record. But the `attorney_label_raw` field can be misleading: "APD" may mean appointed private counsel, not public defender.57- When a hearing note or corroborating memo says defense counsel is appointed private (county-paid, not the PD office), classify as `appointed_private` regardless of the raw label.58- Public Defender User Fee applies **only** when counsel is classified as `public_defender`. Never apply it to `appointed_private`, `retained`, or `unknown`.5960### Case status and disposition6162- Before posting any financial entry, confirm the case has a signed final order. Cases that are `deferred`, `continued`, or `pending` must not receive sentencing financial entries.63- A draft worksheet showing "disposed" does not override a docket note that says the final order was not signed. If the status is genuinely pending, the closeout action is `hold_unsigned_order` or `exclude_pending`.64- Use the disposition date from portal `/api/cases` or the hearing notes, not the audit memo date.6566### Departure status6768- Determine departure from the judge's actual pronouncement in the hearing notes, not from legacy worksheet labels.69- If the judge said "top of the range" or "no departure," the departure status is `no_departure` or `none`.70- For misdemeanors where departure isn't evaluated, use `not_evaluated_misdemeanor`.71- For pending cases with no final order, use `not_entered_pending`.7273### Fee schedule conflicts7475- A fee schedule is current when its `effective_date` is on or before the disposition date and its `end_date` is null or after the disposition date.76- A fee schedule is stale when its `end_date` predates the disposition date.77- Always use the current schedule amount. Flag stale amounts found in local worksheets as audit issues.78- Check `mandatory`: if true, the fee applies regardless of what the worksheet says. If false, check the notes field for applicability conditions (e.g., PD user fee only for public defender cases).7980## Financial Computation8182### Fee calculation83841. Start from `/api/fee-schedules` filtered to the case's jurisdiction.852. For each fee with `effective_date` <= disposition date and (`end_date` is null or `end_date` >= disposition date):86 - Include if `mandatory` is true, or if the fee's `notes` and `statute` support it for this case.87 - Use the portal amount, not any local worksheet amount.883. Court cost is always mandatory for disposed criminal cases. Its amount varies by jurisdiction.894. Assessment fees (drug, crime lab) apply only when the conviction charge triggers them (controlled substance -> drug assessment and/or crime lab fee).905. PD user fee applies only when `counsel_type` is `public_defender` and the case is disposed.916. Fines come from the charge record (`/api/charges`) or hearing notes, not from fee schedules.9293### Payment plan math9495When building an installment schedule from a total balance and monthly payment:9697```98full_payment_count = floor(total_due / monthly_payment)99final_payment_amount = total_due - (full_payment_count * monthly_payment)100total_installments = full_payment_count + (1 if final_payment_amount > 0 else 0)101```102103- If `final_payment_amount` is 0, the schedule has `full_payment_count` equal installments.104- If `final_payment_amount` > 0, the last installment is the reduced amount.105- First due date: add `first_due_days` from the payment policy to the disposition date. If the policy notes specify a calendar convention (e.g., "15th of next month"), use that.106- Return-to-court date: add `return_to_court_offset_days` from the policy to the final due date.107- Down payment: use `down_payment_required` from the policy. Subtract from total before computing installments when nonzero.108- Monthly payment must fall within `[min_monthly, max_monthly]` from the policy. When the requested amount from a petition falls within this band and is supported by the budget, approve it.109110### Payment application order111112Follow the payment policy's `restitution_priority`:113- "Restitution before fines and costs" -> apply payments to restitution balance first, then fines/costs.114- "Restitution before discretionary fines" -> same ordering.115- "Not applicable" -> apply to fines/costs only (no restitution involved).116117### Budget supportability118119When a petition provides income and obligations:120121```122monthly_disposable_income = monthly_income - total_monthly_obligations123```124125- If `monthly_disposable_income >= requested_monthly_payment` and the requested amount is within `[min_monthly, max_monthly]`: `supportable` or `supported_by_budget`.126- If the requested amount is below `min_monthly`: `below_policy_minimum`.127- If the requested amount exceeds `max_monthly`: `above_policy_maximum`.128- If `monthly_disposable_income < min_monthly`: `unsupported_by_budget`.129130## Placeholder Rules131132Use the exact string "TBD from case file" for any field that is required by a form but missing from all available sources (portal, local payloads, hearing notes):133134- SSN, driver's license number, mailing address, residence address, phone number135- Probation officer name, probation office location136- Any party detail not in the case file137138Never invent these values. The form's `placeholder_instruction` from `/api/forms` confirms which fields get this treatment.139140## Exclusion Rules141142Exclude the following from financial postings and register totals unless the portal record or current policy directly supports them:143144- Account management fees when `account_fee` in the payment policy is 0.00145- Collection fees, late payment fees, returned check fees, DMV fees when no triggering event (default, late payment, returned check, DMV referral) is recorded146- Traffic school fees not ordered in the hearing147- Restitution when no restitution order exists148- Court-appointed attorney fees, court reporter fees absent a specific order149- Stale fee schedule amounts -- always use current effective schedule150151When excluding, include each item in the `excluded_charges` or `excluded_financial_items` array with its `reason_code` from the answer template enums.152153## Output Conventions154155- **Dates**: ISO 8601 `YYYY-MM-DD`. Date-times: `YYYY-MM-DDTHH:MM:SS`.156- **Currency**: Numbers to two decimal places (e.g., `150.00` not `150`).157- **Null values**: Use JSON `null` for genuinely absent dates (e.g., no disposition date for pending cases). Never use empty strings for dates or currency.158- **Sorting**: Follow the ordering rules in the answer template. When none specified, sort by case number or citation number ascending.159- **Enums**: Use the exact enum values from the answer template. Never substitute free text when an enum value exists.160161## Anti-Patterns162163- Do not post financial entries for pending, deferred, or continued cases that lack a signed final order.164- Do not carry forward fees or amounts from outdated worksheets or stale schedules.165- Do not add fees (account-management, collection, late, DMV, restitution, copy, certification) unless directly supported by the current portal fee schedule, payment policy, or a specific court order.166- Do not invent identifiers, addresses, phone numbers, or contact details.167- Do not use the audit memo date as the disposition date.168- Do not treat an `APD` label as public defender without checking corroborating sources.169- Do not include markdown or commentary in the JSON output; return only the JSON object.