ZBrain Version 2.4.6 | Jan 29, 2026

Overview

ZBrain HR JD Builder is an AI-powered solution that enables organizations to create, standardize, validate, and govern job descriptions across their entire lifecycle. This release enhances administrative control, governance, and consistency through configurable intake forms, structured JD output management, transparent anomaly validation, and robust dataset administration. It also strengthens JD generation and approvals with mandatory validations, automated anomaly correction, and an integration-driven approval gate, making it easier for HR teams to manage high-quality, compliant job descriptions at scale.

New features

Intake form configuration

Navigation: ZBrain → Solutions → HR JD → Admin Panel → Intake Form

HR JD Builder allows administrators to configure and manage the intake form used to create job descriptions(JD). From the admin panel, users can view a predefined set of JD fields, adjust instructional placeholder text, reorder fields, and manage field behavior through a dedicated configuration panel. All changes are persisted and applied across subsequent JD creation flows, ensuring consistent data capture and standardized inputs across the organization.

Key outcomes

• Standardizes how job information is captured across teams

• Reduces errors through controlled, predefined fields

• Improves consistency and completeness of JD inputs

JD output configuration

Navigation: ZBrain-> Solutions-> HR JD-> Edit App -> Edit JD Output

The JD Output configuration enables administrators to define the structure of the final generated Job Description. Users can toggle predefined output sections on or off, reorder sections, and define the exact sequence in which sections appear. These settings directly determine the layout, visibility, and structure of the final JD, providing greater flexibility while maintaining consistency.

Key outcomes

• Full control over JD structure and section visibility

• Ensures consistent JD formatting across roles and regions

• Allows customization without compromising governance

Anomaly rules visibility

Navigation: ZBrain-> Solutions-> HR JD-> Edit App -> Anomaly Rules

The anomaly rules section provides a read-only view of all predefined validation rules applied during JD generation. These rules cover incorrect content, bias, vague statements, missing sections, and incomplete sections. While not editable, this view offers transparency into how the system evaluates and corrects JDs before finalization or publication.

Key outcomes

• Improves trust through transparent validation logic

• Ensures fairness, clarity, and compliance in JDs

• Eliminates manual review guesswork

Dataset management

Grade codes

Navigation: ZBrain-> Solutions-> HR JD-> Edit App-> Dataset-> Grade Codes

Administrators can manage grade codes to define country-specific exemption status and salary configurations. The dataset supports creating, editing, and deleting Grade Codes, configuring FLSA status, country selection, and salary structures, including default or min–mid–max salary ranges. These grade codes are used during JD generation and approval workflows.

Key outcomes

• Enables consistent compensation alignment across JDs

• Supports country-specific exemption and salary logic

• Reduces downstream HRIS and payroll inconsistencies

Country sets

Navigation: ZBrain-> Solutions-> HR JD-> Edit App-> Dataset-> Country Set

Country sets allow administrators to group multiple countries and associate them with relevant Grade Codes and EOE statements. Country Sets support flexible configuration, multi-country selection, country-aligned grade code mapping, and optional EOE inclusion, enabling accurate regional compliance and compensation mapping during JD generation.

Key outcomes

• Simplifies multi-country JD management

• Ensures region-appropriate EOE and grade code usage

• Reduces compliance risks in global hiring

Physical requirements

Navigation: ZBrain-> Solutions-> HR JD-> Edit App-> Dataset-> Physical Requirement

The physical requirements dataset allows role-specific physical requirement content to be defined and maintained. Entries can be reordered, edited, or removed, and are dynamically applied during JD creation to ensure role-appropriate physical requirement disclosures.

Key outcomes

• Clear role-specific physical requirement disclosure

• Consistent application across JDs

• Reduced compliance and accessibility risks

Hierarchy

Navigation: ZBrain-> Solutions-> HR JD-> Edit App-> Dataset-> Hierarchy

The hierarchy dataset enables administrators to define organizational role levels along with associated education and experience requirements. Roles can be reordered, edited, or removed, providing structured guidance for JD generation based on organizational seniority.

Key outcomes

• Aligns JDs with organizational role structures

• Ensures consistent seniority and qualification standards

• Reduces ambiguity in role expectations

Company settings

Navigation: ZBrain-> Solutions-> HR JD-> Edit App-> Company Settings

The company settings section allows administrators to manage the company-level context used during JD generation. Users can configure the company name, industry, description, offerings, and upload a company logo. Saved settings are automatically applied during JD generation and validation to ensure brand and contextual consistency.

Key outcomes

• Ensures brand-consistent job descriptions

• Reduces repetitive company-level input

• Improves JD contextual accuracy

Final job description generation

Navigation: ZBrain-> Solutions-> HR JD-> Create New

Job description creation now enforces mandatory field validation and dynamic dependency handling, such as department-based sub-department selection. The system generates a read-only JD preview that includes both user-provided and system-generated sections. Detected anomalies are automatically fixed and logged in an Anomaly Panel with detailed change tracking. Users can download, edit, save, copy, or delete Job Descriptions as part of a governed lifecycle.

Key outcomes

• Produces complete, compliant JDs by default

• Automatically detects and fixes inconsistencies

• Improves confidence in final JD quality

Job description lifecycle actions

Users can copy existing job descriptions to create new ones while preserving original data. Copied JDs require mandatory field updates before saving to prevent duplication errors. Job descriptions can also be permanently deleted from the list view, ensuring clean and accurate JD management.

Key outcomes

• Faster JD creation through the reuse of existing content

• Prevention of duplicate or conflicting job descriptions

• Cleaner, more reliable JD repository with controlled deletion

Improvements

Admin panel terminology

Navigation: ZBrain-> Solutions-> HR JD-> Top Right (Admin Panel)

The edit app option has been renamed to admin panel across the application. This update clarifies the purpose of the section and provides centralized access to all configuration and setup components required to manage the HR JD Builder.

Key outcomes

• Clearer navigation and terminology

• Improved admin usability and discoverability

Hierarchy flexibility

Navigation: ZBrain-> Solutions-> HR JD-> Top Right (Admin Panel)-> Data set-> Hierarchy-> Select Role

The education and experience fields in the hierarchy dataset now support free-text input. This enhancement allows administrators to enter detailed, descriptive qualifications and experience requirements instead of being limited to predefined or numeric values.

Key outcomes

• Greater flexibility in defining role expectations

• Supports nuanced and senior-level roles

• Improves JD accuracy and realism

Integration section and approval gate

Navigation: ZBrain → Solutions → HR JD → Admin Panel → Integration Section

The approval section has been renamed to the integration section without impacting existing functionality. The integration section now serves as a mandatory approval gate and includes a configurable set of integration-related fields. These fields must be reviewed and completed before a job description can move from draft to approved status, ensuring completeness and readiness for downstream systems and integrations.

Key outcomes

• Enforces structured, auditable JD approvals

• Ensures integration readiness before approval

• Prevents incomplete JDs from being finalized