Creating, targeting, and managing policies at scale

No. The content editor is Gmail-like, so any HR, compliance, or operations manager can use it without technical training. It supports: copy-paste from Word (formatting preserved), bulk PDF upload, rich text formatting (tables, font color, size, bold, links), and media embedding (images, GIFs, YouTube videos, audio). IT is only involved in initial setup (AD integration, HRMS sync, email gateway), not day-to-day policy operations.

Yes, by design. Copy-paste from Word into the editor preserves formatting. PDFs can be bulk-uploaded and are immediately searchable. For organizations with 50–500+ existing policies, migration effort is measured in hours or days, not weeks. AI enhancement features (summaries, translations, audio) can then be applied to existing content without requiring any rewriting.

Maker-Checker is a governance workflow where a policy created by one admin (Maker) must be reviewed and approved by designated approvers (Checkers) before going live. Recommended or mandated by RBI and other regulators for operational documents, it prevents unauthorized policy publications. The platform maintains a complete trail of who created, who approved, when, and any review comments. This audit trail is available for regulatory inspection.

Any admin with appropriate access can Unpublish a policy instantly, removing it from the employee-facing library with a single click. The urgency of this capability matters most in FSI: when regulatory guidance changes and an existing policy is no longer compliant, the window between the change and the policy update is a risk window. Being able to retract and re-publish in minutes rather than days reduces that window materially.

Targeting is multi-dimensional and combinable: Department, Designation, Grade, Location (state, city, or specific branch), Gender, or a specific list of individual employees. Filters combine, so you can publish to "all female employees at Grade 6 and above in Maharashtra branches." This precision makes policy libraries genuinely personalized, directly improving relevance and read rates.

Yes. The Future Employees feature publishes policies now with instructions to automatically distribute them to any employee who joins and matches the specified profile criteria. When a new joiner is added to HRMS and synced, they receive all relevant pending policies automatically, with no manual action required. Makes onboarding compliance systematic and scalable, particularly for campus hiring and branch expansion.

"Resend to Unread Only" filters for only those employees who haven't opened a specific policy and sends a fresh notification exclusively to them. Rather than a blanket re-notification to all employees (including those who already read and attested, creating noise and resentment), this targeted approach focuses administrative energy on the actual non-compliance problem and avoids the "cry wolf" effect where employees start ignoring notifications.

Yes. Beyond segment-level targeting, the platform supports individual employee targeting, useful for scenarios where a policy is relevant to a specific person (e.g., a confidentiality clause relevant only to employees with access to specific data systems), or for follow-up distributions to employees flagged as non-readers in the compliance dashboard.

Because the platform integrates with your HRMS, employee profile updates (department transfers, designation changes, location moves, grade promotions) sync automatically. When an employee's profile updates in HRMS, PolicyCentral.ai re-evaluates which policies are relevant. Policies for the new role are queued automatically; policies no longer relevant are removed. Transferred employees don't operate with a policy library from their previous role, a common compliance gap in static distribution systems.

Yes. The Top Deck feature allows admins to highlight critical policies. They appear at the top of every employee's dashboard in a visually distinct pinned section. The "Add Sender's Name" feature associates a named executive with a policy (e.g., "Published by the Chief Risk Officer"), adding authority and urgency. Combined, these tools signal priority without resorting to mass email blasts.

A department-based folder structure mirrors your organizational hierarchy: HR policies under HR, InfoSec under IT, product policies under Operations. Each employee sees only folders and policies relevant to their profile. Administrators with cross-department visibility see the full library with filters by department, date, version, and read status.

Archived, not deleted. All previous versions are maintained in a version history log accessible to admins but not surfaced to employees by default. Employees always see the current version; admins and auditors can retrieve any historical version with its original publish date, approver trail, and associated compliance data. Essential for regulatory audits where inspectors ask: "What was your AML policy in Q2 FY24, and do you have evidence employees were aware?"