Something went wrong. Start here.
Practical guidance for buyers dealing with missed deadlines, poor work, communication failures, scope disputes and project breakdowns.
Common freelance problems
This section is about response, not prevention. Start with the problem that is happening now.
Freelancer Disappeared
Steps to take when communication stops after the project begins.
DeadlineFreelancer Missed the Deadline
How to respond without making the project worse.
QualityWork Doesn't Match the Brief
How to separate quality issues from unclear scope.
QualityFreelancer Delivered Bad Work
What to document and how to evaluate next steps.
BudgetProject Is Over Budget
Diagnose why the budget moved and what can still be controlled.
ScopeFreelancer Wants More Money Mid-Project
Determine whether the ask reflects scope change or poor estimating.
RevisionsToo Many Revisions
Fix projects stuck in endless revision cycles.
ScopeScope Creep
Identify uncontrolled additions before they consume the project.
DeliverablesSource Files Withheld
What to check when final working files are not being released.
IntegrityPlagiarized Work
How to respond when delivered work appears copied or stolen.
Keep going
After the immediate problem is contained, strengthen the project structure that allowed it to become expensive in the first place.
When something breaks, identify the failure before reacting.
Freelance projects can fail for different reasons that look similar from the outside. A late delivery may be a timeline problem, a scope problem, a communication problem or evidence that the work itself is not progressing.
Start with four questions
Preserve the evidence
Keep the brief, messages, milestone terms, files, invoices and relevant approvals organized. Clear records make it easier to distinguish misunderstanding from missed obligations.
Classify the problem
Repair, pause or replace
Not every problem requires ending the engagement. Some can be fixed with a clarified scope, revised milestone or better feedback. Others justify pausing further work or replacing the freelancer. Make that decision after identifying what is actually failing.
Diagnose first. Then decide whether to repair, pause or replace.
Different freelance failures require different responses. Before taking action, identify what changed, what remains usable and what the original agreement actually required.
Document the current state
Save the brief, milestone terms, messages, approvals, invoices, files and access details before changing the engagement. A clean record makes it easier to separate a misunderstanding from a missed obligation.
If communication has stopped
Determine what has already been delivered, what access you still control and whether any deadline or response commitment has actually been missed.
If the work is wrong or unusable
Compare the delivered work against the brief and acceptance criteria. The next step depends on whether the problem is quality, scope ambiguity, plagiarism or incomplete delivery.
If the project is consuming more money than expected
Separate true scope growth from weak estimating, revision loops or work that has to be repeated. That distinction changes whether the answer is more budget, a scope reduction or a different freelancer.
If files or ownership are becoming leverage
Identify which assets the business controls now and which deliverables are still missing. Future projects should define source files, ownership, credentials and handoff requirements before work begins.
If the engagement cannot be recovered
Preserve usable work, accounts and documentation before replacing the freelancer. The replacement hire should receive a clear description of what exists, what failed and what remains to be completed.
Use the failure to improve the next project
Once the immediate problem is contained, update the hiring process around the weakness that caused the most damage: verification, scope, payment, revisions, ownership or handoff.