Plan and usage

Plan & Usage answers two questions: which plan your tenant is on, and how much of it you have already used. The screen is read-only. Plans are assigned by the Cooriroo platform team rather than from inside your tenant, so there is nothing here to save — only something to read before you plan the next month of work.

The card at the top names your plan and shows the plan version you are resolving against. Below it, Resource usage lists one row per capped resource: Drivers, Vehicles, Trips per Month, Destinations, Origins, Users, Delivery Pools, Trip Templates, Custom Fields and Storage (MB). When your plan carries a spend cap for the AI assistant, an AI Monthly Spend row joins them.

The page always reports your own tenant — there is no tenant to choose and no way to read someone else’s figures from here.

Each row is measured directly rather than incremented by a counter that could drift, and it is worth knowing what each one actually counts. Drivers counts driver profiles. Users counts every person who belongs to the tenant, drivers included — so taking on a new driver consumes one of each, which is the most common surprise on this page. Storage (MB) is the total size of every file the tenant holds. AI Monthly Spend is the money spent on AI calls so far this month. Deleted records stop counting as soon as they are deleted, so freeing capacity takes effect immediately rather than overnight.

A limit of 0 is not a limit of nothing. Throughout Cooriroo a cap of zero means no ceiling, so a resource your plan does not cap reads Unlimited and draws no bar. This is also what a tenant with no plan resolves to: every cap falls back to zero, which is why a newly created tenant reads as unlimited everywhere until the platform team assigns it a plan. If a resource you expected to be capped shows as unlimited, the plan is the thing to check, not the meter.

Caps are inclusive: a write is refused the moment usage reaches the limit, not once it passes it. A tenant holding 25 drivers against a 25-driver cap cannot add a 26th. The check runs at the write itself, so nothing stops you opening a form — you are stopped when you save it, and the error names the resource together with the two numbers behind the decision.

Storage behaves the same way but is measured in megabytes across every file the tenant holds: trip documents, proof-of-delivery photos and inspection images all count toward it, and the check runs before the upload starts.

The version number beside your plan name is worth understanding. A plan’s limits are immutable once published: changing them appends a new version rather than editing the one you were sold. Your tenant either floats on the plan’s current version, picking up new limits as they are published, or is pinned to one version, which keeps your existing limits even after the plan moves on. The number on the card tells you which version you are actually resolving against, so two tenants on the same plan name can legitimately hold different caps.

Not every plan limit is a metered resource. The cap on stops per trip is a plan limit too, but it is enforced when you save a trip rather than accumulated as usage, so there is nothing to draw a bar for. The same is true of capability switches such as the AI assistant, which your plan either includes or does not. If a feature is missing rather than full, it is a feature flag question, not a usage one.