What’s New in Destiny for K-12 Libraries?
Library Resource
What Destiny for K-12 Libraries Includes
“What’s new in Destiny” refers to the release updates, workflow changes, reporting improvements, and product enhancements that affect districts using Destiny across school libraries, classrooms, and instructional resource programs. For K-12 teams, the useful question is not only which features were added. It is which changes affect daily circulation, reporting, reading programs, resource management, accessibility, and staff training.
At a glance
- Destiny release updates can affect Library Manager, Resource Manager, Destiny Engage, Destiny Discover, and classroom library workflows.
- Recent updates have focused on reporting, usability, accessibility, holds and interlibrary loan workflows, student reading engagement, and district-level visibility.
- Release notes are most useful when translated into role-specific workflow changes and adoption tasks.
- Districts should review permissions, training needs, documentation, and local configuration before broadly introducing a new feature.
- Existing Destiny customers can use release reviews to identify adoption opportunities before considering an account expansion.
The latest Destiny updates should be reviewed as workflow changes, not as a list of isolated features. A K-12 district should first identify which release version applies to its environment, then map each relevant change to the staff member, student, or administrator who will use it.
For library teams, that review commonly includes circulation, catalog maintenance, holds, interlibrary loans, overdue notices, reporting, and student discovery. District administrators may also need to review cross-site reporting, permissions, and configuration standards. Curriculum leaders and teachers may be more concerned with classroom libraries, instructional resources, reading programs, and how activity is measured across schools.
Recent Destiny release materials describe updates across reporting and usability. Destiny 23.5 included Report Builder 2.0 for Destiny Library Manager, expanded reporting options, sublocation data in key reports, CSV downloads, Title Details improvements, language search in Destiny Discover, monthly overdue notices, and changes to Destiny Engage book club and reading program workflows. Destiny 24.0 materials describe updated holds and interlibrary loan workflows, refreshed patron management, bulk copy status changes, sublocation visibility during check-in, expanded reporting, new Engage metrics, and changes to Discover and Engage navigation.
The practical outcome is a repeatable adoption process: confirm what changed, determine who is affected, test the workflow with representative district data, communicate the change, and measure whether staff are using it as intended. Release information should support better daily work, not create another document for staff to read without follow-through.
K-12 Use Cases
District Library Director
A district library director asks site librarians to review new reporting and sublocation capabilities before end-of-year collection reviews. The team agrees on common reports, naming conventions, and a short training session so results can be compared across schools.
School Librarian
A school librarian and district administrator review updated holds, interlibrary loan, and overdue workflows before the next school year. They test common scenarios, document local permissions, and update staff procedures for exceptions.
Curriculum Director and Reading Specialist
A curriculum director and reading specialist examine new Destiny Engage metrics and book club workflows while planning a district reading initiative. They decide which participation measures are useful for program monitoring and which should remain local to each school.
Decision Points
Common Questions
Which release changes affect our district’s actual products, hosting model, and enabled features?
Which workflows need testing before staff and students use the update broadly?
Do reporting, permissions, or configuration changes require a district standard rather than site-by-site choices?
Is the next step training on a feature we already own, or a conversation about an additional Destiny capability?
We’ve evolved with Destiny. It’s rewarding that we have been able to contribute to the new versions over the years as Follett has always welcomed our input on what our district needs.
Coordinator, Library Services, Napa Valley Unified School District
Supporting Data and Evidence
Follett Software Saves Operating Costs and Meets the Needs of Students District-Wide
With more than 16,000 students enrolled in Napa Valley Unified School District (NVUSD) in 16 elementary, four middle, five traditional high, and one distance learning school, MacMillan has placed her trust in Follett Destiny® for many years – for a multitude of reasons.
What's New in the Library Suite
What’s New in the Library Suite Use this as the living source for release-by-release updates; pair each update with role-specific workflow guidance and a clear adoption next step.
Practical Guidance
Confirm details
Confirm the release version, deployment timing, products, and enabled features that apply to your district.
Sort updates by role
Sort updates by role: library staff, district administrators, curriculum leaders, teachers, and students.
Testing process
Test high-volume workflows with representative records, including reporting, circulation, holds, interlibrary loans, and reading programs.
Deploy a plan
Publish a short adoption plan with required permissions, training, local documentation, and a review date.
Defend Your Library Budget, Justify Every Decision, and Prove Program Value
If release updates are prompting your district to review how students participate in reading programs, the Defend Your Library Budget, Justify Every Decision, and Prove Program Value solution page provides broader context for connecting library workflows, classroom activity, and literacy goals.
FAQ
-
Start with the release version and products used by the district. Then identify the changes that affect high-volume workflows, permissions, reporting, and staff procedures before reviewing optional or lower-frequency features.
-
Not necessarily. Availability can depend on the release phase, hosting environment, product, configuration, permissions, and whether a feature is opt-in. District teams should confirm applicability in the release documentation or with their support or account team.
-
Use a familiar reporting question, such as circulation by site, collection activity, or sublocation. Compare the new workflow with the current process, check the output for accuracy, and document who should run, interpret, and share the report.
-
Test the tasks staff perform most often and the exceptions that create the most support requests. Include permissions, saved settings, exports, notifications, student-facing screens, and cross-site behavior when those functions are part of the update.
-
Involve the account team when the update raises questions about licensing, product expansion, enablement, deployment, or how to connect Destiny Engage, Classroom Library Manager, Destiny Resource Manager, or Library AI Assistant to the district’s current environment.
Summary
Destiny release information is most useful when a district translates feature notes into specific changes for library, curriculum, classroom, and administrative workflows. Confirm the applicable version, test the work that matters most, and use the review to identify both training needs and responsible next steps for existing Destiny users.
