Facebook Pixel

From Sample File to Preview: Importing Student Records into eBiddyaPro

November 10, 2026

From Sample File to Preview: Importing Student Records into eBiddyaPro

Entering student information individually can become a demanding task during admission season. School staff must record names, verify dates of birth, organize class placement, and maintain consistent parent information. When hundreds of records are involved, repeating the same entry process can increase the opportunity for mistakes.

The eBiddyaPro Multi Student Import screen provides a structured starting point for adding multiple student records. It brings together a sample import file, academic placement selections, a file upload area, and a Preview Import button.

However, importing students successfully requires more than uploading a spreadsheet. Staff must prepare information in the expected format, select the correct academic context, examine the preview, and verify the resulting records after confirmation.

For schools in Bangladesh, this process can be useful when organizing admission registers, transferring approved records from existing spreadsheets, or preparing student information for a new academic session. This guide explains the workflow shown in the supplied eBiddyaPro screenshot and the practical reviews schools should complete before proceeding.

Understanding the Multi Student Import Screen

The supplied screen places Multi Student Import under Admission. It includes a Download Sample Import File button and an instruction panel explaining how the file should be prepared.

Below the instructions, staff can select an institute, branch, academic session, class, section, and shift. An Admission Date field appears before the file upload area.

The upload area displays support for XLSX, XLS, or CSV files, with a maximum size of 5 MB. The visible action button is Preview Import.

These details establish the preparation stage of the workflow. The screenshot does not show the preview results or final confirmation screen. The instructions do, however, explicitly tell users to preview the file, correct invalid rows, and then confirm valid students for import.

Why Student Import Preparation Matters in Bangladesh

A Bangladesh school may maintain student information across admission forms, registers, spreadsheets, and branch-level records. Moving these sources into a school management platform requires agreement on which information is authoritative.

A student’s English spelling may differ between a spreadsheet and an approved admission form. A birth date may have been entered using an ambiguous numeric format. A class list may include students who are still applicants rather than confirmed admissions.

The eBiddyaPro supplier’s practical guide highlights the need to distinguish applicants from enrolled students and transfer approved information into student records. That distinction is relevant before any bulk import begins.

Schools should establish which records are ready for import and resolve uncertain cases before including them in an operational student list.

Start with the Current Sample File

The instruction panel tells users to download the sample import file first. Staff should follow that instruction rather than adapting an unrelated spreadsheet from memory.

A sample file provides the expected column structure. Even if the school already has a detailed admission spreadsheet, its headings and layout may differ from what the importer expects.

The screen specifically instructs users not to change the sample file’s column headings. Staff should preserve those headings while transferring approved information into the appropriate columns.

Using the current sample also reduces confusion when an older template has been circulated among staff. The person preparing the file should record which downloaded template was used and keep the working copy clearly identified.

Understand the Required Columns

The visible instructions identify student_name, date_of_birth, gender, father_name, and mother_name as required columns.

These headings should remain exactly as provided in the sample. Staff should not replace them with translated labels or more familiar wording unless the current template explicitly permits that change.

Each student row should contain the required information in its intended column. A parent’s name entered under the student’s name may look plausible in a spreadsheet but produce an incorrect student record.

Before uploading, staff should review completeness and accuracy separately. A field can contain text and still be wrong. Successful formatting is only one part of preparing dependable student information.

Verify Names Against Approved Records

Names deserve careful review because they are reused in attendance, examination records, communication, and other school processes.

Staff should compare student and parent names with the school’s approved source documents. They should avoid guessing missing spellings or combining conflicting versions without authorization.

Bangladesh institutions may maintain both Bangla and English names. The supplied instruction panel identifies the required student_name field, but it does not establish every language-specific field supported by the downloaded template.

Schools should inspect the actual sample before deciding where additional name versions belong. Information should not be forced into an unrelated column simply because the school wants to preserve it.

Use the Specified Date of Birth Format

The instruction panel requires the Y-m-d format for dates of birth and provides an example such as 2015-01-30.

This places the year first, followed by the month and day. Staff should follow that order rather than using a format that could be interpreted differently.

For example, a value written as 05/06/2015 can be ambiguous when staff use different date conventions. The prescribed format reduces that uncertainty.

Spreadsheet applications may also change how dates are displayed or saved. Before upload, staff should inspect the final file and confirm that date values remain consistent with the template’s requirements. The preview should then be used to check how the importer interprets them.

Follow the Accepted Gender Values

The visible instructions specify male, female, or other as the permitted values for gender.

Staff should use the stated values rather than introducing abbreviations, Bangla translations, or inconsistent spellings. A school spreadsheet may contain several variations of the same category, but those variations should be standardized according to the current import instructions.

Standardization should reflect the approved information held by the institution. Staff should not change a student’s recorded details merely to remove a validation problem without checking the source.

If a case cannot be represented accurately using the available options, the school should seek clarification before proceeding with that record.

Keep Optional Information Blank When Unavailable

The instructions say to leave optional columns blank when information is unavailable.

This is an important data-quality principle. Entering invented phone numbers, placeholder parent details, or arbitrary dates can make a file appear complete while creating misleading records.

Staff should first confirm which columns are optional in the downloaded sample. Required fields should be resolved through the approved admission process.

Where optional information will be collected later, the school can maintain a controlled follow-up process. It should not assume that an empty field must be filled with a value such as “N/A” unless the template or support guidance allows it.

Select the Institute and Branch Carefully

The import form includes institute and branch selections. These choices should match the student group represented in the file.

The instruction panel states that the selected academic and institutional details apply to every imported student. A file containing students from different branches therefore needs careful preparation before it is uploaded under one branch selection.

A practical approach is to prepare separate batches for groups that share the same required placement. Staff should verify each batch against the approved class or admission list.

This avoids relying on an individual row to override the form selection when such behaviour has not been demonstrated.

Review Academic Session, Class, and Section Together

Academic session, class, and section identify the context in which students are being enrolled.

A correct student name imported into the wrong session can create confusion even when every personal detail is accurate. Similarly, selecting the right class but the wrong section can affect later class lists and attendance work.

Staff should review the full combination before choosing Preview Import. A familiar section label is not enough; Section A must belong to the intended institute, branch, session, and class.

Where the school is preparing a new academic session, administrators should also confirm that the required setup exists before importing students. Importing records is not a substitute for preparing the academic structure.

Understand the Roll Number Uniqueness Rule

The visible instructions state that roll numbers must be unique within the selected session, class, and section.

This means staff should review roll numbers in context. The same roll number may be meaningful in different groups, but duplicate numbers within the stated scope require attention.

The screen does not establish every duplicate-detection rule for student identities. Staff should not assume that a unique roll number guarantees the student has never been imported before.

A reliable preparation process compares the proposed batch with existing records as well as checking the file internally. The institution should confirm how the importer handles conflicts before processing a large batch.

Review Shift and Admission Date

Shift and admission date are also listed among the selections that apply to imported students.

Staff should confirm whether the entire batch belongs to the selected shift. A mixed morning and day-shift list should not be uploaded under one shared selection without understanding the outcome.

Admission Date should reflect the institution’s intended record. It should not be accepted automatically merely because a date is already displayed.

Where students have different admission dates, the school should confirm the supported approach. Separate batches may be appropriate, but the decision should follow the actual workflow rather than an assumption about row-level overrides.

Choose a Supported File and Respect the Size Limit

The upload area shows XLSX, XLS, and CSV as supported file types and displays a maximum size of 5 MB.

The instructions specifically refer to preparing the downloaded CSV sample. Staff should use that sample as the reference structure, even if another supported format is used after testing.

Changing a filename extension does not convert the file into a valid format. The file should be saved properly using the relevant application.

The screenshot does not show a maximum number of student rows. Schools should therefore avoid claiming unlimited imports or a particular row capacity. For larger datasets, they should ask for the supported batch size and test an appropriate working file.

Preserve Text and File Readability

Student data can be altered unintentionally while moving between applications.

Names may contain extra spaces, phone numbers may lose leading zeros, and Bangla text may become unreadable if a CSV file is saved using unsuitable text settings. The correct handling depends on the actual columns and supported importer behaviour.

Staff should reopen the saved file before upload and inspect representative records. This provides a basic opportunity to notice damaged text or shifted columns.

Where the school needs to import Bangla names or other special characters, a controlled test should confirm that those values survive preparation, preview, and final import accurately. Support should be consulted if the expected text does not display correctly.

Use Preview Import as a Review Stage

Preview Import is a significant part of the visible workflow. It gives staff a reason to pause before confirming the import.

The instructions direct users to preview the file, correct invalid rows, and confirm valid students. Staff should treat that stage as an opportunity to review both validation feedback and the meaning of the proposed records.

The supplied screenshot does not show the preview layout, its available controls, or its exact confirmation behaviour. These should be demonstrated in the school’s account.

A preview should not be assumed to mean that every record is already permanently saved. Equally, schools should confirm the actual behaviour before using live student data for their first test.

Correct Errors Without Guessing

When validation identifies a problem, staff should return to the relevant source information and determine why the row is invalid.

An incorrect date format may require a formatting correction. A missing required name requires verified information. A roll conflict may require checking class allocation rather than assigning an arbitrary replacement.

The screenshot does not establish whether invalid rows are excluded automatically, whether partial imports occur, or how a revised file is processed. Schools should confirm these details before finalizing a batch.

After making corrections, staff should review the updated preview again. Fixing one row should not replace a final review of the batch’s shared academic selections.

Prevent Duplicate Imports

A clear record of import activity can help staff avoid uploading the same group twice.

The school can retain the approved source file, the working batch name, the responsible staff member, and the confirmed outcome according to its information-handling policy.

If an upload appears interrupted, staff should check the student list before submitting the same file again. An unclear browser response is not sufficient evidence that no records were created.

The supplied screen does not establish whether importing an existing student updates the record, rejects it, or creates another entry. Those behaviours should be tested and documented rather than assumed.

Verify the Result in Student Manage

The screen includes a Student Manage link. After a confirmed import, staff should review the resulting student records through the appropriate management view.

They should compare the expected number of imported students with the actual outcome and inspect representative records for names, dates, parent information, academic placement, and roll numbers.

If the preview reports rejected rows, those students need a separate resolution process. The school should not consider the admission list complete merely because part of the batch succeeded.

Staff should also confirm any later processes they expect to use. Importing a student record should not automatically be treated as proof that login credentials, fee assignments, transport allocations, or guardian access have been completed.

Protect Student and Parent Information

Import files contain personal information about children and their families. Access should be limited to staff responsible for preparing, approving, and importing the records.

UNICEF’s school data-protection guidance explains that digital education systems require safeguards for children’s and staff members’ personal information. Although that guidance is not a statement of Bangladesh-specific legal requirements, it provides a relevant basis for careful handling of school data.

Schools should avoid circulating complete admission spreadsheets through unnecessary groups or personal accounts. Demonstrations can use fictional sample data, while support requests should include only the information needed to investigate the issue.

A Practical Example for a Bangladesh School

Consider a school preparing approved admissions for a new Class Three section.

The admission officer downloads the current sample file and transfers verified information from the approved register. A second staff member reviews student names, parent names, birth dates, accepted gender values, and roll numbers.

The officer selects the intended institute, branch, academic session, class, section, shift, and admission date. The prepared file is uploaded for preview.

Any invalid rows are investigated and corrected before the authorized confirmation step. After import, the team compares the student list with the approved admission register and reviews selected records.

This example describes a recommended school process. It does not claim that eBiddyaPro automatically performs independent verification or approval.

Frequently Asked Questions

1. What is Multi Student Import in eBiddyaPro?

It is the visible workflow for preparing a file containing multiple students, selecting shared academic details, and using Preview Import before the instructed confirmation stage.

2. Why should schools download the sample file first?

The sample provides the expected structure. Using an unrelated spreadsheet can introduce incorrect headings or column arrangements that do not match the importer’s requirements.

3. Can staff rename the sample column headings?

The visible instructions explicitly say not to change them. Staff should preserve the headings and enter information under the appropriate columns.

4. Which columns are required?

The supplied instructions identify student_name, date_of_birth, gender, father_name, and mother_name as required. Staff should also inspect the current downloaded sample for its complete structure.

5. What birth date format should be used?

The required format is Y-m-d, such as 2015-01-30. Staff should confirm that spreadsheet software preserves this format in the final file and preview.

6. Which gender values are accepted?

The instructions specify male, female, or other. Different abbreviations or translated values should not be introduced without confirming that they are supported.

7. What should happen when optional information is missing?

The instructions say to leave optional columns blank. Staff should avoid inventing values simply to make every cell appear complete.

8. Do the selected class and section apply to every student?

The instruction panel states that the selected placement information applies to every imported student. Batches should therefore contain students suited to those shared selections.

9. Can students from several branches be imported together?

The visible form uses a shared branch selection. Schools should prepare compatible batches or confirm an alternative supported method before mixing branch records.

10. Must roll numbers be unique?

Yes, within the selected session, class, and section, according to the visible instructions. Existing records should also be reviewed when checking for conflicts.

11. Are XLSX and XLS files supported?

The upload area lists XLSX, XLS, and CSV. The downloaded sample and the school’s tested workflow should guide file preparation.

12. What is the displayed file-size limit?

The upload area shows a maximum of 5 MB. The screenshot does not establish a separate row limit or unlimited import capacity.

13. Does Preview Import immediately complete admission?

The instructions distinguish preview from confirming valid students. Schools should demonstrate the actual confirmation process and verify when permanent records are created.

14. What should staff do with invalid rows?

They should investigate the issue, correct the source information or formatting, and review the revised preview. The exact handling of partial imports should be confirmed.

15. Can Bangla student names be imported?

The screenshot does not establish all text-handling behaviour. Schools should test representative Bangla values through preparation, preview, and final import before processing a full batch.

16. Does importing a student automatically create login credentials?

The supplied screen does not establish that outcome. Login creation and credential delivery should be confirmed separately in the configured workflow.

17. Does import automatically assign fees or transport?

That behaviour is not demonstrated. Student creation, fee assignment, and transport allocation should be reviewed as distinct processes unless an integration is verified.

18. What if an upload appears interrupted?

Staff should check the resulting student records before resubmitting. Repeating the file without checking can create uncertainty about duplicate or partially completed entries.

19. Will reimporting an existing student update the record?

The screenshot does not answer this. The school should test whether the importer rejects, updates, or duplicates an existing record under the relevant conditions.

20. Who should approve an import batch?

The institution should assign that responsibility. A second review by an authorized admission officer or administrator can help confirm accuracy before the final import.

21. What should be checked after import?

Staff should reconcile the outcome with the approved list and inspect important personal and academic fields. Rejected or missing students should be resolved separately.

22. How should a school evaluate this feature before adoption?

It should request a demonstration using a realistic sample, including valid records, errors, roll conflicts, preview, confirmation, and post-import verification.

Build Reliable Student Records from the Beginning

A well-prepared import file can help schools organize multiple student records through a consistent process. Its reliability depends on accurate source information, the current template, correct placement selections, and a careful preview.

The eBiddyaPro Multi Student Import screen provides clear starting instructions for required fields, date formatting, roll uniqueness, supported file types, and preview review. Schools can strengthen that process with assigned responsibilities and post-import reconciliation.

For an eBiddyaPro demonstration focused on student import and admission management in Bangladesh, contact 01853330354 / 01853330347. Ask to see the complete workflow from downloading the sample file to verifying the imported student records.