Projects & Job Costing

A manager who needs to know when a task moves is usually made its owner, because owning is the only relationship most tools notify. Watching is a different relationship: who hears about assignments, status changes, comments and mentions, and why the noise problem is settled when each notice is sent.

An auditor does not test the labour total on a project. They pick five entries and ask who worked them, who typed them and when, who approved them, where the rate came from, and whether anything changed after the invoice. What the record answers for each, and how to have it ready before they ask.

A programme director should not read fifteen status reports to find the two projects in trouble. The portfolio dashboard judges every project on schedule, effort and budget, and says which check raised the flag.

Plans are re-planned one task at a time, and halfway through they are always broken. The timeline takes a drag or a keystroke, flags the dependency it broke, and pushes the open tasks downstream by exactly the slip.

Japan makes the main contractor keep a register of everyone working below it, on site — and makes each tier tell the tier above who it engaged. The party who keeps the register is not the party who fills it in, and our supplier portal is already the right channel.

Victoria caps what a builder may hold at each stage as a percentage of the contract price, with the stages defined by what is physically built. Our projects module holds the stages in order and holds no contract price at all.

Singapore's security-of-payment Act defines a day, for every deadline in it, as any day other than a public holiday. Weekends count. That is a third unit of time, and most systems implement two.

A British contractor files monthly, naming each subcontractor, what they were paid, and how much of it was materials. That third figure is defined as what the contractor is satisfied the subcontractor's own materials cost — not a number on any document you hold.

A certified payroll has a period of one week, a scope of one contract, and a signature attesting to three specific things. None is a cost figure — and its most unusual requirement is something this product already does, in the wrong module.

A sprint belongs to a project, and a task can only join a sprint in its own project. For a squad built around one engagement that is invisible; for a standing team carrying a client portfolio it is one cadence turned into four records, four burndowns and four velocities.

Peru sets a monthly valuation cycle for public works with the deadlines written into it — present within the first three days of the following month, supervisor reports within five, entity pays by month end. The binding deadline is not the payment one; it is how fast you can close a month.

A milestone here is a name, a due date, a status and a sort order — the one level between a task and a project that reports cleanly. Turning that date into something that gates, triggers and alerts is an addition we can wire into your workspace.