Question 1

Can I use KYBN with an Excel employee list instead of an HRIS export?

Accepted Answer

Yes. KYBN can work with a maintained employee spreadsheet if it includes enough of the fields used for the workflow, such as employee ID, hire date, termination date, status, employment type, department, location, and other reporting fields.

Question 2

What fields do I need in my HR file?

Accepted Answer

KYBN works best when the file includes employee ID, hire date, termination date, employee status, employment type, department, location, job title, manager, and other fields used for reporting or follow-up. Not every output uses every field, but missing key fields can limit snapshot logic, split charts, or audit checks.

Question 3

Why not start with an active-only list?

Accepted Answer

Because an active-only list answers only one point-in-time question. KYBN works better from a fuller employee extract or maintained employee master file so you can choose the snapshot date inside KYBN, review data quality, and support the same dataset across point-in-time reporting, movements, and follow-up exports.

Question 4

Do I need to export a date-filtered active list from my HRIS first?

Accepted Answer

No. KYBN works best from a fuller employee extract, not just a date-filtered active list. You choose the snapshot date in KYBN, and the active population is determined using mapped source fields such as hire date, termination date, and status.

Question 5

What kinds of files can I upload?

Accepted Answer

KYBN currently supports CSV and XLSX files, including fuller HRIS exports, shared employee master files, and manually maintained employee lists. The best source is the file your team already maintains for recurring HR reporting, not a narrow one-off export made for a single question.

Question 6

What should HR check before sending headcount numbers?

Accepted Answer

Before sending headcount numbers, HR should check the selected snapshot date, active population rules, duplicate employee IDs, missing hire or termination dates, employee status, employment type, department, location, and any fields used for reporting splits. KYBN makes those checks visible before outputs are generated.

Question 7

What is the difference between PPT Pack, Daily Workbook, and Audit Workbook?

Accepted Answer

PPT Pack is for reusable charts and reporting slides. Daily Workbook is for operational employee lists and day-to-day follow-up. Audit Workbook is for deeper field checks, issue review, and audit-oriented support. Standard includes all three output types.

Question 8

Does KYBN replace my HRIS, dashboard, BI tool, or ChatGPT?

Accepted Answer

No. KYBN does not replace your HRIS, spreadsheet, BI dashboard, or AI assistant. It helps HR teams turn employee exports into reviewed, reusable outputs for recurring reporting and follow-up work.

Question 9

Can I try KYBN without uploading real employee data?

Accepted Answer

Yes. New users can start with sample outputs or a sample workspace before using real employee data. The first offer also includes one free PPT Pack, one free Daily Pack, and one free Audit Pack so teams can review the workflow before subscribing.

Question 10

Will my HR data be used to train AI models?

Accepted Answer

No. KYBN does not use customer HR files to train AI models. Uploaded files are used only to support the customer’s selected review and output workflow.

Question 11

Is KYBN safe for employee data?

Accepted Answer

KYBN is designed for intentional HR file review workflows with security, privacy, retention, and deletion controls. Each company should still complete its own vendor and security review before uploading employee data, especially for more sensitive fields.

Question 12

What sensitive fields should I avoid uploading?

Accepted Answer

Avoid uploading fields such as SSN, government ID, bank details, health data, date of birth, home address, or detailed compensation unless the selected workflow explicitly requires them. Start with the minimum necessary fields for the task.

Question 13

Does KYBN require API access to my HRIS?

Accepted Answer

No. KYBN currently works from uploaded HRIS exports or maintained employee files rather than requiring live API access to your HRIS. That makes it a review and output layer, not a real-time integration or system-of-record automation tool.

Question 14

Can I delete uploaded HR files and generated outputs?

Accepted Answer

Yes. KYBN supports deletion workflows for uploaded files and generated outputs, and deletion activity can be reviewed from the Data Lifecycle dashboard. Some minimal lifecycle or operational records may remain for traceability, security, or service operations.

Question 15

Why would I pay monthly if I only report once a month?

Accepted Answer

KYBN is designed for recurring HR reporting cycles, not one-off file conversion. A monthly workspace helps teams reuse setup, review updated files, compare runs, generate new outputs, keep support files, and manage deletion or lifecycle records across reporting periods.

Question 16

When is KYBN not the right fit?

Accepted Answer

KYBN may not be the right fit if you need a full HRIS, payroll processor, benefits administration system, employee self-service portal, case management system, or real-time BI dashboard connected directly to every source system.

Question 17

What’s the difference between Basic and Standard?

Accepted Answer

Basic is a lighter starting point for the core workflow, shared core field review, and PPT Pack export. Standard is the main working plan for teams that need Daily Workbook, Audit Workbook, compare, stronger review support, and broader recurring reporting value.

Frequently asked questions

Need the fuller explanation?