Workflows

Approvals that route to the reporting line the record already holds.

Routing that stays correct

An approval routes to the reporting line the personnel record already holds. When somebody changes team, the routing changes with them — there is no separate workflow map to remember to update, which is the usual reason approvals end up sitting with somebody who left.

Approvals across products

A timesheet approved in Nest is the same approval Loop reads for progress and Books reads for cost. One decision, recorded once, honoured everywhere — rather than an approval in the HR system and a second confirmation in the finance system.

Conditions that read the whole record

Because an approval rule can read any part of the record, the conditions can be the ones that actually matter rather than the ones the HR system happens to know. Route expenses over a threshold to finance, route anything against a fixed-price project to the delivery lead, route a discount past a certain percentage to whoever owns the account. None of that needs a field to be copied between systems first, which is normally what makes conditional routing brittle.

What an approval carries with it

An approval in Treepie records what was approved, by whom, against which version of the record, and what it changed downstream. That last part is the one usually missing: an approved timesheet is not just a state change on a timesheet, it is the reason a payroll line and a project cost exist. When somebody asks in six months why a figure is what it is, the approval is the answer rather than the start of an investigation.

Where approvals are the wrong tool

Not every hand-off should be an approval. A rule that requires sign-off on something nobody ever rejects is a delay dressed as governance, and teams learn to approve without reading, which is worse than no control at all. Approvals are worth adding where a real decision is being made — a price, a commitment, a payment — and worth removing where they have become a formality.