Write a conference travel-grant application around the funder's questions
Answer conference funding questions with a checked activity, intended benefit, status and cost request.
About 4 min read · Allow extra time for the practical checks
Answer the particular funder’s questions with a checked account of the conference, your proposed activity and the support requested. Explain why this event serves a concrete purpose for your work. General enthusiasm about networking cannot substitute for the details an assessor needs to understand the request.
Begin with the current call, eligibility rules, form, deadline and required supporting documents. This is a writing guide, not a list of open awards or a finding that you qualify. Clear prose cannot make an ineligible activity eligible or guarantee funding.
Separate the questions before drafting the story
Make a short map of what each form field asks you to establish. A field about the choice of conference needs a reason connected to that event. A field about development needs an explanation of what participation would help you do. A budget field needs a traceable cost request, not another paragraph about the importance of your subject.
The Association of Commonwealth Universities’ conference-grant application guidance, checked on 3 November 2026, illustrates this separation: it asks about the conference choice, development, knowledge sharing and, for in-person applications, costs. The page is used here as an example of application questions, not as notice that a funding round is open. Follow the actual current call you intend to use.
Keep a required abstract, biography or support letter distinct from the funding explanation. Reusing a conference abstract alone may describe the proposed paper well while leaving the case for attendance unanswered.
Examine an original fictional application map
The applicant, conference, documents and amounts below are invented teaching material. They do not describe an actual award, trip or quotation.
Imagine a fictional researcher studying how historical map catalogues describe uncertain place names. A conference programme lists a relevant cataloguing session. The researcher has submitted a poster abstract but has not received an acceptance decision. An invented funding form asks for the event’s relevance, intended benefit, a knowledge-sharing plan and a cost breakdown.
| Application question | What this fictional record supports |
|---|---|
| Why this conference? | A named cataloguing session connects to the researcher’s problem of describing uncertain place names |
| What will you do? | Attend the relevant sessions; present the poster only if it is accepted |
| What benefit is intended? | Compare approaches to documenting uncertainty and use that discussion to review the project’s catalogue notes |
| How will learning be shared? | Propose a short departmental briefing after the event; do not call it scheduled unless arrangements exist |
A bounded explanation could begin:
The programme’s cataloguing session addresses how collections describe uncertain place names, a problem in my current work on historical map records. I would use the discussion to review the explanatory notes accompanying my catalogue. My poster abstract is under consideration; I would present it if accepted. I also plan to propose a short briefing for colleagues after the conference.
That is an original teaching paragraph, not a reusable statement of eligibility. If the real call requires an accepted presentation, the pending abstract may prevent an application at that stage. Do not turn submitted into accepted to improve the narrative.
Make the amount agree with the explanation
In this fictional exercise, the cost sheet lists registration of £120, travel of £80 and accommodation of £150: a total of £350. It records £50 of confirmed departmental support. A request for the remaining £300 is arithmetically consistent with those invented entries.
The arithmetic does not establish that a real scheme permits each cost, pays in advance or covers a funding gap. Check the call’s categories and the records behind the amounts. Keep estimates distinguishable from confirmed prices, and pending support distinguishable from an award already made. Do not describe the same cost as fully covered by two sources.
If a form asks for a justification, connect each requested item to the proposed activity. Merely repeating a total in words does not explain what it pays for. Preserve the actual assumptions about attendance mode and duration across the narrative and budget.
Check every status claim before submitting
Compare the finished form with the programme, abstract record, cost evidence and supporting documents. Look particularly for claims that a presentation is accepted, a collaboration agreed, a contribution funded or a follow-up event scheduled. Use the status the record establishes.
Read the application once as a non-specialist assessor. Can you identify the activity, its connection to the work, its intended benefit and the amount requested? Remove unnecessary technical detail while retaining the facts needed to assess the case.
The conference-proposal guide helps describe the proposed contribution. The short academic biography guide helps with a separate biographical field when one is required.
