How do I distinguish a completed deliverable from a draft or proposal in my portfolio?
Quick answer
Label each portfolio item by its actual status, such as “Completed,” “Draft,” or “Proposal.” Then state what you personally finished or handed over, what remained incomplete, and—if relevant—whether the proposed work was ever carried out. Keep the label visible beside the item, not buried in a general disclaimer. If the status or your contribution is unclear, explain the uncertainty rather than letting the presentation imply completion.
The question, the details, the next step.
I have a portfolio item that looks polished, but I’m not sure the label makes clear whether it was finished. How should I distinguish a completed deliverable from a draft or proposal?
Make the status explicit, then describe the boundary of the work in one or two plain sentences. A finished-looking file is not, by itself, a clear signal that it was delivered or put into use.
Choose the most accurate label:
- Completed deliverable — the specific item you describe was finished.
- Draft / work in progress — the item was still being developed, reviewed, or revised.
- Proposal / concept — it presented an idea or recommended direction; it was not itself a completed implementation.
Put that label in the item’s title, caption, or a status line directly next to the work. Then say what your part included and, when it matters, what did not happen. Avoid a broad label such as “project complete” if only one part of a larger project was completed.
What if I finished one part, but another person or team was responsible for the rest?
Name the completed part separately from the larger effort. That lets you describe your contribution without suggesting you completed work owned by someone else.
For example, this is an illustrative caption, not a claim about your own experience:
Status: Completed — design handoff “I created and handed over the initial page layouts. The portfolio item shows the design handoff; implementation and launch are not represented here.”
If the next stage is known to be underway, say so only if you have a sound basis for that statement. Otherwise, “implementation is outside the scope of this item” is clearer and avoids guessing. Use “I” for your work and “the team” only when the statement genuinely refers to shared work. If you show a combined result, explain which parts are yours and which are not.
How should I present a proposal that the organization considered but never carried out?
Call it a proposal or concept, and state that it was not implemented. Describe what you actually produced—such as a recommendation, mock-up, outline, or presentation—rather than describing the imagined result as though it happened.
A copyable pattern is:
Status: Proposal — not implemented “I prepared [type of proposal] for [brief context]. It outlined [proposed change]. The work shown here is the proposal; it does not represent a completed rollout or outcome.”
Replace the bracketed text with accurate details. If you do not know whether the proposal was later adopted, do not imply either that it was or that it was rejected. The proposal can still demonstrate how you framed an idea, but keep proposed benefits distinct from observed results.
Can you give me a simple format I can reuse for every portfolio item, including one that is still a draft?
Use a short status-and-scope caption. Keep the status easy to spot, and adjust the wording to match the item rather than filling every field with vague claims.
[Status: Completed / Draft / Proposal] My contribution: [What I personally created or did.] Scope: [What this item includes; what it does not include, if that distinction matters.] Next step or outcome: [A verified handoff or outcome, “not implemented,” or “not yet known,” as appropriate.]
For a draft, an explicitly hypothetical caption could read: Status: Draft — “I prepared an initial outline for [topic]. This version was shared for review and does not include later revisions or approval.” For a completed item, say exactly what was finished; do not let “completed” silently expand from one deliverable to the whole project. When you cannot verify a detail, leave it out or mark it as unknown.
A practical checklist
Choose a status label that describes the item shown, not the entire project by default.
Place the label beside the portfolio item so it is visible without searching for a disclaimer.
State what you personally completed, created, or contributed.
Clarify unfinished, proposed, or out-of-scope work when a reader might otherwise assume it was done.
Separate proposed benefits from outcomes that actually occurred.
Remove or qualify any detail about implementation, approval, or results that you cannot verify.
A few more useful answers
Should I use “final” as the status label?
Use “final” only when it accurately describes the version or deliverable, and explain what was final. It may not tell a reader whether the work was handed over, implemented, or part of a larger unfinished project.
What if I cannot tell whether a proposal was later implemented?
Label the work as a proposal and state that its later status is unknown to you. Do not present the proposed result as an achieved outcome.
Do I need to explain every unfinished part?
No. Clarify the boundaries that could change a reader’s understanding of what you completed or contributed. A concise scope note is usually more useful than a long project history.