How to Budget the IT Part of a Teaching Development Grant

A practical, step-by-step method for academics to scope, phase and cost the software, app, VR or AI component of a TDG or FITE proposal — and avoid the three most common budgeting mistakes.

Gigantic WorkEngineering team • Nov 16, 2026

Many teaching development proposals include something digital: a learning platform, a mobile app, a VR module, an AI practice tool. The pedagogy section is usually strong. The IT section is often a single line — “Development of an interactive platform: HK$200,000” — and that line causes most of the trouble later.

This guide shows how to turn that line into a short, defensible plan that reviewers trust and that a vendor can actually deliver. It applies to internal Teaching Development Grants funded through the UGC’s Teaching Development and Language Enhancement Grant (TDLEG) for 2025–28, and to proposals for the Fund for Innovative Technology-in-Education (FITE), which continues for 2026/27–2028/29.

The short version

Describe what learners will do, break the build into five phases, cost effort in person-days rather than guessing a lump sum, and always include pilot, evaluation and handover. Want a head start? Our Grant IT Budget Planner produces a first draft in a minute.

Step 1: Describe the learning activity, not the technology

Reviewers fund learning outcomes. Start the IT section with one or two sentences about what a student will do:

  • “Students rehearse a clinical interview with a virtual patient and receive structured feedback.”
  • “Students explore 3D models of archaeological artefacts before the museum visit.”
  • “Students ask questions about assessment rules and receive answers that cite the course handbook.”

Only then name the technology. This keeps the scope honest: every feature has to serve the activity.

Step 2: Choose the smallest thing that proves the idea

Grant budgets are fixed and timelines are short. Decide what kind of product you need:

If you need… Consider Why
Content students view on any device A web platform or browser 3D module No app-store approval, works on student laptops and phones
Offline use, camera, notifications A cross-platform mobile app Native device features, but more testing and store review
Full immersion or hand tracking A Unity VR build for headsets Best experience; needs headsets and device management
Answers from course documents An AI assistant with citations Must be grounded in approved materials and hosted to policy

A browser-based module that also runs on a VR headset (WebXR) is often the right first step: it reaches every student and still offers immersion for those with a headset. See our Unity or WebXR guide.

Step 3: Break delivery into five phases

Proposals that show phases are easier to review, easier to report on, and easier to quote. A typical shape:

  1. Discovery & design (≈15% of the timeline) — workshops with teachers and students, user journeys, a clickable prototype.
  2. Build in sprints (≈45%) — working releases every two weeks, reviewed by the teaching team.
  3. Pilot with real users (≈20%) — use in an actual class; collect feedback and usage data.
  4. Evaluate & refine (≈10%) — fix what the pilot revealed; prepare evidence for the report.
  5. Handover & sustainability (≈10%) — documentation, admin training, hosting transfer.

Line these phases up with your semester calendar. A pilot that misses the teaching term usually slips by six months.

Step 4: Cost effort in person-days

Vendors price by effort. Estimating in person-days lets you sanity-check any quotation you receive later. Rough ranges for a standard-scale build:

Project type Typical effort (person-days)
Web platform / course site 25–45
Browser 3D / WebXR module 20–40
AI assistant with citations 25–50
Data dashboard / research database 20–40
Cross-platform mobile app 40–70
Unity VR / AR experience 45–90

Then add what proposals usually forget:

  • Bilingual interface (English / Traditional Chinese): roughly +15% of build effort.
  • Single sign-on or LMS integration: a few days, plus time waiting for central IT approval.
  • Accessibility review against WCAG 2.2 AA: a few days; much cheaper than retrofitting.
  • 3D models and media: content production is often as large as the software itself.
  • Analytics for evaluation: decide now what evidence your final report needs.

Multiply by a realistic day rate and present a range, not a single number. Ranges signal that you understand uncertainty; reviewers trust them more.

Step 5: Budget for life after the grant

The most common failure of grant-funded software is not a bad build. It is a good build that disappears eighteen months later because nobody owns the server, the certificate expired, or an operating-system update broke the app.

Include in the proposal:

  • Where it will be hosted (ideally on university infrastructure).
  • Who receives the source code and documentation.
  • A modest support budget for the first year after launch.
  • A named owner in the department after the project team leaves.

Our guide on keeping grant-funded software alive has a full checklist.

Step 6: Check procurement before you submit

Your budget will eventually become a purchase. Each university sets its own rules for how many quotations are needed at each value, and when a tender is required. Ask your department office early, and size phases so that procurement does not delay your start date.

Three budgeting mistakes we see most

1. One lump sum with no phases — impossible to review or report against. 2. No pilot — the first real users arrive after the money is spent. 3. No handover — the system outlives the grant by months, not years.

A template paragraph

The project will develop a responsive, bilingual web platform with an interactive 3D module, delivered in five phases over 18 months: discovery and design (months 1–3), iterative development (months 4–11), a classroom pilot (months 12–15), evaluation and refinement (months 16–17), and handover (month 18). Indicative external development cost is HK$X–Y (approximately N person-days), plus one year of hosting support. Full source code, documentation and administrator training will be handed over so the platform remains in use beyond the funding period.

Adjust the numbers with the planner, or send us your draft for a free review.

WORK WITH US

Planning a project like this?

Gigantic Work builds web platforms, research portals, AI tools, Unity/VR experiences and cloud infrastructure for Hong Kong universities, grant-funded projects, NGOs and SMEs — and hands over everything at the end.