Hobfolk
Department 02 · Projects

Somebody has to decide
what happens first.

The job is won. Now it needs an order of work, the people it depends on need telling, and the difference between the date you promised and the date it will actually land needs to be somebody’s problem before it becomes the client’s discovery.

Start a conversationSee the whole crew
You go home. It doesn't.Every promise gets a row and a due dateAnswered the same day, not the next working dayA drawing before the quoteUnverifiable is never a passNine desks, one address eachNothing is sent that a human cannot read backThe folder exists before you price itYou go home. It doesn't.Every promise gets a row and a due dateAnswered the same day, not the next working dayA drawing before the quoteUnverifiable is never a passNine desks, one address eachNothing is sent that a human cannot read backThe folder exists before you price it
The case for it

Project office & programme

A promise nobody wrote down is a promise that dies.

Almost nothing is lost at the moment it goes wrong. It is lost in the fortnight beforehand, while a dependency nobody named sat waiting on a person who did not know they were the blocker — the veneer that had to be ordered before the carcass could be cut, the access permit that had to exist before the crew travelled.

A project office is not a Gantt chart. It is a desk whose entire remit is knowing what has to happen next, who it depends on, and which of those two facts changed today. It opens the departments a job needs and stands them down when the job no longer needs them, so nobody is chasing a supplier on a quote that went out to the client last week.

And it makes the uncomfortable call early. Every date on this desk is either the date you were told or a date you have been warned about — there is no third state where the programme has quietly known for three weeks and nobody has said.

The order called, and everybody on the same bar
The order called, and everybody on the same bar
What the desk does

Six things, every day, without being asked

Take the whole desk or one line of it. Everything below is included in the department retainer — there is no menu underneath the menu.
01

The order of work, decided

What has to happen first, what can run alongside it, and what is genuinely on the critical path rather than merely urgent. Written down where the job lives, not held in the head of whoever is nearest to it.
02

Dependencies raised before they bite

Long-lead material, a drawing the floor cannot start without, an access or permit condition, a client decision that has to land by a date. Each one gets an owner and a date, not a mention in a meeting.
03

Every promise held as a dated row

“I’ll come back to you Thursday” becomes a row with a due date in the same minute it is said, and it is swept whether or not anybody remembers making it. A commitment that lives only in a thread dies when the thread scrolls.
04

Departments opened, and stood down

This desk is the tap. A department acts on an open need and stops on a closed one — so the day a quote goes out, procurement freezes instead of chasing suppliers on a job that is now sitting with the client.
05

One owner per thread, visible

Two people answering the same client differently on the same day is the most expensive failure in this whole list, and it is designed out rather than trained against: before anybody touches a thread, they can see who already has it.
06

The slip flagged early — to you, and to them

The moment a promised date stops being achievable, you hear it and the client hears it, with a replacement date and the reason. A date is never allowed to pass unmentioned.
Depth

What this desk actually knows

A project office earns its place in the six days between the weekly meetings. This is what the desk is actually tracking while nobody is in the room.

The programme

  • The critical path separated from the merely urgent — the two are confused daily, and only one of them moves the finish date.
  • Float identified and then spent deliberately, on the risk that deserves it, instead of being consumed quietly by whichever task started late.
  • Long-lead items ordered against the date they are needed on site, worked backwards through the lead time — not against the date somebody got round to raising the order.
  • Sequence written to how the thing is actually built: what has to be dry, what has to be measured on site before it can be cut, what cannot be lifted once the room is finished.

Dependencies and the people in them

  • Every dependency has a named owner and a date. A dependency owned by “the team” is owned by nobody.
  • Client decisions treated as programme items with due dates, because a sign-off that is two weeks late is a two-week delay whatever the contract says about it.
  • Access, permits, power, deliveries, lifts and out-of-hours windows raised at the point they can still be arranged rather than the week of install.
  • Who else is on this thread, before anybody writes to the client. Two people answering the same question differently on the same day is the failure this desk exists to make impossible.

Promises, held

  • Every commitment made to anybody — client, supplier, your own floor — becomes a dated row in the same turn it is made, and is swept whether or not the person who made it remembers.
  • Recurring commitments declared as recurring. A weekly report that carries a single terminal date is a report that silently stops after the first one.
  • Standing instructions are machine-read. Mark a job or an account frozen and every chaser stops — not a note beside the record that nothing reads.

Change and the record

  • Variations captured when they happen, in writing, priced and agreed by you — the unrecorded variation is the single most reliable way to lose money at final account.
  • Delay and its cause recorded contemporaneously, because a programme reconstructed eighteen months later in a dispute convinces nobody.
  • One line per thing to make, at the size it actually is, on a sheet the bench can read — and the marketplace dispatch clock and the trade balance-before-dispatch clock kept in separate blocks, because they are two different promises and merging them breaks both.

None of that is clever. It is the list a good contracts manager carries in their head — written down, and applied to every job rather than the ones somebody had time to think about on Sunday night.

The run of it

How a job moves through

  1. It is won

    The enquiry becomes a job. The folder already exists; now it gets a programme.

  2. The order is set

    First, alongside, and genuinely critical — separated out and written down.

  3. Dependencies are named

    Each with an owner and a date. Long-lead items ordered against the date, not the hope.

  4. Departments are opened

    Only the ones this job needs, and only for as long as it needs them.

  5. The week is worked

    Promises swept, blockers raised, the two clocks — yours and the client’s — kept apart.

  6. A date moves, out loud

    Warned before it slips, with a new date and the reason. Never afterwards.

The limits

What this desk will not do

Every department has a written boundary. A service that claims no limits has simply not found its own yet, and you will find it for them.

Where this desk stops

  • It does not overrule your floor. If production says four weeks, the programme says four weeks. This desk reports capacity; it does not invent it, and it will not book work your people have not said they can take.
  • It does not vary a contract. A change to scope, price or programme that costs money is drafted here and agreed by you — a variation nobody signed is the most reliable way to lose the argument at final account.
  • It does not manage your people. It sequences work and names dependencies. Who does what, and how, stays with whoever runs that floor.
  • It does not quietly absorb a slip. Deliberately. The urge to recover a lost week without telling anybody is how a four-day slip becomes a three-week one.
Questions

Asked before, answered here

Is this a project manager, or project-management software?
Neither. It is a desk that does the work a project manager does between meetings — sequencing, raising dependencies, holding promises to dates, warning before a date slips. It runs inside the tools you already use rather than asking you to move into a new one.
Who decides the dates — you or us?
You do. The desk reports what your floor has confirmed it can take and builds the programme around that. It never books work your people have not said they can do, and it never invents capacity to make a date fit.
What happens when a date is going to be missed?
You hear it and the client hears it, before it passes, with a replacement date and the reason. The one thing that never happens is a date going quiet.
Does it talk to our clients directly?
Only where you want it to, and never about price, scope or anything contractual — those are drafted and a person releases them. Programme updates and a warning about a slipping date are the routine case, and you can have every one of them approved first if you would rather.
We already run a weekly production meeting. What does this add?
The six days in between. A weekly meeting is a good way to agree an order of work and a poor way to notice on Wednesday that the veneer nobody ordered has a three-week lead time.
Next department

Compliance, documents & contracts

And then the documents the programme has to produce.

Open Compliance

Which of the nine is costing you the most this month?

That is the one to start with. Tell us and we will tell you plainly whether we are the right shape for it.

Start a conversation Read the method