Why Managed Time and Growth Time do not convert
Policy
Service buckets
Managed Time and Growth Time are separate on purpose.
Who this is for
customers using the service after launch
customers who want to understand why time is split into two buckets
customers deciding how to plan requests
What this article covers
why the two service buckets are separate
why one does not convert into the other
how to think about the difference in practical terms
The simple reason
Managed Time is for keeping your live site current.
Growth Time is for helping your site grow.
Because those are different jobs, they are tracked separately.
Why the structure exists
Without separate buckets, it becomes harder to protect both kinds of work.
A single pooled model tends to create confusion about what should count as upkeep versus growth. Splitting them makes the service clearer and keeps expectations consistent over time.
What this means in practice
If you have unused Managed Time, that does not turn into Growth Time for a new page.
If you have unused Growth Time, that does not turn into Managed Time for routine edits.
Examples
updating hours on an existing page belongs in Managed Time
adding a new service page belongs in Growth Time
changing images on a live page belongs in Managed Time
adding a new location page belongs in Growth Time
FAQ
Why can’t unused Managed Time be used for a new page?
Because new pages are part of structured site growth, which is what Growth Time is designed for.
Why can’t unused Growth Time be used for edits?
Because Growth Time exists for site growth, not for routine upkeep of existing live pages.
Can I use Growth Time for edits instead?
No. Growth Time and Managed Time serve different purposes and are tracked separately.