The columns you’re missing already exist

A Project table with the four familiar columns next to three highlighted ones - Finish Variance, Remaining Work, Owner - behind Insert Column

Sooner or later the question arrives that the table can’t answer. How far has that delivery slipped? Who owns it? How much work is really left, once you discount the optimistic percentages? You look at the columns in front of you — Task Name, Duration, Start, Finish — and the answer isn’t there.

So the shortcut is right there. An Excel file next to the plan, or the information written wherever it fits: in the task name, in square brackets, “[BLOCKED – ask Smith]”. From that moment you have two archives that don’t talk to each other, and one of them is a title.

What almost nobody knows is that in Microsoft Project the columns you’re missing already exist. They have been there all along — several hundred of them — hidden behind a right-click. You just need to know which ones to call.

How to add a column

The gesture is one, and it works everywhere: right-click a column heading, then Insert Column. Project opens the list of available fields; start typing and the list filters itself.

That’s all there is to it. The rest of this article is knowing what to type in that box, because you can’t guess the right names: nobody searches for “Finish Variance” without knowing it exists.

Three families of columns repay the reading on their own.

The delay columns

Start Variance and Finish Variance tell you how far each task has moved from what you promised. Not “when does it finish”, but how different is that from when it was supposed to finish — which is the real question in every progress meeting.

They have one prerequisite, and it’s the reason they sit empty on most plans: they are computed against the baseline, the photograph of the plan at the moment of commitment. If you never saved one, the columns show zero all the way down — not because you’re on time, but because there is no reference. I wrote about this in the view your boss understands at first glance too: if there is no baseline, saving one today is the first thing to do.

For budgeted plans the same pattern holds: Cost Variance and Work Variance exist, and they answer the same question in a different unit.

The real-work columns

% Complete is the most misunderstood column in Project: it measures elapsed duration, not effort spent. A ten-day task on its sixth day is at 60% — even if the hard part hasn’t started.

The columns that tell the story of effort are two others. % Work Complete measures hours done against hours estimated. Remaining Work says how many hours are left — and it is the most honest number in the plan, because it looks forward instead of backward. When a task has been “at 90%” for three weeks, it’s the Remaining Work column that tells you whether the last 10% is worth two hours or two weeks.

The empty columns with your name on them

Then there is the information Project cannot know: the department, the external owner, the priority agreed with the client, the order code. It’s the information that ends up in the Excel files on the side and in the square brackets.

For that, Project keeps dozens of empty fields ready: Text1 through Text30, Number1 through Number20, plus Date, Flag and Cost fields. They are free columns: you insert them like any other and write whatever you want in them.

The step that turns them from a workaround into a tool is the rename: on the Project tab, in the Properties group, open Custom Fields, select Text1, click Rename and call it “Owner”. From that moment the column list shows Owner, and whoever opens the plan after you understands without asking. A field called Text1 is a private note; a field called Owner is a column of the plan.

One piece of advice from someone who has been there: keep a line somewhere that says which fields you used and what for. Thirty Text fields are a lot, and the mysterious Text7 in an inherited plan is a small corporate whodunit.

The task name is not an archive

It’s worth saying once, explicitly. Every piece of information stuffed into a task name — statuses, owners, notes, asterisks — is information you cannot filter, group or total. It is text, and nothing more.

The same information placed in a column becomes working material: “show me only Smith’s tasks” is a three-click filter if Smith lives in an Owner field, and an eyeball search if Smith sits in brackets across fifty task names. The difference between the two plans isn’t tidiness: one answers questions and the other doesn’t.

What a column does not do

A column shows data that exists. It doesn’t invent the baseline you never saved, doesn’t estimate the hours nobody entered, doesn’t fill in the Owner field for you. If the plan is empty, adding columns only makes it wider.

But if the data is there — and it almost always is, scattered between your head, the emails and the Excel files on the side — the right column is the difference between a plan that describes the work and a plan that answers questions. And there is nothing to build: you only need to know they already exist.


ProjectEdgeTools builds small tools that fix real Microsoft Project headaches — from cleaning sensitive data out of your plans to getting them into Power BI in one click. Have a look at the suite.

#MicrosoftProject #ProjectManagement #PMO #CustomFields #Tracking

This article is part of the guide The plan that holds: Microsoft Project best practices, symptom by symptom, nineteen things you can see in a plan and the move that reveals each one in thirty seconds.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top