> For the complete documentation index, see [llms.txt](https://docs.seedify.fund/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seedify.fund/milestone-guidance-criteria/milestone-change-requests.md).

# Milestone Change Requests

Projects may request milestone modifications before or after evidence submission deadline. Processes are described below.

### Pre-Submission Changes

Type 1: Pivot Request When: Business model or product direction changes significantly

Requirements:

* Detailed justification (market conditions, technical constraints, strategic reasons)
* Proposed new milestone roadmap
* Mapping of old milestones to new milestones
* Impact assessment on timelines and funding

Process:

{% stepper %}
{% step %}
Submit written proposal to Seedify
{% endstep %}

{% step %}
Seedify reviews and posts to Community Voting
{% endstep %}

{% step %}
Community vote (7-day window)
{% endstep %}

{% step %}
If approved: New milestones replace old ones
{% endstep %}

{% step %}
If denied: Original milestones stand
{% endstep %}
{% endstepper %}

***

Type 2: Single Milestone Delay When: Unexpected obstacle delays one milestone

Requirements:

* Maximum 60-day delay
* Detailed explanation of cause
* Mitigation plan
* No impact on subsequent milestone timelines

Process:

{% stepper %}
{% step %}
Submit delay request ≥7 days before deadline
{% endstep %}

{% step %}
Seedify reviews feasibility
{% endstep %}

{% step %}
Community vote (3-day expedited window)
{% endstep %}
{% endstepper %}

***

Type 3: All Remaining Milestones Delay When: Force majeure, regulatory action, critical external dependency failure

Requirements:

* Comprehensive force majeure documentation
* New timeline for all remaining milestones
* Risk assessment update

Process: Same as Type 1 (Pivot Request)

***

Type 4: Early Release (Single Milestone) When: Project completes Milestone N+2 while on Milestone N

Requirements:

* Full evidence for skipped milestone
* Explanation of acceleration
* Confirmation no corners were cut

Process:

{% stepper %}
{% step %}
Submit evidence for out-of-order milestone
{% endstep %}

{% step %}
Seedify & Oracle review
{% endstep %}

{% step %}
Standard Community vote
{% endstep %}

{% step %}
If approved: Funds release, original roadmap continues
{% endstep %}
{% endstepper %}

***

Type 5: Early Release (Multiple Milestones) When: Project delivers 2+ milestones ahead of schedule

Requirements:

* Evidence for all accelerated milestones
* Justification for speed (not sandbagging evidence)
* Quality assurance documentation

Process:

{% stepper %}
{% step %}
Submit comprehensive evidence package
{% endstep %}

{% step %}
Enhanced Seedify review (deeper quality check)
{% endstep %}

{% step %}
Community vote
{% endstep %}

{% step %}
If approved: Redistribute remaining funds proportionally across remaining milestones
{% endstep %}
{% endstepper %}

***

Type 6: Partial Release Request When: Project completes 70-90% of milestone but cannot complete remainder due to external factors

Requirements:

* Clear documentation of what was completed vs. not completed
* Explanation of blocking issue
* Proposal for handling incomplete portion

Options:

* Option A: Release X% of funds now, remaining milestones absorb the gap
* Option B: Extend deadline for full completion

Process:

{% stepper %}
{% step %}
Submit partial completion evidence + gap analysis
{% endstep %}

{% step %}
Seedify reviews and recommends percentage completion
{% endstep %}

{% step %}
Community vote on partial release
{% endstep %}

{% step %}
If approved: Remaining funds redistributed proportionally
{% endstep %}
{% endstepper %}

***

### Post-Vote Changes

Projects may request modification after Community vote under limited circumstances.

Type 7: Dispute (Oracle/Seedify/Community Decision) When: Project believes milestone was incorrectly evaluated

Limitations:

* One dispute per milestone
* Must be filed within 48 hours of Community vote result
* Cannot dispute based on new evidence (only on evaluation of submitted evidence)

Requirements:

* Detailed written argument explaining error
* Reference to specific evidence that was overlooked
* No new evidence allowed (dispute must use original submission)

Process:

{% stepper %}
{% step %}
File dispute with Seedify
{% endstep %}

{% step %}
Seedify re-reviews evidence + dispute argument
{% endstep %}

{% step %}
Seedify publishes response and recommendation
{% endstep %}

{% step %}
New Community vote (7-day window)
{% endstep %}

{% step %}
Second vote is final (no further disputes)
{% endstep %}
{% endstepper %}

Bad Faith Penalty: Frivolous disputes harm project's reputation for future milestone votes.

***

Type 8: Post-Vote Partial Release When: Community  votes NO, but project wants to argue for partial credit

Requirements:

* Can only be used once per project lifecycle
* Must present case for what portion was completed
* Seedify must agree partial completion occurred

Process:

* Same as Type 6 (Partial Release Request)