Projects › Overview
A project-led view of how FlowPlan work turns into a delivery-ready route, from early decisions to vendor-ready scope, clear package boundaries, and commissioning checks.
Select a pathway to see what triggers it, what inputs we need, and what you get, so scope, package boundaries, and verification requirements are defined before vendor conversations begin.
OVERVIEW
Pathways are organised around recurring project situations, so route, package boundaries, and verification requirements can be defined early enough for procurement, delivery, and verification to stay aligned.
Pathways are grouped around common project situations, STP, ETP, reuse, biosolids, equipment, and brine management, so route, inputs, and expected deliverables can be compared early.
That gives the project a clearer basis for procurement, delivery, and verification, while keeping package boundaries and performance requirements visible from the outset.
Common project situations addressed in this section
COMMON SITUATIONS
These are the situations the pathways are designed to get ahead of, so scope, package boundaries, and performance criteria are defined early enough to influence outcomes rather than explain problems after the fact.
Procurement is moving but the scope isn't clear enough yet
Vendors are quoting from different assumptions. You need a basis document that defines flows, loads, package boundaries, and performance criteria before the RFP goes out.
The scheme direction is agreed but hasn't been engineered
You know what you're building but not what the sizing basis is, where the package boundaries lie, or what commissioning needs to verify. That gap needs to close before packages are let.
A system is underperforming and the cause isn't obvious
Treatment isn't hitting targets, or a commissioned system isn't stable. The problem usually lies at a handover point - between process units, between vendors, or between design and operation.
This section shows how that support is structured across scoping, procurement, and implementation, so project requirements are defined early and carried through delivery with less ambiguity.
Select a pathway below - triggers, required inputs, deliverables, and linked sections update in the panel.
Pathway
A structured pathway for new builds or upgrades where biological stability, operability, and performance verification need to be clear before vendor engagement.
Typical triggers
Key deliverables
Inputs needed
Linked sections / tools
Four common ways projects are packaged, from early scoping through commissioning and upgrade planning.
Scoping
When the project intent is clear but the route is not, we set out the main risks, narrow the viable options, and build the inputs checklist for vendor conversations.
View project pathwaysProcurement
Used when multiple vendors exist with overlapping scopes. We define package boundaries, verification points, and bid evaluation criteria so quotes are genuinely comparable.
View advisory routeCommissioning
As installation approaches, the focus turns to readiness. We confirm connections, shutdown periods, and commissioning checks so the completion plan carries through properly.
Start an enquiryUpgrade planning
Where a plant is underperforming or permit limits are tightening, we define the gap, identify retrofit options, and sequence the improvements without rework.
View upgrade pathwaysShare your current stage, constraints, and the decision you need to make. We’ll map you to the right pathway and the next deliverable.
Start an enquiry