How to Say Something Is Not Available in Project Status Conversation English
When you need to tell a colleague, stakeholder, or client that something is not available during a project status conversation, the direct answer is to state the unavailability clearly, then offer the reason and a next step. The exact wording depends on whether you are speaking in a meeting, writing an email, or chatting informally. This guide gives you the exact phrases, tone guidance, and common pitfalls to avoid so you sound professional and helpful, not vague or defensive.
Quick Answer: The Three-Part Formula
Use this simple structure every time you need to say something is not available:
- State the unavailability (use a clear, polite phrase)
- Give a brief reason (keep it factual, not an excuse)
- Offer a next step or alternative (show you are proactive)
Example: “The Q3 report is not ready yet because we are waiting for final sales data. I will share it by Thursday afternoon.”
Key Phrases for Different Situations
Formal / Written (Email or Status Report)
Use these when writing to a manager, client, or in a formal project update.
- “The deliverable is not yet available.”
- “The requested data is currently unavailable.”
- “We do not have access to that resource at this time.”
- “The feature will not be available until the next release.”
Tone note: These phrases are neutral and professional. They do not sound apologetic or defensive. They simply state a fact.
Informal / Spoken (Team Meeting or Chat)
Use these with colleagues you work with closely.
- “That’s not ready yet.”
- “We don’t have that right now.”
- “I can’t get that until later this week.”
- “It’s still being worked on.”
Tone note: These are direct and friendly. Avoid using them with senior stakeholders unless you have a very casual relationship.
Polite / Customer-Facing
Use these when speaking to a client or external partner.
- “I’m afraid that is not available at the moment.”
- “Unfortunately, we are unable to provide that right now.”
- “That option is currently not an option, but here is what we can do.”
Tone note: The word “afraid” or “unfortunately” softens the message. Always follow with a positive alternative.
Comparison Table: When to Use Each Phrase
| Phrase | Context | Tone | Best For |
|---|---|---|---|
| “The deliverable is not yet available.” | Email or formal report | Neutral, professional | Written updates to managers or clients |
| “That’s not ready yet.” | Team meeting or chat | Informal, direct | Internal team communication |
| “I’m afraid that is not available at the moment.” | Client call or email | Polite, soft | External stakeholders |
| “We don’t have that right now.” | Quick verbal update | Casual, clear | Stand-up meetings or Slack |
| “That option is currently not an option.” | Problem explanation | Direct, solution-oriented | When you need to redirect |
Natural Examples in Project Status Conversations
Example 1: Missing Data in a Status Meeting
Colleague: “Can you share the user testing results from last week?”
You: “Those results are not compiled yet. The team is still analyzing the recordings. I can share a summary by Friday.”
Why it works: You state the unavailability, give a short reason, and offer a clear timeline.
Example 2: Resource Not Available in Email
Subject: Update on design assets
Body: “The final mockups are not yet available. The designer is waiting for brand guideline approval. I will send them as soon as I receive the approval, likely by Tuesday.”
Why it works: It is professional, explains the delay without blaming anyone, and sets expectations.
Example 3: Feature Not Ready in a Client Call
Client: “When can we test the new login feature?”
You: “I’m afraid that feature is not available in the current build. It is scheduled for the next sprint, which starts in two weeks. Would you like to see a demo of the current version instead?”
Why it works: You use polite language, give a reason tied to the project plan, and immediately offer an alternative.
Common Mistakes When Saying Something Is Not Available
Mistake 1: Being Vague
Wrong: “It’s not ready.” (No reason, no next step.)
Better: “It’s not ready because we are waiting for the final approval. I will update you by end of day.”
Mistake 2: Over-Apologizing
Wrong: “I’m so sorry, I know this is terrible, but the report isn’t done yet.” (Sounds weak and unprofessional.)
Better: “The report is not yet available. I am working on it and will send it by 3 PM.”
Mistake 3: Blaming Others
Wrong: “The developer didn’t finish it, so I can’t show you.” (Sounds like you are passing blame.)
Better: “The feature is still in development. I will share a timeline for completion in our next update.”
Mistake 4: Promising Without Certainty
Wrong: “It will be ready tomorrow for sure.” (If you are not certain, you lose trust.)
Better: “I expect it to be ready by tomorrow, but I will confirm by the end of today.”
Better Alternatives for Common Situations
When you cannot access a file or tool
- Instead of: “I can’t find it.”
Say: “I do not have access to that folder. Could you grant me permission or share the file directly?”
When a person is unavailable
- Instead of: “He’s not here.”
Say: “He is out of the office today. I can connect you with his backup, or I can take a message.”
When a budget or approval is pending
- Instead of: “We don’t have the money.”
Say: “The budget has not been approved yet. I will follow up with the finance team and update you by Friday.”
Mini Practice Section
Read each situation and choose the best response. Answers are below.
1. A stakeholder asks for a prototype that is still being tested. What do you say?
a) “It’s not done.”
b) “The prototype is still in testing. I can share it once the QA pass is complete, likely by Thursday.”
c) “Sorry, I don’t have it.”
2. In a team stand-up, your colleague asks for a document you haven’t started yet. What do you say?
a) “I haven’t started it.”
b) “That document is not available yet. I will begin working on it this afternoon and share a draft tomorrow.”
c) “It’s not my priority right now.”
3. A client asks for a feature that was removed from the current release. What do you say?
a) “We removed it.”
b) “That feature is not available in this release. It is planned for the next version. Would you like me to show you the current features?”
c) “It’s not possible.”
4. You are in a meeting and someone asks for a number you don’t have. What do you say?
a) “I don’t know.”
b) “I don’t have that number right now. I can check with the data team and send it to you after the meeting.”
c) “Maybe later.”
Answers: 1-b, 2-b, 3-b, 4-b
Frequently Asked Questions
1. Should I always give a reason when something is not available?
Yes, a short factual reason helps the other person understand the situation. It also shows you are aware of the delay. Avoid long excuses or blaming others.
2. Is it okay to say “not available” in a status report?
Yes, it is professional and clear. Just make sure to add a timeline or next step so the reader knows what to expect.
3. How do I say something is not available without sounding negative?
Focus on the solution, not the problem. Use phrases like “not yet available” instead of “not available,” and always follow with what you are doing about it.
4. Can I use “unavailable” in spoken conversation?
Yes, but it sounds more formal. In a team meeting, “not ready yet” or “we don’t have that yet” is more natural. Save “unavailable” for emails or client updates.
Final Tip for Project Status Conversations
When you say something is not available, your goal is to maintain trust. Be honest, be specific, and always point toward the next step. People appreciate clarity more than perfect news. Practice the three-part formula—state, reason, next step—until it becomes automatic.
For more help with common project status situations, explore our Project Status Conversation Problem Explanations or check out Project Status Conversation Polite Requests for polite ways to ask for updates. If you have questions about how we create our guides, visit our About Us page or read our Editorial Policy.