
Your ERPNext Projects Deserve Better Than Spreadsheets
Your ERPNext Projects Deserve Better Than Spreadsheets
Project delivery usually ends up outside the ERP: work items in one tool, hours in a timesheet export, risks in a conversation nobody wrote down. The cost is not the second licence fee, it is that nobody can answer "where are we?" without assembling it by hand. Auri PMS puts tickets, sprints, releases, time logs, risks, dashboards and client status reports on the same ERPNext Project record the rest of the business already uses. It runs on ERPNext v16, is free and open source on the Frappe Cloud Marketplace, and modifies nothing in ERPNext core.
- The problem is not a missing dashboard. It is that delivery data and business data live on different records, so every answer needs reconciling first.
- A health traffic light somebody sets by hand is an opinion. Scored from the project's own data, it is a measurement, and it can say why.
- Weekly client reporting is where scattered data costs the most, because it cannot be skipped and cannot be automated when the inputs are in four places.
- Anything added to a production ERP has to leave core untouched, or you pay for it at the next upgrade.
It is four o'clock on a Friday. A client sends one line: "Where are we on the release?"
Somewhere a project manager opens a spreadsheet, then a chat thread, then a timesheet export, then a half-remembered standup note, and starts stitching an answer together by hand. Forty minutes later a reply goes out that is roughly accurate and already slightly out of date.
That scramble is not a people problem. It is a tooling problem. The work is tracked in one place, the hours in another, the risks in someone's head, and the client report in a deck rebuilt every week from four sources that do not agree with each other. The fix is not another tool to check. It is one fewer.
The question behind the question
"Where are we?" is really four questions wearing one coat. How much is done. How much is left. What is going to go wrong. And what of that is our fault rather than theirs.
Each of those lives in a different place in most setups, which is why the answer has to be assembled rather than read. The work breakdown is in the project tool. The effort is in timesheets. The risk is in a conversation. The client dependency is in an email thread from Tuesday that nobody tagged.
Status should be something you look up, not something you assemble.
Why delivery data drifts out of the ERP
Usually because the ERP was chosen for finance, inventory and operations, and project delivery was never part of that conversation. A dedicated project tool gets added later, often by the delivery team rather than by IT, and it works well enough on its own terms.
The problem shows up at the joins. Hours logged in the project tool have to be reconciled against the ones that reach invoicing. The project a client is billed for and the project a team works in are two different records with two different names. Reporting means exporting both and lining them up in a spreadsheet.
Delivery runs in one system, the business runs in another. Every report begins with reconciliation, and every number has two versions until someone decides which one is true.
Work items are logged against standard ERPNext Projects. The project finance sees and the project the team works in are the same record, so there is nothing to reconcile.
What visibility actually means
Visibility is not a dashboard with more charts on it. It is whether the things that quietly go wrong announce themselves without anyone having to ask.
Most delivery problems are not hidden by bad people. A blocked ticket sits quietly for a week. A risk everyone knows about never gets an owner. A client approval holds up three tasks and nobody can say for how long. None of that is concealed. It is just not counted anywhere.
Four mechanismsWhat counting it looks like in practice
| What goes wrong quietly | How it gets counted |
|---|---|
| Work waiting on the client | A ticket marked Dependent on Client records a note and a waiting-since date. The wait is counted on every dashboard and listed in the client report, so it stops being read as your delay. |
| Risks with no owner | Probability and impact are each scored 1 to 5 and the product sets the level. Every risk carries an owner, a mitigation plan, a contingency plan and a due date. |
| Blocked work moving anyway | Status transitions are configurable per project role. A move the workflow does not allow is refused on the board rather than quietly accepted. |
| Effort overrun found late | Hours are logged against a ticket with an activity type and a billable flag, then read against the estimate. Limits per entry and per day, plus lock days, keep the numbers trustworthy. |
ScoringRisk levels, deliberately boring
Probability times impact, with the level following from the number rather than from whoever is loudest in the room. Open risks pull the project health down automatically, and risks flagged for the client report appear there with their mitigation.
| Impact ↓ / Prob → | 1 | 2 | 3 | 4 | 5 |
|---|---|---|---|---|---|
| 5 | 5 | 10 | 15 | 20 | 25 |
| 4 | 4 | 8 | 12 | 16 | 20 |
| 3 | 3 | 6 | 9 | 12 | 15 |
| 2 | 2 | 4 | 6 | 8 | 10 |
| 1 | 1 | 2 | 3 | 4 | 5 |
Low is 1 to 4, Medium 5 to 9, High 10 to 14, Critical 15 to 25. The thresholds are configurable, which matters more than the defaults do.
Five dashboards, five questions
A dashboard is only useful if it answers a question someone is actually asking. Five come up on nearly every delivery team, and each belongs to a different person.
| Dashboard | The question it answers | Who it is for |
|---|---|---|
| Project Health | Is this project on track, at risk or off track, and why? | Project managers |
| Portfolio | How do all my projects compare on budget burn, overdue work and capacity? | Management |
| My Work | What should I focus on today? | Every team member |
| Quality | Are we opening bugs faster than we fix them? | QA and engineering leads |
| Client Status Report | What do I tell the client this week? | Account and delivery teams |
They share one theme and one range, so switching from one month to overall changes all of them together rather than one at a time. Every count on every dashboard is clickable and opens the tickets or time entries behind it, which is the difference between a number you believe and a number you can check.
Scoring health instead of declaring it
The health verdict is the part worth being careful about, because a traffic light somebody sets by hand is an opinion with a colour attached. Here it is calculated live from the project's own data, and each check that fires costs points and is written out as a reason in plain words, such as "12% of open tickets are overdue (3)."
The thresholds below are defaults rather than laws. They are the first thing to tune once a team has run on them for a month, because a studio doing two-week sprints and an implementation team doing six-month rollouts do not agree on what late means.
| Check | At risk (amber) | Off track (red) |
|---|---|---|
| Overdue open tickets | More than 10% of open tickets | More than 25% |
| Active sprint | Slightly behind the ideal burndown | Well behind it |
| Effort | Hours run ahead of work completed | Hours exceed the estimate |
| Releases | At 80% or less and due within 7 days | Past the due date and under 80% done |
| Risk register | A High open risk, or one past its mitigation date | A Critical open risk |
| Backlog | More created than resolved over four weeks | Not applicable |
Showing the health status on the hub, on the portfolio and in the client report are three separate switches, and all three are off by default. Counts and charts always appear. That lets a team keep the judgement internal while the client sees only what happened, which is usually the right order to introduce it in.
Client reporting without rebuilding the deck
Weekly client reporting is where the cost of scattered data lands hardest, because it is the one task that cannot be skipped and cannot be automated when the inputs live in four places.
When the delivery data already sits in one system, the report stops being an assembly job. Delivered work, work in progress, what is waiting on the client, hours, the plan and the open risks are all read from the same project record.
- Pick a layout, or use the built-in one. Custom email templates work once enabled
- Switch sections on or off and drag them into order, for one send or as the default
- Remove a ticket from this send, or add one with a note for the client
- Preview the report exactly as the client will receive it
- Email it, download the PDF, or schedule it weekly, monthly, or both
- Every send is logged with delivery status, so there is a record of what went out and when
The goal is not more reporting. It is a project where the report writes itself.
How a project moves through the system
From first ticket to final report, the same data carries the project. Nothing is retyped between stages, which is the entire point.
Daily due-date digests keep the team moving between reports, and optional email-to-ticket intake turns an incoming message into a work item without anyone rekeying it.
Getting started without a rollout plan
Adding anything to a production ERP usually means a project of its own. This one does not. The only setup the app requires is adding project members, and ordinary ERPNext projects are left alone until you tick the box that brings one in.
- Enable it on one project
Open an existing ERPNext Project, go to the Auri PMS tab, set a short identifier such as
PASS the project appears on the Project HubAURIand tick Enable. Ticking it selects every active ticket type; untick the ones you do not want. Pick a real project that is already running, not a test one, because the dashboards only say anything useful with real work in them. - Add members and set roles
This is the only setup the app insists on, and it controls who sees the project. Three roles exist at the system level: Admin, Manager and User. Inside a project, each member's project role carries nine capability flags covering who can create, edit, delete, manage releases and members, log time, edit other people's time and be assigned.
PASS each member sees the project, and nobody outside it does - Define your modules before logging tickets
Modules are the parts of the product a ticket belongs to, such as Sales, Stock or Accounts. Do this first. Dashboards, reports and the client report all break their numbers down by module, so tickets logged before the modules exist produce a breakdown with a large unhelpful "none" bucket in it.
PASS the Module field offers your own list - Run one sprint and log time against it
Add tickets, set a goal and dates, press Start. Agree the time rules up front: a limit per entry, a limit per day, and a lock day after which old entries cannot be edited. Set each member's allocation as a share of weekly capacity so over-allocation and burnout flags have something to measure against.
PASS the burndown moves and My Work shows hours against capacity - Log your real risks, then leave the thresholds alone for a month
Score probability and impact, assign an owner, write the mitigation and a due date. Flag anything waiting on a client answer as Dependent on Client with a note. Resist retuning the health thresholds in week one. Give it a month of real data first, then adjust in PMS Settings under Risk and Health.
PASS the health banner shows a status with reasons you recognise - Send one client report by hand before scheduling it
Choose a layout, set the sections and their order, preview it, and send it manually once. Read it as the client will. Only then set the weekly day or monthly date, and add the recipients on the project's Auri PMS tab. Scheduled sends use the defaults in PMS Settings, so get those right before automating.
PASS the send is logged as a Project Status Report with a delivery status
Does it change ERPNext itself?
This is the question that decides whether anything gets installed on a production ERP, and it deserves a direct answer: no.
| Concern | How it is handled |
|---|---|
| Upgrade safety | Nothing in Frappe or ERPNext core is modified. Everything is added through hooks, custom fields, custom permissions and document events |
| Learning curve | Standard Desk UI only. Forms and lists keep the familiar Frappe look, so there is no second interface to train people on |
| Hosting | No OS packages and no custom bench commands at runtime, so it installs on a managed Frappe Cloud site as readily as a self-hosted bench |
| Reversibility | Uninstalling removes the custom fields, the Kanban board, the workspace and the permissions it added. ERPNext activity types are left alone |
| Licence | MIT, with the source public. Free on the Frappe Cloud Marketplace, with no paid tier behind it |
| Version | Frappe v16 and ERPNext v16, with ERPNext as a required app |
Where this falls short
Worth being clear about the edges before you put it on a live client project.
- It needs v16. Frappe and ERPNext v16 are both required. If you are on v15 and not planning to move yet, this is not the quarter for it.
- The dashboards are only as honest as the logging. Health is scored from tickets, hours and risks. A team that logs time on Friday for the whole week, or never raises a risk until it has already happened, will get a reassuring green light that means nothing.
- The default thresholds will not suit everyone. Ten percent overdue is a sensible starting point, not a universal truth. Expect to tune them, and expect the first month of scores to be noisier than the second.
- A health score is a summary, not a judgement. It tells you where to look. It does not tell you whether the client is happy, whether the scope was right, or whether the team is about to quit.
Frequently asked questions
Does this replace ERPNext Projects?
Who can see a project once delivery data sits in the ERP?
Can billable and non-billable time be tracked separately?
How is project health calculated rather than guessed?
Can clients receive status reports automatically?
Does installing it modify ERPNext itself?
Which ERPNext version does Auri PMS need?
Want to see it on your own project data?
Auri PMS is free and open source on the Frappe Cloud Marketplace, so you can install it and judge it yourself. Auriga IT implements and supports ERPNext across manufacturing, distribution and services. If you are weighing whether delivery belongs inside your ERP, we are happy to look at one project with you.
Install from the marketplace → Talk to our ERP team →Verified 26 October 2026 against the Frappe Cloud Marketplace listing and the Auri PMS repository README. Feature names and thresholds reflect the current release and may change in later versions.
Related content
Auriga: Leveling Up for Enterprise Growth!
Auriga’s journey began in 2010 crafting products for India’s [...]






