Career skill · Pro
Project Management VA
Turn messy client requests into clear plans, predictable updates, and delivery teams that know what happens next.
In plain words
Project management is keeping everyone honest about who is doing what, by when — in Asana, ClickUp or Notion. This course teaches the setup and the gentle chasing that keeps clients renewing.
This is for you if
You’re the friend who plans the group trip. You like order and you’re comfortable nudging people.
You walk away with
A project board you can rebuild for any client, a 10-minute status update format, and chase scripts that don’t annoy.
Inside the work
What the job actually owns
A strong Project Management VA is not hired to make a tool look busy. Clients need someone who can own project intake, scope tracking, timeline planning, dependency mapping, notice a broken handoff, and turn ambiguity into a safe next step.
The useful promise is specific: you will build a small operating system around a commercial outcome, document what matters, and raise a risk before it becomes an apology.
Inside the work
The tools are not the skill
You will work in Asana, ClickUp, Notion, Slack, Google Workspace, Loom, and Airtable. Learn the workflow first, then the buttons. A client remembers whether the result was accurate and findable, not whether you knew every menu.
Keep account ownership with the client, use multi-factor authentication, and leave a short map of the systems you touch. Tool confidence without access discipline is expensive confidence.
The eight modules
0 of 8 done
Progress is saved in this browser only. Nothing is sent anywhere.
01
The PM job: clarity before control
Create a shared view of deliveryProPractice18 minCreate a shared view of delivery. This is the operating judgement behind the pm job: clarity before control, not a button-by-button tour.
Start with evidence from the actual account, not a tutorial-shaped assumption. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Name the owner, the decision, and the date before you add another tool. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A client pays for a reliable outcome, so make the path visible enough for someone else to review. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Keep the smallest useful record: what changed, why it changed, and how you checked it worked. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
When information is missing, state the assumption and ask the question that changes the next move. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use a realistic test case before declaring the work finished; a happy-path demonstration is not proof. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Make the trade-off explicit. Faster, cheaper, and more thorough are different promises, not moral qualities. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Good work is calm under pressure because the checklist was written before the pressure arrived. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Avoid turning a temporary workaround into an invisible permanent system; label it and schedule a review. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
The strongest update gives the reader a decision, a consequence, and a recommended next step. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Protect client access and customer information as part of the craft, even when the request feels routine. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A clean handoff note saves more trust than an impressive explanation delivered after something breaks. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use examples from the client’s world. Generic advice sounds polished but does not tell anyone what to do Monday. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
At the end of the week, compare the planned result with the observed result and adjust one variable at a time. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Start with evidence from the actual account, not a tutorial-shaped assumption. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Name the owner, the decision, and the date before you add another tool. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A client pays for a reliable outcome, so make the path visible enough for someone else to review. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Keep the smallest useful record: what changed, why it changed, and how you checked it worked. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
When information is missing, state the assumption and ask the question that changes the next move. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use a realistic test case before declaring the work finished; a happy-path demonstration is not proof. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Make the trade-off explicit. Faster, cheaper, and more thorough are different promises, not moral qualities. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Good work is calm under pressure because the checklist was written before the pressure arrived. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Avoid turning a temporary workaround into an invisible permanent system; label it and schedule a review. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
The strongest update gives the reader a decision, a consequence, and a recommended next step. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Protect client access and customer information as part of the craft, even when the request feels routine. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A clean handoff note saves more trust than an impressive explanation delivered after something breaks. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use examples from the client’s world. Generic advice sounds polished but does not tell anyone what to do Monday. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
At the end of the week, compare the planned result with the observed result and adjust one variable at a time. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Start with evidence from the actual account, not a tutorial-shaped assumption. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Name the owner, the decision, and the date before you add another tool. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A client pays for a reliable outcome, so make the path visible enough for someone else to review. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Keep the smallest useful record: what changed, why it changed, and how you checked it worked. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
When information is missing, state the assumption and ask the question that changes the next move. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use a realistic test case before declaring the work finished; a happy-path demonstration is not proof. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Make the trade-off explicit. Faster, cheaper, and more thorough are different promises, not moral qualities. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Good work is calm under pressure because the checklist was written before the pressure arrived. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Avoid turning a temporary workaround into an invisible permanent system; label it and schedule a review. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
The strongest update gives the reader a decision, a consequence, and a recommended next step. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Protect client access and customer information as part of the craft, even when the request feels routine. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A clean handoff note saves more trust than an impressive explanation delivered after something breaks. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use examples from the client’s world. Generic advice sounds polished but does not tell anyone what to do Monday. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
At the end of the week, compare the planned result with the observed result and adjust one variable at a time. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Start with evidence from the actual account, not a tutorial-shaped assumption. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Name the owner, the decision, and the date before you add another tool. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A client pays for a reliable outcome, so make the path visible enough for someone else to review. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Keep the smallest useful record: what changed, why it changed, and how you checked it worked. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
When information is missing, state the assumption and ask the question that changes the next move. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use a realistic test case before declaring the work finished; a happy-path demonstration is not proof. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Make the trade-off explicit. Faster, cheaper, and more thorough are different promises, not moral qualities. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Good work is calm under pressure because the checklist was written before the pressure arrived. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Avoid turning a temporary workaround into an invisible permanent system; label it and schedule a review. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
The strongest update gives the reader a decision, a consequence, and a recommended next step. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Protect client access and customer information as part of the craft, even when the request feels routine. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A clean handoff note saves more trust than an impressive explanation delivered after something breaks. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use examples from the client’s world. Generic advice sounds polished but does not tell anyone what to do Monday. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
At the end of the week, compare the planned result with the observed result and adjust one variable at a time. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Start with evidence from the actual account, not a tutorial-shaped assumption. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Name the owner, the decision, and the date before you add another tool. In project management work, this module is about translate a vague request into outcomes and constraints. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A client pays for a reliable outcome, so make the path visible enough for someone else to review. In project management work, this module is about name decision-makers without inventing authority. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Keep the smallest useful record: what changed, why it changed, and how you checked it worked. In project management work, this module is about make work visible without turning every task into bureaucracy. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Worked example
A client asks for help late on Thursday. Instead of saying yes to a vague request, you restate the outcome for The PM job: clarity before control, identify the missing input, and propose a small first deliverable. The next morning the client can see what moved, what still depends on them, and why the plan protects the deadline.
Do this
- Translate a vague request into outcomes and constraints.
- Name decision-makers without inventing authority.
- Make work visible without turning every task into bureaucracy.
02
Scoping work that can survive review
Define what done meansProPractice19 minDefine what done means. This is the operating judgement behind scoping work that can survive review, not a button-by-button tour.
Start with evidence from the actual account, not a tutorial-shaped assumption. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Name the owner, the decision, and the date before you add another tool. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A client pays for a reliable outcome, so make the path visible enough for someone else to review. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Keep the smallest useful record: what changed, why it changed, and how you checked it worked. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
When information is missing, state the assumption and ask the question that changes the next move. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use a realistic test case before declaring the work finished; a happy-path demonstration is not proof. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Make the trade-off explicit. Faster, cheaper, and more thorough are different promises, not moral qualities. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Good work is calm under pressure because the checklist was written before the pressure arrived. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Avoid turning a temporary workaround into an invisible permanent system; label it and schedule a review. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
The strongest update gives the reader a decision, a consequence, and a recommended next step. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Protect client access and customer information as part of the craft, even when the request feels routine. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A clean handoff note saves more trust than an impressive explanation delivered after something breaks. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use examples from the client’s world. Generic advice sounds polished but does not tell anyone what to do Monday. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
At the end of the week, compare the planned result with the observed result and adjust one variable at a time. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Start with evidence from the actual account, not a tutorial-shaped assumption. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Name the owner, the decision, and the date before you add another tool. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A client pays for a reliable outcome, so make the path visible enough for someone else to review. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Keep the smallest useful record: what changed, why it changed, and how you checked it worked. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
When information is missing, state the assumption and ask the question that changes the next move. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use a realistic test case before declaring the work finished; a happy-path demonstration is not proof. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Make the trade-off explicit. Faster, cheaper, and more thorough are different promises, not moral qualities. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Good work is calm under pressure because the checklist was written before the pressure arrived. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Avoid turning a temporary workaround into an invisible permanent system; label it and schedule a review. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
The strongest update gives the reader a decision, a consequence, and a recommended next step. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Protect client access and customer information as part of the craft, even when the request feels routine. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A clean handoff note saves more trust than an impressive explanation delivered after something breaks. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use examples from the client’s world. Generic advice sounds polished but does not tell anyone what to do Monday. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
At the end of the week, compare the planned result with the observed result and adjust one variable at a time. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Start with evidence from the actual account, not a tutorial-shaped assumption. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Name the owner, the decision, and the date before you add another tool. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A client pays for a reliable outcome, so make the path visible enough for someone else to review. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Keep the smallest useful record: what changed, why it changed, and how you checked it worked. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
When information is missing, state the assumption and ask the question that changes the next move. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use a realistic test case before declaring the work finished; a happy-path demonstration is not proof. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Make the trade-off explicit. Faster, cheaper, and more thorough are different promises, not moral qualities. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Good work is calm under pressure because the checklist was written before the pressure arrived. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Avoid turning a temporary workaround into an invisible permanent system; label it and schedule a review. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
The strongest update gives the reader a decision, a consequence, and a recommended next step. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Protect client access and customer information as part of the craft, even when the request feels routine. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A clean handoff note saves more trust than an impressive explanation delivered after something breaks. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use examples from the client’s world. Generic advice sounds polished but does not tell anyone what to do Monday. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
At the end of the week, compare the planned result with the observed result and adjust one variable at a time. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Start with evidence from the actual account, not a tutorial-shaped assumption. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Name the owner, the decision, and the date before you add another tool. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A client pays for a reliable outcome, so make the path visible enough for someone else to review. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Keep the smallest useful record: what changed, why it changed, and how you checked it worked. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
When information is missing, state the assumption and ask the question that changes the next move. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use a realistic test case before declaring the work finished; a happy-path demonstration is not proof. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Make the trade-off explicit. Faster, cheaper, and more thorough are different promises, not moral qualities. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Good work is calm under pressure because the checklist was written before the pressure arrived. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Avoid turning a temporary workaround into an invisible permanent system; label it and schedule a review. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
The strongest update gives the reader a decision, a consequence, and a recommended next step. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Protect client access and customer information as part of the craft, even when the request feels routine. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A clean handoff note saves more trust than an impressive explanation delivered after something breaks. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use examples from the client’s world. Generic advice sounds polished but does not tell anyone what to do Monday. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
At the end of the week, compare the planned result with the observed result and adjust one variable at a time. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Start with evidence from the actual account, not a tutorial-shaped assumption. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Name the owner, the decision, and the date before you add another tool. In project management work, this module is about write acceptance criteria a client can verify. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A client pays for a reliable outcome, so make the path visible enough for someone else to review. In project management work, this module is about capture assets, access, and approvals as dependencies. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Keep the smallest useful record: what changed, why it changed, and how you checked it worked. In project management work, this module is about separate a change request from the original promise. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Worked example
A client asks for help late on Thursday. Instead of saying yes to a vague request, you restate the outcome for Scoping work that can survive review, identify the missing input, and propose a small first deliverable. The next morning the client can see what moved, what still depends on them, and why the plan protects the deadline.
Do this
- Write acceptance criteria a client can verify.
- Capture assets, access, and approvals as dependencies.
- Separate a change request from the original promise.
03
Building schedules from real capacity
Plan dates people can useProPractice20 minPlan dates people can use. This is the operating judgement behind building schedules from real capacity, not a button-by-button tour.
Start with evidence from the actual account, not a tutorial-shaped assumption. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Name the owner, the decision, and the date before you add another tool. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A client pays for a reliable outcome, so make the path visible enough for someone else to review. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Keep the smallest useful record: what changed, why it changed, and how you checked it worked. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
When information is missing, state the assumption and ask the question that changes the next move. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use a realistic test case before declaring the work finished; a happy-path demonstration is not proof. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Make the trade-off explicit. Faster, cheaper, and more thorough are different promises, not moral qualities. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Good work is calm under pressure because the checklist was written before the pressure arrived. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Avoid turning a temporary workaround into an invisible permanent system; label it and schedule a review. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
The strongest update gives the reader a decision, a consequence, and a recommended next step. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Protect client access and customer information as part of the craft, even when the request feels routine. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A clean handoff note saves more trust than an impressive explanation delivered after something breaks. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use examples from the client’s world. Generic advice sounds polished but does not tell anyone what to do Monday. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
At the end of the week, compare the planned result with the observed result and adjust one variable at a time. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Start with evidence from the actual account, not a tutorial-shaped assumption. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Name the owner, the decision, and the date before you add another tool. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A client pays for a reliable outcome, so make the path visible enough for someone else to review. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Keep the smallest useful record: what changed, why it changed, and how you checked it worked. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
When information is missing, state the assumption and ask the question that changes the next move. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use a realistic test case before declaring the work finished; a happy-path demonstration is not proof. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Make the trade-off explicit. Faster, cheaper, and more thorough are different promises, not moral qualities. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Good work is calm under pressure because the checklist was written before the pressure arrived. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Avoid turning a temporary workaround into an invisible permanent system; label it and schedule a review. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
The strongest update gives the reader a decision, a consequence, and a recommended next step. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Protect client access and customer information as part of the craft, even when the request feels routine. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A clean handoff note saves more trust than an impressive explanation delivered after something breaks. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use examples from the client’s world. Generic advice sounds polished but does not tell anyone what to do Monday. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
At the end of the week, compare the planned result with the observed result and adjust one variable at a time. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Start with evidence from the actual account, not a tutorial-shaped assumption. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Name the owner, the decision, and the date before you add another tool. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A client pays for a reliable outcome, so make the path visible enough for someone else to review. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Keep the smallest useful record: what changed, why it changed, and how you checked it worked. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
When information is missing, state the assumption and ask the question that changes the next move. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use a realistic test case before declaring the work finished; a happy-path demonstration is not proof. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Make the trade-off explicit. Faster, cheaper, and more thorough are different promises, not moral qualities. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Good work is calm under pressure because the checklist was written before the pressure arrived. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Avoid turning a temporary workaround into an invisible permanent system; label it and schedule a review. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
The strongest update gives the reader a decision, a consequence, and a recommended next step. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Protect client access and customer information as part of the craft, even when the request feels routine. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A clean handoff note saves more trust than an impressive explanation delivered after something breaks. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use examples from the client’s world. Generic advice sounds polished but does not tell anyone what to do Monday. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
At the end of the week, compare the planned result with the observed result and adjust one variable at a time. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Start with evidence from the actual account, not a tutorial-shaped assumption. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Name the owner, the decision, and the date before you add another tool. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A client pays for a reliable outcome, so make the path visible enough for someone else to review. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Keep the smallest useful record: what changed, why it changed, and how you checked it worked. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
When information is missing, state the assumption and ask the question that changes the next move. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use a realistic test case before declaring the work finished; a happy-path demonstration is not proof. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Make the trade-off explicit. Faster, cheaper, and more thorough are different promises, not moral qualities. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Good work is calm under pressure because the checklist was written before the pressure arrived. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Avoid turning a temporary workaround into an invisible permanent system; label it and schedule a review. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
The strongest update gives the reader a decision, a consequence, and a recommended next step. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Protect client access and customer information as part of the craft, even when the request feels routine. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A clean handoff note saves more trust than an impressive explanation delivered after something breaks. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Use examples from the client’s world. Generic advice sounds polished but does not tell anyone what to do Monday. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
At the end of the week, compare the planned result with the observed result and adjust one variable at a time. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Start with evidence from the actual account, not a tutorial-shaped assumption. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Name the owner, the decision, and the date before you add another tool. In project management work, this module is about break deliverables into handoffs and review time. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
A client pays for a reliable outcome, so make the path visible enough for someone else to review. In project management work, this module is about estimate uncertainty honestly. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Keep the smallest useful record: what changed, why it changed, and how you checked it worked. In project management work, this module is about show the critical path without using false precision. Treat it as a repeatable decision: record the context, choose the next action, and leave evidence for the person who follows you.
Worked example
A client asks for help late on Thursday. Instead of saying yes to a vague request, you restate the outcome for Building schedules from real capacity, identify the missing input, and propose a small first deliverable. The next morning the client can see what moved, what still depends on them, and why the plan protects the deadline.
Do this
- Break deliverables into handoffs and review time.
- Estimate uncertainty honestly.
- Show the critical path without using false precision.
The rest of this course unlocks with Pro
5 more modules, the worked examples, the rate tables and every copy-paste template. Pro is ₱199 for 30 days and covers all 18 premium courses.