Five short answers before you start. What project controls is, whether this is written for you, where it can take you, and how to work through it. Seven minutes, and then you will know which track to open.
It is not scheduling. Scheduling is one of its instruments.
A construction project is a large machine with almost no windows. Thousands of things happen every week across engineering, procurement and site, and no one person can see them. Project controls is the instrumentation. It measures what the project is doing, compares that against what the project promised, works out where it is heading, and puts a number in front of the people who can still change the outcome.
The word "control" misleads people. Project controls does not control the project. It cannot pour concrete faster, and it cannot make a vendor deliver on time. What it does is take away the excuse of not knowing. When a project finishes late, it very rarely surprised anyone at the end. It told somebody in month three, quietly, in a number nobody acted on.
That work splits into a handful of disciplines that share one model of the project. Planning owns the time. Cost control owns the money and the cash. Risk owns what has not happened yet. Contract and claims own entitlement, which is the right to more time or more money when something outside your control changed the job. Reporting connects all of them to the people who decide. On a small job one person does all of it. On a megaproject each is a department, and knowing where the boundaries fall is half of working effectively.
The misconception worth killing early. Most people arrive believing project controls means Primavera P6. P6 is a calculator. It answers the question you type into it, and it has no opinion about whether the question was any good. Every serious mistake in this field is made before the software opens.
Probably, if you are already near a construction project.
This curriculum assumes you understand what a construction project is and roughly how one is built. It does not assume you have ever opened scheduling software, run a report, or read a contract clause. Everything technical is built from the ground up.
It is not written for someone who needs to produce a Primavera file by Friday. That is a legitimate need and there are faster answers to it elsewhere. What is here is slower and more durable: the reasoning underneath the file. The tools come later, after the reasoning, because a tool you can drive but not reason about is worth nothing on a site.
One more thing worth saying plainly. This is written from eight years on nuclear, mining, port and high-rise projects, and it reflects how those projects actually behave rather than how a textbook says they should. Where the two disagree, the field wins and the disagreement gets explained.
Project controls is not one job. It is five, and they pay attention to different things.
Most people drift into one of these without choosing it. Knowing they exist early lets you choose. Each has a track here, and each track is a complete curriculum on its own.
You own time. You build the schedule, keep it honest as the job changes, and tell everyone what the current date really is. The most common entry point, and the one closest to the site.
You own money. Budgets, commitments, earned value and the cash the project needs next month. Closer to the commercial team, and the path that leads most directly toward project management.
You own what has not happened yet. Registers, quantification, contingency and the Monte Carlo run behind a completion date. The most analytical of the five, and the smallest job market.
You own entitlement. Notices, variations, extensions of time, and proving a delay was not yours. Two tracks, because reading the contract and proving the delay are different skills.
You own the machine the other four run on. Excel, Primavera, Power BI, field data capture and the interfaces to the cost system. It comes last here on purpose, because a tool without the reasoning is worth nothing.
The usual shape of a project controls career, and why almost nobody follows it exactly.
A common route runs graduate engineer, site engineer, planning engineer, senior planner, project controls lead, project controls manager. Some people then move into project management, some stay technical and go deeper, and some move to the client side where the same skills are used to check other people's numbers instead of producing them.
Two things are worth knowing about that list. The first is that the step from site engineer to planning engineer is the one most people underestimate. It is not a promotion, it is a change of trade. You stop being responsible for work getting done and start being responsible for what the project believes about itself, and the second job needs a different kind of thinking than the first.
The second is that the ladder is not what actually moves people. What moves people is the size and type of project they have been on, and whether they can defend a number in a room that does not want to hear it. That skill is not taught by title. It is the thing this curriculum is trying to build.
There is a reading order, and there is permission to ignore it.
Track 1 is where to start. It is the foundation the other four stand on, and it assumes no software and no prior planning experience. If a term is unfamiliar, it gets defined the week it is first needed.
Track 1 is the foundation everything else stands on. Cost, risk, contract and claims all assume it. After Track 1 the order is genuinely yours, because those four are independent of each other and each says so where it depends on something you have not read yet.
Every lesson is a single article of roughly seven minutes, published one week at a time, each one building on the last. There is nothing to install and no exercise you have to complete before the next one opens. The fundamentals are free and stay free. The digital phase, when it arrives, is where the tools are taught, and it comes last because it depends on everything before it.
What you are looking at. Five tracks complete, 117 lessons published, one lesson a week, and a toolbox after the theory. Written by one planning lead, from the field, and corrected wherever the field disagreed with the book.