State what was commissioned, which stages were completed and where the engagement stopped. Show only work you may disclose, explain unresolved questions and avoid claiming a launch or outcome that did not happen. Keep explanations factual and proportionate without assigning motives or revealing unnecessary details about the client relationship.
Establish the actual stopping point
Create a simple timeline from the agreed brief to the last completed activity. Mark milestones as completed, in progress or not started. A project might have reached an approved outline without producing final pages, or completed research preparation without recruiting participants. These are meaningful differences. Describe the status using project records rather than the stage you expected to reach when the engagement began. A case study should show the work that exists, not silently fill in an intended ending.
Check the publication conditions before deciding whether the engagement belongs in a portfolio. An incomplete project may involve unresolved approvals, sensitive discussions or artifacts not cleared for public use. The fact that you created something does not settle whether you can share it. If permission or ownership is unclear, pause the affected material and seek clarification. A smaller permitted description or an independent practice example may be more appropriate than a detailed account of the stopped engagement.
Explain the work without inventing a finished story
Choose a bounded decision or artifact from the completed portion. Explain its purpose, the information available and your responsibility at that stage. Label drafts, proposals and untested assumptions accurately. Avoid visual treatments that make a concept appear to be a live product or a final approved deliverable. The reader should understand both the professional reasoning you can demonstrate and the additional work that would have been required before the artifact could be used.
If the reason for stopping is relevant and may be disclosed, state it briefly in factual terms. “The project paused before implementation” may be sufficient. Do not speculate about budgets, internal disagreements or a contact’s motives. A portfolio is not the place to settle a dispute through selective narration. Keep the emphasis on your work, the project boundary and what the available evidence can show rather than casting another participant as an obstacle to a heroic success story.
Describe what remains unknown
Identify the decisions, checks or implementation steps that did not occur. A draft may still require technical review, user evaluation or organizational approval. Explain these gaps near the artifact rather than reserving them for a small disclaimer. Do not claim that a proposed approach would definitely have succeeded if the engagement had continued. A counterfactual outcome is not a project result, even when you have a strong professional preference for the direction proposed.
Finish with a limited reflection on your own process. You might explain a scoping question you would ask earlier or a dependency you would make more visible. Keep the reflection tied to evidence and avoid presenting confidential lessons as universal rules about clients. Review the title and summary for completion language such as launched, delivered or transformed. If the engagement later resumes and you may update the case, retain a clear distinction between the original stopping point and subsequent work.
Fictional example: a structure that never reached publication
A fictional writer, Dario, works through an invented documentation project that stops after the structure review. His example case includes an outline comparison and an unresolved-question register. It labels the structure as a proposed draft and explains that factual editing, technical approval and publication did not occur. Dario describes the organization decision rather than presenting a finished help centre.
The fictional reason for the pause is kept brief because it does not change the writing decision. Dario notes that his future scoping process would make source-approval dependencies explicit earlier. He does not claim that the unimplemented structure improved user performance or blame unnamed stakeholders for the missing launch. The case remains useful as an examination of partial work with a visible boundary.
A checklist for your next step
- Map completed and unfinished stages.
- Review disclosure conditions.
- Label drafts and proposals.
- State the stopping point factually.
- Keep hypothetical outcomes out of results.
Common questions
Can an incomplete engagement be a portfolio case?
Yes, when publication is permitted and the case clearly identifies completed work, unfinished stages and evidence limits.
Must I explain every reason it stopped?
No. Include only relevant, disclosable facts. A clear status may be enough to interpret the work fairly.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.