T2 reviewed
Published entry path
Shown only where the public pricing source supports it.
R3 school workflow review
Verify adults near children with reviewed consent
Schools, daycares, and tutoring centers can scope annual verification for staff, transport drivers, tutors, vendors, and contractors while preserving consent, minimization, renewal, and support boundaries.
R3 reviewT2 reviewedStaff and transportMinor-sensitive controlsNo board approval claimNo safety guarantee
Sample preview — no real PII
Annual staff verification ledger
Transport drivers
Scoped role
Renewal trackedTutors
Consent pending
No secret checkVendor staff
Review queue
Manual reviewStudent data
Not required
MinimizedNo school-board approval or official audit-report automation is claimed.
R3
Rollout stage
Pilot, waitlist, and target capabilities stay labelled.
Consent
Processing posture
Pricing, volume, parent visibility, support, renewal, and audit materials require signed scope.
Audience stakes
Adults near children need careful verification workflows without unsupported board approval, safety guarantees, or unnecessary student data processing.
The redesign makes every page explain the buyer's operational world before asking for a conversion.
Workflow pressure
Schools users need verification that fits the way they already operate.
Consent pressure
The person being verified must see the purpose and consent before processing starts.
Evidence pressure
Teams need a readable signal and audit trail without exposing more PII than required.
Specialized module
Adult-near-children safeguarding workflow
Annual staff, transport, tutor, vendor, and contractor verification workflows for adults near children.
Schools teams
Operations owners
Compliance reviewers
People being verified
Who this is for
Role-based trust, not one generic buyer.
Each stakeholder gets the decision surface they need while the person being verified keeps consent and rights visible.
Schools owner
Risk, time, and decision clarity
PRAMAAN view: Status, consent, and exception queue.
Person being verified
Purpose, control, and correction
PRAMAAN view: Consent notice, report visibility, support and DSR routes.
Reviewer
What to do with an incomplete signal
PRAMAAN view: Review-needed state and responsible-use notes.
Workflow
Request, consent, signal, review, and audit stay connected.
The person being verified sees the purpose before checks run; the operator receives a decision-support signal and escalation path.
- Request1
Choose the purpose
The workflow starts with an explicit purpose and requester role.
- Consent2
Subject consents or declines
The person sees the purpose, support route, and sharing boundary.
- Review3
Reviewer sees permitted signals
Operational views prefer verdicts and status over raw identity documents.
Capabilities
Built around the segment's daily operating model.
Capabilities are useful only when the live/planned/target boundary is visible.
Schools workflow
A verification path shaped around this audience, not a generic form.
Consent record
Purpose, requester, timestamp, and support path are part of the result.
Role-based views
Operators see the signal they need without default access to raw documents.
Exception queue
Incomplete, disputed, or adverse signals route to manual review.
Rollout clarity
Live, supported, planned, target, and by-agreement capabilities remain marked.
Responsible use
The page explains what PRAMAAN does not replace or guarantee.
Consent and DPDP
Minor-sensitive consent posture
Adult-near-child workflows must keep purpose, role, consent, minimization, renewal, support, correction, DSR, and grievance routes visible.
Purpose shown before staff, tutor, transport, or vendor checks
No student or guardian data unless necessary and reviewed
Parent or committee views avoid raw reports by default
Refusal, incomplete consent, and manual review stay visible
Sample preview
Annual staff verification ledger
Every preview uses dummy, masked data and is labelled so it cannot be confused with a real report.
Sample preview — no real PII
Annual staff verification ledger
Transport drivers
Scoped role
Renewal trackedTutors
Consent pending
No secret checkVendor staff
Review queue
Manual reviewStudent data
Not required
MinimizedNo school-board approval or official audit-report automation is claimed.
Use cases
Specific workflows a buyer can recognize.
Primary workflow
Use PRAMAAN for the highest-frequency verification path.
Less document forwarding and clearer consent.
Exception review
Route amber, incomplete, or disputed signals to a human reviewer.
Better decisions without automatic rejection.
Renewal or expiry
Refresh signals when a badge, pass, or role context becomes stale.
No reliance on old screenshots.
Responsible use
Child-facing institution guardrails
The page avoids unsupported board, safety, legal, criminal, and parent-facing status claims.
No school-board approval claim
No official audit report automation unless implemented
No student data processing unless necessary and legally supported
Police verification requirements still apply where applicable
School workflow scope
T2 reviewed
Pricing, volume, parent or committee visibility, support, renewal cadence, and board/audit materials require a signed school workflow scope.
- No fixed public monthly price or included volume
- No official board approval claim
- No parent outcome or safety guarantee
School workflow review
R3
School workflows are R3. School names, counts, board acceptance, parent outcomes, safety outcomes, and pilot metrics are not published without approval.
Integration and operations
Institution rails
Separate school-facing status, parent/committee visibility, and government-school workflows.
Staff workflow
By agreement
Transport workflow
By agreement
Parent/committee view
By agreement
Board/audit packet
By agreement
Government school
Planned
Proof and pilot clarity
Proof and child-safety posture
School workflows are R3. PRAMAAN does not claim school-board approval, official safety certification, parent trust outcomes, coverage benefits, or live government-school deployment.
FAQ
Schools verification FAQ
Short, specific answers with consent, visibility, pricing, rollout, and limitation boundaries.
Related journeys
Move to the nearest workflow without losing context.
Review an adult-near-child verification workflow
Give staff, transport, tutor, vendor, and contractor roles a consented, reviewable, renewal-aware workflow without overclaiming safety outcomes.