The project is waiting for the customer. When waiting becomes a way of working
Identify what is missing, what can still move forward and how to assess a realistic restart when customer materials arrive.
Article language: English

In this article
"We are waiting for the customer's materials" sounds like a calm administrative status. In practice, someone may open the same project every morning, check the inbox, put the work aside and return to it in the afternoon. The project is standing still, but it still occupies attention. When the materials finally arrive, the team has to reconstruct the agreements and find room for the work among current tasks.
Several different situations can sit behind that wait. One photograph is missing, but the rest can be completed. Approval of the whole concept is missing, so continuing risks working from the wrong basis. Or a decision is missing because the customer cannot make it from a question that was too broad. One shared label, "with the customer", does not distinguish these situations.
What exactly stopped the work?
Consider a fictional studio preparing a multilingual technical catalogue. The customer has supplied some product descriptions. Some entries lack data; others await approval of their names. The studio has someone available for layout but does not know whether to work with draft text. Starting could create visible progress and, at the same time, work that needs correcting later.
The first question concerns the specific blocked result. Is information missing for the entire catalogue or for five selected product cards? What has already been confirmed? Can the remaining sections be prepared without assuming that missing material will look like the previous material? The answer separates possible work from the appearance of progress.
The British GovS 005 standard for digital services, updated on 1 October 2026, includes dependencies on other organisations involved in a user's journey within service management. The standard applies to public administration. It nevertheless provides a useful example of treating a dependency as part of the picture of a service, rather than an invisible extra.
In our catalogue, the customer participates in producing the result. They must supply some information and confirm selected decisions. The team can describe this dependency without judging the customer's intentions. "We have not received the specifications for five products" gives a basis for action. "The customer is blocking us again" mainly gives people something to sigh about at the coffee machine.
A request for materials needs preparation too
Check what the company actually sent. "Please send all the content" might mean a folder from the past year to the customer, but approved descriptions in an agreed format to the studio. If the difference emerges a week later, another reminder is not the best place to start. First explain what is missing for a specific action.
A request for catalogue data can identify five particular cards, the required fields and an example of correctly supplied information. It should also explain which materials are drafts and which will form the basis of further work. The recipient needs to know who on their side can confirm the content. Without that, a file can circulate among people who each believe someone else will approve it.
GitLab's description of its professional services operations gives preparation and project planning a visible place in its process. It mentions gathering information needed for scheduling and assigning a team, among other steps. This is an example of one company's own practice, not a universal rule for working with customers.
For the studio, the practical lesson is simple: check that the inputs are ready before treating a project as active delivery. You may have an agreed direction and still lack data for layout. If the company says work will start after receiving materials, it must be able to recognise whether the package received meets that condition. The presence of an attachment alone is not enough.
If the missing input is a decision, examine the quality of the question. "Please approve the catalogue" may ask the recipient to assess dozens of details at once. In our example, the studio can specify that layout depends on confirming a name for a particular product group. Include the options, their visible effects and a place for the customer to raise a missing condition. Do not choose the answer for them just to move forward.
Also identify who collects material on the customer's side and who confirms its content. The person sending a file may coordinate its movement without having product knowledge. If the company expects a decision that person cannot make, more reminders will change little. The conversation should lead to participation by the right person without judging the customer's commitment from the waiting time alone.
Partial progress needs an explicit basis
Sometimes the studio can prepare the layout, work on confirmed products or check visual materials. Mark the basis on which each part was produced. If the team knowingly uses draft data, it should know which elements need checking later. Otherwise a version prepared "for the moment" can become accepted truth after several handovers.
Not every free hour has to be filled with work on the stopped project. Check the cost of reconstructing context and making later corrections. If the missing names will change half the layout, apparent progress may burden the next phase. With too much work already started (in Polish), such moves also make it harder to see what is actually nearing completion.
Remember the other tasks already accepted. A project waiting for outside information may occupy a reserved place in the plan even though the real restart date is unknown. People planning the work need to see a decision to shift attention elsewhere. Without it, the team maintains several overlapping ideas of what the same coming week will hold.
If you need to choose what to do during the wait, project priorities with a limited team (in Polish) can help. Keep a record that the order changed because particular data was unavailable. When the material returns, the team can see why the earlier time reservation no longer describes the current situation.
While waiting, set the next check-in and the reason for contact. A reminder makes sense when it restates a specific need or helps explain an obstacle. An automatic "are the materials ready?" every morning may add no new information. The customer should know whether the company is offering help defining the scope, checking for a change or explaining the effect of the missing input on the plan.

If the customer expects to send data next week, record that with the project. It does not yet mean the work will definitely be ready to resume, but it gives the team a sensible point at which to check again. If the date passes, the next contact can refer to the specific agreement. If materials arrive early, the person in charge needs a visible way to start checking them.
If the customer does not know how to answer a request for data, offer a short joint review of the particular gap. For the catalogue, that might mean identifying what product information is needed and where the customer can confirm it. This assistance has a defined purpose. It should not turn into the studio inventing specifications or adding unconfirmed data just to fill an empty cell.
Pay attention to changes in the customer's personnel as well. A successor may receive an old reminder without knowing what has already been supplied. A concise note helps: what the project concerns, what has been confirmed and which single gap is stopping the next stage. There is no need to resend the entire history if its current meaning can be reconstructed and the necessary basis identified.
A return does not automatically turn the calendar back
Three weeks later, the customer sends a complete set of descriptions. That is an important change, but it does not yet confirm a new date for the finished catalogue. Someone needs to check completeness, consistency with the earlier scope and the possibility of further work within the current schedule. Simply shifting the original date by the number of days spent waiting may not describe any real plan.
Separate receipt of materials from confirmation that work has resumed. The customer can quickly be told that the files arrived and when the next step will be assessed. A deadline promise passed from sales to delivery (in Polish) should preserve that distinction. The contact person does not need to pretend they personally know everyone's availability.
If the material differs from the earlier agreement, name the change and take it to the appropriate discussion. New products, another language or an additional layout variant may require agreement on a change to the scope of a service project (in Polish). Assessing the impact on delivery is a separate task from acknowledging receipt of a file.
We do not determine the legal consequences of a delay or the terms of a particular contract here. Day-to-day service needs clarity: what material arrived, what can be confirmed on that basis and who will return with information about the remaining work. A further date should follow from checking the current ability to deliver.
After work resumes, check whether the team is still using the same assumptions. During the pause, the customer may have changed part of its offer while the studio started using a newer template. A short review of the basis before continuing can reveal discrepancies. Do not assume consistency merely because the folder name and order number remain the same.
A service page can explain the conditions earlier
Many misunderstandings arise before a project starts. An offer describes the finished result but omits the customer's input. The recipient does not know that approved descriptions, photographs or a person to agree details will be needed. They find out only when the team expects everything tomorrow. Set out the time and tasks the customer needs to use the service (in Polish), so preparing data and approvals have a visible place in the plan.
The service page can show what is needed for a first conversation, what is needed to begin delivery and what will be agreed together. These three moments do not need identical lists. A list that is too long before contact may discourage someone who needs help defining the scope. An overly broad description can hide the customer's actual participation.
Aeneia Design helps turn an offer and contact process into a clear site. In our example, a starting point would be to describe the materials needed for the catalogue and the steps after an enquiry. That scope connects the content to the actual start of a working relationship rather than promising that everything will happen without the customer's participation.
Aeneia Design
Clarify on the site what the customer should prepare and what they can expect after getting in touch. Start with the service where missing materials most often stop work from beginning.
Explain the conditions for starting work together
Adapt the preparation guidance to the service. For a catalogue it may be approved data and photographs. For a service starting with an assessment of the situation, a short description of the problem may be enough as an input. Do not copy one project's list to every offer. The page should help the customer prepare a feasible first step, even when they do not yet know the final scope.
A waiting case should survive a change of people
While a project waits, its contact person may move to another task or hand over a shift. The successor needs to know what was requested, what has arrived and what to check after a new message. This is a specific case of handing over work in progress (in Polish). The status "waiting" alone does not preserve readiness to respond.
For a larger team change, handing a project between people and teams (in Polish) is also useful. Preserve the basis of the latest agreement, not just the date of the last email. If a request changed in a phone call, the next people need a way to find its current meaning.
Start by reviewing three waiting projects. For each, identify the specific gap, the work still possible and the condition for checking again. One project may allow partial progress, another may need a clearer request and a third may be waiting for a scope decision. That review yields three different next actions. A shared folder labelled "customer has not sent it" mainly yields a collection of unfinished sighs.











