Tasks and scheduling
- Task kanbanConfigurable stages with WIP limits.
- GanttDependencies, critical path and drag-to-reschedule.
- Subtasks and checklistsBreak big work into small steps.
- Chatter on tasksNotes, attachments and @mentions.
Fidar Projects puts tasks, schedules and team timesheets next to the project’s contract, billing and costs — so project managers know where the work is and finance knows whether the project really makes money. The module is on the roadmap.
On the roadmap · designed for services, contracting and tech companies
This module is in development. What you read on this page is our design and plan for this module, not something you can use today. We publish its schedule and status on the roadmap.
Problem and solution
The team works in a task tool, hours are collected in spreadsheets and project invoices are issued in the accounting package. Nobody knows until the end whether the project made or lost money.
The team fills in hours from memory at month end and half the work goes unlogged.
Daily timesheets on the task itself, approved by the project manager and marked billable or non-billable.
Labour, purchases and travel for the project are recorded in different places.
Live profitability: billed revenue against actual timesheet, purchase and expense costs, on the project itself.
A milestone is reached but nobody remembers to invoice it.
Billing by time spent or by milestone; reaching a milestone prepares a draft invoice.
One late task pushes five others back and nobody notices.
Gantt with dependencies and critical path; moving a task shows its effect on the rest.
Capabilities
Timesheets are only accurate when entry is simple and daily. Ask the team to log time on the task itself at the end of each day; weekly entry from memory usually misses a big share of the work.
Build each role’s cost rate from actual staff cost, not the sale rate. Project profitability only means something when costs are real.
For long projects, define small, measurable milestones. Staged billing improves cash flow and surfaces disagreements with the client earlier.
Start a project from the contract, not the task list. Record the scope, milestones, payment terms and budget first, then place tasks under each milestone. That way every hour of work is tied to part of the contract and out-of-scope requests show up early.
Run the weekly project meeting on three numbers: actual progress, budget consumed and the next milestone. If budget is burning faster than progress, decide on scope or resources that week — not at the end of the project.
Finally, close projects formally. A project that is never closed keeps collecting stray timesheets and purchases, which distorts both its own profitability and the next project’s. Closing locks the budget, archives the tasks and leaves a clean record for comparing future estimates with reality.
Integration
A Fidar project starts from a won deal or contract, draws its people from HR and records its revenue and cost as an analytic dimension on every financial document.
Reports
Project managers see progress, finance sees profit — from the same data.
Access
Team members see the tasks of their own projects, and project financials are limited to project managers and finance.
Security and user accessLeave your email and be first to try the beta of this module. If you have specific requirements, add them to the message so we can design for them.
Projects, timesheets and services are on the roadmap after HR. Use “Notify me” to hear when it’s ready.
Task tools only manage work; Fidar Projects connects work to contracts, billing, cost and profitability because everything sits in one ERP.
Yes — Gantt with task dependencies, critical path and drag-to-reschedule is part of the design.
From approved timesheet hours or contract milestones. Once Accounting ships, invoices and financial entries are created automatically.
Record project deals in CRM and meetings in Activities; that data links to Projects later.
Services, consulting, contracting, software and any organisation whose revenue comes from projects or time-based contracts. See ERP for services companies.
Pipeline, leads and deals, kanban stages and revenue forecast.
Calls, meetings and tasks with Jalali or Gregorian calendar and reminders.
Employee records, attendance, payroll and Iranian social insurance.
Standard chart of accounts, automatic journals and bank reconciliation.
When Projects ships, won project deals become projects with no data migration.