| Task | Owner | SLA # Days from previous event |
Estimated Working Days From Start of Build |
Example Days of Week |
|---|---|---|---|---|
| Instance Build Begins | Intelitics | - | - | Wed. Week 1 |
| Start Setting up Client tracking | Intelitics | 1 | 1 | Thu. Week 1 |
| 1st Round DNS Verification Records Delivered | Intelitics | 1 | 2 | Fri. Week 1 |
| 1st Round DNS Verification Records Successfully Placed | Client | 2 | 4 | Tue. Week 1 |
| 1st Round DNS Verified | Intelitics | 0 | 4 | Tue. Week 2 |
| 2nd Round DNS Records Delivered | Intelitics | 1 | 5 | Wed. Week 2 |
| 2nd Round DNS Records Successfully Placed | Client | 2 | 7 | Fri. Week 2 |
| 2nd Round DNS Verified | Intelitics | 0 | 7 | Fri. Week 2 |
| Instance Final Testing (Started) | Intelitics | 1 | 8 | Mon. Week 2 |
| Instance Administrator Login Delivered | Intelitics | 2 | 10 | Wed. Week 3 |
- SLAs are based on completion of previous events. If a Client misses a timeline, we will not expedite any future SLAs to get back on track.
- Eg. If Client takes 3 days to successfully place 1st round DNS records (normally 2 day SLA) then the timeline of all subsequent events are pushed back by one (1) day.
- Items completed quicker than SLAs do not “shorten” the timeline. SLAs remain unchanged.





