Online Test Series Setup Checklist for Coaching Institutes

• Write the purpose of the test in one sentence.
• Define the intended learner group, level, and prerequisite knowledge.
• Record the current official rule source, syllabus or bulletin edition, and date checked.
• Decide whether the test is practice, evaluated, ranked, or qualifying.
• Assign one academic owner and one operations owner.

Output: a one-page test brief that every author, reviewer, and operator can use as the same source of truth.

• List every section and its order.
• Allocate question counts or marks across topics.
• Define an intended easy, moderate, and difficult mix.
• Choose supported question formats for each learning objective.
• Estimate realistic solving and review time by section.
• Reconcile section counts, total marks, and total duration.

Output: a versioned blueprint that can be checked against the final test before publication.

• Confirm every question is authorised for your institute to use.
• Use clear language; review examples for avoidable bias and verify that images remain legible on smaller screens.
• Have a second qualified reviewer independently check options, plausible distractors, and the answer key.
• Add a concise explanation or solution where result review will show one.
• Apply consistent topic and difficulty labels.
• Validate every import row and resolve errors before assembling the test.

Output: Edugenie currently supports manual question entry and validated CSV imports of up to 100 question rows per file; this is not positioned as unlimited migration.

Preparing rows in a spreadsheet? Use the question-bank CSV preparation worksheet and validation guide. It is a review worksheet, not a guessed upload schema.

• Set positive marks for each question or supported section rule.
• Set negative marks only where the exam design requires them.
• Define partial-credit behaviour for supported multiple-answer questions.
• Verify accepted responses for supported user-input questions.
• Calculate sample correct, incorrect, skipped, and partial answers by hand.

Output: a scoring reference with worked examples that academic reviewers and support staff can verify independently.

Need a worked example? Use the negative-marking, rank, and percentile guide to calculate a uniform score, compare percentile methods, and document tie rules.

• Set and review the opening and closing date and time.
• Confirm the total duration and any supported section timing.
• Choose the maximum number of permitted attempts.
• Decide whether question-order randomisation supports the test purpose.
• Define result timing, explanations, eligible ranking cohort, attempt used, and tie handling.

Output: Write these rules in learner-facing language and verify that the configured behaviour matches the instructions.

• State the time zone, allowed materials, timing, navigation, marking, submission, support, and result rules.
• Test mobile, tablet, and desktop layouts plus keyboard access, visible focus, zoom, and reflow.
• Verify answer states use understandable text or symbols as well as colour, and configure approved accommodations before launch.
• Confirm supported answers autosave during a live attempt.
• Test the permitted in-progress recovery path after an accidental exit.

Output: Autosave and resume reduce avoidable loss; they are not an offline-testing guarantee or a substitute for clear incident handling.

Accessibility: A time limit that is essential to an assessment does not remove the need for keyboard operation, visible focus, labelled controls, text-based errors, and a process for applicable accommodations. Do not claim WCAG compliance without auditing the complete workflow.

• Compare the assembled test against the approved blueprint.
• Have an independent reviewer solve every question.
• Compare expected and generated scores for representative answer patterns.
• Pilot timing, slow or interrupted connectivity, supported browsers, and representative devices.
• Inspect result totals, answer review, explanations, rank, and percentile behaviour.

Output: Record issues, the person responsible, resolution evidence, and the final approval version before opening the test to learners.

• Freeze and record the approved test version before launch.
• Tell learners where and how to report a genuine attempt issue.
• Review early attempts for configuration or content defects.
• Use a documented correction and communication process when required.
• After the test, review item performance, learner feedback, and operational incidents.

Output: Keep the original attempt and scoring evidence required for support or academic review; define retention with the appropriate legal and operational owners.