Internal Task Management

12.1 Why Tasks Belong Alongside the Register

The register captures every fact about every asset, but it does not, on its own, coordinate the human work that keeps the register accurate and the school in compliance.

A quarterly Ed Code 35168 attestation, a month-end depreciation posting, a federal-grant biennial inventory, an audit-finding remediation, and a new-hire equipment onboarding are all recurring, cross-functional efforts with multiple people, sequenced steps, deadlines, and approvals — the kind of work that usually scatters across email threads, spreadsheets, and calendar reminders, which is precisely the failure mode the register was built to eliminate.

Internal Task Management brings the same discipline to that work: every task is a structured record, routed to an owner, tied to the asset or module it concerns, and audit-logged from creation to close. It is distinct from the maintenance work orders of Section 6 — a preventive-maintenance interval on an HVAC unit is a work order; the annual review of the preventive-maintenance calendar is an internal task.

12.2 The Task Record

Every task is a single record carrying a title, description, category, priority, status, assignee, optional watchers, start and due dates, estimated and actual hours, a percent-complete figure, and an operational section reference that ties it to a specific area of the platform.

A task can also link directly to an asset, work order, purchase order, invoice, lease, vendor, or audit record, so a reader who opens the task can jump to the underlying entity and a reader who opens the entity sees every open task related to it.

Status flows through six defined stages — new, not started, in progress, waiting, completed, and cancelled — and priority through four levels, so filtering and reporting behave consistently rather than depending on free-text conventions, while eight categories align tasks with how the business office already thinks about work.

Every change to a task is captured on an immutable activity log, so a later question about who moved the due date or reassigned the owner is answered from the record itself.

12.3 The Views a User Works In

The same task record is exposed through several purpose-built views, so a user chooses the one that fits the moment:

Users who work repeatedly against the same filter combinations save them as pinned Saved Views — a compliance officer might pin “Overdue compliance tasks” and “Due this week — audit prep” and open one as the first act of the morning rather than reconstructing the filter each time.

12.4 Recurring Schedules and Reusable Templates

Two features turn a passive list into an operating rhythm. Recurring Schedules materialize tasks on defined cadences — daily, weekly, monthly, quarterly, or annually — so the quarterly Ed Code 35168 attestation, the monthly depreciation posting, and the biennial federal-grant inventory appear on the assigned owner's list on their own, at the right time, every time; the calendar of the business office is embedded in the platform rather than living in someone's head.

Task Templates are the reusable blueprints that define what each recurring or one-off task looks like — title, category, priority, estimated hours, default owner, and standard checklist items. Seeded templates cover common school workflows out of the box, from new-hire equipment onboarding and quarterly compliance verification to month-end depreciation posting and audit-finding remediation, so institutional knowledge about how the school performs each effort becomes durable rather than tribal.

12.5 Automations and Cross-Module Triggers

Two layers convert events into automatic action. Task Automation Rules apply lightweight if-this-then-that logic to a task's own lifecycle — when a task is created, changes priority, or moves into “due soon” territory, actions run to set a priority, attach an SLA, add a tag or watcher, or log an entry — and every execution is captured with an outcome of applied, skipped, or errored, so automation behavior is debuggable rather than opaque.

Task Trigger Rules are the wider bridge from the rest of the platform: a purchase order rejected, a compliance check failed, or a lease approaching renewal can auto-create the corresponding task — a “Review and revise purchase order” task to the requesting department, a remediation task tied to the failing asset, or a “Renewal decision required” task to the finance administrator. Deduplication windows suppress duplicate fires, so a chatty upstream module does not swamp the inbox, and every dispatch and suppression is logged so a later question about why a task did or did not appear is answered from the record.

12.6 Approval Workflows for High-Consequence Tasks

Not every task is a single-owner effort. A capital-refresh decision, a disposal of federally funded equipment, or a change to a critical internal control requires a defined chain of sign-off rather than a single click of Completed.

Task Approval Chains are reusable multi-step workflows in which each ordered step names an approver role or user, scoped by priority, category, and an optional estimated-hours threshold so formal approval triggers only where it is warranted. When a task enters approval the chain is snapshotted onto the request, freezing the path at the moment of submission, and every action — submission, approval, rejection, delegation, comment, or cancellation — is recorded on an immutable log with the actor and the step. Approvals are sequential rather than parallel, mirroring how school approval chains actually operate and keeping the audit trail unambiguous.

12.7 Collaboration and Notifications

Every task carries a threaded comment thread, so the conversation about the work lives on the task rather than in an email chain that eventually gets lost; in-text mentions turn a comment into a targeted request for input, and comments are edit-tracked and soft-deletable so a mistaken post can be corrected without erasing the trail.

Notifications are the umbrella that keeps people informed — assignment, reassignment, status change, SLA warning and breach, mention, comment reply, and each approval event — and dedupe logic prevents the classic problem of the same at-risk task firing the same warning every cycle, so a user who signs in sees a small, curated set of items that actually require attention rather than a cluttered inbox.

12.8 Goals and Milestones

School work is rarely atomic. A year-end close or an audit engagement is a portfolio of tasks that succeed or fail together. Task Goals are named objectives that group related tasks under a shared banner with a target date, an owner, a status, and an accent color, and because a task can link to more than one goal, a single “Reconcile federal-grant equipment inventory” task can advance both the annual audit-prep goal and the 2 CFR 200.313 compliance goal without duplicating the record.

Goal progress aggregates automatically from the linked tasks — total, completed, in-progress, overdue, and a live percent-complete — so the CBO looking at the audit-prep goal at the end of September sees in one number whether the year-end effort is on track without opening every task in the portfolio.