2. Project Selection, Charter and Governance

Introduction and Context

Logistics projects are usually initiated because an organisation is experiencing a performance gap, a strategic opportunity, a regulatory requirement, or a significant change in its operating environment. Examples include redesigning a distribution network, implementing a warehouse management system, reducing transport emissions, introducing cross-docking, improving inventory accuracy, or outsourcing fulfilment activities. Although such projects may appear operational, their consequences are often strategic: they affect customer service, working capital, technology investment, labour, suppliers, risk exposure, and competitive positioning.

A common reason logistics projects fail is not poor technical execution but weak selection and definition at the beginning. Organisations sometimes approve projects because they are fashionable, requested by a powerful stakeholder, or associated with a new technology. The problem may not be clearly established, benefits may be overstated, responsibilities may be ambiguous, and governance may be too weak to control changes. Project selection, charter development, and governance therefore form the foundation of disciplined logistics project management.

Project selection determines whether an initiative deserves scarce organisational resources. The project charter converts the selected idea into an authorised and shared statement of purpose. Governance establishes how decisions will be made, monitored, escalated, and controlled. Together, these activities connect corporate strategy with practical implementation.

Learning Objectives

By the end of this chapter, the learner should be able to:

1. Explain why project selection is strategically important in logistics and supply chain management.

2. Develop a business case and a precise logistics problem statement.

3. Formulate objectives, scope boundaries, deliverables, assumptions, constraints, and success criteria.

4. Construct a work breakdown structure, high-level schedule, and preliminary budget.

5. Define project roles, decision rights, governance gates, and reporting arrangements.

6. Evaluate common risks, ethical issues, and implementation challenges in logistics projects.

7. Apply charter and governance principles to a realistic logistics project scenario.

From Operational Concern to Project Opportunity

A project should not be confused with routine logistics operations. Routine operations are continuous and repetitive, whereas a project is a temporary undertaking designed to create a specific improvement, capability, or outcome. A warehouse operates every day; the redesign and implementation of a new warehouse layout is a project. Transport deliveries are routine; the introduction of a route-optimisation platform is a project.

The first discipline is to distinguish symptoms from causes. “Late deliveries have increased” is a symptom. Possible causes include inaccurate inventory records, poor carrier performance, unrealistic delivery promises, congestion at a distribution centre, or an inadequate transport planning process. A project selected without investigating the causal system may improve one indicator while worsening another.

A useful problem statement identifies:

• the current condition;
• the evidence that the condition exists;
• the affected customers, processes, or stakeholders;
• the consequences of leaving it unresolved; and
• the desired direction of improvement.

For example, “The company needs a new transport system” is a weak statement because it prescribes a solution. A stronger statement is: “During the last two quarters, on-time delivery for regional customers fell from 94% to 86%, while manual route planning increased planner overtime and produced inconsistent vehicle utilisation. The causes and the most effective corrective intervention have not yet been established.” This wording preserves analytical flexibility.

Selecting the Right Project

Project selection is a portfolio decision. Resources such as capital, skilled employees, management attention, data, and implementation capacity are limited. Approving one project may delay another. Selection should therefore consider strategic value, feasibility, risk, cost, urgency, and the organisation’s ability to absorb change.

A business case provides the reason for investment. It normally compares the current state with one or more alternatives, including the option of doing nothing. Its main components are:

• strategic alignment: contribution to corporate, customer, sustainability, or supply chain priorities;
• problem or opportunity: the measurable issue requiring attention;
• alternatives: possible responses, including maintaining the status quo;
• benefits: financial and non-financial improvements expected;
• costs: capital, operating, implementation, training, and transition costs;
• risks: events that could reduce benefits or increase cost and time;
• feasibility: technical, operational, financial, legal, and organisational practicality; and
• recommendation: the preferred option and the basis for approval.

Financial appraisal may include payback period, return on investment, net present value, or total cost of ownership. These measures should not be used mechanically. A project with modest direct savings may be essential for regulatory compliance, business continuity, customer retention, or strategic capability. Conversely, an attractive projected return may depend on unrealistic adoption rates or benefits that cannot be measured.

A weighted scoring model can support comparison. Criteria may include strategic alignment, customer impact, economic value, implementation complexity, risk reduction, sustainability, and readiness. Each project receives a score against each criterion, multiplied by an agreed weight. The model does not replace managerial judgement; it makes assumptions visible and supports transparent discussion.

A project should also pass a feasibility and readiness test. Relevant questions include: Is reliable baseline data available? Are process owners willing to participate? Can the organisation fund the work? Are required technologies compatible with existing systems? Is the project sponsor sufficiently influential? Are suppliers and employees likely to accept the change? A technically attractive project may be premature if the organisation lacks data quality or implementation capacity.

The Project Charter as a Contract of Understanding

Once a project is selected, the charter formally authorises it. It is not a detailed project plan. Rather, it is a concise management agreement describing why the project exists, what it will produce, who is accountable, and how authority will operate. The charter should be approved by a sponsor or appropriate governance body before substantial project work begins.

A strong charter generally contains the following elements.

Purpose and Business Case

This section links the project to the business case and organisational priorities. It explains why action is required and what value is expected. Statements should be evidence-based and should distinguish confirmed benefits from hypotheses.

Problem Statement and Objectives

The problem statement describes the current gap without prematurely dictating the solution. Objectives translate the problem into measurable results. A well-designed objective identifies the performance dimension, baseline, target, timeframe, and measurement method. For example: “Increase inventory record accuracy in the central warehouse from 92% to at least 98% within six months of stabilised implementation.”

Objectives should be ambitious but controllable. If delivery performance depends substantially on external events, the project should identify the contribution it can reasonably influence rather than promise an outcome entirely outside its control.

Scope and Boundaries

Scope defines what the project will and will not address. In logistics, scope may involve facilities, product families, geographic regions, transport modes, systems, suppliers, processes, or organisational units. Explicit exclusions are particularly valuable. For instance, a warehouse slotting project may include fast-moving consumer products and the central distribution centre but exclude automation procurement and satellite warehouses.

Unclear scope produces scope creep: unapproved expansion that consumes resources and delays benefits. Scope should be tested against objectives. Every major activity should contribute to an objective, and every objective should have an identifiable activity or deliverable supporting it.

Deliverables and Acceptance Criteria

A deliverable is a verifiable output, such as a validated process design, configured software module, trained user group, supplier contract, facility layout, or performance dashboard. Acceptance criteria specify how the sponsor will determine that the deliverable is complete and fit for use. “System implemented” is weak; “system processes approved inbound receipts in the pilot site with reconciliation accuracy of at least 99% for four consecutive weeks” is more useful.

Assumptions, Constraints, and Dependencies

Assumptions are conditions treated as true for planning purposes, such as the availability of subject-matter experts or the continuity of a supplier contract. Constraints are limits, including budget ceilings, fixed implementation dates, labour agreements, or regulatory requirements. Dependencies are relationships with other activities or projects, such as an enterprise resource planning upgrade that must precede warehouse system integration.

These items should be recorded because untested assumptions often become project risks.

Preliminary Resources, Schedule, and Budget

The charter should provide an initial estimate of duration, major phases, key resources, and cost. At this stage, estimates are uncertain and should be presented with assumptions and confidence ranges rather than false precision. The detailed baseline is normally developed after planning and decomposition.

Decomposing the Work: Deliverables and the WBS

The work breakdown structure (WBS) is a hierarchical decomposition of the total project scope into manageable work packages. It is deliverable-oriented: it describes what must be produced, not merely a list of departments or meetings. A logistics WBS for a warehouse management system project might include governance, requirements, process design, integration, configuration, testing, training, pilot, deployment, and transition to operations.

The 100 per cent rule requires the WBS to represent all approved project work and only approved project work. If training, data cleansing, cutover planning, or post-implementation support is omitted, the schedule and budget will be understated. If unrelated operational improvements are included, accountability becomes confused.

A work package should be sufficiently small to estimate, assign, schedule, and monitor, but not so small that administration becomes excessive. Each package should have an owner, expected output, estimated effort, dependencies, and acceptance condition. The WBS becomes the foundation for scheduling, budgeting, responsibility assignment, risk identification, and progress reporting.

Building the Schedule and Budget

A high-level schedule converts the WBS into a sequence of activities. The project team identifies logical relationships, estimates duration, considers resource availability, and determines milestones. Common logistics milestones include charter approval, requirements sign-off, design approval, supplier selection, pilot readiness, go-live decision, and benefits review.

The critical path is the sequence of activities that determines the shortest possible project duration. Delays to critical-path activities may delay the project unless corrective action is taken. However, a schedule should not focus only on the critical path. Non-critical activities may consume scarce experts, create safety risks, or affect operational continuity.

A budget should include direct project labour, external consultancy, software and equipment, data preparation, training, travel, testing, temporary operational capacity, communication, and contingency. Contingency is not a reward for poor estimation; it is a controlled allowance for identified uncertainty. Management reserve, where used, is normally held outside the project manager’s baseline and released through governance authority.

Benefits should be separated from costs. A reduction in inventory may improve working capital but could also increase stockout risk. Lower transport cost may increase lead time or reduce resilience. The budget and business case must therefore consider total system effects rather than isolated local savings.

Governance: Authority, Accountability, and Control

Project governance is the framework through which a project is directed and controlled. It clarifies who makes decisions, who provides assurance, how performance is reviewed, and how exceptions are escalated. Governance is not the same as excessive administration. Effective governance provides proportionate control while preserving the project team’s ability to act.

The sponsor owns the business case, secures organisational support, resolves escalated issues, and protects the project’s strategic purpose. The project manager coordinates planning and execution, manages resources and risks, reports performance, and facilitates decisions. A steering committee provides cross-functional oversight and approves major changes. Process owners ensure that the redesigned process can operate in practice. Subject-matter experts contribute specialist knowledge. Users, suppliers, information-technology teams, finance, human resources, legal advisers, and health-and-safety specialists may also have defined responsibilities.

A responsibility assignment matrix, often expressed as RACI, distinguishes who is Responsible for performing work, Accountable for the outcome, Consulted before decisions, and Informed about progress. Each significant deliverable should have one clear accountable role, even if several parties are responsible for activities.

Governance Gates

Governance gates are formal decision points at which evidence is reviewed before the project proceeds. A typical logistics project may use the following gates:

1. Concept gate: confirms that the problem is material and the project is aligned with strategy.

2. Business-case gate: assesses alternatives, value, risk, and feasibility.

3. Initiation gate: approves the charter, sponsor, resources, and governance structure.

4. Design gate: confirms that requirements and the proposed solution are sufficiently mature.

5. Pilot or readiness gate: determines whether testing, training, data, controls, and contingency arrangements support a pilot or go-live.

6. Deployment gate: authorises broader implementation based on evidence from the pilot.

7. Closure and benefits gate: confirms handover, lessons learned, outstanding actions, and benefits ownership.

A gate should be a decision, not a ceremonial meeting. Possible decisions include proceed, proceed with conditions, revise and resubmit, pause, or terminate. Termination is not necessarily failure; ending a project that no longer offers value can protect organisational resources.

Success Criteria and Benefits Realisation

Project completion and project success are different. Completion means that planned work has been performed and deliverables accepted. Success concerns whether the organisation receives the intended benefits and whether the change remains sustainable.

Success criteria may include cost, schedule, quality, service, safety, adoption, resilience, employee experience, sustainability, and financial performance. Each criterion requires a baseline, target, measurement frequency, data owner, and review period. For example, a route-planning project may target a 7 per cent reduction in kilometres travelled without reducing on-time delivery below the agreed service level.

Benefits realisation should continue after project closure. The project team may deliver a dashboard and training, but an operational manager normally owns the continuing benefit. Benefits can be direct, such as reduced freight expenditure; indirect, such as improved planning visibility; or enabling, such as a data capability that supports future optimisation.

Applied Case: NorthRiver Distribution Network Project

Background

NorthRiver Distribution, an illustrative mid-sized distributor of food-service products, operates one central warehouse and three regional depots. Customer demand has become more geographically dispersed, but the network has evolved through incremental decisions rather than a formal design process.

Situation and Problem

Transport expenditure has increased for three consecutive planning periods, while delivery reliability has declined for smaller regional customers. Management initially proposed purchasing a transport management system. The operations director requested a project charter before approving the investment.

The project team examined shipment records, depot utilisation, carrier invoices, customer complaints, and planning practices. The analysis suggested several interacting causes: inconsistent delivery-zone definitions, limited consolidation, manual carrier allocation, and poor visibility of depot capacity. The team concluded that technology might help, but technology alone was not yet justified.

Business Case and Selection

Three alternatives were compared: maintain current operations, redesign transport planning and controls without new software, or combine process redesign with a phased transport management system. The third option had the highest potential value but also the greatest implementation risk. A weighted assessment gave substantial weight to service reliability, implementation feasibility, total cost, and future scalability. The steering group approved a phased project, beginning with process standardisation and a pilot in two delivery zones.

Charter and WBS

The charter defined the objective as improving on-time delivery from 88 per cent to at least 95 per cent in the pilot zones within four months of stabilisation, while reducing avoidable transport cost per shipment by 5 per cent. Scope included delivery-zone rules, carrier allocation, planning procedures, data standards, pilot configuration, user training, and performance reporting. It excluded fleet acquisition and a redesign of depot locations.

The WBS included: project initiation; baseline validation; process mapping; requirements; solution evaluation; data preparation; pilot configuration; testing; training; pilot operation; performance review; deployment recommendation; and closure. Each work package had an owner and acceptance criteria.

Governance and Approach

The operations director acted as sponsor. The project manager reported fortnightly to a steering committee comprising operations, finance, customer service, information technology, and a regional depot manager. A readiness gate required validated master data, trained planners, tested exception procedures, and an agreed fallback process before the pilot could begin.

The team used a controlled pilot rather than immediate network-wide deployment. Pilot results were reviewed against the baseline, and user feedback was analysed alongside financial and service measures.

Outcome

The illustrative case assumes that the pilot met the service target and achieved part of the cost target, but also revealed that carrier appointment discipline was weaker than expected. The steering committee authorised limited expansion subject to a corrective action plan and a revised benefits forecast. This outcome demonstrates why governance gates should test assumptions rather than merely confirm management enthusiasm.

Learning Points

The project began with a business problem rather than a predetermined technology purchase. Its scope protected the team from attempting a full network transformation at once. Measurable objectives, explicit exclusions, staged approval, and a pilot created learning before major commitment. Most importantly, governance enabled the organisation to proceed conditionally rather than treating approval as an irreversible decision.

Risks, Common Mistakes, and Professional Judgement

Several recurring mistakes undermine logistics projects. The first is solution-first thinking, in which a preferred technology or supplier is selected before the problem is understood. The second is confusing activity with progress: meetings, configuration, and documents do not prove that operational capability is improving. The third is weak baseline data. Without a reliable baseline, claimed benefits cannot be demonstrated.

Other risks include underestimating change-management effort, ignoring frontline employees, excluding suppliers from relevant design decisions, failing to plan cutover and fallback operations, and assigning accountability to a committee rather than an individual. Local optimisation is another danger. A warehouse project may reduce handling cost while increasing transport delays or damage. Decisions should therefore be assessed across the end-to-end supply chain.

Ethical and governance considerations include honest benefit estimates, fair treatment of employees affected by automation, protection of commercially sensitive data, non-discriminatory use of performance data, transparent supplier evaluation, and compliance with procurement, labour, safety, environmental, and data-protection requirements. If algorithms influence carrier selection or workforce allocation, managers should understand the data used, monitor for systematic bias, and retain human oversight for exceptional decisions.

Digital project tools can improve version control, collaborative planning, dashboard reporting, schedule tracking, and risk registers. Process-mining and advanced analytics may help establish baselines and identify bottlenecks. Artificial intelligence can support scenario analysis or demand and routing decisions, but its outputs require validation. Poor master data, opaque models, cybersecurity weaknesses, and automation bias can create operational harm. Technology should strengthen governance, not replace accountable judgement.

Current Developments and Best Practice

Contemporary logistics projects increasingly combine operational resilience, sustainability, and digital transformation. Project selection now commonly considers carbon emissions, energy use, circular flows, supply disruption, cyber risk, and workforce capability alongside cost and service. Scenario planning is useful where demand, regulation, or geopolitical conditions are uncertain.

Best practice is to maintain a traceable chain from strategy to problem, objective, deliverable, activity, metric, and benefit owner. Use evidence before approval, make assumptions explicit, involve process users early, and adopt stage gates proportionate to risk. Establish a single source of truth for scope, decisions, issues, risks, and changes. Review benefits after implementation rather than declaring success at go-live. Finally, design governance to encourage timely escalation: hidden problems are more expensive than visible problems.

Chapter Summary

Project selection, charter development, and governance determine whether a logistics initiative is worth undertaking and whether it can be controlled responsibly. Selection requires comparison of strategic value, feasibility, risk, cost, readiness, and alternatives. A business case explains the investment logic, while a problem statement defines the evidence-based performance gap without prematurely prescribing a solution.

The charter authorises the project and establishes its purpose, objectives, scope, deliverables, assumptions, constraints, resources, schedule, budget, and success criteria. The WBS decomposes approved scope into manageable work packages and supports planning and accountability. Governance assigns decision rights through sponsors, project managers, steering groups, process owners, and other stakeholders. Stage gates provide evidence-based decisions at critical points. Success depends not only on delivering outputs but also on achieving and sustaining measurable operational benefits.

Key Terms

Business case: A structured argument explaining why a project should be funded and undertaken.

Problem statement: An evidence-based description of a current performance gap or opportunity.

Project: A temporary undertaking that creates a specified product, service, capability, or improvement.

Project charter: An approved document that authorises a project and defines its initial direction and authority.

Scope: The boundaries of work and outcomes included in a project.

Deliverable: A verifiable output produced by project work.

Acceptance criterion: A condition used to determine whether a deliverable is complete and acceptable.

Assumption: A condition treated as true for planning purposes but requiring monitoring.

Constraint: A limitation affecting project cost, time, resources, or methods.

Dependency: A relationship in which one activity, project, or decision relies on another.

Work breakdown structure: A hierarchical decomposition of total project scope into manageable work packages.

Work package: The lowest practical unit of planned work in a WBS.

Critical path: The sequence of activities determining the shortest possible project duration.

Governance: The framework of authority, accountability, decision-making, and control applied to a project.

Steering committee: A senior group that provides oversight and approves major project decisions.

RACI matrix: A responsibility tool identifying who is Responsible, Accountable, Consulted, and Informed.

Stage gate: A formal review point at which continuation, revision, pause, or termination is decided.

Baseline: An approved reference point against which performance is measured.

Benefits realisation: The process of ensuring that intended project benefits are achieved and sustained.

Scope creep: Uncontrolled expansion of project work beyond approved boundaries.

Review Questions

Short Answer Questions

1. Why should a logistics project begin with a problem statement rather than a preferred technology?

2. Distinguish between a project charter and a detailed project plan.

3. What is the purpose of a work breakdown structure?

4. Explain the difference between an assumption and a constraint.

5. Why is benefits ownership required after project closure?

Long Answer Questions

1. Explain the major components of a logistics project business case and discuss how they support portfolio decisions.

2. Describe how objectives, scope, deliverables, and acceptance criteria should be connected in a project charter.

3. Discuss the roles of the sponsor, project manager, steering committee, and process owner in logistics project governance.

4. Explain the purpose of governance gates and illustrate suitable decisions at different project stages.

5. Analyse the relationship between the WBS, schedule, budget, risk register, and performance reporting.

Analytical / Application Questions

1. A company wants to introduce warehouse automation because competitors have done so. Develop a problem statement and identify the evidence required before selecting the project.

2. A transport project reduces cost by 8 per cent but causes a decline in delivery reliability. How should the business case and success criteria be reviewed?

3. Prepare the principal charter elements and a high-level governance structure for a project implementing a transport management system in two pilot regions.

22. Multiple Choice Questions with Answers

Question 1

Which statement best represents a well-formed logistics project problem statement?

A. The company must purchase a transport management system immediately.

B. The warehouse should be fully automated within six months.

C. On-time delivery has declined from 94% to 86%, while manual planning has increased overtime and vehicle underutilisation.

D. The project team will redesign transport operations.

Correct Answer: C. On-time delivery has declined from 94% to 86%, while manual planning has increased overtime and vehicle underutilisation.

Question 2

What is the primary purpose of a project charter?

A. To provide a detailed daily operating procedure

B. To formally authorise the project and establish its initial direction and authority

C. To replace the organisation’s financial budget

D. To guarantee that all expected benefits will be achieved

Correct Answer: B. To formally authorise the project and establish its initial direction and authority

Question 3

Which item is an example of an acceptance criterion?

A. The project will improve warehouse performance

B. Users will be consulted during implementation

C. The pilot system will process inbound receipts with at least 99% reconciliation accuracy for four consecutive weeks

D. The sponsor supports the project

Correct Answer: C. The pilot system will process inbound receipts with at least 99% reconciliation accuracy for four consecutive weeks

Question 4

Under the 100 per cent rule, a work breakdown structure should:

A. Include only activities on the critical path

B. Represent all approved project work and exclude unrelated work

C. Contain only tasks performed by the project manager

D. Be limited to technology-related activities

Correct Answer: B. Represent all approved project work and exclude unrelated work

Question 5

Which governance decision is most appropriate at a readiness gate?

A. Whether the original business problem exists in the industry

B. Whether testing, training, data, controls, and fallback arrangements support deployment

C. Whether routine warehouse staff should be scheduled next year

D. Whether all future projects should use the same supplier

Correct Answer: B. Whether testing, training, data, controls, and fallback arrangements support deployment

Question 6

A project has attractive projected savings, but its benefit estimate assumes immediate adoption by all depots. What should the selection team do first?

A. Accept the estimate because it is financially attractive

B. Remove adoption from the business case

C. Test the assumption and model phased adoption or alternative scenarios

D. Approve the project without a pilot

Correct Answer: C. Test the assumption and model phased adoption or alternative scenarios

Question 7

Who is normally accountable for protecting the project’s strategic purpose and resolving escalated issues?

A. The project sponsor

B. Every project team member equally

C. The external supplier

D. The warehouse shift supervisor

Correct Answer: A. The project sponsor

Question 8

Which situation is the clearest example of scope creep?

A. Adding approved training activities to the WBS

B. Including data cleansing required for the agreed system implementation

C. Adding a fleet replacement programme unrelated to the approved warehouse project

D. Breaking a design deliverable into smaller work packages

Correct Answer: C. Adding a fleet replacement programme unrelated to the approved warehouse project

Question 9

Why should project success criteria include baselines, targets, data owners, and review periods?

A. To increase the number of project documents

B. To make benefits measurable and assign responsibility for tracking them

C. To ensure that the project cannot be terminated

D. To eliminate the need for operational managers

Correct Answer: B. To make benefits measurable and assign responsibility for tracking them

Question 10

A pilot meets its service target but fails to achieve the expected cost reduction because carrier appointment discipline is weak. What is the best governance response?

A. Declare complete success based only on service performance

B. Terminate the project immediately without analysis

C. Authorise expansion unconditionally because the pilot met one target

D. Review the evidence, assign corrective actions, and revise the benefits forecast before further deployment

Correct Answer: D. Review the evidence, assign corrective actions, and revise the benefits forecast before further deployment