A client says, “Everything looks good—go ahead.” You block out Tuesday, open the project folder, and immediately discover that the logo file is missing, the decision-maker is on vacation, and nobody knows who can grant account access. The work has technically started, but the project is already waiting.
For a small service business, these half-started projects create a particular kind of drag. They occupy mental space, interrupt the schedule, and make it difficult to tell whether the delay belongs to you or the client. A useful fix is a ready-to-start gate: a short set of conditions that must be met before a project moves from “booked” to “in progress.”
This is not a way to make clients jump through hoops. It is a way to make the first working day productive and to give everyone a shared definition of what “start” means.
Why a verbal green light is not enough
Most custom work depends on inputs that arrive from different people and systems. A designer may need brand files and final copy. A bookkeeper may need complete records and permission to view an account. A consultant may need a named decision-maker and a clear problem statement.
When those inputs are collected casually, the gaps only become visible after you have reserved time. Then there are two unattractive choices: chase information repeatedly or begin with assumptions that later need to be undone.
A start gate moves this discovery earlier. It separates agreement to work together from having what is needed to do the work well. That distinction protects both your calendar and the client’s result.
A project is not ready because it has been sold. It is ready when the next useful action can happen without a guessing game.
Build the gate around your actual first hour of work
Do not copy a large agency’s intake process. Start by looking at what you genuinely need in the first hour of a typical project. The answer should be concrete enough that a client can supply it or name the person who will.
For many service businesses, the gate has five parts.
1. A defined outcome
Write the deliverable in plain language. “Improve our online presence” is an ambition, not a working brief. “Create a five-page website using the approved copy and existing brand assets” is closer to an outcome.
Include the boundaries that affect effort: what is included, what is not, and what counts as completion. This prevents a client from assuming that an adjacent task is automatically part of the job.
2. One person who can decide
Projects often stall because feedback comes from several people but no one is responsible for resolving conflicts. Ask for one named contact who can consolidate comments and approve routine decisions.
This does not mean that one person must know everything. It means you need to know where a final answer comes from. If a board, partner, or department must approve major changes, note that before scheduling the work.
3. The materials you cannot reasonably invent
Make this list specific. “All materials” invites confusion; “the current logo in a usable file format, final service descriptions, and three approved photos” is actionable.
Some items can be optional. If you can use temporary image placeholders or draft headings during an early phase, say so. The gate should identify the missing inputs that would truly stop or distort the next stage.
4. Necessary access or a workable alternative
If the job requires access to a platform, account, shared drive, venue, or software system, settle that before the start date. Avoid asking clients to send passwords by email. Use the account’s normal invitation or permissions process where available, or agree on a screen-sharing session if direct access is unnecessary.
Also decide what happens if access is delayed. Could you complete a planning phase first? Can the client perform a step while you guide them? A backup route makes the gate practical rather than brittle.
5. The commercial trigger
Use the payment and agreement steps that fit your normal business process. The important point is consistency: do not mark work as underway merely because a proposal was discussed or a tentative date was mentioned. Your internal project status should reflect the conditions you actually require before reserving substantial production time.
Turn the gate into a client-friendly checklist
The checklist should fit in one email, client portal page, or shared document. It is not a contract replacement and should not read like one. Its job is to make the next step obvious.
A simple version might look like this:
- Project: the agreed deliverable and any key boundary.
- Primary contact: name, email, and role in approvals.
- Materials due: a short itemized list, with a place to upload or send each item.
- Access needed: the systems involved and the preferred invitation method.
- Open decisions: choices that must be made before production, such as audience, priority service, or tone.
- Start condition: the sentence that says when the project enters the schedule.
Use verbs and nouns the client recognizes. Instead of “Provide brand collateral,” write “Upload your logo, color references, and any brand guide you use.” Instead of “Confirm stakeholder governance,” write “Tell us who will gather feedback and send final approval.”
Classify items so the list does not become a bottleneck
Not every unanswered question deserves to stop a project. Mark each item in your own workflow as one of three types:
- Required to start: Without it, you cannot make a sound first move. An event photographer, for example, needs the event date and location.
- Required before a later stage: You can plan before it arrives, but cannot finish a later piece. A web developer might plan structure before final photographs are ready.
- Helpful but optional: It improves the work if available, but should not hold up the project. Examples may include older marketing samples or extra background notes.
This classification keeps your gate lean. If everything is labeled urgent, clients will either feel overwhelmed or send a rushed pile of material that creates more cleanup work.
Set a scheduling rule that you can uphold
The gate only works if it changes how you schedule. A fair rule is usually conditional rather than punitive: the project enters the production queue when the required start items are complete. Until then, it remains booked but unstarted.
Be precise about what that means in your own capacity planning. You might hold a tentative window for a limited period, begin with the next available opening once the materials arrive, or reserve a short setup session rather than an entire production week. Choose a rule you can apply consistently across similar clients.
Avoid vague promises such as “I’ll try to fit it in.” They make delayed projects look like your failure to prioritize them. A calm, clear alternative is: “Once the checklist is complete, I’ll confirm the next available production slot.”
Use one reminder, then make the status visible
Clients are busy; a missing file is often an oversight rather than resistance. Send one concise reminder that names only the items preventing the start. Include the easiest possible action: a reply, upload link, or invitation request.
After that, update the project status rather than sending a stream of increasingly urgent messages. Labels such as “waiting for start items,” “ready to schedule,” and “in production” can be useful in any basic project tracker. They give you an honest view of your workload and help you follow up deliberately.
If a project sits for a long time, review it against the agreement and your own scheduling policy before making promises about dates. The lesson is not to punish a late client; it is to avoid silently carrying inactive work as if it were active.
A realistic example: a brochure project with a hidden delay
Imagine a freelance designer is hired to create a printed service brochure. Without a gate, the designer starts laying out pages from a kickoff call. Two days later, the client changes the featured services, asks a colleague for updated pricing language, and cannot locate the logo in a usable format. The designer has work on screen, but little of it is stable.
With a start gate, the designer sends a short checklist after the project is agreed: approved list of services, final contact details, logo file, photo selection, one approval contact, and the initial commercial step used in the designer’s process. The designer also identifies photographs as a later-stage requirement if placeholders can be used.
Once the service list, contact details, logo, and approver are in place, the designer can begin the layout confidently. The photos can arrive later without blocking early work. The client sees exactly why the project can move forward, and the designer avoids building around changeable assumptions.
Common mistakes that weaken a start gate
Making it a surprise after the sale
Introduce the process while discussing the next steps, not after the client believes work has begun. A brief explanation is enough: completing these items lets you use their scheduled time on the work rather than on chasing prerequisites.
Asking for a perfect brief
Clients often hire a specialist because they need help clarifying the work. Require only the decisions and information necessary to begin. Discovery may be a paid, defined first phase rather than something you demand they complete alone.
Confusing silence with approval
If an item needs a decision, leave it open until the responsible person answers. Proceeding on an unconfirmed assumption may feel efficient, but it commonly creates avoidable revisions.
Creating exceptions that become the real policy
There will be urgent situations and long-standing clients with established workflows. Make exceptions deliberately and note why. If every project bypasses the gate, the checklist is not too strict; it is probably asking for the wrong things or being introduced too late.
Start with one service, not your whole business
Pick the service that most often becomes stuck after a client says yes. Review the last few projects of that type and write down the first missing item that caused real waiting or rework. That item belongs in the gate.
Then draft a checklist with no more than six required lines. Send it on the next suitable project, notice which instructions create questions, and simplify the wording. A useful start gate is not impressive paperwork. It is a small operational promise: when the work begins, it can actually move.
Ad