Modules · 4 of 16

Records & finance

Statutory clocks, transfer transcripts, contract renewals and the money — all of it counted from the date received rather than the date somebody got to it.

A contract that auto-renews unnoticed, an APRA request logged three weeks late, a transcript sitting in a counselor inbox: each is a deadline nobody was counting, and each becomes visible only after it is missed.

Student records

Inbound transcripts tracked through a seven-step chain with one owner at every point.

When a student transfers in, the transcript usually arrives before they do. Every step has one owner and one next action, and due dates are counted from the date the record was received rather than from the day the step became your turn.

module key: records · independently toggled per district

What it does

  • Seven-step chain: intake, match, counselor review, transcription, credit evaluation, schedule, filing
  • Counselor resolved from the caseload — last-name ranges per building, per year
  • Credit evaluation triggered only for out-of-state or non-accredited sources
  • Due dates counted from receipt, so a stalled step does not reset the clock
  • Transcription queue for the registrar, with review notes emailed to the transcriber
  • Full audit of who did what to a student record and when

Public records

Indiana APRA request intake, deadline tracking and annual state reporting.

Requests arrive through a public form or informally by post, email, phone or in person — and both end up in the same queue. The statutory clock starts when a request is received, so a request nobody logged is a deadline nobody is counting.

module key: apra · independently toggled per district

What it does

  • Public submission form usable without a district account
  • Log non-portal requests that arrived by post, email, phone or in person
  • Request queue with handler, date received and statutory due date
  • Correspondence kept on the request rather than in a personal mailbox
  • Dashboard of what is close to deadline
  • Annual APRA reporting for the state

Contracts

Contract lifecycle, CFO and Board review, COI compliance and the renewal calendar.

Renewal terms are the field people skip and the one that costs money. A contract that auto-renews unless cancelled ninety days out needs that ninety days recorded, or the reminder arrives too late to act on.

module key: contracts · independently toggled per district

What it does

  • Vendor, term, value, renewal terms and internal owner on every contract
  • CFO review and Board review queues, with thresholds set per district
  • Renewal calendar with staged email reminders at 90 / 60 / 30 days
  • COI compliance tracking: current, lapsed and expiring soon
  • Vendor registry, contract type templates and approval workflows
  • Configurable statuses and per-status notification recipients

Finance

Spend, revenue, outstanding balances and budgets, assembled from the modules that create them.

Nothing here is typed in twice. The figures are assembled from the modules that generate them — device fees, supply orders, contracts, facilities work, reservations revenue — which means a number that looks wrong is wrong at its source, and can be followed back to the record that produced it.

module key: finance · independently toggled per district

What it does

  • Dashboard showing where the fiscal year stands overall
  • Spend committed, by vendor and by budget account
  • Revenue by source, including facility rentals
  • Outstanding balances traced back to the incident or order behind them
  • Budget commitment and remaining, by account
  • Board-pack PDF, year-over-year comparison and utilisation reports

Walk through Records & finance on your own data

We load a copy of your buildings and roles, turn on the modules you asked about, and show you the queues your staff would actually see.