Opening a Store: Build the Project Plan

An opening date is a milestone, not a project plan. The plan should show what must be decided or completed before the store can be ready, how each workstream affects another and who owns the next decision. The store manager needs a clear view of those links so an issue is raised while there is still time to act.

Start with the approved brief, opening date and the project team's schedule. Group work into useful streams such as space and fit-out, people, stock, systems, operations and launch. Use the project's own categories and controls where they exist; do not create a competing tracker that becomes a second source of truth.

For each milestone, record the accountable owner, due date, evidence of completion and any work that depends on it. A decision with no owner or date is still open. A task marked complete without the required evidence may still leave a readiness gap. Ask the project lead to resolve ownership where teams share a dependency.

Look for links that affect store operations. Hiring dates may affect training. A delivery plan may depend on receiving access and storage. A systems rehearsal depends on the right equipment, access and trained users. These are examples to check against the actual plan, not fixed requirements for every store.

At each project review, bring a short update: what changed, which milestone is at risk, what the store team needs and who will make the decision. Escalate a conflict through the agreed project route. The project lead owns the integrated schedule; the store manager makes the operational impact clear and follows up on assigned actions.