Work backwards from site
Start with the required-on-site date agreed by the project team. Then record the steps that make it achievable: technical review, order authority, manufacture, transport and access. A single delivery field cannot explain which dependency has moved.
Keep commitments and forecasts distinct
Record who supplied each date and when. A supplier forecast is different from a confirmed commitment, and both can change. Retain the update history so the team can see the basis of the current position.
Connect the approval record
An unresolved submittal can prevent an order from being released. Link the procurement item to the relevant submission or RFI instead of duplicating technical discussion across several spreadsheets.
Escalate a decision, not a coloured cell
If the forecast falls after the required date, identify the person who can decide the next step. Your administrator can document the risk and follow up the response; programme changes, substitutions and additional expenditure need the appropriate authority.
See an example
Explore fictional registers and a downloadable weekly report in the sample Control Centre.
Open sample workspace