Teloa
Scope & Request Definition Policy
Last revised on Feb, 2026

- Core Principles
Teloa operates on a structured capacity model.
Each request is expected to represent a reasonable, focused scope of work aligned with the standard delivery window defined for that service.
A single request should focus on one clear deliverable.
Examples:
- One landing page
- One dashboard flow
- One logo concept direction
- Your work and requests are never lost during an upgrade
- Ad designs set (within defined limits)
Requests should not bundle multiple large deliverables into one submission.
- When Scope Exceeds a Standard Request
If the submitted brief includes a scope that exceeds what is considered a reasonable single deliverable for the selected service:
- The request will be reviewed by the Teloa team.
- The user will be asked to split the work into multiple requests, or Teloa will do so upon receiving the user's confirmation.
- Each split request will follow its own delivery window and active slot usage.
In this case:
- If the scope exceeds a reasonable single deliverable, it becomes multiple requests.
This ensures:
- Predictable timelines
- Fair capacity allocation
- Consistent service quality
- No mid-project disruptions
- Delivery Windows & Scope Assumption
All delivery windows (e.g., 2-4 business days, 5-7 business days) are based on a standard scope assumption.
These timelines assume:
- A clearly defined brief
- A focused outcome
- A reasonable quantity for that service type
If the quantity or complexity substantially exceeds a typical scope, additional requests may be required.