Service overview
Research planning, literature synthesis, methodology, proposals and feasibility work. This service is part of that division and is scoped individually around what you need to learn, decide or publish.
Decisions about technology, equipment and process change are often made on the basis of slides, anecdotes or a single vendor claim. A technical report or feasibility study replaces that with a documented comparison: what the options are, what evidence supports each, how they perform against the criteria that matter and what could go wrong. The report becomes a record of why a choice was made, which protects both the organisation and the people who made it.
Feasibility studies are particularly valuable at early stages when the cost of changing direction is low. They are not a substitute for detailed design, regulatory approval or professional certification, but they help decide whether such investments are justified. This service structures and writes the study from information you provide and analysis that is agreed in scope.
If you plan to publish the outcome, see manuscript & publication support, for example computational & simulation manuscripts or original research article writing.
What this service covers
Problems this service can address
- Decisions being made without a documented comparison of options
- Technical findings buried in raw data or slides
- Reports whose assumptions are not traceable
Methods and analytical approaches
- Option definition and screening criteria
- Technical and, where scoped, economic comparison
- Risk and sensitivity review
- Assumption and source traceability
Applications
- Technology selection studies
- Pilot-project feasibility assessments
- Technical documentation for funders
Relevant engineering disciplines
Scope, inputs and deliverables
Scope of work
- Review of your objectives, constraints and the evidence already available
- Selection of methods suited to the question and the data
- Analysis or synthesis with documented, repeatable steps
- Written outputs you can reuse in a thesis, proposal or report
- Feasibility check on: problem context and decision to be informed
Typical inputs required from you
- Problem context and decision to be informed
- Available data, drawings or prior studies
- Audience and required format
Deliverables
- Structured report with executive summary
- Option comparison tables and figures
- Assumption register and recommended next steps
Highly specialised requests are first checked for feasibility from this information. Please do not send confidential data through the public form; describe it first and agree secure transfer afterwards.
Project workflow and method
- 01Enquiry and requirement assessment
- 02Technical scoping and proposal
- 03Execution
- 04Quality review and delivery, with an agreed round of revisions
Read the full project workflow.
In depth: how the work is done
Defining the decision and the options
A feasibility study should answer a specific question, such as whether a process can meet a target at acceptable cost or which of several technologies best fits a set of requirements. We define the decision, the stakeholders and the constraints, then list the options including the baseline of doing nothing. Clear option definitions prevent comparisons of unlike things and make it possible to say what each option does and does not include.
Screening criteria and technical comparison
Criteria are derived from requirements and weighted according to their importance, with the weights discussed rather than hidden. Options are compared on technical performance, maturity, integration effort, operational implications, safety and environmental considerations as relevant. Quantitative evidence is used where it exists; where it does not, expert judgement is recorded as judgement. The comparison table makes it visible why an option scores as it does.
Risk, uncertainty and sensitivity
Each option carries uncertainty. We identify the assumptions that most affect the outcome, test how the ranking changes if they are wrong and describe which uncertainties could be reduced by further testing or data. Risks are listed with their likely consequences and possible mitigation. This protects against the common failure of presenting a single point estimate as certain.
Traceable assumptions and sources
A report is only as credible as its inputs. All numerical inputs, assumptions and data sources are recorded in an assumption register so that a reader can see where each came from and update it if conditions change. Figures and tables are tied to those sources, and unsourced statements are avoided or flagged. The register makes later review and revision far easier than reconstructing the reasoning from memory.
Presenting findings to different audiences
A single study often needs to serve different readers: an executive who wants the recommendation, an engineer who wants the evidence and a regulator or funder who wants the assumptions. We structure the report in layers, with a one-page summary, the main body and technical appendices, and we use figures that stand on their own with clear captions and units. This layered approach means each reader can find what they need without wading through material meant for someone else.
Quality control and good practice
Quality-control approach
- Search, selection or analysis steps are documented so another researcher can repeat them.
- Assumptions, exclusions and limitations are stated rather than implied.
- Numbers in text, tables and figures are cross-checked for consistency.
- Conclusions are limited to what the evidence supports.
Common pitfalls this service helps avoid
- Starting with the preferred answer. Studies designed to justify a decision already taken tend to omit alternatives and understate risks.
- Hidden weighting. Unstated weights in a scoring matrix let the result depend on arbitrary choices.
- Mixing evidence grades. Presenting vendor claims, measured data and opinion in the same table without distinction misleads readers.
- No next-step recommendation. A report that ends without saying what to do next leaves the decision-maker without direction.
What good reporting looks like
A typical structure includes an executive summary with the recommendation and its confidence, the problem and requirements, the options considered, the method of comparison, the technical analysis, risks and sensitivities, the assumption register and recommended next steps. It is written for a decision-maker who may not be a specialist, with technical detail in appendices. It reflects the information supplied and the analysis scoped; it is not a design certification, a regulatory submission or a guarantee of performance.
An illustrative scenario
Hypothetical example written for explanation. It is not a client case, a result or a testimonial.
Suppose an organisation wants to decide between two cooling approaches for an electronics enclosure. The report defines requirements for temperature, noise and maintenance, compares the options in a table with stated weights and tests how the ranking changes if the heat load is higher than assumed. It finds that the preferred option is sensitive to ambient temperature and recommends a short measurement campaign before purchase. The assumption register lets the client's engineers update the inputs themselves.
Questions to settle before you begin
- What decision will this report inform, and who will make it?
- Have I included the do-nothing baseline?
- Which assumptions drive the result most?
- What evidence do I have, and how reliable is each piece?
- What would I recommend if the key assumption turned out wrong?
Key terms
- Feasibility study
- An assessment of whether a proposed solution can work within constraints.
- Baseline option
- The reference case, often the current situation, against which options are compared.
- Sensitivity analysis
- A test of how results change when inputs change.
- Assumption register
- A list of assumptions with sources and effects.
- Decision criteria
- The factors used to compare options.
Working together on Research & Academic Consulting projects
Research and academic consulting engagements usually begin with a short conversation and a written summary of the question, the existing evidence and the intended outcome, such as a thesis chapter, a proposal or a journal article. We ask for what you already have, however rough: notes, drafts, data tables and the instructions of the committee or funder. Review is iterative and focuses on reasoning rather than wording, so you should expect questions that challenge assumptions. Authorship, scientific claims and institutional compliance remain yours. Deliverables are written so that you can reuse them directly in your own documents and defend them when asked how a decision was reached.
Frequently asked questions
Is a feasibility study a substitute for detailed design?
No. A feasibility study screens options and risks at an early stage. It does not replace detailed design, certification or regulatory review.
Can the report include cost analysis?
A basic economic comparison can be included when cost data are supplied and the scope includes it. Detailed financial modelling is outside the standard scope unless agreed.
Who owns the report?
Ownership and confidentiality terms are set out in the project agreement before work starts.
Can the study be used to apply for funding?
It can provide supporting evidence, but funders have their own formats and criteria.
What if data are missing?
Missing data are flagged and bounded with explicit assumptions, and the report suggests how to obtain better data.
How is this service scoped and priced?
After your enquiry we review what you need, ask for missing information and send a written scope and quotation. Price depends on complexity, deliverables and timeline. See the project workflow.
Further detail
Who uses feasibility study services
feasibility study support is requested by researchers preparing a study, engineering teams without spare analysis capacity, and organisations that want an independent technical view. ENGRexpert is a consultancy: you describe the problem and a suitable specialist or coordinated team is proposed after scoping. It is not a freelancer marketplace and does not state staff numbers or credentials that have not been verified.
Outsourcing a feasibility study: what to send
- The proposed concept or project and its objectives
- Available data, drawings or prior studies
- Decision criteria and constraints
- Audience for the report
Deliverables that can be agreed
- Options assessment with stated assumptions
- Risk and uncertainty discussion
- Clear findings and next steps
- A formal technical report
How a quotation is prepared
Send the requirements through the enquiry form. The scope, assumptions, deliverables, timeline and fee are agreed in writing before work begins. This website states no prices, response times or free-consultation terms. Related services: engineering research consultancy, industrial R&D.