Start with the decision
A feasibility study can answer many questions. It becomes more useful when one decision gives the work its direction: whether to proceed, which route to investigate, or what needs to be resolved before investing.
Write that decision in plain language. A brief that says “compare two processing routes for this material stream” provides a clearer starting point than “study the opportunity”.
Define the boundary
Describe what sits inside the study: the feedstock, location, intended product or fuel user, and the interfaces with existing operations. Record what is outside the scope as well.
This gives the technical and commercial teams a common frame for comparing options.
Separate information from assumptions
A useful brief distinguishes available records, initial estimates and questions that still need investigation. Keep an assumptions register and identify which uncertainties could change the recommendation.
Agree what a useful answer looks like
Before work begins, align on the outputs and the basis of comparison. These could include technical options, investment sensitivities, implementation constraints and a recommendation for the next stage.
The objective is a clearer decision, with enough visibility into the reasoning to act on it.
A general discussion guide, not a site-specific engineering assessment. The right approach depends on the project and its operating context.
