The MSP SITREP: Progress, Plans & Problems

In the military, a SITREP, or Situation Report, gives leadership a concise picture of the current situation so they can understand what is happening and make decisions.

An IT Managed Service Provider can apply the same basic discipline.

Your weekly report should not be a list of every ticket you touched, every email you sent, or every Teams conversation you had.

Management needs the situation.

A simple way to provide it is the PPP SITREP:

Progress. Plans. Problems.

Three sections. A few bullets each. Useful information.

1. PROGRESS: What Did You Accomplish?

Report outcomes, not activity.

Your ticketing system already contains the details of individual tickets. Your SITREP should tell management what actually got accomplished.

Weak:

Worked on several Microsoft 365 issues this week.

Better:

Completed Microsoft 365 onboarding for ABC Manufacturing, including 28 users. Three endpoints remain pending because they are off-network.

Other examples:

Completed the firewall replacement for Client ABC.

Closed 22 service tickets; two were escalated to engineering.

Finished MDR deployment to all currently available customer endpoints.

Completed Microsoft 365 security review and documented remediation items.

Resolved recurring backup failures affecting a client's server.

Think:

What is different today because of the work I completed?

That's Progress.

2. PLANS: What's Next?

Plans tell management what you intend to accomplish during the next reporting period.

For an MSP, that might include:

Complete a client onboarding.

Deploy security agents to remaining endpoints.

Finish a Microsoft 365 configuration project.

Resolve an outstanding escalation.

Complete documentation.

Prepare for a customer's quarterly business review.

Perform scheduled vulnerability or compliance work.

Plans aren't simply a personal TODO list.

They communicate intent and priority.

That's important because your manager may look at your SITREP and say:

"Don't spend Thursday on that. The customer migration needs to come first."

That's a successful SITREP.

The team aligned priorities before spending the time.

Think:

What are my next objectives?

That's Plans.

3. PROBLEMS: What's Blocking the Mission?

This is potentially the most valuable part of the MSP SITREP.

Problems aren't necessarily failures.

They're roadblocks.

In an MSP those roadblocks could be:

Waiting for customer authorization.

Waiting for credentials or access.

Waiting for another technician.

Vendor support escalation.

Hardware that hasn't arrived.

Licensing issue.

Scope uncertainty.

Customer hasn't responded.

Technical problem requiring engineering assistance.

Multiple high-priority commitments competing for the same resource.

Don't hide these things.

Surface them early.

Instead of:

Still waiting on the customer.

Write:

Firewall deployment is blocked waiting for the customer to approve the maintenance window. Need confirmation by Wednesday to maintain Friday's planned deployment.

Now your manager knows four things:

Situation: Firewall deployment
Problem: No approved maintenance window
Impact: Friday deployment is at risk
Assistance required: Obtain customer approval by Wednesday

That's actionable information.

Report Problems Before They Become Emergencies

One of the worst outcomes in an MSP is discovering late Friday afternoon that something everyone assumed was progressing has actually been blocked since Tuesday.

A SITREP should expose that earlier.

There should be no penalty for identifying a legitimate problem.

In fact, employees should become comfortable saying:

"I'm blocked and this is what I need."

Management then has a responsibility too.

CLEAR THE ROAD.

Maybe the technician needs a decision.

Maybe sales needs to clarify scope.

Maybe the account manager needs to call the customer.

Maybe engineering needs to join the escalation.

Maybe another technician already knows the solution.

The employee's responsibility is to identify and communicate the obstacle clearly.

Management's responsibility is to help remove obstacles that the employee cannot remove alone.

The MSP SITREP Format

Keep it simple enough that people will actually use it.

SITREP: [Employee Name]
Reporting Period: [Date – Date]
PROGRESS
Accomplishment/result
Accomplishment/result
Accomplishment/result
Accomplishment/result
Accomplishment/result
PLANS
Next objective
Next objective
Next objective
Next objective
Next objective
PROBLEMS
Issue:
Impact:
Assistance Needed:
Issue:
Impact:
Assistance Needed:

No problems? Say "None."

That's useful information too.

A Realistic MSP Example

PROGRESS

Completed new-client Microsoft 365 onboarding for 24 users.

Finished deployment of endpoint security agents to 46 of 50 workstations.

Resolved recurring backup failure on the customer's file server.

Closed outstanding documentation items from last week's network upgrade.

PLANS

Deploy agents to the four remaining endpoints.

Complete Microsoft 365 security remediation.

Begin firewall replacement project.

Update customer network documentation.

PROBLEMS

Endpoint deployment: Four laptops have not connected this week. Assistance needed: Account manager to coordinate with the customer.

Firewall project: Maintenance window has not been approved. Impact: Friday deployment may need to move. Assistance needed: Customer approval by Wednesday.

That's a report a service manager can actually do something with.

Five Rules for a Good MSP SITREP

1. Keep it short.

Aim for 3 to 5 meaningful items per section.

Don't copy your ticket queue into the report.

2. Report outcomes, not effort.

"Spent four hours troubleshooting" tells me about effort.

"Identified the failed switch as the cause and scheduled replacement" tells me about progress.

3. Use numbers when they add meaning.

Instead of:

Deployed a bunch of agents.

Use:

Deployed agents to 46 of 50 endpoints; four remain offline.

4. Problems should identify what's needed.

Don't just report:

I'm stuck.

Report:

I'm blocked because ____. The impact is ____. I need ____.

5. No surprises.

If something threatens a customer commitment, security, service quality, or a deadline, don't wait for the weekly SITREP. Escalate it immediately.

The SITREP summarizes the situation. It should never become an excuse to delay an urgent escalation.

Use the SITREP to Run the Weekly 1:1

The employee should provide the SITREP before or at the beginning of the weekly meeting.

That changes the conversation.

Instead of:

"So...what did you work on this week?"

Start with:

What did you accomplish?

What are you accomplishing next?

What's standing in your way?

What do you need from me?

Now the 1:1 isn't merely a status meeting.

It's a decision and obstacle-removal meeting.

The Bottom Line

MSPs have plenty of data.

Tickets. Alerts. Timesheets. Project plans. Documentation. Security dashboards.

What management often needs isn't more data.

It needs a clear picture of the situation.

That's what the PPP SITREP provides:

PROGRESS: Here's what I accomplished.

PLANS: Here's what I'm doing next.

PROBLEMS: Here's what's standing in the way.

And there's a responsibility on both sides.

Employees: Report the situation.

Managers: Clear the road.

Everyone: Keep the mission moving.