T3 reviewed
Published entry path
Shown only where the public pricing source supports it.
R4 mid-market branch ops
Coordinate branch verification without forwarding raw reports
PRAMAAN helps 50-500 person companies manage candidate, contractor, and vendor verification status across branches with consent evidence, role-scoped views, and reviewed rollout terms.
R4 mid-marketT3 reviewedBranch queuesConsent-firstNo automatic rejectionAPI by scope
Sample preview — no real PII
Branch HR dashboard
Delhi branch
42 candidates
11 pending consentBengaluru branch
88 contractors
7 amber reviewCSV import
May field cohort
SupportedAudit export
Branch packet
ReadyDummy cohort data. CSV/API status should be verified before production rollout.
R4
Rollout stage
Pilot, waitlist, and target capabilities stay labelled.
Consent
Processing posture
Bulk, branch, API, export, support, and migration terms follow current pricing or signed scope.
Audience stakes
Growing companies need one verification operating view without promising automatic HR decisions, legal clearance, or unscoped integrations.
The redesign makes every page explain the buyer's operational world before asking for a conversion.
Workflow pressure
Mid-Market 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
Mid-market branch operations
R4 mid-market branch HR playbook for scoped bulk, branch, API, and export workflows.
Mid-Market 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.
HR operations
Cohort progress and pending consent
PRAMAAN view: Branch dashboard with consent, completed checks, and amber review.
Branch manager
Local hiring status
PRAMAAN view: Branch-level queue and ageing items.
Compliance reviewer
Audit export and retention
PRAMAAN view: Exportable consent and status evidence.
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.
Mid-Market 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
Consent and DPDP-native workflow
Each page keeps consent, purpose, minimization, DSR, support, and grievance paths visible.
Explicit consent before checks
Purpose shown before processing
Operational views prefer signals over raw documents
DSR, correction, support, and grievance routes visible
Sample preview
Branch HR dashboard
Every preview uses dummy, masked data and is labelled so it cannot be confused with a real report.
Sample preview — no real PII
Branch HR dashboard
Delhi branch
42 candidates
11 pending consentBengaluru branch
88 contractors
7 amber reviewCSV import
May field cohort
SupportedAudit export
Branch packet
ReadyDummy cohort data. CSV/API status should be verified before production rollout.
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
Mid-market guardrails
PRAMAAN should not be positioned as automatic rejection, universal legal proof, guaranteed audit clearance, or a replacement for HR policy.
Existing BGV migration requires mapping and consent review
Branch privacy needs role-based access
Adverse signals require review
ATS/API integrations must be marked from source-of-truth scope
Mid-market pricing posture
T3 reviewed
Use current pricing or signed scope for monthly price, included checks, branch access, API, migration, support, export, and refund terms.
- No hard-coded included volume without approval
- No ATS/API entitlement unless scoped
- No audit-outcome promise
Mid-market branch ops
R4
Mid-market copy is reviewed before claiming included volume, ATS/API availability, audit outcomes, customer metrics, or migration/backfill support.
Integration and operations
Bulk, CSV, and API status
Mid-market teams can begin with dashboard workflows and evaluate bulk, API, webhook, migration, or ATS readiness as scoped production steps.
Dashboard queue
Supported
Branch dashboards
By agreement
Bulk / CSV
By agreement
API / webhooks
By agreement
ATS sync
By agreement
Proof and pilot clarity
Mid-market proof clarity
Talpro in-house use can be referenced as internal proof. Named customers, branch counts, cohort metrics, savings, and time-to-hire claims require approval.
FAQ
Mid-Market verification FAQ
Short, specific answers with consent, visibility, pricing, rollout, and limitation boundaries.
Related journeys
Move to the nearest workflow without losing context.
Unify verification across branches
Move verification out of spreadsheets and into a consent-first operating view with plan-scoped support and integrations.