We're making Project Flow's terminology more consistent

You may have noticed that some terms in Project Flow don't always match what you see elsewhere in the platform. We're fixing that.

What's changing

We've defined clear naming standards for Project Flow, and we're rolling them out across the platform. Over the coming weeks, you'll see some labels change to match these standards.

What's not changing

This is a labeling update only. The data behind each term stays exactly the same. Nothing changes in how numbers are calculated. If a field used to say "X" and now says "Y," the value itself hasn't moved.

Why we're doing this

Project Flow has grown a lot, and with that growth, small naming differences crept in between features. Consistent terms make Project Flow easier to learn, easier to explain to your team, and easier to use.

What to expect

Because Project Flow is a big platform, this rollout won't happen everywhere at once. We're working through it over the next few weeks. If you spot a term that looks out of place or inconsistent, let us know. We'd rather hear about it than leave it unfixed.

Want to know what a term means?

Check our growing glossary. It lists the current terms used across Project Flow, what they mean, and how they're calculated where relevant.
Project Flow Glossary : Milient Software