IT consulting, software and support · Dhaka

+880 163 028 7321 WhatsApp
Webbly Consulting Solutions

Industries / University and higher education

Admission and results should not depend on one teacher's laptop.

We have built admission and tabulation software for departments at the University of Dhaka. We know how the regulation works, and we know who has to sign at each step.

Discuss Your Requirement See what we built

Delivered in this sector

University of Dhaka

Executive MBA admission software

Faculty of Business Studies, University of Dhaka

Examination tabulation software

Department of Finance, University of Dhaka

Where it breaks

Two places every department feels it.

Teaching is not the bottleneck. Admission season and tabulation season are.

Admission and registration

Paper forms and one Excel file

01

Application forms are collected by hand, then the same information is typed again for scrutiny.

02

Payment is verified by matching bank slips against a list, one by one.

03

The merit list is prepared in Excel by one or two teachers, usually at night, close to the deadline.

04

Viva and written test schedules are made manually, then changed over phone when clashes appear.

05

Quota and category seats are counted by hand, and one miscount means the whole list is revised.

06

Course registration each semester brings the same queue outside the same office door.

Examination and results

Tabulation is where the real risk sits

01

Marks arrive from first, second and third examiners on separate sheets, at separate times.

02

Moderation and averaging are done by hand, then checked by hand again.

03

CGPA is calculated against regulations that differ by programme and by batch year.

04

Improvement, retake and carry-over cases are tracked outside the main sheet.

05

One arithmetic slip means a published result has to be corrected, which is the worst outcome of all.

06

Publication waits for whichever tabulator is available, not for when the marks were ready.

Send us your regulation. We will read it first.

Before any proposal, we go through your grading rules, your committee structure and who signs at each stage. That is where these projects succeed or fail.

Discuss Your Requirement

What we build

Six systems, department by department.

Not one university-wide platform on day one. One department, one process, done properly.

01

Online admission portal

Application, document upload, payment verification and admit card, in one flow the applicant completes himself.

02

Automated merit list

Marks, quota, category and tie-breaking rules applied by the system, with the reasoning visible for every applicant.

03

Tabulation system

Examiner-wise mark entry, moderation, averaging and CGPA against the exact regulation for that programme and batch.

04

Result verification trail

Who entered which mark, who moderated it, and when. A correction is traceable instead of unexplainable.

05

Course registration

Semester registration, section capacity and clash checking, done by the student instead of at a counter.

06

Transcript and certificate

Grade sheets and transcripts generated in the approved format, with a record of every copy issued.

What we have already built at Dhaka University

Our work

Case study 01

Executive MBA admission software

Faculty of Business Studies, University of Dhaka

The problem

Executive MBA applicants are working professionals. Collecting forms, verifying payment and preparing the merit list by hand was taking weeks of teachers' time every cycle.

What we built

An admission system covering online application, document upload, payment verification, scrutiny by the admission committee, and merit list preparation against the programme's own rules.

What it changed

The committee now reviews applications on screen instead of in files, and the merit list is produced from the same data that was submitted, not retyped.

Why it mattered

Admission is the first thing an applicant sees of the programme. A professional process is part of the programme's reputation.

Read the full case study

Case study 02

Examination tabulation software

Department of Finance, University of Dhaka

The problem

Marks from multiple examiners, moderation, averaging and CGPA calculation were being done on paper and in spreadsheets, where a single arithmetic error can reach a published result.

What we built

A tabulation system with examiner-wise mark entry, moderation, automatic averaging and CGPA calculated against the department's regulation, including improvement and retake cases.

What it changed

Tabulation no longer depends on one person's availability or attention, and every figure in a grade sheet can be traced back to the examiner who gave it.

Why it mattered

A corrected result costs a department far more than a delayed one. The safest tabulation is the one nobody has to recalculate.

Read the full case study

How a result actually moves

Five steps, and a mistake at any one of them.

This is the flow a tabulation system has to protect, not replace.

01

Marks come in

Each examiner enters his own marks. Nobody sees another examiner's figures.

02

Moderation

Differences beyond the allowed range are flagged for the third examiner, not missed.

03

Averaging

Applied by the rule for that programme, the same way for every student.

04

CGPA

Calculated against the regulation for that batch, including improvement cases.

05

Grade sheet

Generated in the approved format, with the trail behind every figure.

Outcomes

What changes for the department

Teachers preparing merit lists at night

Produced by the system

Bank slips checked one by one

Payment verified on entry

Marks moved on paper between rooms

Entered once by the examiner

CGPA calculated by hand

Calculated by the regulation

Results wait for the tabulator

Ready when the marks are

A correction nobody can explain

Every figure has a trail

Why universities are different

A department is not an office.

Five conditions that decide whether the system is still used next session.

Condition 01

The regulation is the specification

Every programme has its own rules for averaging, grading and promotion, approved by the academic council. They cannot be simplified to suit software.

So the system must

We read the regulation first and build to it exactly, including the exceptions.

Condition 02

A published result cannot be wrong

A late result is a complaint. A corrected result is a much bigger problem, for the student and for the department.

So the system must

Validation before publication, and a trail behind every figure afterwards.

Condition 03

Authority is divided

Teachers, examiners, the tabulator, the chairman and the controller each have their own role and their own limit.

So the system must

Access is by role, so nobody can see or change what is not his responsibility.

Condition 04

Staff change every year

Committees rotate, tabulators change, and student assistants come and go.

So the system must

If it needs training every time, it will go back to paper. It has to be obvious.

Condition 05

Work comes in bursts

Nothing happens for weeks, then admission or tabulation arrives all at once.

So the system must

Built for the peak week, not for the average day.

Get in touch

Tell us which process is the problem.

+880 163 028 7321Call [email protected]Email Message on WhatsAppChat

Plot 22, Road 17, Sector 13,
Uttara West, Dhaka 1230, Bangladesh

Start a conversation
Talk on WhatsApp