Introduction: Why, How and Who Uses PM Documents

Welcome

Imagine you have just joined a company as a Project Coordinator or junior Project Manager. On day one, your manager says: "We have signed a new website project. Please set up the project documents." Where do you start? What do those documents look like? Who reads them?

This course answers exactly that. Instead of theory alone, you will see one real-style project from start to finish, and every document a Project Manager creates along the way, filled in with realistic dates, rupee amounts and decisions.

By the end of this course you will be able to:

1. Explain what each of the 34 common project documents is for, in simple words.
2. Understand how one document feeds into the next (for example, how hours in the WBS become money in the Budget).
3. Read basic project numbers like budget, margin, cash flow, CPI and SPI.
4. Talk confidently about real project documents in a job interview.

First, what is a project?

A project is temporary work done to create something new, with a clear start and end. Building a website, organising a wedding or constructing a house are all projects. Running the office canteen every day is not a project; that is ongoing operations.

Every project is balanced on three things. If one changes, the others are affected:

If the client asks for more pages (scope goes up), you either need more time, more money, or both. Much of project management is about protecting this balance.

What does a Project Manager actually do?

Think of a Project Manager like a wedding planner. The planner does not cook the food or play the music, but makes sure the caterer, decorator and band all know what to do, when to do it, and within what budget. When something goes wrong, the planner is the first to know and the one who fixes it.

In the same way, a Project Manager:

1. Plans the work: what, who, when and how much.
2. Coordinates the team and the client.
3. Tracks progress, cost and risks every week.
4. Controls changes so the project does not grow out of control.
5. Communicates status clearly to everyone.

Why are there so many documents?

Think about building a house. You would never start without a drawing, a cost estimate, an agreement with the builder and a list of who does what. If you skipped them, you would end up arguing about what was promised, how much it should cost and whose fault a delay was. Project documents do the same job for any project:

Meet the project: WEB-2026-01

Here is the story you will follow through the course:

1. The need: A company, called [Client Name] in the documents, has an old website that is slow and not mobile-friendly. Their marketing team cannot even change a line of text without a developer.
2. The request: In September 2026 they send out an RFP (Request for Proposal) asking companies to quote for a new website.
3. The offer: Our company, [Your Company], sends a Technical Proposal (how we will build it) and a Commercial Proposal (the price: ₹5,96,500 plus GST).
4. The agreement: The client accepts, and both sides sign a Statement of Work. The project starts on 5 October 2026.
5. The work: Over 10 weeks the team plans, designs, builds, tests and launches the website. Along the way, content arrives late, the client's Managing Director asks for a design change, and the cost goes over plan. You will see how the PM handles each of these.
6. The finish: The website goes live on 9 December 2026, the client is trained, and the project is formally closed on 23 December 2026.

The 5 phases of the project

Every project moves through five phases. The lessons in this course follow the same order, so you learn each document at the moment a real PM would create it.

Three kinds of documents

At the top of every lesson you will see an Audience label. It tells you who is allowed to see the document:

Why this matters: A common beginner mistake is sending an internal document, such as the budget with our profit margin, to the client. Always check the audience before you share.

Who is who in this project

How to study each lesson

Every document lesson has the same layout, so you can read them quickly:

1. Phase and Audience: where the document sits in the project and who sees it.
2. Purpose: one line on why the document exists. Read this first.
3. Document details: document number, version, date and owner, as in a real company.
4. Numbered sections: the actual content, usually tables. This is what you would fill in on a real project.
5. Notes: short explanations that point out the learning or a common mistake.

While reading, ask yourself three questions: Who prepares this? Who approves it? What happens next because of it?

Placeholders: Items in square brackets, such as [Client Name] or [PO number], are placeholders. Replace them with real details when you use a document as a template.

Key terms you will meet

Do not worry about memorising these now. Come back to this list whenever a word is unfamiliar.

Course map

Study tip: Keep a notebook. For each lesson, write one line on why the document exists and one number or fact from it. By the end you will have your own interview cheat sheet.

Next lesson: Project Dashboard Overview, where you will see the whole project on one page.