Most professional development requests fail not because the request is unreasonable but because it is framed badly. Staff ask for a course they want; managers hear a cost and a day of lost cover. The staff who consistently get their development funded and their time protected have learned to make the case in terms the institution already cares about — and to make it easy to say yes.
This is a learnable communication skill, and it works whether you are a teaching assistant in Manila asking for conference funding or a senior administrator in Berlin proposing a leadership programme. It also matters when you advocate for your team's development, not just your own. This article sits in our Leadership, Service & Committees collection; read it alongside our guide to common development mistakes.
Speak the institution's language
Every institution runs on a small number of priorities — usually some mix of teaching quality, research performance, student outcomes, financial sustainability and risk. Managers approve things that visibly advance these. A request framed as "I would find this interesting" competes poorly against one framed as "this will improve our student satisfaction scores" or "this closes a compliance gap that currently exposes the department."
Before you ask, find the language. Read your department's strategic plan and your institution's priorities, and connect your development explicitly to one of them. Frame time and money not as things you want but as investments in an outcome your manager is accountable for. This reframing — from personal benefit to institutional benefit — is the single biggest lever in the whole conversation, and it applies equally when you argue for workload relief, as covered in our workload management guide.
Frame development as a return on investment
Managers weigh cost against benefit, often informally. Help them do the sum. A specific request with a clear payback beats a vague one every time: "a two-day grant-writing course costing X, after which I will lead two funding applications this year with a target of one award" is far more compelling than "I'd like to go on a grant course." Name the cost honestly, including cover, and name the benefit concretely, ideally something measurable.
Where you can, offer to reduce the cost or share the benefit. Propose to cascade what you learn to colleagues, or to trial a cheaper option first. Reference recognised frameworks to show your development is credible and portable — the Vitae Researcher Development Framework is widely respected for exactly this. Showing you have thought about return, not just want, signals maturity and makes approval low-risk for your manager.
Prepare for the development review conversation
The appraisal or development review is your annual formal opportunity, and most staff waste it by improvising. Come prepared with three things: a concise record of what you have achieved and developed since the last review, a clear statement of your goals, and one or two specific development requests linked to those goals and to institutional priorities. This turns a passive form-filling exercise into a negotiation you are driving.
Bring evidence, not assertions. "I led the new-student induction redesign, which raised attendance by 15%" opens a very different conversation than "I've had a busy year." The AcademicStaff development ledger makes this preparation trivial: it holds your logged achievements and development activities year-round, so you walk into the review with a complete, credible record rather than a hastily reconstructed one. A manager faced with concrete evidence and a specific, well-framed request finds it far harder to defer.
Advocating in committees and for your team
If you chair or sit on a committee, or manage a team, you often advocate for development on behalf of others — and the same principles scale up. When proposing a team development budget or a new programme, lead with the institutional problem it solves and the risk of inaction, quantify where you can, and anticipate the objections about cost and cover before they are raised. Committees approve proposals that are pre-answered.
Be strategic about timing and allies. Raise significant proposals when they align with budget cycles and strategic reviews, and line up support from colleagues before the meeting rather than hoping for it in the room. Our Leadership, Service & Committees collection covers committee craft in depth. Advocating well for your team also builds your own leadership record — it is development in both directions.
Reporting outcomes so the next request is easier
The most under-used tactic is closing the loop. Staff win development approval, complete the activity, and never report back — so the next request starts from zero. A short, unprompted note to your manager after the fact — "the course I attended has directly enabled X, and I have shared it with the team" — is disproportionately powerful. It proves the investment paid off and makes your next ask almost automatic.
Treat every completed development as a small case study of your judgement. Record the outcome in your ledger and communicate it upward. Over a few cycles this builds a reputation as someone whose development requests reliably deliver value, which is the strongest position you can occupy when the budget is tight. Reporting outcomes is also how you make the case, over time, for bigger investments in your growth.
When the answer is no
Sometimes the request is refused, usually for budget or timing. A "no" handled well becomes a "not yet." Ask specifically why, and ask what would need to be true for a yes — a different funding source, a later cycle, a cheaper alternative, a demonstrated need. Convert the refusal into a documented plan with a review date, so it does not simply vanish.
Explore alternatives that do not depend on your manager's budget: free professional-body resources, mentoring, stretch assignments, and open programmes. Many high-value development activities cost time rather than money. Employment-relations bodies such as the UK's Acas and their international equivalents also set out how development and appraisal should be handled fairly, which is useful if you believe a refusal is inconsistent. Keep the record, stay constructive, and return with evidence when the moment is right.
The Development Request Scripts & Business-Case Template
Ready-to-adapt scripts for asking your manager, plus a one-page business-case template that frames any development request in terms of institutional priorities, cost, and measurable return.
Want the full article?
Enter your email for free access to the rest of this guide and our TEQSA resource library.
Frequently asked questions
How do I ask my manager for development funding without seeming self-interested?
Frame the request around an institutional outcome your manager is accountable for, not around personal benefit. Name the cost honestly, state a concrete, ideally measurable payback, and offer to cascade what you learn. Managers approve investments with clear returns far more readily than personal wants.
What should I bring to a development review or appraisal?
Bring a concise record of what you achieved and developed since the last review, a clear statement of your goals, and one or two specific development requests linked to those goals and institutional priorities. Evidence of outcomes turns a form-filling exercise into a negotiation you drive.
My development request was refused — what now?
Ask specifically why and what would need to be true for a yes, then convert the refusal into a documented plan with a review date. Pursue no-cost alternatives such as mentoring, stretch assignments and professional-body resources, and return with evidence when timing improves.
The AcademicStaff editorial team writes practical, evidence-based guidance for university staff — drawing on sector reporting, funder guidelines and the lived administrative reality of academic work. Every guide is reviewed for accuracy against current Australian higher-education practice.