Answer
What is the clock policy?
A Production Build's six weeks start at the access gate, pause while work is blocked on the client side with the reason recorded, and end at release to the agreed production environment with the agreed user group. A 30-day live-use acceptance window follows.
Start, pause, stop
| Event | What happens to the clock |
|---|---|
| Access gate | Starts. The four roles on your side are named, access is granted and the threshold is signed. |
| Work blocked on your side | Pauses, with the reason recorded. |
| Release | Stops, when the tool reaches the agreed production environment with the agreed user group. |
Why it works this way
A timeline only means something if both sides know what counts. Starting at the access gate means no weeks are lost to waiting for access before anyone can build. Pausing when work is blocked on your side, and writing down why, keeps a delay from being argued about later. Both sides can see which days were build days and which were waiting days.
The clock ends at release, and release has a specific meaning: the agreed production environment and the agreed user group, not a demo or a test site.
After the clock stops
Release starts the 30-day live-use acceptance window. The last 20 percent of the Build fee depends on whether the crew is using the tool by the end of that window, measured from your own records. See how we work for the usage terms.
Questions people ask
What is the access gate?
The point where the four roles on your side are named, access is granted and the usage threshold is signed.
Is every pause recorded?
Yes. When the clock pauses because work is blocked on your side, the reason is written down.
Does the live-use window count toward the six weeks?
No. The six weeks end at release. The 30-day live-use acceptance window comes after.