Why a defined workflow
Why a defined workflow matters
Research projects fail less from lack of skill than from unclear scope, missing data and misaligned expectations. A defined workflow lets both sides know what happens next, what each party must provide and how decisions are made. This page describes the stages of an engagement with ENGRexpert, from the first enquiry to delivery and follow-up. The same structure applies to modelling and simulation projects, data analysis projects, technical consulting and manuscript support, with adjustments for each.
The process at a glance
The eight steps from enquiry to delivery. Detail on each stage follows in the next section.
- 01
Initial enquiry
You describe objectives, data situation, deliverables and timeline through the enquiry form.
- 02
Requirement assessment
We review the enquiry, check for missing information and clarify what a successful outcome looks like.
- 03
Technical scoping
We define the questions, methods, inputs, assumptions and acceptance criteria, and check feasibility.
- 04
Expert identification
We identify the technical expertise the scope requires and confirm availability before committing.
- 05
Proposal and quotation
You receive a written scope, deliverables, timeline and quotation to approve before work starts.
- 06
Project execution
Analysis, modelling or writing proceeds against the agreed scope, with check-ins on material decisions.
- 07
Technical quality review
Results, assumptions and numbers are checked for consistency, and manuscripts are verified against your source data.
- 08
Delivery and agreed revisions
Deliverables are handed over with documentation, and the agreed round of revisions is completed.
Stage by stage
How each stage runs in practice, including what we check and what we ask of you.
- Stage 1
Enquiry and initial discussion
The process begins with a short description of your project through the contact page: the research question or technical problem, the field, the data or models you have, the intended output such as a paper or report, your deadline and any constraints. Please avoid sending confidential or personal data at this point.
We reply with clarifying questions and a first impression of feasibility. If the work is outside our competence or integrity boundaries, we say so and, where we can, suggest alternatives.
- Stage 2
Scoping and agreement
Scoping turns a general request into a defined piece of work. We identify objectives, success criteria, inputs, methods, deliverables, assumptions, risks and responsibilities. We agree on communication channels, review points, file formats, confidentiality arrangements and the handling of intellectual property and authorship. We produce a written scope with a timeline and an estimate of effort.
The scope also states what is not included. This reduces disputes and protects both sides.
- Stage 3
Data and materials intake
We request the data, models, drafts or documents needed, together with metadata: units, sources, collection methods and known issues. We check completeness and quality, and we report any problems such as missing values, inconsistent units or undocumented transformations. Files are exchanged by a method agreed at scoping.
If the data are insufficient for the planned analysis, we discuss alternatives before proceeding.
- Stage 4
Planning the technical approach
For simulation work, planning includes model formulation, geometry and mesh strategy, boundary conditions, material data and verification and validation plan. For data analysis, it includes data cleaning, features, validation design and baselines. For optimisation, it includes the objective, constraints and algorithm choice. For manuscripts, it includes diagnosis of structure, target journal fit and editing plan.
We share this plan so the client can correct misunderstandings early.
- Stage 5
Execution with checkpoints
Work proceeds with agreed checkpoints. At each, we share intermediate results, assumptions and open questions. Clients review and provide feedback. Changes to scope are discussed and documented. Important decisions, such as choosing a model simplification or excluding data, are recorded with reasons.
Checkpoints are where many errors are caught, because the client knows the physical system or the field context.
- Stage 6
Verification and quality review
Before delivery, we check the work. For models: convergence, conservation, comparison with benchmarks or measurements. For data analysis: reproducibility of scripts, sanity checks, sensitivity analysis. For manuscripts: consistency, references and figure-data agreement. A second reviewer examines significant deliverables.
We report what was checked and what could not be checked.
- Stage 7
Delivery and documentation
Deliverables are provided in agreed formats, with documentation: methods description, assumptions, input files, scripts, results and limitations. For manuscript work, tracked changes and comment summaries are provided. Clients are encouraged to review everything and ask questions.
Documentation enables the client to reproduce and defend the work in meetings, theses and peer review.
- Stage 8
Revision, follow-up and closure
After delivery, a defined period is available for clarifications and minor corrections. For manuscripts, support can continue through peer review if agreed. At closure, files are returned or deleted according to the agreement and a short retrospective may capture lessons.
If new work arises, it is scoped as a new stage.
Scope, price and what we need
How a technical project is scoped
Scoping turns an enquiry into a written plan: the question to be answered, the methods, the inputs required, the deliverables, the assumptions and the criteria for calling the work complete. We identify missing information, check feasibility and record assumptions, then quote against that scope.
What affects scope and price
- Complexity of the problem and the number of cases or variants
- Data readiness: clean, documented data reduce effort
- Deliverables: analysis only, or analysis plus manuscript text
- Timeline and review rounds
- Need for specialised expertise
What we need from you early
- Objectives and the decision or publication the work supports
- A description of existing data, models or drafts (not confidential files via the public form)
- Constraints: deadlines, journals, standards, confidentiality
What we need from you during the project
Timely access to data and materials, clear decisions at checkpoints, honest disclosure of constraints such as funding rules, deadlines and confidentiality, and willingness to review deliverables carefully. We also need confirmation that you have the right to share the data and that ethical approvals are in place.
Delays in input will delay the timeline.
Running the project
Typical timelines by project type
A feasibility discussion usually takes a few days. A pre-submission manuscript review typically takes under a week for a standard-length paper. A modelling or simulation study can take from a couple of weeks to several months depending on complexity, geometry preparation, validation data and number of scenarios. A data analysis study depends mainly on data quality and the number of models to compare. Systematic reviews take months because of searching and screening. We give a specific estimate after scoping and revise it if inputs change.
These are general descriptions, not commitments. A timeline is only reliable when inputs arrive on time.
Communication and decision-making
We use email and scheduled calls, with written summaries after calls. Questions are collected and answered in batches to avoid fragmentation. Decisions that affect scope, cost or integrity are made in writing. A single named contact on each side prevents conflicting instructions.
If you will be unavailable, tell us in advance.
Version control and file management
We name files with clear versions and dates, keep a change log, and use tracked changes for documents. Data files are kept unmodified, and processed data are saved separately with scripts. For code and models, version control records changes. Clients receive a final package with an index of files.
Good file management reduces errors and makes later revisions easier.
Risk management in research projects
Common risks are missing or poor-quality data, ambiguous objectives, model complexity beyond data, changing requirements, delayed feedback and tight deadlines. We discuss these at scoping, prioritise mitigation, and identify early signs, such as a model that fails to converge or data that contradict assumptions.
If a risk materialises, we propose options: simplify the model, collect more data, reduce scope or revise the timeline.
Examples of how the workflow adapts
For a doctoral student preparing a journal paper, the workflow may skip modelling stages and focus on diagnostic review, restructuring, figures and revision support. For an industrial team wanting a simulation of a heat exchanger, it may emphasise geometry, material data, mesh study, validation against test data and a report. For a research group designing a survey of the literature, it focuses on protocol, search, screening and synthesis.
In each case, scope, deliverables and checkpoints are tailored.
Quality gates and sign-off
Quality gates and sign-off
Each major deliverable passes a quality gate before release. Gates check that scope has been met, assumptions are documented, results are reproducible and limitations are stated. For deliverables that influence decisions outside research, such as design choices, we remind clients that professional sign-off by licensed engineers may be required and that our work is research support.
Sign-off by the client confirms they have reviewed the deliverable and that it meets the agreed scope.
Frequently asked questions
Do I have to pay before work starts?
Terms are agreed at scoping and are in the engagement agreement; the website terms page describes use of this website.
Can I change the scope?
Yes, by agreement, with adjustments to timeline and cost.
Can I speak to the person doing the work?
We aim to make the contact clear at scoping.
What happens to my data after the project?
It is deleted or returned according to the agreement.
Can you work under a non-disclosure agreement?
We can discuss reasonable confidentiality agreements; send the document at the scoping stage.
Do you offer a trial?
We can discuss a small initial piece, such as a review of an abstract or a plan, to check fit.
Starting your project
Use the contact page to send a short description. If you prefer to look at examples of how services are structured first, browse the service catalogue or the research-area pages. When you are ready, we will propose a scoping conversation and give you a written scope within a reasonable time.