We run a custom fabrication company where projects take four to six months to complete, so weekly revenue numbers swing wildly. How do we structure weekly Scorecard measurables when project milestones and billing cycles are inherently lumpy?
Long-cycle project businesses often struggle with weekly Scorecards because top-line milestones and billings happen months apart. If you try to track completed projects or billed revenue week to week, your Scorecard will show zero for six weeks followed by a massive spike, rendering the data useless for weekly management.
To run a lumpy business on data, you must deconstruct your multi-month delivery timeline into weekly operational rhythms. You are not measuring the completion of the entire project; you are measuring milestone progress and capacity consumption.
Focus on these four categories of weekly measurables for long-cycle environments:
- Phase gate pacing: Track the number of project milestone sign-offs completed against the weekly project schedule. If your engineers must hit five specific design review gates this week across all active jobs, your target is five.
- Earned value or labor hours burn: Track actual labor hours worked versus budgeted hours for active project phases. A sudden divergence tells you that project scopes are creeping long before the budget is blown.
- Upstream procurement pacing: For construction, manufacturing, or custom fabrication, track the percentage of long-lead material orders placed on or ahead of the procurement schedule. Delays here stall production sixty days later.
- WIP billing triggers: Rather than tracking cash received, track billable project milestones earned that have not yet been invoiced.
When your pipeline operates on four to six month horizons, weekly activity is the only safeguard against massive project write-downs. Shift your focus from terminal outcomes to pipeline progression velocity. If the weekly milestone pace is green, your delivery and profitability will take care of themselves.
Category: Scorecards & Data