--- title: "Project Reports and Analytics Software | Orangescrum" description: "Project reports built from the work itself: progress, burndown and velocity, time and utilisation, cost against budget, and defect trends." canonical: https://www.orangescrum.com/project-reports-analytics --- # Project Reports and Analytics Software | Orangescrum > For the complete documentation index, see [llms.txt](https://www.orangescrum.com/llms.txt). [Home](/) / [Features](/features) / Reports and Analytics Reports and analytics # Project Reports Built From _the Work, Not a Spreadsheet_ Every report here reads the real tasks, hours, and costs. Nobody types the numbers in, so nobody can get them wrong. Available in[Cloud](/pricing "Cloud - included")[Self-Hosted](/self-hosted "Self-Hosted - included")Open Source [Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=project-reports-analytics)[Book a Demo](https://calendly.com/orangescrum) Free forever plan · No credit card required · Set up in minutes ## What are project reports and analytics? Project reporting turns the work a team is already doing into answers about progress, effort, cost, and quality. The value depends entirely on where the numbers come from. Orangescrum builds every report from the actual tasks, time logs, and cost records, so a report is a view of reality rather than a summary somebody assembled by hand. The problem ## Why reporting _is not trusted_ Numbers are typed in Someone rekeys progress into a slide, so the report is a summary of a summary. ✓ Reports read the tasks directly. Reporting is a weekly job Hours go into building the same report instead of doing the work. ✓ Live reports that need no assembly. Delivery and money are separate One report says the project is on track, another says the budget is gone. ✓ Progress and cost from the same data. What you get ## The reports teams _actually run_ Every report named as it appears in the product, grouped by the question it answers, plus the dashboard, the filters that narrow them, and the ways to get the answer out. 01Task reports - ### A task report with three views The same work as a task type breakdown, a statistics table, and a trend line over time. - ### A pie chart grouped six ways Group by assignee, task type, priority, status, epic, or task group and see the split immediately. - ### Average age How long the work that is still open has been sitting open, across the period you pick. - ### Resolution time How long work takes from being raised to being resolved. - ### Created against resolved Whether the team is clearing work faster than it arrives, or falling behind. - ### Recently created tasks What has just landed on the team, before it turns into a surprise. - ### Time since a task moved Which work has been untouched the longest, which is usually where the trouble is. - ### Task cycle How long work spends in each status, so you can find the stage that slows everything down. - ### Pending tasks Everything still open, by person and project, exportable for a one to one. - ### Planned against actual Estimated effort and dates set against what really happened, with a column picker on the table. - ### Due date change reasons Every date that moved, who moved it, and the reason they picked from your own list. - ### Team task report The same view organised by team rather than by project or person. - ### Defect trend, status, and severity Three separate bug reports covering volume over time, current status, and the severity split. 02Sprint reports - ### Velocity How much the team actually completes per sprint, so the next commitment is based on evidence. - ### Burndown Work remaining against time remaining, so a sprint that will not land shows up early. - ### Completed sprint report What was committed, what shipped, and what carried into the next sprint. - ### Reopen or remove a sprint Correct the record when a sprint was closed too early, without editing history by hand. - ### A PDF of the sprint report Render the completed sprint report to PDF for whoever wants a document rather than a link. - ### A probabilistic forecast In the Self-Hosted edition, a delivery forecast built from your own past throughput. 03Time reports - ### Hours spent, four ways The same time data as a burndown, a pie, a grid, and a line, because different people read different shapes. - ### A timesheet report Approved hours by person and project, as a table and as a chart. - ### Weekly usage How much the team logged week by week, and who did not log at all. - ### Billable against non billable Split every logged hour by whether it can be invoiced, down to the individual task. - ### A timesheet workspace In the Cloud edition, daily and weekly timesheet views with approvals and their own reporting. 04People and cost - ### Resource utilisation Where each person's hours went, by date, project, task, label, status, and billability. - ### Resource allocation Estimated against spent hours by week, drilled from role to project to person. - ### Team utilisation Utilisation by role, role group, project, and person, viewed by month or by week. - ### Profitability Revenue against cost per project, filtered by client, manager, project type, status, and date. - ### Resource availability Who has room and who does not, feeding the workload summary on the dashboard. - ### Cost per project and per resource A red amber green cost view and a resource cost view sit on the project overview in every edition. 05Dashboard - ### KPI cards across your work The counts that matter to you, on the screen you land on. - ### Programme, project, and milestone summaries Each one with its own progress view, so a portfolio is not just a list of names. - ### Workload summary Who is loaded and who is free, without opening a separate report. - ### Budget and cost report and chart Budget against actual as a table and as a chart, built from logged hours and your rates. - ### Top projects, active against completed, and clients Three widgets that answer where effort is going and for whom. - ### Your tasks, your overdue, your hours, your progress Four personal widgets so an individual sees their own position, not just the company's. - ### Task status and task type charts The shape of the work in flight, refreshed from the tasks themselves. - ### Activity feed and bookmarks What just happened, and the things you told the system you care about. - ### Storage used overall and per project Where your file storage is going, before somebody asks why the bill went up. - ### Every widget is permission checked A widget only appears for people whose role is allowed to see what is behind it. - ### Hide a widget organisation wide In the Self-Hosted edition an owner can switch a widget off for everybody at once. 06Project overview - ### Status, time worked, and people The three questions asked about a project most often, on the project itself. - ### Files, task types, and to dos What has been produced, what kind of work it is, and what is still outstanding. - ### Recent activity and project notes What changed lately, and the notes the team keeps against the project. 07Filters - ### Twenty one date ranges Today, this week, this month, this quarter, this year, the last and next of each, rolling windows, everything, or your own dates. - ### Daily, weekly, monthly, quarterly, or yearly periods The trend reports let you set the bucket size and how many buckets back to go. - ### By project, person, label, status, and billability Narrow to the slice you are actually being asked about rather than exporting everything. - ### Choose your columns Pick which columns a report shows, and the choice is remembered for next time. 08Export - ### CSV from the table reports Due date changes, resource utilisation, team utilisation, pending tasks, and profitability all export. - ### A real spreadsheet file Resource utilisation writes a spreadsheet file as well as CSV, so formatting survives the handover. - ### A PDF sprint report The completed sprint report renders to PDF, which is what usually ends up in a board pack. - ### Save a chart as an image or PDF Take any chart out of the tool straight from the chart itself. - ### Scheduled email reports Weekly usage, a task status digest, daily due reminders, a daily update report, estimate against actual, and team utilisation. How it works ## How to _get a report out_ 1 Work normally Tasks get updated and hours get logged. That is the data collection step. 2 Pick the report Choose the standard report that answers your question. 3 Filter it Narrow by project, person, date range, or your own custom fields. 4 Share or export Send it, export it, or put it on a schedule so it arrives by email. Who it's for ## Different questions, _different reports_ Delivery leads Is this sprint going to land, and what is blocking it. [Learn more →](/agile-project-management) Finance and ops What did this project cost, and was it profitable. [Learn more →](/budget-and-cost-management) Resource managers Who is over capacity and who has room. [Learn more →](/resource-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. The report suite is in Cloud and Self-Hosted. The dashboard and project overview are in every edition. | Capability | CloudManaged SaaS | Self-HostedOn-premise / private cloud | Open SourceCommunity Edition | | Dashboard widgets and KPI cards | ✓ | ✓ | ✓ | | Project overview widgets and cost views | ✓ | ✓ | ✓ | | Scheduled email reports | ✓ | ✓ | ✓ | | Task, age, resolution, and cycle reports | ✓ | ✓ | ✗ | | Planned against actual and due date reasons | ✓ | ✓ | ✗ | | Defect trend, status, and severity reports | ✓ | ✓ | ✗ | | Sprint burndown, velocity, and sprint report | Pro | ✓ | ✗ | | Time and timesheet reports | Pro | ✓ | ✗ | | Cost, budget, and profitability reports | Pro | ✓ | ✗ | | Utilisation, allocation, and availability | Premium | ✓ | ✗ | | Twenty one date ranges and period bucketing | ✓ | ✓ | ✗ | | Column pickers on the table reports | ✓ | ✓ | ✗ | | Export to CSV, spreadsheet, PDF, and image | ✓ | ✓ | ✗ | | Daily and weekly timesheet workspace | ✓ | ✗ | ✗ | | Probabilistic delivery forecast | ✗ | ✓ | ✗ | | Hide a dashboard widget organisation wide | ✗ | ✓ | ✗ | | Custom dashboards and BI | Premium | ✓ | ✗ | Frequently asked questions ## Reports and analytics _FAQ_ ### What reports does Orangescrum include? Task reports covering type, statistics, and trend, plus average age, resolution time, created against resolved, recently created, time since last change, task cycle, pending tasks, planned against actual, and due date change reasons. Sprint burndown, velocity, and a completed sprint report. Hours spent in four views, timesheets, and weekly usage. Resource utilisation, allocation, team utilisation, availability, and profitability. Defect trend, status, and severity. ### Where do the numbers come from? From the tasks, time logs, and cost records themselves. Nothing is typed into a report, which is why the numbers cannot drift away from what the team is actually doing. ### Can I build my own reports? Yes. Custom dashboards and the advanced BI layer let you build reports against your own data, including your custom fields. That is on the Cloud Premium plan and included in Self-Hosted. See the advanced reporting page for detail. ### Can I export to Excel? Yes. The table reports export to CSV, resource utilisation also writes a real spreadsheet file, the completed sprint report renders to PDF, and any chart can be saved as an image or a PDF. ### Can reports arrive by email? Yes. You can schedule weekly usage, a task status digest, daily due reminders, a daily update report, an estimate against actual management report, and team utilisation reports, choosing the frequency and who receives each one. ### How far back can I filter? There are twenty one date ranges built in, from today through to rolling windows and the whole history, plus your own custom dates. The trend reports also let you set a daily, weekly, monthly, quarterly, or yearly bucket. ### Do custom fields appear in reports? Yes. Anything you capture in a custom field is available for reporting, which is normally the reason for creating the field. ### Is reporting in the free Community Edition? The report suite is not. The Community Edition does include the dashboard with its widgets, the per project overview with its cost views, and scheduled email reports, but the ProjectReports and Reports suite, sprint reporting, and utilisation reporting are in Cloud and Self-Hosted. ### Can I report across several projects at once? Yes. Reports can span projects, which is what you need for portfolio and programme level questions rather than single project status. ## Get reports you can actually trust The report suite is in Cloud and Self-Hosted. Every plan includes unlimited users. [Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=project-reports-analytics_cta)[Book a Demo](https://calendly.com/orangescrum) ## Related capabilities [Advanced reportingBuild your own dashboards](/advanced-reporting)[DashboardOne screen for status](/all-in-one-project-management-dashboard)[TimesheetApproved hours behind the numbers](/timesheet)[Budget and costWhere cost reporting comes from](/budget-and-cost-management)