This Is How I Stopped Chasing Project Status Updates For Good...
Without More Spreadsheets, Meetings, or Tools.
Most Technical Project Managers and Project Engineers are burdened with reporting admin that pulls them away from the important strategic work needed to lead complex projects.
The Project Leader Stop Chasing Updates Protocol is designed to eliminate follow-ups and make project updates happen, using your existing tools, without you chasing.
This Is How I Stopped Chasing Project Status Updates For Good...
Without More Spreadsheets, Meetings, or Tools.
Most Technical Project Managers and Project Engineers are burdened with reporting admin that pulls them away from the important strategic work needed to lead complex projects.
The Project Leader Stop Chasing Updates Protocol is designed to eliminate follow-ups and make project updates happen, using your existing tools, without you chasing.
Here's the Difference Between My Reporting Process and Yours
Your team is probably providing updates, just not consistently.
And that leaves you following up, sending 'just checking in...' reminders, and doing your best to piece together the information from multiple PM tools.
But, this isn't about finding a way to follow up more efficiently.
You just need to know what's missing from your current reporting process that's preventing your team from taking full ownership of the updates.
My strategy eliminates the need to follow up because of these five Reporting Ownership Principles (I definitely didn't know them in the beginning)... And once you follow them, your team will fully own the reporting process.
The Stop Chasing Updates Protocol shows you exactly how to stop chasing status updates by your next reporting cycle by implementing the five Reporting Ownership Principles... into your existing reporting workflow.
Have you been frustrated that some team members share updates, some forget, and some assume it's just not necessary... and then you're left coordinating it all?
I spent years stuck in that administrative chaos. I couldn't figure out why my role ended up becoming professional cat-herding. I tried templates, having regular status meetings, and even creating action logs... but nothing helped.
It took me a long time to figure out I was just missing these five Reporting Ownership Principles needed to stop my team from treating status updates as separate from their project deliverables.
Inside the Stop Chasing Updates Protocol is everything you need to make your project status reporting process happen consistently.
Imagine your next reporting cycle having all the information updated by your team in your reporting system without your intervention.
If you are spending hours chasing project updates, something in your process is quietly relying on you...
Your team needs you to make this one project leadership shift.
Once you know which Project Leader Reporting Ownership Principle is missing and how to fix it, you'll never have to ask "can you update the status on this deliverable?" again.
This Protocol Is For Project Leaders Who Are Ready To Reset Ownership of Project Status Updates For Good.
This is FOR you if:
- You lead complex, multi-discipline projects.
- You rely on other people for project status inputs.
- You are tired of sending reminders before every report.
- Your team uses tools, but updates still do not happen consistently.
- You want ownership behavior, not another reporting template.
This is NOT for you if:
- You manage short-term projects or a small team.
- You want a new software tool to add to your project tools suite.
- You are unwilling to reset expectations with your team.
- You want a new project status dashboard or template.
- You're not willing to make this one shift in how you lead your team.
What Happens After Implementing This Protocol
After this protocol, you'll install the five Project Leader Reporting Ownership Principles that make your team own their progress updates - not "I'll do it later", not "I'll just send you an email", but integrate project status updates as part of their scope of work.
And once you've integrated these into your workflow, this protocol will naturally replicate across all your reporting cycles... weekly, monthly, quarterly... saving you countless hours of status coordination.
You'll finally understand why some team members don't follow through, and how to flip that switch so updates are given consistently before the deadline.
No more chasing.
Just the project leadership principles that restore ownership of reporting where it belongs.
Fix this once, and save yourself countless hours and the frustration of piecing together progress reports.
This Protocol Comes From My Decade of Project Leadership Experience on Complex, Multi-Million Dollar Projects
I did not create this protocol from the outside looking in.
I created it from years of working inside complex project environments where the Project Leader often becomes the one chasing updates, filling reporting gaps, and manually piecing together status to keep leadership and clients informed.
I have seen firsthand how easily project reporting turns into a follow-up problem on the surface, when the real issue is about ownership behavior and accountability.
That is why the Stop Chasing Updates Protocol is designed to help you fix the pattern at the system level.
This is not generic productivity advice. It is not “communicate better” advice. And it is not built for simple project environments where status requires a few bullet points.
It is built for Project Leaders working on complex projects where visibility pressure is high and reporting easily ends up coordinated by the Project Leader.
Jennifer Glatz, P.Eng., PMP
Founder, Project Leadership Coach &
Certified Talent Optimization Consultant
This Frees Up Time In Your Workday Because These Project Leader Reporting Principles Activate OWNERSHIP Behavior
And that's what us Project Leaders want, isn't it?
Not holding everything together.
Not being the center point of information.
But having more time available in our workday for leading the project, not shuffling paper.
Adopting these reporting ownership principles shifted my role in the reporting process from manager to leader, and they will for you, too.
These five Project Leader Reporting Ownership Principles empower your team by giving them the things they need to be successful in integrating reporting in their workflow - not relying on you to be the single point of contact... sorry Spock. 🖖
And Just So You Know... This Protocol Is NOT Going To Tell You To:
❌ Have additional meetings about meetings ❌ Add more tools or software
❌ Follow up more ❌ Send more reminders ❌ Add more complexity
❌ Have additional meetings about meetings
❌ Add more tools or software
❌ Follow up more
❌ Send more reminders
❌ Add more complexity
You’re not asking your team to do more work. You’re making updates part of the work —so they happen without you having to coordinate them yourself.
It’s a lightweight protocol you can learn in under an hour, using the tools and structure you already have. And once it’s in place, the system - not you - drives the behavior.
STILL HAVE QUESTIONS?
Frequently Asked Questions
What exactly do I get when I purchase this?
You’ll get access to the Project Leader Stop Chasing Updates Protocol document, which helps you diagnose why you’re stuck chasing updates and identify where ownership is breaking down on your project.
You'll learn the 5 Project Leader Reporting Ownership Principles used in the diagnosis so you can reset expectations and stop chasing updates without adding more spreadsheets, meetings, or tools.
How long does it take to implement this?
Most Project Leaders start shifting ownership in their next reporting cycle.
Do I need new tools or software to make this work?
This is not another tool you have to manage. The Protocol works inside the tools you already use. There’s nothing new for your team to learn or adopt—just a clearer way to manage ownership so you can stop chasing updates.
Is this a training or something I can apply immediately?
This is designed for immediate application—not theory or generic training.
What kind of results should I expect?
Most Project Leaders see a reduction in follow-ups within the first reporting cycle.
As the protocol takes hold, you’ll spend less time chasing updates, your reports are built from what’s already in the system, and your team starts taking ownership of both their work AND their reporting.
At steady state, you’re no longer coordinating updates—your team consistently reports progress as part of their work, and you lead the project based on what’s already visible instead of chasing information.
Is this specific to a certain industry or type of project?
This works across industries—including construction, engineering, IT, operations, higher ed, etc.—because it focuses on ownership and reporting behavior, not technical workflows.
Whether you're managing trades, technical teams, or cross-functional stakeholders, the same issue of chasing status updates shows up—and this gives you a consistent way to solve it without changing how your project is structured.