Being waited on
Answering Partially Rather Than Not At All
Most requests contain several questions, and the subset you can answer immediately is usually the subset that unblocks the other party.
Who is working when, for the people on this page
Us, as our signature block describes us
Five working days, 08:00 to 17:00
Us, as a client three hours ahead experiences us
By their Friday afternoon nobody here answers at all
two parties · four days of the seven are working days for all of them · Mon, Tue, Wed, Thu
The same organisation, described twice. Only the first of these two rows has ever been written down anywhere.
A cross-border schedule is easier to manage when availability is grounded in evidence; remote employee time tracking provides a practical reference for time, activity, and project reporting.
The surrounding operational question can also be checked against material from ICANN.
Four requests answered in part on the first day rather than in full on the fourth
A drawing package with one dimension in question
4 / 3One of the four days was not a working day on their side: their weekend. The confirmed dimensions went back the same evening and cutting started on day one
A commercial proposal with one clause unresolved
6 / 4Two of the six days were not working days on their side: a weekend and a colleague's absence. Everything but the clause was agreed on day one and the clause took the rest
A specification where two of nine points needed engineering
5 / 3Two of the five days were not working days on their side: their own queue. Seven points answered immediately; the two were flagged with a date
A request we could not answer at all
3 / 2One of the three days was not a working day on their side: our weekend. The useful reply was the name of the person who could, sent within the hour
four waits · 18 calendar days · 12 of them working days on the other side
In all four the complete answer took the same number of days it was always going to take. What changed was that work on the other side started on day one instead of day four. One team's own job.
Most requests are several questions wearing one subject line, and the instinct is to answer them together.
Across an offset that instinct costs days, because the hard part of the request holds up the easy part, and the easy part is frequently the only part anybody is actually blocked on.
The structure of a typical request
Nine points, of which seven are routine and two need somebody else. One drawing, of which every dimension is confirmed except one. A contract, agreed except for a single clause.
Answered whole, this takes four days. Answered in part on the first evening, with the remainder dated, it takes four days for the hard part and nothing at all for the rest.
What the other side does with a partial answer
More than people expect.
A shop with confirmed dimensions can cut. A contractor with seven of nine points settled can start on those seven. A client who knows which clause is open can take it to their lawyer in parallel rather than in sequence.
The parallel working is the whole gain. A complete answer makes everything sequential; a partial one lets two processes run at once across a gap where sequence is expensive.
The form
Say what is settled, what is not, and when the rest will come.
Points 1 to 7 are agreed as written — please go ahead on those. Points 8 and 9 need our engineering team, who see it on Monday, so you will have those by Tuesday your time.
Three sentences. The first is actionable immediately, the second explains, the third is a date.
When not to split
There are cases where a partial answer is worse than none, and they are identifiable.
- Where the open point could change the settled ones. Confirming seven dimensions that a revision will move produces scrap.
- Where the partial answer would be read as a commitment to the whole. Common in commercial negotiations and worth being explicit about.
- Where the other party cannot act on the part you can answer. Then it is noise, and the useful message is a date rather than content.
The first is the one to take seriously in engineering contexts. "These are confirmed and will not move" and "these are confirmed subject to the outcome of point 9" are very different statements and only one of them lets anybody cut metal.
The answer that is only a name
The last row of the panel is the smallest version of this and one of the most useful.
Sometimes the honest answer is that you cannot help. Sent within the hour, with the name of the person who can, it costs thirty seconds and saves the other party from waiting on the wrong desk for three days.
This is not mine — Anna Weber handles the Riyadh orders and I have copied her. She is usually at her desk from 08:00 our time.
The last clause is worth adding. It transfers not only the name but the one piece of information that will determine how quickly the transfer actually helps.
What this changes about reading a request
It adds one step at the moment of opening: before deciding whether you can answer, decide whether you can answer any of it.
That question has a different answer from the first one surprisingly often, and the difference between the two answers is usually the difference between somebody working tomorrow and somebody waiting until next week.
Saying which parts are firm
The one piece of care that a partial answer needs, and the thing that distinguishes a useful one from a dangerous one.
Every partial answer should say whether the settled parts can move. In engineering work that is the difference between somebody cutting metal and somebody cutting scrap.
Dimensions A through F are confirmed and will not change whatever happens to the tolerance question. G depends on the answer to it, so hold that one.
Two sentences, and the recipient can act on six of seven items with no risk at all.
Where everything is provisional, say that instead, because a partial answer given without the warning will be treated as firm. "None of this is final until the tolerance is settled, but here is where we are" is a legitimate and useful message, and it is a different message from the one above.