Internal Inquiry Reports: A Practical Example for Libraries

When something goes wrong inside a library, gut feelings are not enough to fix it. If users keep complaining about long waiting times at the circulation desk, or if staff morale quietly drops, the management needs a clear, written account of what happened, why it happened, and what should be done next. That document is an internal inquiry report. It is one of the most practical pieces of formal writing a library professional will ever produce, because it turns a messy problem into an organised, evidence-based plan of action.

What an internal inquiry report is and why libraries need one 🔗

An internal inquiry report is a formal document prepared after an organisation investigates a specific problem within its own walls. The problem could be a service failure, a complaint, a workplace dispute, or a sudden drop in performance. The report records the facts gathered during the investigation and presents conclusions and recommendations to the people who can act on them.

Libraries are service organisations. Their success is judged almost entirely by how satisfied their users are. Research on academic libraries in the country has consistently shown that factors like responsiveness, reliability, staff knowledge, and communication strongly shape user satisfaction. When any of these slip, the effect is felt quickly. A formal inquiry helps a library find the root cause instead of reacting to symptoms.

The report matters for another reason too. It creates an official record. A well-prepared investigation document protects the organisation if a decision is later questioned, because every conclusion can be traced back to verifiable facts rather than opinion or assumption. This is why the structure and the language of the report are taken so seriously.

The BIBLIO library case study 🔗

Consider a fictional public library called BIBLIO. Over three months, the management noticed two linked problems. First, the suggestion box and feedback forms filled up with complaints about slow book issue and return, rude responses at the counter, and frequent system breakdowns. Second, two senior counter staff submitted written grievances about being overworked and unsupported. User satisfaction and employee satisfaction were both falling at the same time. The Director ordered an internal inquiry and asked a three-member committee to prepare a report.

Why a structured inquiry was the right response 🔗

The Director could have simply issued a circular telling staff to be polite and quick. That would have ignored the real cause. Library studies repeatedly find that user dissatisfaction often grows out of a weak relationship between users and employees during the service encounter, which itself can be a sign of deeper staffing or workflow problems. An inquiry forces the committee to look at both sides of the counter before drawing any conclusion.

Setting the terms of reference 🔗

Before collecting a single fact, the BIBLIO committee agreed on what it was investigating and what it would leave out. This is the terms of reference, and it keeps the inquiry focused. A good terms of reference statement sets out the scope of the work to be undertaken and the expected output such as findings and recommendations. For BIBLIO, the committee defined its task as examining the causes of user complaints and staff grievances at the circulation section over the previous three months, and recommending corrective measures. Pay and promotion policy were placed outside the scope, so the inquiry would not drift into unrelated territory.

Breaking down the report structure 🔗

A formal report follows a logical chain that moves from context to evidence to decision. Most business and investigation reports share the same core sections, organised so that a busy reader can find exactly what they need. The standard flow is background and scope, methodology, findings, conclusions, and recommendations. The BIBLIO report used this skeleton.

Executive summary 🔗

The executive summary comes first but is written last. It is a condensed version of the whole report for readers who may not study every detail. Good practice is to keep it to about one page, write it in plain language, and end it with a short recommendation for action. Crucially, an effective executive summary can stand alone, because decisions may be made on its strength alone. The BIBLIO summary stated in a few sentences that complaints were caused mainly by understaffing and an outdated issue-return system, that staff grievances were genuine, and that three corrective steps were recommended.

Terms of reference 🔗

This section repeats, in the report itself, the scope agreed at the start. It tells the reader exactly what the committee was asked to do and what it deliberately excluded. Placing it early prevents misunderstanding. If anyone later asks why the report said nothing about salaries, the terms of reference provides the answer.

Findings 🔗

The findings are the factual heart of the report. Here the committee presents what it discovered, in a neutral and objective tone, without yet drawing conclusions. The committee at BIBLIO described its methodology first: it reviewed three months of feedback forms, examined circulation system error logs, and interviewed staff and a sample of users. Describing how the investigation was conducted, including interviews completed and documents reviewed, is essential because transparency about method builds trust in the findings.

The actual findings were presented as facts. The circulation system had failed on eleven separate days. Two staff members were handling a counter designed for four. Average waiting time at peak hours was over twenty minutes. Each statement was tied to a specific piece of evidence. A strong report makes sure that every factual statement is supported by referenced evidence, so nothing rests on the writer’s memory or impression. Vague phrases such as “staff behaved badly” were avoided in favour of specific, observable behaviour.

Conclusions 🔗

Conclusions are where the committee interprets the findings and states what they mean. This section answers the question the inquiry was set up to ask. At BIBLIO, the committee concluded that the user complaints and the staff grievances were not two separate problems but two results of the same root cause: severe understaffing combined with failing equipment. The rude behaviour users complained about was largely a symptom of exhausted, overstretched staff. This is the point where the report links cause and effect, but it does not yet prescribe a remedy.

Recommendations 🔗

Recommendations set out the specific actions the organisation should take. Each recommendation must flow directly from a finding and a conclusion. The recommendation is advice, not a command, because the final decision rests with management. The BIBLIO committee recommended deploying two additional staff at the circulation desk during peak hours, replacing the unreliable issue-return system within the next quarter, and introducing a short staff training programme on user interaction. Because the conclusions had already shown the cause, these recommendations targeted corrective action that would stop the problem from recurring rather than simply punishing the staff at the counter.

Key takeaways for writing your own report 🔗

The BIBLIO example points to three skills that separate a useful report from a weak one.

Collect data before you write 🔗

A report is only as strong as the evidence behind it. Feedback forms, complaint records, system logs, and interviews all count as data. In a library setting, a suggestion box that gets timely responses can itself become a valuable source of user feedback. Gather facts first, then write. Never start with a conclusion and look for evidence to fit it.

Analyse in a structured way 🔗

Raw data is not analysis. Grouping related complaints under common themes makes patterns visible. Structuring a report by grouping related findings under a clear theme is a recognised practice in formal report writing, recommended in the guidance issued by the Institute of Internal Auditors. Themes turn dozens of scattered complaints into a handful of clear issues a manager can act on.

Make recommendations actionable 🔗

A recommendation that says “improve service” helps no one. A useful recommendation names the action, and ideally an owner and a timeline. The clearest investigation reports end with practical recommendations that guide corrective steps and prevent future issues, which is exactly what a template from the UK advisory service Acas builds into its standard investigation format through dedicated sections for findings and recommendations.

How internal inquiry reports improve organisational efficiency 🔗

An internal inquiry report does more than solve one problem. It builds an institutional memory. The next time a similar complaint pattern appears, the library has a documented precedent and a tested method for responding. It also forces clarity: writing the report compels managers to separate facts from assumptions, which often reveals causes that were invisible during day-to-day work.

For libraries specifically, this discipline supports a user-centred culture. When management responds promptly and positively to user input, it can enhance the overall user experience and meet evolving patron needs more effectively. The inquiry report is the bridge between a complaint and a genuine improvement. Without it, feedback piles up unanswered. With it, dissatisfaction becomes data, data becomes analysis, and analysis becomes a concrete plan that makes the whole organisation run better.

What do you think? If you were on the BIBLIO committee, which finding would you treat as the most urgent, and why? And in your own college or workplace library, what is one recurring complaint that a structured inquiry report could finally help solve?

References

1. https://journal.ilaindia.net/index.php/lib/article/view/1085
2. https://www.caseiq.com/resources/top-10-investigation-report-must-haves
3. https://digitalcommons.unl.edu/context/libphilprac/article/5748/viewcontent/auto_convert.pdf
4. https://wiseworkplace.com.au/wp-content/uploads/2021/08/DraftingaTermsofReference.pdf
5. https://www.business-in-a-box.com/template/business-report-D12762/
6. https://www.boisestate.edu/cobe/cobe-writing-style-guide/guidelines-for-reports/
7. https://adrinvestigations.com/investigative-report-writing-best-practices/
8. https://hr.un.org/en/faq/conclusions-and-preparing-investigation-report
9. https://www.researchgate.net/publication/384646646_A_Comprehensive_Study_On_Library_Service_Quality_Bridging_User_Perception_Gaps_And_Implementing_Effective_Improvement_Strategies
10. https://www.theiia.org/globalassets/site/auditing-report-writing-toolkit.pdf
11. https://www.acas.org.uk/investigation-plan-and-report-templates