Ever launched a website that was “basically done” for three weeks? Chances are the missing piece was never code. It was the logo file the client promised, the copy the writer said would arrive on Friday, or the login details from whoever manages the domain. A waiting-for list is a tiny habit that stops this from happening, and this explainer shows what it is and how a website project can use it.
The idea in one breath
You keep a list of everything you have asked someone else for. Beside each line you jot who owes it, when you asked and when you will ask again. That is the whole thing. It sits next to your normal task list but holds a different sort of item: not “things I will do”, but “things I am expecting”.
Why websites are especially prone to stalling
Building a site looks like one project, yet it is really a pile of small dependencies tied together. The developer needs text, images, brand colours, hosting access, plugin licences and sign-off on designs. The client needs mock-ups, staging links and answers to questions. Marketing needs tracking codes in place. Each piece sits in somebody else’s inbox, and none of them feels urgent to that person until the deadline looms.
Because the work is digital, delays are invisible. A half-built wall is obvious to everyone who walks past it. A page waiting for a paragraph of text just looks like a page. The waiting-for list makes the hidden queue visible, one line at a time.
What goes on a website project’s list
- Content: page copy, product descriptions, team bios, testimonials.
- Assets: logos, photos, fonts, brand guidelines.
- Access: domain registrar, hosting panel, analytics account, email service.
- Approvals: design sign-off, staging review, legal wording on forms.
- Third parties: payment provider set-up, plugin vendor replies, translation work.
Think of each as a little parcel in the post. Until it lands, a piece of your build cannot move. Writing it down means you can ask “where is it?” at a sensible moment instead of discovering the gap on launch day.
A tiny example
Say you are building a service business site. You email the client for three things: a list of services with short descriptions, a handful of photos and a decision on which contact form fields to include. Your list now holds three lines. Beside the first you write “client owner, asked Monday, nudge Thursday”. Beside the photos, “client or their photographer, asked Monday, nudge Friday”. For the form decision, “client, asked Monday, nudge Wednesday”.
On Wednesday the form question comes due. You send a short note: “Quick check on the contact form fields, since I build that page tomorrow.” You get an answer within the hour. Without the list, this would have become an awkward discovery at the end of the week.
Pages that persuade visitors, like an article on turning service pages into client enquiries, depend heavily on content that only the business owner can supply, which makes this kind of tracking especially valuable.
Waiting-for versus a project board
You might ask whether a project management board already does this. Sometimes it does, if every card carries an owner and a due date and people actually update them. In practice, boards fill with tasks and lose track of requests directed outside the team. A separate list has one clear job and stays small enough to read in a minute. Many teams use both: the board for work, the list for expectations.
The four fields, explained
The item. Be specific. “Images” is vague; “homepage hero photo, landscape orientation” is useful.
The owner. Name a role or organisation. If it is “whoever deals with it”, the line is broken.
The date asked. This lets you see how long something has been waiting, which is surprisingly easy to misjudge.
The nudge date. This is the day you will politely ask again. Choose it when you send the request, while the reasonable timescale is fresh in your mind.
Writing a friendly nudge
The best reminders are short and warm. Mention what you need, say why the timing matters and make replying easy. For example: “Hi, just checking on the about-page text. I am scheduling the build for Tuesday, so anything you can send by Monday evening keeps us on track. Even a rough draft is fine.” Notice there is no blame, no sigh. You are simply handing over the useful facts.
Trust-building pages are a good case study. A piece like a discussion of why the About page builds confidence shows how personal and hard to rush such content can be, so a polite follow-up is often exactly what the owner needs.
What if people ignore the nudge?
It happens. After a second reminder, try a different route. A quick call or message to another person involved often shifts things. If that fails, tell your own manager or client the knock-on effect: “The launch date depends on the product photos; here is the date I need them by.” This is not a complaint but a fact, and a clear fact usually triggers action. Record the escalation on the list so there is a trail.
A brief aside on bigger life projects
The habit is not limited to websites. Any project where other people hold your next step benefits. Consider someone researching a home purchase using a site such as Propraahi, a website for people researching property to buy in India. They would likely be waiting on answers from several quarters at once. A private list would help them keep track, whichever resource they use.
Handing the list to a client
One underrated trick is to share the relevant lines with the client in a simple table at the start of each week. They see precisely which items are theirs, which are yours and which are with outside vendors. Many clients are surprised to learn that the biggest source of delay is their own pending material, and a friendly table makes the point without a lecture. It also gives them an easy way to say “that one is coming tomorrow”, which is more useful than silence.
How it helps after launch
The list does not retire when the site goes live. Maintenance brings a fresh set of dependencies: a hosting provider confirming a renewal, a plugin author fixing a bug, a content editor delivering the monthly post, an analytics colleague sharing a report. Keeping the habit means that small post-launch requests do not drift. Sites that are looked after tend to stay secure and current partly because someone notices when a promised update has not appeared.
A quick glossary
- Dependency: something your work needs from someone else before it can proceed.
- Owner: the person or team responsible for supplying it.
- Nudge: a short, polite follow-up sent on a planned date.
- Blocker: a dependency that is holding up other work right now.
- Close: to cross a line off after the item arrives.
Common beginner slips
- Adding items hours after the request, by which time details have blurred.
- Skipping the owner field, so nobody knows whom to chase.
- Setting nudge dates that are far too optimistic and then ignoring them.
- Never closing lines, so the list swells until nobody reads it.
Getting started today
Open a blank note. Think of the last three things you asked someone for on a current project. Write each as a line with its owner, its asking date and a date to chase. Then set a recurring reminder, perhaps each morning, to look at the list for thirty seconds. Within a week you will probably notice that you are catching delays earlier, and conversations with clients and colleagues become calmer because you can state exactly where things stand.
Nothing more to it. A waiting-for list is not clever software or a productivity system with a fancy name. It is a handful of lines that remind you what others owe you, so that projects keep flowing and no one is surprised.