This policy explains how Stravix Technologies sets, manages and communicates delivery timelines, and how delays are handled when they occur.
1. Timeline estimation
Timelines in proposals are based on the approved scope, an assumption of timely client cooperation, and the availability of any third-party dependencies identified during discovery.
Estimates are produced by the engineers who will perform the work, not by a sales function, and include allowance for testing, security review and deployment.
2. Delivery increments
Work proceeds in two-week increments. Each increment concludes with a defined deliverable and a progress summary published to your client portal, showing completed work, upcoming work and any emerging risk.
3. Milestones
Engagements are structured around milestones with defined acceptance criteria. Milestone status is visible continuously in your client portal, with dates, completion status and dependencies.
4. Client-side delays
Where delivery depends on client input — approvals, content, data, credentials or third-party access — and that input is not provided within the agreed period, the timeline extends by the duration of the delay.
Where a delay exceeds twenty business days, resource allocation may be released to other engagements, and a revised start date is agreed on resumption.
5. Third-party dependencies
Where delivery depends on third parties outside our control, dependencies are identified in the proposal. Delays caused by third parties extend the timeline accordingly, and we maintain communication and escalation on your behalf where we hold the relationship.
6. Scope changes and timelines
Every change order states its timeline impact before approval. Accumulated small changes affect delivery dates, and we report cumulative impact rather than absorbing it silently.
7. Communication
- A written progress summary at the end of each two-week increment
- Continuous milestone and status visibility in the client portal
- Immediate notification of any risk affecting the delivery date
- A nominated delivery contact for the duration of the engagement
- Escalation path published at engagement commencement
8. Go-live and hypercare
Production release follows a documented deployment plan with a tested rollback position. A hypercare period follows go-live, during which response targets are elevated and the delivery team remains assigned to the engagement.
Questions about this policy?
Contact Stravix Technologies LLC at [email protected] or call +1 (862) 260-4180. We respond to policy enquiries within five business days.
Contact us