Operations platform
The plan, the timesheet
and the invoice, reconciled
Atmora Track runs delivery portfolios where a slipping task has to change the forecast, the utilisation picture and the revenue schedule at the same time. Time and materials, fixed price and milestone billing coexist inside one project without a parallel spreadsheet.
- Cloud
- Private cloud
- On-premise
Overview
Plans, capacity, timesheets and billing on one model, so the schedule and the invoice agree.
Atmora Track is built for delivery organisations that have to reconcile three things every month: what was planned, what was worked, and what can be invoiced. Plans, resource capacity, timesheets, billing and revenue recognition share one data model, so moving a task two weeks changes the projected finish, the bench forecast and the revenue schedule together. Billing types mix inside a single project, because real engagements do: time and materials through discovery, fixed price for the build, milestones for the rollout, and a change request that moves the baseline without erasing what was originally agreed.
Track is not an issue tracker and is not a substitute for Jira. It reads from Jira, Azure Boards and GitHub for delivery signal and leaves day-to-day engineering workflow where it already lives. Teams that bill nothing and forecast nothing will find the financial half of the product dead weight, and a lighter task tool will serve them better. Track earns its place at the point where utilisation, margin and delivery dates are argued about in the same meeting, typically somewhere above fifty billable people.
- 92%
- Timesheets submitted before Monday midday at Orbit Supply
- -6
- Days from milestone acceptance to invoice raised
- +/-4%
- Revenue forecast accuracy at an eight-week horizon
- -31%
- Bench time across a 900-person delivery organisation
Modules
What ships in the box
- Portfolio, programme and project planning
- Resource capacity and skill matching
- Timesheets, leave and approvals
- Billing, invoicing and revenue recognition
- Risk, issue, change and decision registers
- Delivery reporting and client portal
Integrates with
- Jira
- Workday
- Salesforce
- Microsoft Teams
- SAP S/4HANA
- Tally Prime
- GitHub
- Okta
Capabilities
What it does
Scheduling that respects dependencies and calendars
Finish-to-start links, lag and per-resource working calendars are honoured when a task moves, so downstream dates shift with it instead of quietly going red a fortnight later.
Capacity planned by skill, not headcount
Demand is expressed as role and skill, matched against availability net of leave, holidays and existing allocation, so a plan cannot assume a person who is already fully booked.
Timesheets with a real approval chain
Entries post against a task and a billing type, route to the project manager and then the engagement owner, and freeze at a lock date after which nothing can be edited silently.
Three billing types inside one project
Time and materials, fixed price and milestone billing coexist. Revenue recognition follows percentage of completion or milestone acceptance and never disagrees with the timesheet data.
Change requests that move the baseline
An approved change updates scope, dates and value together while preserving the original baseline, so schedule slip and scope growth can be told apart at the steering meeting.
Burn against budget in both hours and money
Effort and cost burn are plotted against plan with a projected finish, which makes an overrun visible at 40 per cent complete rather than confirmed during handover.
Registers with owners and an ageing clock
Risks, issues, decisions and dependencies each carry an owner and a due date. Anything untouched for two weeks appears in the steering pack without a project manager curating it.
A client portal with a controlled view
Customers see milestones, pending approvals and their own change requests. Internal margin, charge rates and staffing detail stay out of that view through field-level permissions.
Built for
Where this is deployed
Industry
Manufacturing
Getting the plant floor and the ERP to agree on what actually happened during the shift.
Industry
Real Estate & Construction
Model data, site records and payment workflow in one auditable trail from design to handover.
Industry
Telecom & Media
OSS, BSS and delivery platforms that keep working after launch night.
Industry
Public Sector
Digital services that work for everyone who has to use them, including on a five-year-old phone.
Industry
Banking & Financial Services
Payment rails, risk engines and core-adjacent systems built by people who have run them at 03:00 on a settlement night.
Industry
Education
Student and learning systems that survive enrolment week and the statutory return that follows it.
FAQ
Questions we get asked
- Do engineers have to leave Jira?
No. Track syncs epics and issues from Jira, Azure Boards or GitHub and maps effort to plan items, so engineers keep working where they are. Only timesheets and approvals require them to open Track, and those can be submitted from Microsoft Teams or Slack.
- How does it handle fixed-price work that goes over?
Cost keeps accruing against the project while revenue stays capped at the contracted value, so margin erosion appears immediately rather than at closure. The overrun is visible per phase, which is usually enough to decide whether to raise a change request or absorb it.
- Is it suitable for internal IT projects with no billing?
Partly. Planning, capacity and registers work well for internal delivery, but roughly a third of the product concerns invoicing and revenue recognition and will sit unused. If nothing is billed and nothing is forecast, a lighter task tool is the honest recommendation.
Related
More Operations platforms
Operations
Inventory Management
Multi-warehouse stock, batch traceability and counting on handheld scanners.
Operations
Visitor Management
Visitor, contractor and delivery access control for multi-site campuses.
Operations
Booking Platform
Slots, resources and reschedules for organisations where an empty hour costs real money.