Interior design software for project managers
You already know it slipped.
You already know it slipped.
You need to know what it moved.
A sofa acknowledges four weeks late and everything downstream quietly changes — the install date, the trades you booked around it, the client email you now owe. Workroom holds the dependencies, so a slip arrives as a recalculated plan instead of a rumour you have to chase down.
Utilizationplanned · 4 people
Team avg 74% · 118h planned
MemberJUL 27W31AUG 3W32AUG 10W33AUG 17W34AUG 24W35AUG 31W36
Team 74%72%88%79%108%46%—
AMAndrea Martinez40h/wk68%92%84%112%41%—
MCMaya Chen40h/wk81%77%94%85%32%—
DLDana Lee32h/wk43%72%64%96%38%—
Andrea is at 112% in the week of 17 August. You can see that today, not on the Monday it becomes a problem.
Trusted by the studios doing the work
5 views
table, kanban, gantt, portfolio and utilization over one plan
Told, not shown
install risk reaches you as an alert, not as a number you remember to check
Chased for you
silent shipments and lead-time drift raise themselves
On the record
approvals and client threads sit on the project, not in an inbox
The date you promised
Install day is the only deadline a client remembers
Everything upstream is negotiable. The day the client walks into a finished room is not. Workroom works backwards from it — and tells you when it stops being true.
- Dependencies that hold — No custom drapery PO before the final field measure. The block is real, and the trigger chases the measure instead of waiting for you to notice.
- The punch list, on the record — Damage, shortfalls and repairs raised against the item and the PO they belong to, with photos attached, rather than as a thread nobody can find in March.
- Slips that arrive worked out — A late acknowledgement moves the dates, flags what depended on it, and opens a review task with the client update already drafted.
Chasing, without the chasing
The vendor who goes quiet is the one that hurts
Nobody emails to say they are running late. The information you need most is the absence of information — a ship date that passed with no tracking, an acknowledgement that quietly came back four weeks past the quote.
Workroom fires on those. A silent shipment raises a task against the buyer with the vendor and the days elapsed already in the title. Lead-time drift flags the schedule impact before it reaches the install date. You spend the morning resolving things instead of discovering them.
Silent shipment — chase the vendorActive
Install confidence
The number you never have to look at
Every project carries a live install-readiness score, worked out hourly from your procurement dates. It is not a tile on a dashboard and there is nothing to check — you build one automation, and it tells you when the install date stops being safe.
How the score is worked outEllis Residence · install day 14 Nov · 20 ordered items
Alert when confidence drops below
12Deliveredhas a delivered date
3On trackETA at least 3 days before install
5At riskno ETA, or an ETA that is too late
(Delivered + On track) ÷ total ordered × 100 = (12 + 3) ÷ 20
75%
Crossed the 80 band
Hourly readings, and what you would hear about
How you find out
You build it once, and then forget it exists
There is no screen to monitor. The trigger fires the moment the score crosses a band you chose, and the run does whatever you told it to — email the client, raise a task to expedite, notify the project manager.
Nothing is sent until you enable the automation, and you can pause it at any time.
Install at risk — EllisPaused
Install day, resolved in order
An installation milestone task in WIP if you have one, otherwise the project's estimated completion date, otherwise the project end date. Set the milestone and the score gets sharper.
Three days of cushion
An item only counts as on track if its estimated delivery lands at least three days before install day. That gap is staging and prep, not optimism.
Live values in the message
Drop {confidence-score}, {at-risk}, {install-date} and {project-name} into the email or task the automation raises.
Two honest caveats. The score lives on the project record rather than on any dashboard, and it recalculates hourly — so an alert lands within about an hour of the data changing rather than instantly. And it is only as good as your procurement dates — a stale ETA makes a stale score. Items you have not ordered yet do not count against you; this measures whether what you bought will land in time.
The connected record
Where a project manager stops being the router
Approvals live on the item
A client approves a product in Comms and the record changes. No screenshot, no "did you see my email", no chasing a decision that was already made.
Change orders keep the original
Scope moves without losing what was agreed, and the budget follows — so the conversation about the overage happens before the invoice, not after.
Capacity before you commit
Utilization shows whether the team can absorb the next project before the principal says yes to it, which is the conversation you would rather have early.
Files where the work is
Cut sheets, shop drawings and receiving photos attached to the item, the PO or the task — not to a folder somebody named on a Friday.
Ask instead of assemble
"What is at risk for the November install?" is a question, not an afternoon. Walter reads across the same connected records you do.
Time against the plan
Hours land on the phase and the task, so the estimate for the next project is built from what this one actually took.
Case study — interview with Tessa B.
“Knowing something slipped was never the hard part. Knowing what else it moved — that is the part I used to rebuild by hand every Monday.”
Tessa B.Operations Lead · Toronto
Questions we hear
Running projects, specifically answered
We already use Asana. Why move the plan?
Because a task tool does not know what a purchase order is. It can hold "chase the sofa" as a card, but it cannot know the sofa was acknowledged four weeks late, that the acknowledgement moved install readiness, or that six drapery items are blocked behind a field measure. The plan and the procurement have to be the same record for a slip to recalculate anything. Asana and Trello integrations are on the roadmap for teams that want to keep both.
What actually happens when a delivery slips?
The item's dates move, the hourly recalculation picks it up, anything dependent on it is flagged, and a review task opens with the recalculated install date, a drafted client email and the schedule notes already assembled. You review and send. The consequence arrives handled rather than as an alert you have to act on from scratch.
Can I see every project at once?
Yes. Portfolio view runs across projects, and utilization shows the team's load against it. Both read from the same phases and tasks as the single-project views, so there is no separate roll-up to maintain.
Does the client see all of this?
No. Clients see the polished side — selections, approvals, documents and the financials you choose to share. The schedule, the margin and the internal notes stay yours. Client collaboration →
Do I have to build the automations myself?
No. Silent shipment, lead-time drift, install confidence and dependency blocks all ship as templates. Describe anything else in a sentence and Walter drafts it — and nothing runs until you enable it.
For the person holding the date
Bring us the project you are most worried about.
We will set it up on the call and show you what is actually at risk on it — not a demo project, yours.