Move this to Power BI

This preview is built from the same model the kit contains, so each visual maps one to one.

Download the kit (.zip)Copy DAX

Steps

1. Load the three CSV files with the queries in power-query.m.
2. Create the relationships: MasterLog to Projects on Project, to Tiers on Tier, to Date on NeedBy.
3. Add the Date table and all measures from measures.dax.
4. Apply theme.json for the tier colors.
5. Build the visuals using the map on the right. Matrix cells use gradient background formatting, one column at a time.
6. When the real source is known, change only the Source step of each query.

Model

MasterLog (item rows) joins to Projects, Tiers and Date. Every visual is a count of MasterLog rows sliced by one of those tables.

Measures

Visual map

Preview visual	Power BI visual	Fields
Tier, Item type, Stage filters	Slicer (tile style)	Tiers[Tier], MasterLog[Type], MasterLog[Stage]
Count cards	Card	[Total Items], [Tier 1 Items] to [Tier 4 Items]
Items by project and tier	Stacked bar chart	Y: Projects[Project]. X: [Total Items]. Legend: MasterLog[Tier]
Items by need-by month	Stacked column chart	X: Date[Month]. Y: [Total Items]. Legend: MasterLog[Tier]
Items by stage	Donut chart	Legend: MasterLog[Stage]. Values: [Total Items]
Portfolio read	Two Multi-row cards	[Insight On Track 1 to 3], [Insight Focus 1 to 4]
Projects by tier	Matrix	Rows: Projects[Project], Projects[Code]. Values: [Submittal Items], [Procurement Items], [Tier 1 Items] to [Tier 4 Items], [Total Items]
Item detail	Table	MasterLog columns, sorted by NeedBy

Using real data

Replace the CSV Source steps with the client's Procore export or warehouse tables. Keep the ten MasterLog columns. If the tier is not stored on each row, calculate it in Power Query from the need-by date once the client confirms their tier definitions.

Assumptions in the sample

Tier windows (about 2, 6 and 13 weeks), the four stages, item names and owners are placeholders. Project names and tier counts follow the workbook screenshots.