Dear Community,
We’re preparing our reporting framework to support parent–child project hierarchies.
We want to hear your thoughts on how each existing report (from the list below) should look and behave when it’s run for a parent project versus a child project. Your input will help us avoid double‑counting, make drill‑downs intuitive, and keep financials audit‑ready across rollups.
What feedback we’re collecting:
- UI expectations per report: what should change when the report scope is a parent vs child project?
- Aggregation rules: what must be summed, averaged, recalculated, or eliminated at the parent level?
- Filtering & drill‑down: which filters, groupings, and drill paths are essential (e.g., Parent → Child → Cost Code → Transaction)?
- Gaps: any missing reports you rely on for parent-child project management that aren’t listed below.
Please evaluate your feedback against these parent–child project types:
- Parent Project – container
- only aggregates cost and revenue from child projects
- each child project is billed separately
- Parent Project – main contract
- aggregates costs from child projects
- parent project is billed directly
Consider the following reports (displayed in their current design):
- Project WIP Adjustment
- Substantiated Billing
- Subcontract Audit
- Construction Bonding Report
- Employee Hours
- Project Profitability
- Project Cash Flow
- Project Variance
- Project Committed Cost Summary
- Project Transaction Details
- Project Financial Vision
- Cost Projection by Date
Thank you in advance for your input!
