Society worker verification without replacing the existing gate workflow

Challenge

The committee needed a consented way to verify recurring domestic help, drivers, and vendors without asking residents to exchange raw ID documents in chat groups.

Rollout / solution

PRAMAAN sits beside the existing society workflow. Residents and workers complete hosted consent; committee visibility is limited to status, receipt, and renewal signals.

Outcome status

Detailed outcome metrics will be published with the society's consent.

Workflow preview

What the story can safely show

Resident/worker invite

Hosted consent

Committee status view

Renewal signal

Timeline

Publication status

Intake

Pilot / seed workflow

Consent review

Outcome publication pending

Metrics disclosure

Outcome metrics are pending written consent. Detailed results will publish only after customer validation and approval.

Quote consent

Testimonials publish only with explicit quote approval. This page intentionally uses no invented quote.

What PRAMAAN learned

Safe product lessons

Avoid raw document sharing in informal channels.

A visible consent path reduces ambiguity.

Badge portability can reduce repeated proof requests where appropriate.

Story-specific guardrails

No society name or logo.
No resident quote.
No rollout date or metric until written consent.

Other proof shells

Consent-first candidate verification for a 15-year-old IT staffing firm Portable QR badge so workers do not repeat verification every month Verification workflow for teams that cannot run enterprise procurement