Comparison
Destiny Resource Manager vs Frontline Asset Management (formerly TIPWeb-IT)
Two tools districts shortlist for device tracking and IT operations, compared the way a buying committee actually reads them: what each is, what each does well, and what to check before signing. We build Chalk, a third option in this space — that context is worth knowing as you read, and it is why every claim below carries its basis.
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
Frontline Asset Management (formerly TIPWeb-IT)
The asset-tracking module of Frontline Inventory & Help Desk Management, originally built by Hayes Software Systems as TIPWeb-IT, sold alongside Instructional Materials Management and Help Desk Management.
Where Frontline Asset Management (formerly TIPWeb-IT) is strong
- The deepest procurement and receiving workflow in the K-12 asset field: a PO header carrying PO number, purchase date, vendor, funding source, and E-Rate Funding Request Number, a real ship-then-receive flow with admin and site views, two bulk receiving import paths with field mapping and validation, and warehouse as a first-class site type.
- Funding-source governance that no one else matches: each source carries a 'Transferring Restricted To' list controlling which users may move tags funded that way — E-Rate restrictions genuinely block transfers — plus nightly end-of-life status notifications to named recipients.
- Serious audit machinery: site audits containing room audits, due dates with overdue highlighting, Verified/Missing/Misplaced resolution, a compliance status, a Police Report Required flag for lost and stolen items, and Sync Found Items cross-matching across audits.
- The only product here with RFID, reading passive tags at roughly fourteen feet and bulk-reading full carts. Frontline claims up to 20% less inventory time, which is a vendor figure rather than an independent one.
- A native mobile app spanning both Asset Management and Help Desk — scan and track assets, work tickets, and build dashboards from a phone.
- Automatic SIS-driven reassignment is the most praised feature in its reviews: inventory follows students and staff between campuses off the nightly file without anyone touching it.
What to check before you buy
-
No warranty tracking and no insurance or protection-plan module. The nearest features are Purchase Date and a product-level Projected Life that computes a projected replacement date, which is not warranty end; districts improvise with custom fields.
Basis: zero occurrences of warranty or insurance terms across roughly 300KB of extracted text from Frontline and Hayes' own manuals, including the 387-page admin reference guide, plus nothing in the help center or public API
-
No online payment collection. The charge ledger itself is fully featured — district-defined charge types, bulk assessment, refunds, voids, satisfied and unsatisfied states, charge receipts — but there is no payment gateway and no processor partner, so staff key in payments by hand. The gap is collection, not tracking.
Basis: vendor manuals plus the absence of any charge or payment endpoint in the public REST API
-
No parent portal and no student or family self-service. What exists is staff-initiated: distribution and collection receipts with signature capture producing a signed PDF, plus a district setting allowing sites to email those receipts. There is no acceptable-use-policy e-signature workflow and no SMS — communication is email-only.
Basis: vendor manuals document receipt signature capture and email delivery only
-
Documented rostering is a nightly batch file import for both staff and students, and the manuals warn that manual edits are overwritten by the next import. ClassLink appears only as a SAML SSO provider, never as a roster source.
Basis: vendor manuals describe nightly integration; note these manuals straddle the Frontline rebrand, so a post-acquisition release may have added more
-
Fines are not unified across Frontline's own products. Asset Management (devices) and Instructional Materials Management (textbooks) maintain entirely separate charge systems with separate charge type tables, so a family can owe money in two places that never add up together.
Basis: the Asset Management and Instructional Materials district manuals document independent charge structures
-
Funding-source accountability is a self-named lookup table with no built-in ESSER or Title I field, so grant tagging works by naming convention and depends on staff discipline.
Basis: vendor manual documentation of the funding source lookup
-
The API authenticates with a login token rather than OAuth, and the vendor's own documentation warns that writes hit the live production database in real time and are irreversible — there is no staging or preview step.
Basis: Frontline's public API documentation
-
Interface age and click-depth are the most consistent complaints in public reviews, with reviewers describing the interface as looking like something from the 90s and saying it takes way too many steps to complete a task.
Basis: verbatim reviewer feedback on Capterra
How Chalk compares with Frontline Asset Management (formerly TIPWeb-IT) →
The third option: Chalk
If you are weighing Destiny Resource Manager against Frontline Asset Management (formerly TIPWeb-IT), 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.
See all three on your own roster.
Chalk installs to a populated inventory in about 30 minutes. Self-host free under AGPL-3.0, or let us run it — priced by fleet size, never per seat.