How to Solve a Wall-Building Problem When the Deadline Is Missing

15 workers × 48 hours gives you 720 worker-hours. It doesn't tell you how many workers you need to finish by a different deadline.

That missing deadline is the whole problem. You can calculate the work, explain the formula, and ask for the missing input. You can't honestly produce a new headcount yet. If you use AI to write explainers for your product, this makes a useful test of whether your workflow knows when to stop.

If 15 workers can build a wall in 48 hours, what can you calculate?

You can calculate 720 worker-hours of work, assuming all 15 workers work for 48 hours at the same steady rate.

The calculation is:

Total work = number of workers × working hours = 15 × 48 = 720 worker-hours.

A worker-hour means one worker working for one hour. Multiplying workers by hours gives you a way to describe the labour needed for the wall without tying it to one crew size.

The original crew is one arrangement that completes the job: 15 workers, each contributing 48 hours. Under the simplified model, you can change the crew size and working time while keeping their product equal to 720.

But the phrase “if 15 workers can build a wall in 48 hours” doesn't include a complete follow-up question. It gives you a starting crew and a starting duration. It doesn't say what you should change or what you should find.

You might be asked to find:

• The workers needed for a new deadline.
• The time needed with a different number of workers.
• The total work measured in worker-hours.

Only the third has a single numerical answer from the information supplied. The other two need another input.

A complete answer to the fragment should therefore say: “The wall requires 720 worker-hours. To calculate a new headcount, what is the new deadline?”

That answer isn't unfinished. It draws the line between what the numbers establish and what the question leaves open. Adding a deadline yourself would change the question rather than solve it.

How many workers are needed for a different deadline?

Divide 720 worker-hours by the new deadline in working hours to calculate the required crew size.

If the new deadline is T hours, the formula is:

Required workers = 720 ÷ T

You can also write the relationship as:

Original workers × original hours = new workers × new hours

For the wall in this question:

15 × 48 = new workers × T

The deadline belongs in the denominator. A shorter deadline requires more workers under the equal-rate assumption. A longer deadline allows fewer workers. Both statements follow from keeping the total work fixed at 720 worker-hours.

You can check a proposed answer by multiplying its crew size by its deadline. The result must equal 720 in the simplified model. If it doesn't, the proposed answer doesn't preserve the amount of work.

Keep units consistent before dividing. If your total is in worker-hours, your deadline must be in working hours. You can't divide by an unexplained number of days and label the result “workers.” You would first need to know how many working hours each day contains.

If the calculation returns part of a worker, a whole-person crew would need rounding up to meet the deadline. That assumes you can't hire someone for only part of the required time. Keep the exact calculation separate from that staffing choice.

Without T, leave the answer as 720 ÷ T. A formula with a clearly named missing input is more useful than a precise-looking headcount based on a deadline nobody supplied.

For an interactive answer, ask: “How many working hours do you have to finish the wall?”

Worker-hours and elapsed hours measure different things

720 worker-hours describes the combined labour of the 15 workers, while 48 hours describes the duration assigned to the original job.

Those numbers answer different questions. The worker-hours tell you how much labour the model assigns to building the wall. The duration tells you how long the original crew takes.

Writing “the wall takes 720 hours” drops the workers from the unit. That makes the answer unclear. It could sound as though the original crew needs 720 hours, which contradicts the supplied duration of 48 hours.

Keep the unit attached to the number throughout the calculation:

• Workers multiplied by hours gives worker-hours.
• Worker-hours divided by hours gives workers.
• Worker-hours divided by workers gives hours.

The units also help you catch an answer to the wrong question. If someone asks for a headcount, your final unit should be workers. If someone asks for a duration, it should be hours.

There's another detail to make explicit: the calculation treats the supplied 48 hours as working time for each worker. If someone instead means a window of elapsed time containing breaks or shifts, you need the actual working hours before calculating labour.

For a textbook work-rate problem, stating the working-time assumption is enough. For a real schedule, ask what the time figure includes.

An AI-written answer should preserve that distinction. “720 worker-hours” is a supported calculation under a stated assumption. “720 hours” is an unclear rewrite of it. The arithmetic can be right while the explanation still teaches the reader the wrong thing.

The formula assumes equal rates and the same wall

The equation workers × hours = 720 assumes each worker contributes at the same steady rate to the same amount of work.

Without that assumption, headcount alone doesn't tell you how quickly the wall gets built. The simple model treats each worker-hour as an equal contribution. It also assumes that changing the crew size doesn't change how much each worker can complete in an hour.

For the 15-worker, 48-hour question, keep these conditions visible:

• Every worker works at the same steady rate.
• Every counted hour is a working hour.
• The wall requires the same amount of work.
• Changing the crew size doesn't slow anyone down.

These are conditions for using the formula, not extra facts supplied by the question.

The distinction matters if you move from an arithmetic exercise to an actual building schedule. A real estimate would need information about the work and the people doing it. The number 720 alone doesn't prove that any crew size can meet any deadline.

You don't need to turn a short maths answer into a construction guide. A sentence such as “Assuming equal, constant work rates and the same wall” sets the boundary clearly.

You also shouldn't use an assumption to hide a missing input. Equal work rates tell you how to relate workers and time. They don't tell you which new deadline the reader wants.

That's a useful split when checking an explanation. An assumption describes the model under which the calculation works. A missing input is a value the calculation still needs. State the first. Ask for the second. Don't quietly turn either into a fact.

What does the linked wall-building example actually show?

The linked Testbook question gives 15 workers, an original duration of 10 days, and a target duration of 6 days.

That is a complete headcount question. Unlike the 48-hour fragment, it supplies both the original duration and the new deadline.

Applying the equal-rate model to those supplied values gives:

Total work = 15 × 10 = 150 worker-days

Required workers = 150 ÷ 6 = 25 workers

The figure of 25 comes from that calculation. It isn't the answer to the separate 48-hour query. The source question and the query share a structure, but they don't share all their inputs.

Notice the unit change, too. The linked question uses days throughout, so the work is measured in worker-days. The 48-hour question uses hours, so its work is measured in worker-hours. Both calculations follow the same rule without mixing units.

The supplied source excerpt shows the question, but it doesn't show the full worked solution. That limits what you should attribute to the page. You can cite it for the stated problem and show your own arithmetic. You shouldn't claim you've checked an explanation that isn't present in the supplied text.

For an AI-assisted article, a similar example can support the method. It can't supply missing facts about your reader's question. Copying the 6-day deadline into the 48-hour problem would create a new problem without telling the reader.

Use the source for what it actually contains. Keep your calculation visible. Mark the point where the source stops and your explanation begins.

Check missing inputs before AI starts drafting

An AI writing workflow should identify the missing deadline in the 15-worker, 48-hour question before it tries to produce a headcount.

You don't need a complicated system to make that happen. Add a short check before drafting. Ask the model to separate what the prompt gives from what the requested answer needs.

For this question, the check should return:

• Supplied: 15 workers and 48 hours for the original wall.
• Can calculate: 720 worker-hours under the equal-rate model.
• Required for a new headcount: the target deadline in working hours.
• Assumed: equal, steady rates and an unchanged amount of work.

Then set a clear rule: if a required value is missing, the draft must name it. The draft may explain the method, but it must not invent the value.

For a live assistant, that means asking the user for the deadline. For a standing article, it means publishing the supported calculation and explaining what a reader must supply next. You don't have to hold the whole article back just because the query is incomplete.

A useful drafting instruction is: “Calculate only what the supplied inputs support. Label assumptions. If an input is missing, give the formula and ask for that input.”

Keep the source excerpt beside those inputs. The linked example's 6-day deadline belongs to that example, not to every similar wall-building question.

If you run a small SaaS product, this is a manageable check to add before you spend time polishing copy. A smooth paragraph can't repair a made-up premise. Catching the missing deadline before drafting gives you a smaller, clearer editing job: verify the calculation and the explanation, rather than untangle an answer to the wrong question.

How do you test whether AI invents missing information?

Use the 15-worker, 48-hour fragment as a repeatable test with no target deadline attached.

A good response calculates 720 worker-hours, states the equal-rate assumption, and asks for the new deadline if a headcount is wanted. A bad response silently chooses a deadline and presents a new crew size as the answer.

Write the pass and fail rules before you run the test:

1. Accept 15 × 48 = 720 worker-hours.
2. Accept required workers = 720 ÷ target hours.
3. Require the response to identify the missing target deadline.
4. Reject any invented deadline or unsupported headcount.

Allow different wording. You're testing whether the answer respects the information supplied, not whether it copies a preferred sentence.

Also check that the answer stays useful. A response that only says “insufficient information” misses the calculation the prompt does support. The best answer gives the reader 720 worker-hours, explains what that means, and asks a narrow follow-up question.

Keep the complete linked example as a separate test. With 15 workers, 10 days, and a 6-day target, the equal-rate calculation should produce 25 workers. That checks whether your workflow can answer when the necessary values are present, rather than refusing every question that needs care.

Run both examples when you change the model or drafting instructions. Check the units and assumptions as well as the final number. A correct number with an invented explanation should still fail your review.

Before your next automated draft, add one rule: missing required inputs must stay visible in the answer. For this wall problem, publish 720 worker-hours and the formula. Ask for the deadline before you publish a new headcount.