Assessment methodology
How the assessment works
The assessment structures your answers across eight operational areas. It shows which foundations are already sufficiently described, where further clarification is needed, which automation areas may warrant evaluation, and which assumptions should be validated before supplier or internal investment discussions.
What the assessment does
- Structures operational inputs
- Explains preparation topics and contributing answers
- Highlights automation areas worth evaluating
- Produces supplier questions and planning assumptions
How to interpret the results
- A preparation indicator
- Areas requiring further clarification
- Indicative planning ranges requiring validation
What the results do not mean
- No technical approval
- No supplier recommendation
- No guaranteed ROI
- No prediction of project success
Eight preparation areas
Each area contributes to one or more preparation outputs: the preparation indicator, automation areas worth evaluating, supplier questions, or indicative business-case assumptions.
Warehouse profile
Site size, storage locations, SKU range, order-line volumes, and operational structure help define the scale and complexity of the preparation task.
Labour dependency
Staffing levels, shift structure, labour-intensive processes, and recruitment pressure help identify where operational dependence on manual work is highest.
Process variability
Peak fluctuations, order-profile stability, exceptions, and the distribution of work indicate how predictable and repeatable the operation is.
Operational challenges
Productivity, walking distance, transport effort, accuracy, space constraints, and scalability challenges help identify preparation priorities.
Systems and technology foundation
WMS maturity, scanning coverage, existing automation, system interfaces, and integration conditions help explain technical prerequisites and expected complexity.
Data confidence
Confidence in inventory, location, movement, and volume data affects the quality of planning assumptions and the reliability of later validation.
Automation conditions
The assessment compares operating conditions, current processes, and open prerequisites with the typical conditions associated with different automation areas.
Business-case drivers
Labour profile, operating volumes, shift structure, operational pressure, and selected assumptions influence the indicative planning ranges.
How results are formed
Preparation indicator
Summarises how completely the main operational, data, systems, and decision inputs have been described. It helps identify preparation topics but is not a technical approval or prediction of project success. The value is a structured preparation indicator, not a certified readiness score.
Existing automation foundation
Describes the current level of systems, scanning, material-handling technology, and integration. It helps explain prerequisites and complexity but does not determine whether a new solution should be implemented.
Automation areas worth evaluating
The assessment compares your answers with operating conditions commonly associated with different automation areas. It highlights areas that may warrant evaluation and explains relevant prerequisites and open questions.
Indicative business-case ranges
Ranges are derived from selected operational inputs and standard assumptions. They provide a starting point for validation and are not supplier quotes, guarantees, or investment recommendations. Normal and peak operating conditions should be modelled separately.
Important limitations
The method uses structured operational indicators and explicit assumptions. Results should always be reviewed against actual process data, site constraints, supplier evidence, and internal requirements.
- Indicative ranges are not precise project calculations.
- Actual savings depend on operational details not fully captured by the assessment.
- Building constraints, lease terms, safety requirements, and existing automation contracts require separate review.
- Supplier claims and proposed performance levels require evidence and validation.
- Industry-specific requirements may not be fully reflected in the standard model.
- Technical feasibility requires engineering analysis and site-specific validation.
Start the assessment
Answer 21 structured questions and receive a preparation workspace with practical outputs for internal review and supplier discussions.
Start Free Assessment