If an X client asks when you can start, give a project start date only after you have checked the work against your schedule and confirmed what must happen before work begins. If scope, approval or client inputs are still missing, offer the earliest *possible* date and say what would make it firm. A consultation you can take next week is not the same as project work you can begin next week.
Clarify what “start” means
A client might mean “When can we talk?”, “When can I book you?” or “When will you begin the work?” Those questions can have different answers. If their post is ambiguous, ask which milestone matters. If they need work underway by a particular date, do not answer with your next available call slot as though it meets that need.
Name the distinction plainly: “I have time for an initial call on Thursday. My earliest possible project start is later, once we agree on scope.” You can offer the conversation now without implying that the project has been scheduled.
Find the earliest start your schedule can support
Look at the work already committed during the proposed week, not just an empty calendar square. Allow for the time this project will need at the start and any work you must finish first. If someone else must do part of the work, check their availability too. The date you give should be one you can support alongside existing obligations, not simply the first date on which you could take a meeting.
Then separate what you can control from what is still pending. An open work slot does not resolve an unapproved scope or missing materials. Before calling a date confirmed, check the fields below against your actual process:
- Project scope: Do you know what work begins on day one, and has the client agreed to it? If not, identify the decision needed before you can estimate or reserve the right amount of time.
- Your capacity: Is the required time genuinely available, including any teammate or subcontractor whose work is necessary? Decide whether you can hold that time or are only describing current availability.
- Client inputs and approvals: Which brief, access, files or decisions must arrive before work can begin? Check any contract, payment or internal approval that your own process requires before treating the date as booked.
Give a confirmed date—or the path to one
Use “I can start on [date]” only when you have capacity for the agreed work and the prerequisites for that commitment are met. If the slot is open but a prerequisite is unresolved, say “The earliest possible start is [date], subject to [specific condition].” If you cannot assess the work or availability yet, skip the speculative date and say what you need to check and when you can get back to the client. Do not describe a tentative opening as a reservation unless you actually intend to hold it.
Consider a fictional designer with an available consultation slot on November 12, 2026, and room for new project work beginning November 23. The prospective client has not sent a final brief or approved the scope. The designer can offer the November 12 conversation, but cannot yet commit to beginning the project on November 23. A suitable public reply is: “I can talk through the project on November 12. My earliest possible work start is November 23, but I’d need your final brief and an agreed scope before confirming that date. Would the November 12 conversation help us settle those details?”
Now change the fictional facts: the final brief has arrived, the scope is agreed, any required approval is complete, and the designer has checked and reserved sufficient capacity from November 23. The answer can become: “I can start the agreed project on November 23. I also have a consultation slot on November 12 if you’d like to walk through the kickoff beforehand.” If the client’s proposed work differs from the agreed scope, check the schedule again rather than carrying the date over automatically.
Keep a public reply to the timing and next step; discuss private project materials through an appropriate channel. If the client is asking whether a *shipped order* will arrive by a deadline, use the separate delivery-deadline guide. Questions about who helps a software customer get set up belong in the onboarding-support guide, not in a project start promise.
Check the suggested reply against your schedule
ReachFast surfaces relevant public X posts and prepares a reply; selecting a lead opens the X thread with that reply typed for you to decide whether to send from your own account. For a start-date question, treat the draft as a response to edit, not as a calendar check. Replace any unsupported date or implied booking with the answer your capacity and prerequisites justify, then review the final wording before sending it.
