Adding New Requirements
New requirements follow formal approval.
Adding new requirements means introducing features, tasks, or deliverables outside the approved scope. GigBig handles these requests through structured review and approval to protect timeline discipline and financial transparency.
New requirements include
- Additional pages or features
- Expanded functionality
- Extra content beyond agreed volume
- New integrations
- Design direction changes
- Additional team involvement
- Extended package days
What counts as a new requirement?
- Additional pages or features
- Expanded functionality beyond approved scope
- Extra content beyond agreed volume
- New integrations or systems
- Design changes that alter approved direction
- Additional team involvement in Team Service
- Extending beyond allocated package days
Anything outside the originally documented scope qualifies.
Why new requirements must be structured
- Prevents timeline disruption
- Protects budget balance
- Reduces resource overload
- Prevents package day overuse
- Limits uncontrolled revision cycles
Structured handling protects both parties.
Adding requirements in Single Service
- Project Manager evaluates feasibility
- Timeline impact is assessed
- Additional cost is calculated if needed
- A revised proposal is shared
- Work proceeds only after approval
New tasks do not begin without formal confirmation.
Adding requirements in Team Service
- Remaining package capacity reviewed
- Additional team days may be required
- Package extension or upgrade proposed
- Budget adjustments documented
Package duration discipline is maintained.
Formal approval is mandatory
- Scope updates documented
- Timeline adjustments confirmed
- Budget changes approved
- Milestones revised accordingly
Execution does not proceed based on informal messages.
What is not a new requirement
- Minor corrections within scope
- Fixes aligned with approved deliverables
- Clarifications of agreed functionality
The key distinction is whether workload expands beyond approved terms.
Documentation and transparency
- New requirements recorded in dashboard
- Milestone definitions updated
- Timeline changes reflected
- Billing records adjusted
This ensures accountability and clarity.
If new requirements are not approved
- Work continues under original scope
- Timeline remains unchanged
- Budget remains aligned with approved deliverables
- Structured scope control is maintained
Why structured requirement management matters
- Predictable execution
- Controlled project expansion
- Fair compensation
- Reduced dispute risk
- Professional project governance
It maintains balance between flexibility and structure.