How to Write a Project Plan When You've Never Done It Before

You've been handed a task. Someone — your boss, a client, a partner — said: "Put together a project plan." And now you're sitting in front of a blank page, wondering: where do I even begin?

That feeling is completely normal. Most people who write project plans today never learned how to do it in any formal training. They simply started doing it — and learned along the way. This guide is here to make your journey a little shorter and a little less painful.

What is a project plan and why do you need one?

A project plan is not a magical document that solves every problem. It is an agreement with yourself (and with everyone involved in the project): what we're going to do, who does it, when, and on what budget.

Without a plan, one of two things happens: either everyone assumes someone else is handling the important things, or you reach the end of the project and discover you've built something completely different from what was originally intended.

A good project plan doesn't have to be long or complicated. It has to be an honest, concrete, living document — not something you finish and forget in a drawer.

7 steps to writing your first project plan

Step 1: Write down what you're actually doing

The very first and most important question is: what is the goal of the project?

Don't write: "We're developing our company's digital presence." Write: "We're building a website for the company that will be ready by September 1st and that the client can update with content themselves."

A good goal is specific, measurable and time-bound. If you can't describe the project's goal in a single sentence, the goal isn't clear enough yet — and that's a sign you should work on the goal a bit more before writing the plan.

Step 2: Who's involved and who does what?

List everyone who comes into contact with the project in any way:

• Project manager — holds the threads together, tracks the schedule and clears obstacles
• Team members — do the substantive work
• Decision-makers — approve the results of the work (often the person who commissioned the project)
• External parties — partners, suppliers, clients

Write down who is responsible for what. Vague roles are one of the most common reasons projects fall apart.

Step 3: Break the project into tasks

A big goal feels overwhelming. Small, concrete tasks are achievable.

Ask yourself: what actually needs to get done in order to reach the goal? Write down all the activities — no matter how small. Then group similar activities together and assign each task:

• An owner (one person, not "the team")
• A deadline
• An estimated time cost

Don't worry if the list gets long. An overly detailed plan is better than one where big chunks of work are hidden behind a single line.

Step 4: Build a schedule

Once the tasks are written down, draw the lines between them: what has to be finished before the next thing can start?

For a simple project, a table is enough: task — owner — start date — end date. For a more complex project, a Gantt chart is useful — a visual timeline that shows how tasks overlap or follow one another.

One piece of advice that beginners often ignore: leave buffer time in the schedule. Things always take longer than you thought. Plan for it instead of crying about it later.

Step 5: Estimate the budget

Even if you don't have an official budget, write down:

• People's time cost (in hours or days)
• External costs (tools, services, materials)
• A buffer for unexpected costs (recommendation: at least 10–15%)

The budget doesn't have to be accurate down to the cent. But it has to exist — otherwise there's no way to assess later whether the project went according to plan.

Step 6: Think through the risks

Ask yourself: what could go wrong? This isn't pessimism — it's professionalism.

Some common risks:

• A key person gets sick or leaves
• A supplier fails to deliver on time
• Requirements change mid-project
• The technical solution turns out to be more complex than you thought

For each risk, write down how likely it is to happen and what you'll do if it does. You don't have to foresee everything — but thinking through the risks helps you react faster mid-project.

Step 7: Find a system for following through

A project plan is useless if you make it once and put it in a drawer. Decide how you will:

• Track task progress (a weekly review?)
• Record decisions (who decided what and when?)
• Communicate with the team (meetings, comments, notifications?)

Common mistakes beginners make

"The plan is in my head, no need to write it down."

A plan in your head isn't a plan — it's an intention. If the project involves more than one person and lasts longer than a week, always write it down.

"Let's get it done first, then see what it cost."

The budget and schedule need to be set before you start. Tracking during the project shows whether you're on the right path.

"Risks — things like that don't happen to us."

They do happen. Always. The only question is when, and with how much impact.

How Projektiassistent makes all of this easier

This is where a tool comes into play that was built for exactly the kind of person you are — someone who has never put together a project plan before, but has to do it well and fast.

Projektiassistent is an innovative Estonian project management platform that walks you through the entire process step by step. You don't need to know project management jargon or decide whether you need Scrum or the Waterfall method — the system asks you for the project's goal, type and timeframe, and generates a structured project plan with the help of artificial intelligence in minutes.

Take a look at how Projektiassistent solves exactly the steps we just talked about:

What does this mean in practice? You don't have to start with a blank page. Describe the project idea, choose the project type (IT development, event, consulting, construction, etc.) and Projektiassistent creates a working plan you can start using right away — tasks, phases, risks and roles included.

Meeting notes? It helps with those too.

One thing beginners often struggle with: something was agreed in a meeting, but nobody wrote down who's supposed to do what. Projektiassistent's meeting notes processing feature solves this: upload your meeting notes and the AI automatically extracts the tasks, decisions and owners — adding them straight into the project with one click.

And a bad decision won't slip through.

Projektiassistent's unique stop check means the system won't let you formally approve a project if important prerequisites aren't met — regulatory requirements, budget alignment, missing owners. For a beginner, it's like a mentor who says: "Wait, you forgot about this."

In summary: you've got this

A project plan is not a work of art. It's a working document — and like all working documents, it gets better over time.

Start simple: write down the goal, break it into tasks, assign owners and deadlines. That's a project plan. Everything else — risk management, budget tracking, the decision log — comes on top as the project grows.

And if you'd like someone (or something) to guide you through this process, try Projektiassistent — the first 14 days are free, and that's enough time to get your first professional plan done.