Destiny Resource Manager vs Incident IQ

Destiny Resource Manager

Follett's district resource-tracking system, part of the Destiny suite, used to manage technology devices alongside textbooks, curriculum materials, and other non-library resources, with bidirectional MDM sync and an optional help desk.

Where Destiny Resource Manager is strong

• ● The strongest permission model in the K-12 asset field: roughly 69 discrete Resource Manager permissions spanning search, resource management, circulation, fines, fees, and administration, with add, edit, delete, and duplicate as separate grants.
• ● Two-tier district and site administration — access levels definable by the district administrator, a site administrator, or both, with district settings pushed out and enforced district-wide or selectively.
• ● Resource Groups provide a second, orthogonal scoping axis, so access is bounded both by permission and by branch of the district's shared resource tree.
• ● Offline-capable mobile scanning through the Destiny Back Office app on iOS and Android, plus Follett's own VersaScan handheld and PocketScan Bluetooth scanner. Both inventory and circulation work offline, with SSO and multi-site switching without re-authenticating — the only offline-capable option in this comparison.
• ● Genuine bidirectional MDM sync across Google Workspace, Intune, and Jamf Pro, with rule-driven write-back that can change device state or organizational unit based on actions taken in Destiny.
• ● Digital Signature Agreements that hard-block checkout when unsigned, map agreements to resource type, patron persona, and site, can require a signature on every checkout, and ship Block Overrides and Needs Signature compliance reports.

What to check before you buy

• No warranty field is documented. The Add/Edit Item field list runs from Status and Condition through Purchase Price, Purchase Order, Funding Source, and Projected Life without a warranty field anywhere in it; Date Acquired plus Projected Life models asset life and depreciation, not warranty end.

  Basis: the complete documented item field list in Follett's own help docs

• Purchase order support is a plain text field on the item record — the docs describe it as the PO number used for the items. There is no approval routing, no line items, and no vendor records. The separate Resource Orders module is internal district-warehouse fulfillment with pick lists and shipments, not external procurement.

  Basis: Follett help documentation for item fields and the Resource Orders module

• No native OneRoster, Clever, or ClassLink rostering is documented. Rostering is a nightly patron import via CSV with XSLT transform files. ClassLink and Okta appear only as SSO providers for Destiny Help Desk, never as roster sources.

  Basis: Follett patron import documentation; absence of any documented rostering connector in public docs

• No parts inventory and no repair-cost tracking in native help tickets — tickets carry priority, status, expected completion date, notes, assignment, and reopen, and nothing about the money or materials a repair consumed.

  Basis: Follett help desk ticket documentation

• No insurance or protection-plan object. Insurance is modeled as a generic fee, with no coverage terms, claims workflow, deductibles, per-incident tracking, or renewals.

  Basis: Follett documents insurance as an intended use of the generic fee type

• Digital Signature Agreements is described by Follett as a hosted cloud app requiring an external internet connection, and Destiny AI is available only to hosted customers. A district running Destiny on-premises or air-gapped cannot have either at any price.

  Basis: Follett product documentation stating the hosted-cloud requirement

• Destiny Help Desk is a paid subscription add-on that additionally requires Resource Manager 22.5 or later with Unified Navigation enabled, so older on-premises installs cannot adopt it without upgrading first.

  Basis: Follett add-on packaging and stated version floor

• The native fee 'Pay' permission records a payment rather than processing one. Actual online collection requires Destiny Fee Manager, a separate Stripe-powered product whose best parent-portal experience additionally depends on Follett's own Aspen SIS.

  Basis: Follett Fee Manager product documentation

How Chalk compares with Destiny Resource Manager →

Incident IQ

A K-12-only operations platform that combines IT ticketing, asset management, facilities work orders, event management, instructional resources, and HR service delivery in a single hosted suite.

Where Incident IQ is strong

• ● The broadest suite in K-12 operations: IT ticketing, assets, facilities, events, resources, and HR service delivery under one portal — the 'one platform, one portal' consolidation story is its most-cited win.
• ● Smart Audits can verify a device's presence automatically from MDM and sign-in activity, so a chunk of an inventory audit completes without anyone physically touching the device.
• ● Mature bulk-deployment tooling built for scale: rapid scan sessions, spare-pool allotments per building, and rollout accuracy checks aimed at large 1:1 distributions.
• ● Native iOS and Android apps with camera barcode scanning and voice lookup for technicians working in hallways and classrooms.
• ● AI ticket assistance for classification, suggested knowledge-base articles at submission time, and ticket summaries.
• ● Warranty status is a first-class field on the asset record and visible inside a ticket, with warranty claim submission through hardware partners.

What to check before you buy

• Hosted SaaS only — there is no self-hosted or on-premises option, so district data lives in the vendor's cloud and the software cannot be run or inspected independently.

  Basis: vendor site offers only a hosted product; no self-host or source distribution is published

• No public pricing. Every cost conversation starts with a sales demo, and pricing scales with student enrollment.

  Basis: vendor pricing page directs all buyers to schedule a demo for a tailored quote

• Price relative to value for smaller districts is the most frequently cited drawback in buyer reviews.

  Basis: recurring theme in public review-site feedback

• Limited customization is the second most cited drawback — districts report workflows and fields being harder to bend to local process than expected.

  Basis: recurring theme in public review-site feedback

• Online fee payment is not native. Collecting money means integrating a third-party processor such as InTouch, MySchoolBucks, Square, Stripe, or Vanco.

  Basis: vendor documents payments as partner integrations rather than a first-party module

• Warranty claim handling depends on hardware reseller partnerships rather than a vendor-neutral claims workflow.

  Basis: vendor documents claims through named hardware partners

• MDM integration is ingest-oriented: iiQ reads device state from Google, Jamf, and Intune rather than pushing a reviewed set of changes back into them.

  Basis: vendor asset documentation describes sync into iiQ, with no diff-preview write-back workflow

• Incident IQ is not an identity provider and does not serve a OneRoster API — it consumes rostering data rather than publishing it to other systems.

  Basis: vendor documents SIS connectors as inbound integrations only

How Chalk compares with Incident IQ →

The third option: Chalk

If you are weighing Destiny Resource Manager against Incident IQ, Chalk belongs on the same shortlist. It is the open-source K-12 IT stack: device inventory that fills itself in from Google Admin, Intune, and Jamf against a roster synced from your SIS, a 1:1 circulation desk with agreements and fees, repairs with parts and costs, a help desk that already knows who is asking, and a built-in SAML/OIDC identity provider.

• ✓ Self-host it free forever under AGPL-3.0 — the entire feature set, one binary, your infrastructure — or use the hosted version, priced by fleet size with no per-seat or per-student fees and the price ladder published.
• ✓ Built only for K-12: students, buildings, custody, funding sources, and ChromeOS auto-update expiration are native concepts, not custom fields.
• ✓ Writes back to Google Admin as a reviewed diff — every OU move, disable, and deprovision previewed before it executes — and serves a OneRoster 1.1 API so other district systems can pull the roster from Chalk.
• ✓ Fees are assessed and tracked without touching payment cards, keeping the asset system out of your PCI scope.