---
title: "Project Management for Schools | Orangescrum"
description: "Project management software for schools, colleges, and universities. Unlimited users on every plan, a self-hosted edition for campus servers."
canonical: https://www.orangescrum.com/solutions/education
---

# Project Management for Schools | Orangescrum

> For the complete documentation index, see [llms.txt](https://www.orangescrum.com/llms.txt).

[Home](/) / [Solutions](/solutions) / Education

Education

# Project Management for _Schools and Universities_

Coordinate campus projects, accreditation work, research administration, and IT rollouts, with everyone included rather than a licensed few.

Recommended editions[Cloud](/pricing "Cloud - included")[Self-Hosted](/self-hosted "Self-Hosted - included")[Open Source](/open-source/free-download "Open Source - included")

[Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=solutions/education)[Book a Demo](https://calendly.com/orangescrum)

Free forever plan · No credit card required · Set up in minutes

## What does education project management need?

An institution runs on an academic calendar that does not negotiate. Term dates, admissions cycles, accreditation visits, and grant reporting deadlines all arrive whether the work is ready or not. The people doing that work are spread across faculties and professional services, most of them part time on any given project. What that needs is a shared plan everyone can actually access and a cost model that does not punish you for including people. Orangescrum is priced flat with unlimited users, and can run on your own campus servers.

The problem

## Why campus projects _drift_

License budgets decide who participates

Per seat pricing means the project office gets accounts and the academic staff doing the work do not.

✓ Unlimited users on every plan.

Work is invisible between term dates

A project agreed in June has done nothing by September because nobody owned the summer steps.

✓ Named owners and dates on every task.

Accreditation evidence is a summer scramble

Six weeks before a review, staff hunt for minutes and approvals across shared drives and mailboxes.

✓ Evidence attached to the work as it happens.

Every faculty runs its own spreadsheet

Central teams cannot see the estate of projects, so the same rollout is planned three times.

✓ One system, with each faculty scoped to its own projects.

What matters here

## Everyone included, _on a calendar that holds_

-   ### Unlimited users
    
    Flat monthly pricing regardless of headcount, so academic and professional staff can both be inside the system.
    
-   ### Calendar and milestones
    
    Term dates, admissions deadlines, and review visits tracked as real milestones rather than diary reminders.
    
-   ### Faculty level access
    
    Role based permissions per project, so each school or department sees its own work.
    
-   ### Runs on campus
    
    The Self-Hosted edition installs on your own servers or private cloud, with LDAP or Active Directory sign in.
    
-   ### Wiki for standing knowledge
    
    Procedures and handover notes stay with the project when staff and student assistants change over.
    
-   ### Reporting for committees
    
    Progress and effort reporting that can be taken to a committee without building the pack by hand.
    

How it works

## How an institution _gets going_

1

Start with one area

Estates, IT, or the project office, on the free plan or the Community Edition if you want to try it first.

2

Put the calendar in

Add the fixed dates for the year as milestones, then plan backwards from them.

3

Open it up

Add academic and professional staff. Unlimited users means there is no case for leaving anyone out.

4

Roll out across faculties

Each department gets its own projects, with central teams seeing the whole estate.

Who it's for

## Where institutions _use it_

Campus and IT projects

System rollouts and estates work with owners and dates.

[Learn more →](/work-management-software)

Accreditation and review prep

Tasks and evidence in one place before the visit.

[Learn more →](/document-management)

Research administration

Grant funded work tracked against its budget and reporting dates.

[Learn more →](/budget-and-cost-management)

Availability

## Which edition includes _what_

Orangescrum runs as managed cloud, self-hosted on your own servers, or as the open-source Community Edition. Here is exactly what each one includes.

Available in Cloud, Self-Hosted, and the free open source Community Edition.

| Capability | CloudManaged SaaS | Self-HostedOn-premise / private cloud | Open SourceCommunity Edition |

| Projects, tasks, and boards | ✓ | ✓ | ✓ |
| Calendar view and milestones | ✓ | ✓ | ✓ |
| Role based access control | ✓ | ✓ | ✓ |
| Time logging | ✓ | ✓ | ✓ |
| Runs on your own servers | ✗ | ✓ | ✓ |
| Gantt schedule and dependencies | ✓ | ✓ | ✗ |
| Wiki | ✓ | ✓ | ✗ |
| LDAP and Active Directory sign in | ✗ | ✓ | ✗ |

Frequently asked questions

## Education project management _FAQ_

### Is Orangescrum a learning management system or a student information system?

No, and we would rather be clear now than have you find out in a demo. There is no course delivery, no gradebook, no enrolment, no timetabling, and no student records. Orangescrum manages the projects an institution runs: IT and estates work, accreditation preparation, research administration, events, and improvement programmes. It sits alongside your LMS and SIS, not in place of them.

### Do we pay per student or per staff member?

No. Pricing is a flat monthly plan with unlimited users: Basic is 29 dollars a month, Pro is 69, and Premium is 349. There is also a free forever cloud plan for one project and one user, and a free open source Community Edition with no user limit at all.

### Can we run it on our own campus servers?

Yes. The Self-Hosted edition installs on your own infrastructure or private cloud and supports LDAP and Active Directory sign in, so accounts follow your existing directory. The Community Edition is also self-hosted and free under the AGPL license.

### What is the difference between the Community Edition and the paid editions?

The Community Edition covers the core: projects, tasks and subtasks, Kanban boards, calendar, time logging, milestones, checklists, comments, and role based permissions. Gantt charts and dependencies, reporting and analytics, the wiki, custom fields, and client access are in the Cloud and Self-Hosted editions rather than Community.

### Can students or student assistants be given access?

Yes. Because there is no per user charge, you can add student assistants, research assistants, or society organisers and scope them by role to the specific project they are working on. They see that project and nothing else.

### Can each faculty keep its work separate?

Yes. Permissions are role based per project, so a school or department only sees its own projects. A central project office can still be given visibility across everything for reporting.

### Does it help with accreditation or quality review?

Indirectly, and honestly that is how most institutions use it. You track the preparation work as tasks with owners and dates, attach the evidence to those tasks, and the activity history records who did what and when. It is not a compliance product, but it means the evidence is gathered as the year goes rather than in a panic before the visit.

### Can we track grant funded projects against a budget?

Yes. Set a budget per project, define rates, and actual cost builds from logged time, so a grant funded piece of work can be reported against its allocation. Budget and cost tracking is on Pro and above in Cloud, and included in Self-Hosted.

## Get the whole institution on one plan

Free forever plan, a free open source Community Edition, or unlimited users from 29 dollars a month.

[Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=solutions/education_cta)[Book a Demo](https://calendly.com/orangescrum)

## Related capabilities

[Open source editionFree, self-hosted, no user limit](/open-source)[Self-Hosted editionRun it on campus servers](/self-hosted)[Project calendarTerm dates and milestones](/project-calendar)[Wiki managementKnowledge that survives handover](/wiki-management)