How can we help you?

Vidyapeeth360 helps authorised school staff prepare student records and consent evidence for UDISE+ and APAAR work. Government portals, the school's official records, and the instructions issued for the relevant cycle remain authoritative. The product does not generate an APAAR ID, submit a government filing on the school's behalf, or represent a generally available live UDISE+, Aadhaar, DigiLocker, or ABC synchronisation.

What the workspace does

• Shows coverage and missing-field findings for supported identity fields, including a missing PEN. It does not currently validate every possible PEN format.
• Lets authorised staff review and correct supported fields inline.
• Captures versioned guardian-consent decisions and can send a time-bound consent link through a configured communication channel. Provider acceptance or delivery is separate evidence.
• Previews and imports APAAR IDs after the government has generated them. Unmatched rows are skipped for review.
• Prepares supported CSV exports for school review and later submission through the applicable government process. An export is not proof that a government portal accepted the record.

Aadhaar is stored only as the last four digits in this workflow, not as a full Aadhaar number.

Step by step

1. Confirm the school's UDISE code and the current government instructions outside Vidyapeeth360.
2. Open Compliance and review the readiness counts and missing-field findings.
3. Correct only the fields supported by the inline review and verify them against the school's source documents.
4. Capture and review guardian consent where required. Messaging depends on the configured channel, consent policy, and provider evidence.
5. Export the supported file and inspect it before using the applicable government portal or authorised process.
6. After an APAAR ID is generated externally, preview the PEN/admission-number mapping and import only reviewed matches.

Compliance scan and explanations

The pre-submission scan is deterministic and reports the rules currently implemented by the product, such as missing identity fields or consent evidence. It is not a legal opinion and is not an exhaustive government validation. When an eligible Aira workflow is enabled, a supported explanation uses the rule and aggregate count rather than the student row; generated wording still requires staff review.

Boundaries to keep visible

• Vidyapeeth360 prepares and records evidence; the government system generates the APAAR ID.
• A consent record does not prove message delivery or replace the school's responsibility to verify authority and current requirements.
• DigiLocker/provider adapter code does not prove a configured, generally available live connector. Confirm deployment-specific integrations during implementation.
• A clean readiness score or exported CSV does not prove government acceptance.

FAQ

Q: Do we store a parent's full Aadhaar number in this workflow?

A: No. This workflow keeps only the last four digits. Verify the permitted identity process with the school's authorised policy.

Q: What happens if a parent does not consent?

A: The student is excluded from product actions that require recorded consent. The school remains responsible for the official process and any lawful alternative.

Q: Does Vidyapeeth360 create the APAAR ID or push it live to DigiLocker?

A: No general live-generation or synchronisation claim is made. The product prepares records, captures evidence, exports reviewed data, and can import an ID after it is generated externally.