Prepare and correct a school submission
A practical workflow for checking office identity, preparing school information, confirming a saved submission and requesting a correction.
Published 17 October 2026 · Publisher: Munish Pathak · About this independently operated site
1. Confirm the office and the request
Start with the request title, the office level and the reporting period. Different school tasks may have different requests and reporting periods. When a form uses a UDISE lookup, check the school name returned by the lookup before filling in the remaining fields. A successful lookup is not a reason to continue if the returned school is different from the one you intended.
In an account workspace, also check the active role and selected district. The district selector narrows the information displayed; it does not grant access to an office outside your assignment. If the office is absent, contact your administrator instead of entering the same information under another school.
2. Prepare a working copy
Collect the information actually requested by the form. Keep counts for the same period and separate a zero count from information that has not been checked. For example, a confirmed count of zero and a blank value have different meanings. Do not copy last period's figures solely to make every field look complete. If the form does not explain how to represent an unknown value, ask the request owner.
For a staff list, review spelling and the person's current school or office against your own records. Collect only the details the request requires. Do not add personal identification numbers, passwords or unrelated documents in a comments field.
3. Check before saving
- Read the school or office identity once more.
- Check that totals and their component counts refer to the same period.
- Review names, dates and any uploaded attachment.
- Keep a working copy until the portal confirms that saving succeeded.
Closing a browser tab is not confirmation of a saved submission. Read the result displayed by the form. If a connection fails and you do not receive a result, check the existing submission before trying again; this avoids treating uncertainty as a reason to create a second record.
4. Keep evidence of the saved version
Where your account offers My Submissions, use it to check the request, office, submitted time and revision. An available download can be kept with the supporting records for that request. A browser's earlier working copy and the saved portal version may differ, so use the version actually shown as submitted when discussing a correction.
5. Request a correction without losing context
Reading and editing depend on the request settings. If an entry is locked, send the responsible request administrator or portal administrator the request title, office identity, field to correct, proposed value and reason. An authorised person may reopen the submission when the request allows it. After resubmitting, confirm the new result and keep track of the revision. Do not send login credentials with the request.