Here is how most projects go wrong. Nothing dramatic happens. A supplier says "end of the week" and the week ends. Someone waits on an answer from a client and doesn't mention it, because it seems too small to raise. A task that was meant to take two days is on day six, and the person doing it is sure they'll finish tomorrow. Everything else on the board keeps moving, so the board looks fine.
Three weeks later the client asks where things are, and the honest answer is "late, and we've known for a while, we just hadn't said it."
Stopping that slow slide is most of what a project manager is for. This post covers what a project manager does day to day, what a project manager job description usually asks for, how the job differs from a project coordinator and a program manager, and a RAID log you can copy and use this week. Near the end it covers which parts of the job an AI project manager can take on. We make Sanaf, an AI employee that can hold that job, so we have an interest in that section. Everything before it stands on its own.
The short answer
A project manager is the person responsible for getting a piece of work finished on time, within budget and to the agreed scope. They turn a goal into a plan, break the plan into tasks with owners and dates, track progress against it, deal with risks and blockers, keep everyone who cares about the project informed, and raise the hard choices early when the plan stops matching reality. They usually don't do the work itself. They make sure the work gets done and that nobody is surprised by how it is going.
What does a project manager do, week by week?
Project management guides describe the job in five phases: initiating, planning, executing, monitoring and closing. That's accurate, but it isn't what a project manager's calendar looks like. It's easier to see the job as the handful of things that fill an ordinary week.
1. Turning a goal into a plan
Somebody says "we need the new website live before the spring campaign" or "the Hendricks kitchen needs to be finished by the 14th." That's a goal. It's not yet a plan.
The project manager works backwards from it. What has to be true for the goal to count as done? What are the pieces of work? Which pieces depend on others? Copy can't be loaded until the pages are built, and cabinets can't go in until the floor is down. Those links are the project dependencies, and they matter more than any single task, because a delay on a task that other tasks are waiting for moves everything behind it.
From there come the project milestones: a handful of dates that mean something to the people paying for the work. Design signed off. First fix done. Site in review. A plan with forty tasks and no milestones is hard to talk about. A plan with five milestones is easy to explain to a client in one sentence.
On bigger projects this step gets formal names, like a work breakdown structure for the list of pieces and a critical path for the chain of dependent tasks that sets the finish date. On most projects it's a list, an order and some dates, and that's enough.
2. Getting everyone moving
A project kickoff meeting is where the plan stops being one person's document. Everyone involved hears the goal, the milestones, who owns what, how updates will happen and what counts as done. It doesn't need to be long. Its main job is to make sure every task has a name next to it and every name knows it's there.
Ownership is where many projects quietly fail. "The team" can't own a task. "Whoever's free" can't own a task. A good project manager is slightly annoying about this and keeps asking "who has this one?" until each line has one name.
3. Tracking progress against the plan
This is the bulk of the job and the least glamorous part. Every day or two, the project manager compares the plan to what's actually happening. Which tasks finished? Which ones started late? Which ones haven't moved at all?
The tasks that haven't moved matter most. A finished task is easy to see. A task that's late but active is easy to see too. A task that stopped moving five days ago, with no update, is invisible unless someone goes looking. Project tracking is mostly the habit of going looking.
The information is almost never in one place. Some is in the project tool. Some is in a chat thread. Some is in an email from a supplier. Some only exists in someone's head until you ask them. Collecting it is a real job, and it's the first thing to get skipped in a busy week, which is exactly the week it's needed.
4. Managing risks, issues and dependencies
A risk is something that might go wrong. An issue is something that already has. The project manager keeps a list of both, decides which ones need attention now, and makes sure each has an owner and a next step.
The classic tool is a risk register, or the broader RAID log (risks, assumptions, issues, dependencies), which has a template further down. You don't need a formal process to get value from one. Writing "the tile supplier has been late twice this year" down on day one, and checking it weekly, is the difference between ordering early and finding out on the morning of the install.
5. Keeping people informed
Clients, owners, managers and the people doing the work all want to know how the project is going. They want different levels of detail. The owner wants three lines. The person doing the next task wants to know whether the task before theirs is finished.
So the project manager writes the update. Usually that's a weekly project status report with a short summary, what got done, what's next, what's late and what needs a decision. Many teams add a RAG status: red, amber or green for the whole project, or for each milestone. Green means on track. Amber means at risk but recoverable. Red means the date, budget or scope won't hold without a decision. RAG is useful because it forces a judgment. It stops being useful the day amber turns into the colour everything is so nobody has to say red.
We covered the status update in more depth, with a template you can copy, in AI in project management for teams without a project manager.
6. Handling change
Every project changes. The client wants an extra page. A material becomes unavailable. A new requirement turns up halfway through. Unmanaged, this turns into scope creep: the project slowly grows while the date and the budget stay the same, until something breaks.
The project manager's job is to make change visible. That's what a change request is: a short note saying what's being added or changed, what it does to the date and cost, and who has agreed to it. It sounds bureaucratic. In practice it's one message: "Adding the booking page pushes launch from the 3rd to the 10th. OK to proceed?" Asking that question out loud protects everyone.
7. Closing the project
When the work is done, a project manager confirms it's actually done, gets sign-off, hands over whatever needs handing over and closes the loose ends. Then comes the part most teams skip: lessons learned. A short project retrospective asks what went well, what didn't, and what to do differently next time. Write the answers somewhere the next project will actually see them. A lessons learned file nobody opens is a diary.
What a project manager job description usually asks for
If you're writing a project manager job description, or reading one, the duties usually come down to the same list:
- Defining project scope, goals and deliverables with the client or sponsor.
- Building the project plan, timeline and milestones.
- Assigning tasks and agreeing owners and dates.
- Tracking progress, budget and resources against the plan.
- Identifying and managing risks, issues and dependencies.
- Running the kickoff, regular check-ins and the closing review.
- Writing status reports for clients, owners and the team.
- Managing change requests and keeping scope under control.
- Raising problems early, with options, to whoever has to decide.
The project manager skills that show up most often are organisation, clear writing, comfort with a project tool and a spreadsheet, the confidence to give bad news early, and the ability to get an answer out of a busy person without souring the relationship. Certifications appear in some job ads, especially in larger companies and regulated industries. In most businesses a record of finished projects counts for more.
A useful line to add to any job description: who makes the final call when the plan and reality disagree. If that isn't written down, the project manager either ends up making decisions they shouldn't, or waiting for decisions nobody knows they're meant to make.
Project coordinator vs project manager
The two titles get used interchangeably, but they describe different jobs, and the difference matters if you're deciding what kind of help you need.
A project manager owns the outcome. They make the plan, make trade-offs inside their authority, and answer for whether the project lands.
A project coordinator supports the project. So what does a project coordinator do? They keep the task list current, schedule meetings, chase updates, collect documents, track deadlines, keep notes, and prepare the status report for the manager or the client. It's the administrative spine of the project. Coordinators often grow into project managers, and on small projects one person does both.
| Project coordinator | Project manager | |
|---|---|---|
| Owns | The tracking and the paperwork | The plan and the outcome |
| Typical work | Updating tasks, chasing owners, scheduling, notes, status drafts | Planning, trade-offs, risk calls, client conversations |
| Decides | Very little; flags and escalates | Scope, sequence and priorities within their authority |
| When it's missing | Updates stop and nobody knows where things are | Nobody makes the call when the plan breaks |
This split is the most useful way to think about an AI project manager, too. Most of what an AI does well is coordinator work. The manager's half, the judgment and the accountability, should stay with a person.
Project manager vs program manager
A program manager looks after several related projects that together serve one larger goal. Think of a company opening three new locations, where each opening is its own project. The program manager watches how the projects affect each other, shares people and budget across them, and reports on the whole. A project manager runs one of those openings.
In most businesses this distinction never comes up. If you have more than three or four projects running at once and they keep competing for the same people, you're doing program management whether or not anyone has the title.
A RAID log you can copy
A RAID log is one table, reviewed weekly. Keep it short. Ten live rows is plenty for most projects. Close rows when they no longer matter, rather than letting the list grow forever. The rows below are made-up examples from a remodel and a website build, so swap in your own.
| Type | What | Impact if it happens | Owner | Next step | Review by |
|---|---|---|---|---|---|
| Risk | Tile supplier has been late twice this year | Install slips, plumber has to be rebooked | Ops lead | Place order this week, not next | Friday |
| Assumption | Client signs off designs within 3 days | Build start moves with every extra day | Project manager | Confirm turnaround in writing at kickoff | Kickoff |
| Issue | Staging site login broken since Tuesday | Client review can't start | Web developer | Fix or share screenshots instead | Tomorrow |
| Dependency | Copy from client before pages can be finished | Launch date at risk | Client contact | Send reminder with the date it's needed | Wednesday |
Four habits make it work:
- Every row has one owner, a named person.
- Every row has a next step that's an action, not a worry.
- The review date is real. If it passes and nothing happened, the row goes into the status report.
- Anything red goes to whoever decides, the same day it turns red.
You'll see risk register and RAID log used for the same thing. A risk register usually holds only risks, with likelihood and impact scores. For most teams the RAID table above is more useful, because the thing that sinks a project is usually a dependency or an unspoken assumption rather than a classic risk.
The project manager most teams don't have
Most businesses that run projects don't employ a project manager. They have an owner who keeps the dates in their head, a lead who updates the board when someone asks, and a client who occasionally finds out about a delay before the team does.
That setup works until it doesn't. It usually breaks in the same three places:
- Status updates only happen when somebody chases for one.
- The task list goes stale within a week of being written.
- A project slips and nobody notices until the client asks.
None of those failures is about judgment. They're about the coordinator half of the job: someone checking the plan against reality every day, chasing the quiet tasks, and writing it down. That's the half that disappears first when the people who'd normally do it are busy doing the actual work.
What is an AI project manager?
An AI project manager is software that takes on the recurring, administrative half of project management. It builds and updates the plan, tracks deadlines across the tools where the work happens, follows up on tasks that have stopped moving, spots delays early and writes the status update. The decisions stay with a person: changing scope, moving a client date or pulling someone off a job.
Search for AI project manager tools and you'll find three quite different things under the same label:
- AI features inside a project tool. Summaries of a board, suggested subtasks, a chat box that answers "what's overdue?" Useful if everyone already keeps the tool current. They can only see what's in the tool.
- A general chat assistant. You paste in notes and ask for a plan or a status report. Good for a first draft. It knows nothing about your project beyond what you paste, and it only works when you remember to ask.
- An AI employee holding the project job. Something that works across your project tool, calendar, email and team chat on a schedule, follows up with people, and posts the update whether or not anyone remembered to ask for it.
The third kind is the one that fixes the "nobody looks" problem, because the checking happens anyway.
What it should do
The coordinator half of the job fits an AI well. A good one can:
- Draft a project plan from the goal and the pieces of work you describe, with dependencies and milestones.
- Keep the task list in step with what's actually happening in your project tool, email and chat.
- Notice tasks that have stopped moving and ask their owners, politely and on a rhythm you set.
- Compare the plan to reality every day and say which dates no longer look realistic.
- Keep the RAID log current and flag anything that turns red.
- Write the weekly project status report and post it where the team already reads.
What it should leave alone
The manager half should stay with people, and a well-built AI makes that easy:
- It raises the risk and stops there. Rescoping, moving a client date or changing who works on what is a person's call.
- It doesn't quietly move dates. If a date no longer works, it says so and asks.
- It says when it's guessing. "No update on this task for six days" is a fact. "This task is probably fine" isn't, and it shouldn't say it.
- It doesn't speak for you to the client about changes unless you've approved the message.
Can AI be a project manager?
It can do a lot of the work, and in a team with no project manager at all it can cover most of what's missing day to day. It can't be accountable for the outcome. Deciding what to cut when a project is late, handling an unhappy client and knowing which of two slipping tasks actually matters are judgment calls. They need someone who answers for the result. For a team that already has a good project manager, an AI that takes over the chasing and the status writing frees them for the part of the job only they can do.
How to start managing a project properly this week
Whether or not you ever use an AI for it, these steps take an afternoon and make most projects calmer:
- Write the goal in one sentence, with a date.
- List the five to eight milestones that matter to the client or owner.
- Under each milestone, list the tasks, and put one name and one date on each.
- Mark which tasks wait on others. Those are your dependencies, so watch them hardest.
- Start the RAID log with three rows: the riskiest supplier, the biggest assumption and the slowest dependency.
- Pick a status day. Same day, same format, every week, even when nothing much changed.
- Agree who decides when the plan breaks, and write that name at the top of the plan.
Whoever ends up running the project, a person, a coordinator or an AI, will do a much better job with step 7 written down.
Where Sanaf fits
Sanaf is an AI employee. It works in your team's Slack or Microsoft Teams and inside the apps you connect. Project management is one of the jobs it can take on, and the AI project manager page sets out exactly what that job covers. The AI employee roster shows the others.
In practice it does the coordinator half described above. It creates project plans, tracks deadlines, assigns tasks, monitors progress, identifies delayed tasks and sends status updates. It works in Asana, Trello, Google Calendar and Gmail, and only in the ones you connect. You can ask in a sentence, like "post a status update in the projects channel every Friday at 3, and tell me the same day any task goes five days without moving", and it happens in the same channel.
The limits are the ones listed earlier. It raises the risk and a person makes the call. Rescoping, moving a client date or pulling someone off a job is always a person's decision. Anything it can't undo asks first, and each job leaves a work log the team can read. If projects keep stalling because nobody is chasing suppliers, that's a separate job, covered on the AI procurement page. If the bigger problem is meetings and dates rather than tasks, the best AI scheduling assistant post covers that. And if project work is one job among several, the AI chief of staff post explains how Sanaf hands work to agents that report to it.
On price, you start with $120 of free credit and no card, and that free credit lasts 30 days. After that you buy credits from $20 when you need them, and credit you buy never expires. You pay for the work, not per seat. The pricing page has the details, and hiring an AI employee shows what the first day looks like.
A good first test: connect the project tool you already use, point Sanaf at one live project, and ask for this week's status update and a list of tasks that haven't moved in five days. Then check it against what you already know.
Questions people ask about project managers
What does a project manager do?
A project manager is responsible for getting a project finished on time, within budget and to the agreed scope. They build the plan, assign tasks with owners and dates, track progress, manage risks, issues and dependencies, keep clients and the team informed with status reports, control changes to scope, and raise problems early to whoever has to decide.
What are a project manager's main responsibilities?
The main project manager responsibilities are defining scope and goals, building the plan and timeline, assigning tasks, tracking progress and budget, managing risks and dependencies, running kickoff and review meetings, writing status reports, handling change requests and closing the project with a lessons learned review.
What does a project coordinator do?
A project coordinator supports a project manager or a project team. They keep the task list current, chase updates from task owners, schedule meetings, keep notes and documents in order, track deadlines and prepare status reports. They flag problems to the project manager rather than deciding how to fix them.
What is the difference between a project coordinator and a project manager?
A project manager owns the plan and the outcome and makes trade-offs within their authority. A project coordinator owns the tracking and the administration that keep the project visible. On small projects one person often does both.
What is the difference between a project manager and a program manager?
A project manager runs one project with a defined end. A program manager oversees several related projects that serve one larger goal, and manages how they share people, budget and timing.
What is a RAID log?
A RAID log is a table that tracks a project's risks, assumptions, issues and dependencies. Each row has an owner, a next step and a review date. Teams review it weekly and escalate anything that turns red.
What does RAG status mean in project management?
RAG status rates a project or milestone as red, amber or green. Green means on track, amber means at risk but recoverable, and red means the date, budget or scope won't hold without a decision.
What is scope creep?
Scope creep is when a project's work grows after it starts, without the date or budget changing to match. It's controlled by writing each change down as a change request that states its effect on time and cost and who approved it.
What is an AI project manager?
An AI project manager is software that takes on the administrative half of project management: drafting the plan, tracking deadlines, following up on stalled tasks, spotting delays and writing status updates. Decisions such as rescoping or moving a client date stay with a person.
Will AI replace project managers?
AI is good at the coordination half of the job: tracking, chasing and reporting. It isn't accountable for the outcome, so the judgment calls stay with people. For teams without a project manager, the realistic change is that the tracking finally happens every day.