Every academic has felt it: the grant that stalled because a costing was submitted late, the ethics application bounced on a formatting technicality, the teaching timetable that collided with your fieldwork. And every academic has, at some point, quietly blamed "admin" for it. That instinct is both understandable and self-defeating, because the professional services staff who run research offices, libraries, IT, finance, student administration and quality assurance are not obstacles to your work — done well, they are the single largest source of workload relief available to you.
The relationship between academic and professional services staff has a name in the research on higher education: the "third space," the blended territory where neither group's traditional role fully applies and the most important institutional work actually gets done. This playbook shows how to operate in that space deliberately — who does what, how to partner rather than delegate, and how to convert good collaboration into hours back in your week.
The third space: where the real work happens
The old model imagined a clean split: academics create knowledge, professional staff process paperwork. That model never described reality and describes it less every year. Research funding, ethics governance, learning technology, data management and quality assurance all require deep collaboration in which professional staff carry genuine expertise and academics carry genuine dependency. This blended zone is the third space, and treating it as a hierarchy — where academics command and professional staff obey — reliably produces worse outcomes for everyone.
The mindset shift is to see professional services colleagues as partners with expertise you lack, not as a service counter. A research development manager understands funder psychology better than most principal investigators. A learning technologist knows what actually works in your virtual learning environment. Engaging them early, as collaborators shaping the work rather than processors receiving it at the deadline, is the highest-leverage habit in this whole domain. Our Workload, Wellbeing & Productivity hub explores the wider picture.
Who does what: mapping your support network
Most academics use a fraction of the support available because they never mapped it. Beyond your department there is typically a research office (pre-award costing, post-award management, ethics, contracts), a library with subject specialists and open-access and data expertise, IT and learning-technology teams, a graduate school, finance and HR business partners, and a quality or academic-standards unit. Each holds knowledge that can save you days, and each has capacity you are probably not tapping.
Spend an hour building your own support map: for each function, note the specific person or team, what they can do for you, and their real lead times. Lead times are the hidden variable — the difference between a research office that transforms your grant and one that "failed" you is almost always that you gave them three days instead of three weeks. For a related view on evidencing your own contribution across these boundaries, see our guide to a data-driven approach to career growth. National research-integrity and governance expectations, such as those published at nih.gov, often assume exactly this kind of professional-academic partnership.
Partnering with the research office
The research office is where the partnership pays off most directly, because grant success depends on things academics are rarely trained in: accurate costing, funder-specific compliance, contract negotiation, and post-award financial management. A research development professional who is brought in at the idea stage can shape a proposal toward what the funder actually wants, catch eligibility problems, and build a realistic budget — but only if you engage weeks, not hours, before the deadline.
The practical protocol is simple and transformative: notify your research office as soon as you decide to apply, share the call and your draft aims, and ask what they need from you and by when. Treat their internal deadlines as real, because they exist to protect your submission, not to inconvenience you. When the award lands, keep them close for reporting and financial reconciliation — the same partnership that won the grant keeps it compliant. AcademicStaff's grant progress-report generator helps here by turning your milestones and spend against your work plan into the structured reports funders and research offices both need, so reporting stops eating your research time.
Library, IT and data teams as force multipliers
Subject librarians, learning technologists and research-data specialists are among the most underused colleagues on any campus. Subject librarians can run systematic-review searches, teach information literacy to your students, and manage open-access compliance and article-processing charges. Research-data staff can help you write a data-management plan that satisfies funders and keeps your data usable a decade later. Learning technologists can rescue a struggling online module far faster than you can teach yourself the platform.
The pattern is the same across all three: they multiply your effort when engaged as design partners and merely patch problems when called in at the end. Bring the learning technologist into course design, not into fixing a broken quiz the night before it opens. Bring the data specialist into the grant proposal, where a strong data-management plan can even strengthen your case. This early-partner habit connects directly to keeping a clean research identity and output record, which the library often helps maintain.
Reducing friction and mutual resentment
Friction in the third space is usually structural, not personal. Academics feel slowed by process; professional staff feel treated as servants and blamed for rules they did not write. Both feelings are valid and both dissolve with a few habits. Give realistic notice. Explain the why behind your request so colleagues can find the best route rather than the literal one. Acknowledge their expertise and constraints. Say thank you specifically and publicly — recognition is scarce for professional staff and disproportionately valued.
Just as importantly, distinguish a process from a person. When a form is maddening, the person administering it is your ally in navigating or improving it, not the author of your frustration. Academics who build genuine, respectful relationships with professional colleagues get faster turnarounds, earlier warnings about problems, and the benefit of the doubt when they need a favour — none of which appears in any policy document. These relationships are a quiet but real component of the career progression picture.
Turning collaboration into workload relief
The ultimate point of the third space is not harmony for its own sake — it is workload. Every task a professional colleague can do better and faster than you is a task you should not be doing yourself. Auditing your week for work that belongs to another function, and then genuinely handing it over with enough notice and context, is one of the most effective wellbeing interventions available to an overloaded academic.
Be systematic about it. List your recurring tasks, mark which ones sit in someone else's expertise, and build the relationships and lead times that let you route them there reliably. AcademicStaff's workload calculator can make this visible by showing where your hours actually go, so you can identify the professional-services partnerships that would return the most time. Reference authoritative expectations on research and administrative governance, such as those at ukri.org, to justify the collaborative model to sceptical colleagues.
Your Campus Support Map Template
A fill-in template to map every professional services function you can call on — research office, library, IT, data, finance — with the right contact, what they do for you, and realistic lead times.
Want the full article?
Enter your email for free access to the rest of this guide and our TEQSA resource library.
Frequently asked questions
My research office feels like a bottleneck. How do I fix that?
Almost always by engaging earlier. Notify them the moment you decide to apply, share the call and draft aims, and respect their internal deadlines, which exist to protect your submission. A research office given three weeks transforms a proposal; one given three days can only rubber-stamp it.
Isn't delegating to professional staff just pushing my work onto them?
No — it's routing work to the person who does it best. Costing, data-management planning, learning-technology setup and systematic searching are their expertise, not yours. Handing these over with proper notice and context produces better outcomes and frees you for the work only you can do.
How do I build goodwill with professional services colleagues?
Give realistic notice, explain the why behind requests, respect their expertise and constraints, and thank them specifically and publicly. Distinguish a frustrating process from the person administering it — they're your ally in navigating it, not its author.
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.