Studio Matrx Monthly · Volume 1 · Issue 2 · July 2026
Amogh N P
✦ In loving memory of Amogh N P — Architect · Designer · Visionary ✦
An interior fit-out site with several trades working in coordination — carpentry, electrical, finishing — a supervisor with a tablet, warm daylight, workers who look Indian, no legible text
Unit VProject Management in Interior Design

Updating & Resource Allocation

The plan changes — and the same crew can't be everywhere at once

50 minByAmogh N P· Architect & interior designer

No project runs exactly to plan, so a manager updates it — comparing actual progress to the schedule and re-forecasting, which may reveal a new critical path. A resource histogram makes the demand for people visible; smoothing flattens its peaks using float without moving the deadline, while levelling respects a resource limit and may extend the project. Much of interior project management is vendor coordination — and the software computes the schedule but does not manage the project.

Learning objectives

By the end of this lesson, you will be able to — mapped to the course outcomes for Project Management in Interior Design:

1
CO5 · Apply

Decide when to update a project and revise the schedule as reality diverges.

2
CO5 · Evaluate

Use resource histograms, and distinguish resource smoothing from levelling.

3
CO5 · Evaluate

Allocate work to vendors and use PM software as a tool, not a manager.

The plan meets reality

Updating the plan

Updating compares actual progress with the schedule at a status date, records what has changed, and re-forecasts the rest — closing the control loop. It reveals the truths a static plan hides: a delay may have created a new critical path. A plan updated is a plan alive; a plan never revised is a plan already wrong.[1]

Updating the plan Compare plan to reality, then re-forecast time → status date (today) PLANNED the original bar ACTUAL progress so far re-forecast → Behind by the gap between planned and actual — the finish moves right. work done up to today A plan is a living document — update it as the work really unfolds
DiagramA schedule being updated: a planned bar versus the actual progress diverging at a status-date line, with a re-forecast

The plan meets reality

No project runs exactly to plan. UPDATING is the discipline of periodically comparing the ACTUAL progress with the schedule — at a chosen STATUS date — recording what is done, what is late, and what has changed, and then RE-FORECASTING the rest. This closes the control loop: you plan, you measure, you compare, you decide, you revise, and around again. Updating tells you the truths a static plan hides — is the project still on the critical path you drew, or has a delay created a NEW critical path? Regular, honest updating is how a manager keeps a grip; a plan updated is a plan alive, and a plan never revised is a plan already wrong. This is the CONTROL that Unit I promised, made concrete.[1]

Seeing the demand for people

Resources — histograms, smoothing, levelling

A schedule fine in time can be impossible in resources. A histogram makes the demand visible. Smoothing shifts non-critical activities within their float to flatten peaks, keeping the end date (time rules); levelling respects a resource limit and may extend the project (resource rules). Ask which is truly fixed.[1, 2]

Resource histogram How many workers each week — peaks and troughs weeks → workers available resource limit over! W1 W2 W3 W4 W5 W6 W7 An uneven profile means some weeks demand more crew than you have
DiagramA resource histogram: bars of labour demand over weeks with an uneven peak-and-trough profile against an available-resource limit line
Smoothing vs levelling Flatten the peaks — but does the end date move? SMOOTHING shift within float, end date SAME limit peaks trimmed, same finish finish fixed LEVELLING hard limit, project EXTENDS hard cap finish slips later Smoothing keeps the date; levelling accepts a later date to respect the limit
DiagramTwo panels: resource smoothing flattening peaks within float with the end date unchanged, versus levelling that extends the project to respect a resource limit

Seeing the demand for people

A schedule that is fine in TIME can be impossible in RESOURCES: it might need eight carpenters on Tuesday and none on Wednesday, when you have four all week. A RESOURCE HISTOGRAM makes this visible — a bar chart of how much of a resource (labour, a machine, a trade) the schedule demands over time. Its PEAKS and TROUGHS reveal an uneven, often unworkable demand, against the flat line of what is actually AVAILABLE. You cannot manage what you cannot see, and the histogram is how resource demand becomes visible. Reading it is the start of fixing it — because a plan that assumes resources you do not have is not a plan, it is a hope.[1, 2]

The designer as coordinator

Vendors, and software as a tool

An interior project is delivered by many vendors, and much of managing it is allocating and scheduling them without clashes — the designer is often the coordinator. Adding people to a late job can make it later (Brooks’s Law). And PM software computes the schedule but does not manage the project — garbage in, garbage out.[1, 3]

Brooks's law More hands on a late job is not always more speed adding more people to a late project makes it FASTER every new person adds more links to talk across The truth often makes it LATER, because: - newcomers need training - old hands stop to teach - more people = more talking - links grow n(n−1)/2 Plan the resource early; piling on crew late rarely rescues a schedule
DiagramThe myth that adding more people to a late project makes it faster struck out in red, with the truth that it often makes it later
Project-management software A Gantt view to schedule, resource and track GANTT SCHEDULE amber = critical tasks The tool draws the plan; the manager still makes the decisions
DiagramA screen showing a Gantt-style bar schedule representing project-management software for scheduling, resources and tracking

The interior designer as coordinator

An interior project is delivered by MANY hands — the main contractor, and a crowd of specialist VENDORS: carpenters, electricians, the false-ceiling crew, the stone supplier, the furniture maker, the curtain and blinds vendor. Much of interior project management is ALLOCATING the right work to the right vendor, scheduling them so they do not clash (the painter cannot start until the plasterer is done and dry), tracking their progress, and managing quality and payment. The designer is very often this COORDINATOR. And here Brooks's Law bites: adding more hands to a job that is already LATE often makes it LATER — new people need briefing, work must be re-divided, and coordination multiplies. Realistic allocation from the start beats a panic of extra labour at the end.[3]

Fact vs folklore

At a glance

AspectThe factThe folklore
Updating a projectCompares actual to plan and RE-FORECASTS — closes the control loopIs optional once the plan is made
A resource histogramMakes the demand for people over time VISIBLEShows only cost
Resource smoothingUses FLOAT to flatten peaks — end date UNCHANGED (time rules)Always extends the project
Resource levellingRespects a resource LIMIT — may EXTEND the project (resource rules)Never changes the finish
Adding people to a late jobOften makes it LATER (Brooks's Law)Always speeds it up
PM softwareA powerful TOOL — computes, doesn't manage (GIGO)Manages the project for you
Vocabulary

Key terms

Updating

Periodically comparing actual progress with the schedule at a status date, recording what has changed, and re-forecasting the rest — the control loop made concrete.

Resource histogram

A bar chart of how much of a resource (labour, a machine, a trade) a schedule demands over time — its peaks and troughs against what is actually available.

Resource smoothing

Shifting non-critical activities within their float to flatten resource peaks WITHOUT moving the end date — used when the deadline is fixed (time rules).

Resource levelling

Adjusting the schedule to respect a hard resource limit, which may EXTEND the project duration — used when the resource is fixed (resource rules).

Vendor allocation

Assigning the right work to the right specialist vendor, scheduling them without clashes, and tracking progress, quality and payment — much of interior project management.

PM software (GIGO)

Tools (MS Project, Primavera) that compute schedules, critical paths, float and resources — powerful, but garbage in, garbage out: they compute, they do not manage.

Apply it — the capstone

Study task

Imagine your interior fit-out is two weeks in and running late. First, update it: pick a status date, mark what is actually done versus planned, and re-forecast the finish — and check whether the delay has created a new critical path. Next, draw a rough resource histogram for one trade (say carpenters) across the weeks, and decide how to fix a peak: would you smooth it (shift non-critical work within its float, keeping the deadline) or level it (cap the crew and accept a later finish)? Say which — deadline or resource — is truly fixed here. Then resist the instinct to simply add people, and explain, using Brooks’s Law, why that might make it later. Finish with one line on what the software could compute for you here, and what it still could not do. The goal is to manage a real project through change.

Check your understanding

Self-assessment

1. What is updating a project, and why does it matter?

2. What does a resource histogram show?

3. What is the difference between resource smoothing and levelling?

4. What is the honest limit of project-management software?

In a nutshell

Recap

UPDATING compares actual progress to the schedule at a status date and re-forecasts the rest — closing the control loop, and revealing any new critical path a delay has created.
A RESOURCE HISTOGRAM makes the demand for a resource over time visible — its peaks and troughs against what's actually available.
RESOURCE SMOOTHING uses float to flatten peaks with the end date UNCHANGED (time rules); RESOURCE LEVELLING respects a resource limit and may EXTEND the project (resource rules).
Interior project management is largely VENDOR ALLOCATION and coordination — and adding people to a late job often makes it LATER (Brooks's Law).
PM SOFTWARE (MS Project, Primavera) is a powerful tool that COMPUTES but does not MANAGE — garbage in, garbage out; judgement, estimates and communication stay human.
The evidence

References & further reading

  1. [1]B. C. Punmia & K. K. Khandelwal, Project Planning and Control with PERT and CPM — project updating, resource usage profiles, histograms, resource smoothing and levelling, and computer applications. https://www.laxmipublications.com/
  2. [2]Jerome D. Wiest & Ferdinand K. Levy, A Management Guide to PERT/CPM, Prentice-Hall of India — resource allocation, smoothing and levelling. https://www.phindia.com/
  3. [3]R. A. Burgess & G. White, Building Production and Project Management, The Construction Press, London — allocating and managing vendors and manpower on building and fit-out projects. https://www.routledge.com/

Further reading

  • B. C. Punmia & K. K. Khandelwal, Project Planning and Control with PERT and CPM.
  • Jerome D. Wiest & Ferdinand K. Levy, A Management Guide to PERT/CPM.
  • R. A. Burgess & G. White, Building Production and Project Management.

Sources gathered and fact-checked June 2026. Published values vary by source, sample and method — treat as indicative and confirm against the cited standard before structural use.

A

The author

Amogh N P

Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.

More about Amogh →