What support files are available and when to use them

KYBN generates a PPT report pack by default. Support files such as snapshot summaries, run manifests, and issue exports are available when teams need more review detail, cleanup support, or run traceability.

What these files are really for

The report pack is the main deliverable. The support files are there to help teams review what was counted, understand how a run was produced, and work through issues without digging back through the raw export from scratch.

They matter most when the conversation shifts from “show me the chart” to “show me what changed” or “show me how this run was put together.”

Short answer

The PPT report pack is the main output. The support files are there for the moments when a team needs something other than slides: a cleaner review record, a technical run record, or a row-level list of issues to fix.

Which files are available

PPT report pack

The main generated output. Use it when you need working charts and slides for recurring HR reporting.

Snapshot summary (PDF)

Use it when you want a review-friendly summary of what was counted for a specific run without opening the full report pack.

Run manifest (JSON)

Use it when you need structured traceability for the run, including metadata that helps with reproducibility or audit review.

Issue exports (CSV)

Use them when you need row-level detail for missing values, duplicates, conflicts, or other issues found during review.

When teams usually reach for them

Use the PPT report pack when the goal is to deliver charts and slides that can be reused or adapted.
Use the snapshot summary when you need a lightweight, review-oriented record of a specific output run.
Use the run manifest when someone asks how the run was configured or needs a more technical record.
Use issue exports when the work shifts from reporting into cleanup, reconciliation, or audit follow-up.

Which file to reach for first

You need a presentation-ready reporting output.

PPT report pack

It is the main business-facing deliverable and the file most teams circulate first.

A reviewer wants a compact record of what was counted in one run.

Snapshot summary (PDF)

It keeps the run easier to review without opening or editing the full slide deck.

Someone asks how the run was configured or what settings were applied.

Run manifest (JSON)

It preserves technical run details that help with traceability, reproducibility, and audit follow-up.

A cleanup owner needs row-level evidence for data issues.

Issue exports (CSV)

It gives the operational detail needed to correct missing values, duplicates, or conflicting records.

A simple way to think about it

PPT is the default output.
Support files are available on demand when needed.
They are meant to support review, traceability, and cleanup work around the report pack.

Why these files matter on recurring reporting cycles

On a one-off run, teams may only care about the finished deck. On monthly or quarterly cycles, the surrounding files become more useful because reviewers start asking what changed, what was counted, and where issues still need follow-up.

That is where support files stop being “extra downloads” and become part of the operating workflow. They reduce back-and-forth between reporting owners, data reviewers, and cleanup owners because each group can work from the file that best matches the task.

Common questions

Is the PPT report pack the main output in KYBN?

Yes. The PPT report pack is the default output and the file most teams use for recurring HR reporting. The other files exist to support review, traceability, and cleanup work around that main output.

When should I use the snapshot summary instead of the full report pack?

Use the snapshot summary when you need a lighter record of a single run, especially for review or sign-off, without opening the full deck or working through presentation slides.

What is the run manifest for?

The run manifest is for structured traceability. It helps when someone needs to understand how a run was configured, what metadata was attached to it, or how to reproduce or audit the output later.

When do issue exports become important?

Issue exports matter when reporting work turns into cleanup work. They provide row-level detail for missing values, duplicates, conflicts, and similar issues so teams can follow up in the source data.

Keep reading

For the broader reporting workflow, read Why HR reporting stays manual after the HRIS export. For the source-data setup behind the workflow, read One dataset, multiple reporting views. For the snapshot-date counting logic, read How KYBN determines active population for a selected snapshot date. For plan details, see Product & Pricing. For shorter answers, see the FAQ.

Open Workspace View Product & Pricing See all FAQs