How can we help?

Open the project entry screen and record the header — code, name, description, owner, priority, customer, type, start and finish dates and budget. The project is created at Active status and lands under the Active tab of the projects list, ready to be broken into a WBS. See Projects & Portfolio.

Add work-breakdown tasks under the project on the new-task screen. Each task carries its own code, name, owner, assigned user, priority, type, start and finish dates, budget and progress percentage — mirroring the project header at task level. Tasks can be linked to a predecessor to establish sequence. See WBS, Tasks & Dependencies.

The projects list groups projects into tabbed grids by status — Active, Inactive, On Hold and Completed. A project's status and status date move it between tabs over its life: it starts Active, can go On Hold and back, and moves to Completed once all its tasks reach 100% progress. See Projects & Portfolio.

Open a project and switch to the Gantt Chart view: every WBS task is drawn as a bar positioned by its start, finish and duration, laid out against a timeline. It is the schedule dashboard for the project — you see at a glance which tasks run when, which overlap, and where the critical path sits. See Gantt Scheduling.

Each task can record a predecessor (parent) task within the project. That link says the task cannot start until its predecessor is done, which defines the WBS ordering and drives the sequence shown on the Gantt. Chaining predecessors builds the dependency network the whole schedule hangs on. See WBS, Tasks & Dependencies.

Edit the task's start and finish dates and the Gantt redraws its bar against the timeline. Because dependent tasks are linked by predecessor, moving one task shows the knock-on effect on the tasks that follow it — so you can see a slip's impact on the schedule before it becomes a surprise on site. See Gantt Scheduling.

A task Bill of Resources is a three-level structure — header, process and resource — that plans what a task consumes: a task quantity and unit, the operations or parameters within it, and the material, labour and machine resource lines, each with a quantity per parent, unit and rate drawn from the Resource master. It is the project-side analogue of a Bill of Materials. See Bill of Resources & Costing.

Cost estimation rolls the task Bill of Resources up — quantity times rate for every resource line — into an estimated task and project cost, and BOR cost analysis breaks that estimate down by resource. Because the project and each task hold both a budget and an actual budget, you can compare estimated cost to budget before and during execution. See Bill of Resources & Costing.

Material for a task is drawn from stock through the shared store engine, issued against the task, and labour and machine consumption is recorded — converting the planned Bill of Resources into actual consumption and the project's actual budget. That is what lets you compare estimated-versus-actual cost as the project runs. See Inventory & Procurement.

The Resource master holds the machines, labour and tools a task Bill of Resources draws from — each with a code, description, type, category, price or rate, working hours per day and efficiency. Those rates flow straight into cost estimation and project billing, so a rate maintained once is used everywhere. See Resource Management.

Resources are classified by resource group, resource category and resource type, with resource parameters attached where needed. That classification keeps a large resource pool navigable and lets Bill of Resources lines and reports be organised by group — for example separating machine hours from labour categories from consumable tools. See Resource Management.

Yes. A resource report lists the resource pool with its rates and classification, alongside the task Bill of Resources report and the master BOR roll-up that totals the resource requirement across a project's tasks. Together they show what every task needs and what the whole project will consume. See Resource Management.

On the project billing screen, create a bill header with a bill number and date, the project and the bill-to party and address, then add resource-itemised lines keyed to tasks — each with resource group, code, quantity, unit, rate and amount. The bill can then be printed as a bill document. See Project & Milestone Billing.

Because bill lines are keyed to tasks and resources, a bill can cover a defined stage of work rather than the whole project — milestone billing. Progress or RA (running-account) bills invoice work completed to date, so you bill as the project advances instead of waiting for completion, keeping cash flow aligned with delivery. See Project & Milestone Billing.

Supplier and subcontractor bills can be passed and cleared against a purchase order — the bill is checked against what was ordered and delivered before it is approved for payment, with supplier bill clearance and reporting to track it. That keeps subcontractor cost on a project controlled rather than paid on trust. See Fast Billing & Accounts.

Material for a task is issued through the shared store engine, so planned Bill of Resources consumption becomes real stock movement and actual cost. Where stock is short, a project purchase requisition raises procurement against the project. It all rides the same Item master and stock ledger the inventory module uses. See Inventory & Procurement.

Project, milestone and subcontractor bills post alongside the platform's invoicing on the same party master, so a bill raised against a project flows into Fast Billing and accounts without re-keying. The customer who becomes the project's bill-to party is already on the shared master. See Fast Billing & Accounts.

Dhruv AI is our AI analytics layer. It adds a project role dashboard over live data with AI insight summaries on progress, cost-vs-budget and schedule slippage, answers plain-English questions through a safe read-only query sandbox, and clusters delay-cause and task-log remarks into named recurring themes — so the biggest project risks name themselves. See Dhruv AI Analytics.