Handbooks, manuals and donor rules, answered with the page.

The sentence we hear

“Which rule applies to a student who missed the add-drop deadline, and where is it written?”

The problem

Admission rules, fee schedules, academic regulations, course files and notices sit in handbooks, PDFs and a decade of circulars. Front-desk staff answer from memory, students ask on social media, and three offices give three answers.

What changes

• Staff and students ask the way they speak, in Bangla, English or both.
• Bahlul SI answers from the regulations, handbooks, course files and notices the registrar's office loaded, and names the document and page.
• Public documents go first; nothing a student may not see is loaded in the first phase.
• When the handbooks do not hold the answer, it says so.

What stays with a person

The registrar's office approves every source, and a named officer confirms any answer that changes a student's standing or fees.

The result

The same sourced answer at every desk and campus, with fewer calls to the registrar's office.

Draws on

The sentence we hear

“Our field offices phone Dhaka to ask what the donor allows, and Dhaka phones the donor.”

The problem

An NGO runs several programmes, each with its own manual, donor agreement, procurement thresholds, per diem rates and reporting formats. Field offices have weak internet and a printed copy that is two versions old. Audit findings often come down to a rule nobody could find on the day.

What changes

• Programme manuals, donor agreements and procurement rules are loaded once, with the version and date marked.
• A field officer asks in Bangla and gets the clause, the threshold or the format, with the document and page.
• A Team server in a regional office answers on the local network when the link to Dhaka drops; new versions sync from the country office when it returns.
• Every question is logged, so the audit trail shows what was asked and which version answered.

What stays with a person

The programme head confirms any answer that commits money or changes a report to a donor.

The result

Field offices work from the current manual, and fewer audit findings come down to a rule nobody could find.

Draws on

The sentence we hear

“Every branch manager has a copy of the operations manual, and no two copies are the same version.”

The problem

Loan products, the operations manual, the regulator's circulars and internal office orders change often. Field officers carry what they remember, and head office answers the same questions by phone every day. Member records are the most sensitive data the institution holds, and they stay out of this.

What changes

• The operations manual, product rules and the regulator's circulars are loaded with their dates; old versions are retired, not deleted.
• A field officer or branch officer asks in Bangla and gets the rule with its page, from a server in the head or regional office.
• No member file, loan ledger or identity document is loaded in the first phase; the answer comes from rules, not records.
• The log shows who asked what, which the internal audit team can read.

What stays with a person

The branch manager confirms any answer before a member is told what they are owed or must pay.

The result

Every branch works from the same current manual, and head office answers fewer phone calls.

Draws on

The sentence we hear

“We hold records on 20,000 students and nobody has a list of where they all are.”

The problem

Admissions files, transcripts, scholarship forms, member registers and payroll sit across departments, spreadsheets and paper. The Personal Data Protection Act 2026 asks for consent, notice, security measures and breach notice, and fines reach BDT 25 lakh, or BDT 50 lakh for significant data controllers, once the transition ends (confirm with counsel). Before any of this touches Bahlul SI, the institution needs to know what it holds.

What changes

• A data inventory lists every store of personal data, its class, its owner and who may see it.
• The inventory decides which document sets Bahlul SI may read in a later phase, and which stay out.
• Policies, notices and a breach procedure are drafted in Bangla and English and reviewed by a partner law firm.
• Permissions on the SI server follow the register, linked to the institution's existing staff accounts.

What stays with a person

The institution's data owner, or its Chief Data Officer where the Act requires one, signs the register and every change to it.

The result

A register of processing, a set of reviewed policies and a clear line between what SI may read and what it may not.

Draws on

The sentence we hear

“In admission season the phone line is busy from nine to five, and most calls ask the same five things.”

The problem

Applicants and members ask about deadlines, documents, fees and branch hours. A busy line or an unanswered message costs an application or a repayment visit. Chat and voice in Bangla is the second SI pattern, and it is built only after the helpdesk has passed its test.

What changes

• A chat window on the website, and later a voice line, answers in Bangla from the published notices and FAQs.
• Every answer names its notice, and anything about a named person is handed to staff.
• Questions the notices do not cover are logged, so the notices improve.
• Each new channel is tested in Bangla before it goes live, like the first.

What stays with a person

An admissions or member services officer handles every handover and reviews the log each week.

The result

Routine questions answered at any hour; staff time kept for the questions that need a person.

Draws on