Fox & SantiagoTechnology, applied.Call (877) 244-9687

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 period with stabilization follows.

Start, pause, stop

Event What happens to the clock
Access gate Starts. The four roles on your side are named and access is granted.
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 period, with stabilization included. We fix whatever gets in the crew's way, and at the end of it you sign operational acceptance: the tool is live with the agreed crew. See how we work for the full terms.

Questions people ask

What is the access gate?

The point where the four roles on your side are named and access is granted.

Is every pause recorded?

Yes. When the clock pauses because work is blocked on your side, the reason is written down.

Does the 30-day live period count toward the six weeks?

No. The six weeks end at release. The 30-day live period comes after.