> For the complete documentation index, see [llms.txt](https://orglayout.gitbook.io/orglayout-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://orglayout.gitbook.io/orglayout-docs/auditing-workday-and-excel-rosters-before-exporting-16-9-org-chart-decks.md).

# Auditing Workday & Excel Rosters Before Exporting 16:9 Org Chart Decks

Local spreadsheet and HRIS roster reconciliation checklist for 16:9 department org chart decks, masked salary views, and row-traceable payroll rollups.

Raw HRIS and payroll exports rarely map cleanly into presentation slides on the first pass. When People Ops or FP\&A teams pull an active employee list from Workday, ADP, BambooHR, or Excel before a board review or M\&A diligence meeting, three failure modes show up almost immediately:

1. **Silent hierarchy drops:** Terminated or contractor `Manager_ID` references, duplicate cost-center rows, and circular reporting (`A → B → A`) cause standard diagramming tools to silently drop headcount without warning.
2. **Unreadable wall-of-boxes slides:** Forcing 140+ employees onto a single canvas shrinks labels below readable size in 16:9 slide decks.
3. **Accidental compensation exposure:** Sharing live spreadsheet-linked charts in a meeting risks flashing individual base-pay columns while reviewing department totals.

## Step 1: Reconcile Every Source Row Locally

Before rendering boxes, enforce a strict row-level equation across your `.xlsx` or `.csv` export:

`Source Rows = Mapped in Hierarchy + Flagged Exceptions`

In [OrgLayout](https://orglayout.com/), parsing runs 100% inside local browser memory with zero cloud uploads. If a 148-row roster has 142 valid reporting chains and 6 broken records (missing `Manager_ID`, duplicate `Employee_ID`, or circular loops), those 6 rows are isolated in the **Discrepancies** queue with exact spreadsheet row numbers (`Row 42`, `Row 87`, `Row 119`) rather than disappearing from headcount totals.

## Step 2: Mask Individual Pay While Preserving Rollup Totals

During live leadership reviews, individual salaries stay masked (`••••••`) by default while preserving recursive team rollups:

* **Span of control & layer depth:** Audit `L1–L5+` depth and direct-report counts per manager using the [Span of Control & Payroll Rollup Calculator](https://orglayout.com/headcount-span-of-control-calculator/).
* **Row-traceable audit trail:** Every department headcount, FTE sum, and payroll subtotal maps back to exact source spreadsheet row ranges (for example, `Rows 12–59`) so Finance and HR numbers tie out to the dollar.

## Step 3: Paginate Into 16:9 Department Decks & Native `.PPTX`

<figure><img src="https://3196614739-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMbobnM3sKHY3aIWk2Oli%2Fuploads%2FNdpIBR00e48RApJkNyUs%2Forglayout-rollup.jpg?alt=media&amp;token=84d1f1b4-f7bf-46e9-b719-fd6812184428" alt=""><figcaption></figcaption></figure>

Instead of exporting one giant flattened image, split the hierarchy into readable presentation views:

* **Page 1 — Executive Overview:** Top leadership layers (`L1–L2`) with department headcount and masked/unmasked budget rollups.
* **Pages 2+ — Department Deep-Dives:** Dedicated 16:9 5-layer pages per Supervisory Organization or functional group via the [Workday Org Chart Export workflow](https://orglayout.com/workday-org-chart-export/).
* **Editable handoff:** Export synchronized vector `.PDF` decks, native OpenXML PowerPoint shapes via the [Excel to Editable Org Chart Generator](https://orglayout.com/excel-org-chart-generator/), and a 3-sheet `.XLSX` reconciliation workbook.
* **HRIS CSV exports (Rippling, ADP, BambooHR, Gusto):** Parse name-based `Reports To` or numeric `Manager ID` columns directly via the [CSV Roster to Org Chart Converter](https://orglayout.com/csv-to-org-chart/) to paginate 16:9 org chart slides locally.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://orglayout.gitbook.io/orglayout-docs/auditing-workday-and-excel-rosters-before-exporting-16-9-org-chart-decks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
