Direct Analytical Access
Governed cost, schedule, and status records in native Excel tables — custom EAC formulas, pivot analyses, and project dashboards work against the same rows ProjectXL's own compute engines use.
The value of workbook-resident storage is realized through direct analytical access. If governed plan data were stored in native Excel tables but could only be accessed through ProjectXL's own reporting surfaces, the architecture would still be interesting — but the real leverage comes from the fact that the data is fully accessible to every Excel analytical capability that the analyst already knows how to use.
Analysts Can Extend Beyond Built-In Reports
ProjectXL ships with its own reporting surfaces — the cost plan views, schedule analysis outputs, EAC reconciliation view, and BI export. Those surfaces cover the standard analytical needs for the core project control workflow. But analysts often have project-specific questions, organization-specific KPIs, or custom calculations that are not covered by any standard report. In ProjectXL, those questions can be answered by building directly against the governed table data — using Excel formulas, Power Query, pivot tables, or any other analytical approach.
The Same Data the Product Uses
The table rows a custom analysis references are the same rows ProjectXL's own compute engines consume when they calculate labor cost, evaluate schedule health, or generate BI exports. There is no distinction between "analytical data" that is safe for custom use and "authoritative data" that is reserved for the product. The governed tables are the authoritative record, and they are equally available to the product's engines and to the analyst's custom formulas.