All modules Leadership & Analytics

Library Reports software for Indian schools

Issues and overdues

Feature identity
Library Reports
An illustration, not a screenshot. The interactive example below shows what this capability actually does.

Library Reports in a school workflow

Filter-aware example

School scopeSelected periodAuthorised columns

Evidence fieldSourceReview state

Issue, return and overdue tracking with live fine accrualScoped school recordReviewable

Fines outstanding vs collected in the module summaryScoped school recordReviewable

Reservation-queue visibility with waitlist positionsScoped school recordReviewable

Category facets computed across the whole catalogueScoped school recordReviewable

Code-native illustrative example · not live product UI · no customer dataExample labels and outcomes come from this capability's reviewed catalogue record.

Product scope

What it does

Library KPIs at a glance — titles, copies, currently issued, overdue count, fines outstanding vs collected, reservations waiting — with live accrued fines shown on open overdue loans. Book-360 shows a title's loan history and availability in one view.

The school problem

School teams need a dependable way to handle Library Reports: Issues and overdues. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

Issues and overdues.

Issue, return and overdue tracking with live fine accrual
Fines outstanding vs collected in the module summary
Reservation-queue visibility with waitlist positions
Category facets computed across the whole catalogue

Operational result

What your school gets

Current circulation, overdue, fine and reservation indicators tied back to books, copies and loans.

Access and ownership

Who typically uses it

Librarian
School administrator
Principal

What each person can actually see depends on the role you give them and which classes or records you assign.

Availability and setup

What to confirm before rollout

Included from Growth

Catalogue, circulation and library-report workflows.

A plan that includes Library, plus circulation history
Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Connected operating context

Available workflows

These are the documented neighbouring capabilities that school teams may review with this module. A related page does not imply that every hand-off is automatic or enabled in every plan.

Explore all modules

Buyer questions

Frequently asked questions

The questions school owners ask before they subscribe: what it does, who can see it, and what to set up first.

Does Library Reports work on its own?

Library Management, Export Excel are the documented neighbouring capabilities. They help a school evaluate the surrounding hand-offs, but a related page does not mean every integration is automatic or included in every plan.

What should our school prepare before enabling Library Reports?

A plan that includes Library, plus circulation history. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Is AI used in Library Reports?

No AI capability is asserted for Library Reports. Its documented work remains controlled by school records, roles and permissions.

How do we confirm the plan and implementation scope?

Library Reports is included from Growth in the current public plan matrix. Final rollout scope, services and external dependencies are confirmed in your written proposal.

See the Leadership & Analytics workspace Compare plans and commercial costs

See it in your school context

Run library reports the connected way.

See how this workflow fits your school's current records, roles, plan and rollout requirements.