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.
A proposal is an argument for a future piece of work: that a problem matters, that the proposed approach can address it, that the team can deliver it and that the resources requested are appropriate. Reviewers read many proposals quickly, and those that fail usually fail on coherence rather than on a lack of ideas. Aims do not match the work plan, the plan does not match the timeline, or the novelty is not shown against what already exists.
Support for proposals and grant applications concentrates on that coherence. It does not substitute for the researchers' own scientific vision, and it does not guarantee funding, which depends on competition and priorities that no adviser controls. It does help to make the idea legible, the plan credible and the document consistent with the funder's guidelines.
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
- Aims that are ambitious but not supported by a credible work plan
- Unclear novelty relative to existing literature
- Methodology and timeline that do not match each other
Methods and analytical approaches
- Aims, objectives and work-package structuring
- State-of-the-art positioning
- Feasibility and risk review
- Impact and dissemination narrative
Applications
- PhD research proposals
- Grant applications to public or private funders
- Internal R&D funding requests
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: call or guideline document
Typical inputs required from you
- Call or guideline document
- Draft idea, abstract or previous proposal
- Budget and team constraints
Deliverables
- Structured proposal draft or review notes
- Work-plan and risk table
- Alignment checklist against the call
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
Structuring aims and work packages
Good aims are few, specific and linked to measurable deliverables. We work from the central question to aims, from aims to objectives and from objectives to work packages with tasks, milestones and dependencies. A logic check confirms that every task serves an aim and every aim has tasks that address it. Overlong lists of objectives are consolidated so that the plan remains credible within the time and budget.
Positioning against the state of the art
Reviewers need to see what is already known and what remains. A concise state-of-the-art section shows the most relevant prior work, what it achieved and its limits, then leads naturally to the proposed contribution. We help identify the closest competing approaches and articulate the difference precisely, avoiding both false claims of being first and vague statements of novelty that reviewers cannot assess.
Feasibility, risk and resources
Feasibility is demonstrated through preliminary data, access to equipment and expertise, a realistic schedule and an analysis of risks with mitigation. We review whether the budget and timeline match the work plan, whether critical dependencies such as materials, permits or collaborators are secured and whether contingency plans exist. Honest risk analysis strengthens a proposal because it shows that the team understands where the work is difficult.
Impact, dissemination and fit with the call
Funders look for relevance to their priorities. We compare the draft with the call text and evaluation criteria and check each requirement is addressed visibly. Impact is described concretely: who could use the results, how they will reach them and what outputs, such as publications, datasets or prototypes, will be produced. Claims of impact are kept proportionate to what the project can plausibly achieve.
Reviewing the document as a whole
A final consistency pass reads the proposal as a reviewer would, quickly and critically. We check that the abstract matches the aims, that every aim appears in the work plan, that terminology is used consistently, that figures and tables are referenced and legible, and that the budget justification mirrors the activities described. Page limits and formatting rules are verified against the call. Small inconsistencies can undermine confidence, so this pass is often where a good proposal becomes a convincing one.
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
- Too many aims for the time and budget. Overambitious plans signal poor judgement and undermine confidence in the team.
- Novelty stated but not shown. Without a comparison to the closest prior work, reviewers cannot see what is new.
- Ignoring evaluation criteria. A proposal that does not map to the scoring criteria makes the reviewer's job harder and costs points.
- Last-minute drafting. Late preparation leaves no time for consistency checks between the narrative, the budget and the timeline.
What good reporting looks like
The outputs are a structured draft or annotated review of the proposal, a work-plan and risk table, a checklist mapping the text to the call's requirements and a consistency review of aims, tasks, timeline and budget. The content remains the researchers' own scientific plan; budgets, institutional approvals and eligibility are the applicants' responsibility. No outcome is guaranteed, and statements about expected results are phrased as hypotheses rather than promises.
An illustrative scenario
Hypothetical example written for explanation. It is not a client case, a result or a testimonial.
Consider a team drafting a proposal for a three-year project. Their first draft lists six aims and a one-page timeline. Review finds that two aims share the same task, one aim has no deliverable and the timeline front-loads work that depends on equipment arriving in year two. The revised version has three aims, work packages with named deliverables, an explicit risk table for equipment delay and a narrative that places the contribution against two close competing approaches.
Questions to settle before you begin
- What is the central question that all aims serve?
- Does every task map to an aim and every aim to deliverables?
- What preliminary evidence shows the plan is feasible?
- Which risk would hurt the project most, and how will I respond?
- Where does the call's evaluation criteria appear in my text?
Key terms
- Work package
- A defined group of tasks with a goal, deliverables and timeline.
- Milestone
- A checkpoint that marks completion of a significant stage.
- Deliverable
- A tangible output of the project.
- State of the art
- The current best knowledge or practice in the area.
- Risk mitigation
- Planned actions to reduce the likelihood or impact of a risk.
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
Do you write the proposal for me?
We can draft and edit text from your ideas and data and review structure and feasibility. The scientific vision and responsibility for the submission remain yours, and nothing is invented on your behalf.
Can you write the whole proposal for me?
We can draft and structure text from your ideas and materials. The scientific content, claims and commitments must be yours and accurate.
Do you guarantee funding?
No. Funding decisions depend on competition and funder priorities.
Can you help with a PhD research proposal?
Yes. The principles are similar: a focused question, a justified method and a feasible plan within the programme timeframe.
Can you check my budget?
We can check that the budget is consistent with the work plan. Eligibility rules and institutional costing remain the responsibility of your research office.
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.