The Work That Never Becomes a Project
Requests from other teams, work that comes round every month, and processes that only exist in one person's head. Put all of it somewhere you can see it.
Free forever plan · No credit card required · Set up in minutes
What operations teams are really managing
Operations work does not look like a project. Most of it is a queue: requests arriving from other teams, work that repeats every month, and processes that run the same way every time but are written down nowhere. A tool that only understands a start date and an end date does not help with that. What helps is one intake point, a board per process, statuses that match how the work actually moves, and a record of what was done. Orangescrum handles that alongside your formal projects, which is why it is usually called work management rather than project management.
Why operations work stays invisible
One place for the work that keeps arriving
One intake point
Requests land in a single project with an owner, a priority, and a status, instead of in somebody's inbox.
Work that repeats
Templates and checklists, so a monthly or quarterly process is set up the same way every time it comes round.
A board per process
Custom statuses that match how the work really moves, rather than a generic To do and Done.
Visible load
Reports and workload views showing what the team is carrying, which is usually the argument for another pair of hands.
The process written down
A wiki for how things are done, with versioned documents and approvals in Self-Hosted.
Everyone can raise work
Unlimited users on every plan, so the teams you serve can submit and follow their own requests.
How to set it up
Where operations teams use it
Which edition includes what
| Capability | CloudManaged SaaS | Self-HostedOn-premise / private cloud | Open SourceCommunity Edition |
|---|---|---|---|
| Projects, tasks, and Kanban boards | ✓ | ✓ | ✓ |
| Custom task statuses | ✓ | ✓ | ✓ |
| Checklists on work items | ✓ | ✓ | ✓ |
| Role based permissions | ✓ | ✓ | ✓ |
| Reporting and analytics | ✓ | ✓ | ✗ |
| Custom fields on intake | Pro | ✓ | ✗ |
| Workload management | Premium | ✓ | ✗ |
| Visual workflow designer | ✗ | ✓ | ✗ |
Business operations FAQ
We do not really run projects. Is this still useful?
Yes, and this is the most common starting point for operations teams. A project in Orangescrum can just be a container for a process or a request queue, with its own board and its own statuses. You get owners, dates, history, and reporting on work that currently lives in email.
Can we use it as an internal request queue?
Yes. Create one intake project, give it statuses like New, Triaged, In progress, and Done, and let other teams raise items with mentions and watchers so they can follow their own request. It is not a full ITSM suite: there are no SLA timers, no escalation rules, and no CMDB, so if you need formal service level reporting you would want a dedicated service desk.
How does Orangescrum handle recurring work?
Through project templates and checklists rather than an automatic scheduler. You build the process once as a template with its steps and checklists, then create the next instance from it, so nobody rebuilds the month end close or the onboarding sequence from memory. It is worth being clear that this is a reuse mechanism, not a robot that raises the tasks for you.
Is this a CRM or an accounting system?
No to both. There is no CRM, no sales pipeline, no general ledger, and no accounting. Orangescrum handles project cost and client invoices only. If you are looking for a system to run your finance function or your sales process, this is not it, and we would rather you knew that now.
Can other teams submit work without a license cost?
Yes. Every plan includes unlimited users on a flat monthly price, so there is no reason to keep anyone out. Role based permissions control what each person can see and change, so a requester can raise and follow work without seeing the whole operation.
Can we shape the workflow to our process?
Custom task statuses are available in every edition, including the free Community Edition, so each process can have its own stages. The Self-Hosted edition adds a visual workflow designer where you define which transitions are allowed, what rules apply, and who is permitted to make each move.
Is there a genuinely free version?
Yes. The Community Edition is free and open source under AGPL with no user limit, and you install it yourself. It includes projects, tasks, Kanban, calendar, time logging, custom statuses, checklists, milestones, and role based permissions, but not reporting, custom fields, or the workflow designer.
How do we show leadership how busy the team is?
Time logging is on every plan, so hours against work items build a real picture rather than an impression. Reporting and analytics on Cloud and Self-Hosted show throughput and progress, and workload management on Premium shows who is over capacity, which is the chart that usually wins the headcount conversation.
Get the invisible work onto a board
Free 14 day trial, no credit card. Unlimited users on every plan, or run the free open source edition.