Monthly Progress Report Template (Copy-Paste + Example)

A monthly progress report tells a manager or client what moved forward, what remains unfinished, and which decisions are needed next.

The most useful version compares the month’s plan with actual results. It distinguishes work you completed from work awaiting approval, explains meaningful changes, and gives the reader clear next steps.

Copy the template below, replace the placeholders, and remove any section that does not apply. A fictional example follows.

Copy-paste Monthly Progress Report Template

Monthly Progress Report

Project or work area: [Name]

Reporting period: [Start date] to [End date]

Prepared by: [Name and role]

Prepared on: [Date]

Overall status: [On track / At risk / Blocked]

1. Executive summary

[Write 3-5 sentences covering the most important result, progress against the plan, the main unresolved issue, and the next priority.]

Decision or action needed: [What you need, from whom, and by when. Write “None” if no action is needed.]

2. Planned work versus actual progress

Priority 1: [Name]

• Planned: [What was supposed to happen this month.]
• Actual: [What was completed or delivered.]
• Approval or acceptance: [Approved / Awaiting approval / Not applicable.]
• Evidence: [File, task record, test result, or dated confirmation.]
• Remaining work: [What still needs to happen.]

Priority 2: [Name]

• Planned: [Expected result.]
• Actual: [Result achieved.]
• Approval or acceptance: [Status.]
• Evidence: [Supporting record.]
• Remaining work: [Next action.]

Priority 3: [Name]

• Planned: [Expected result.]
• Actual: [Result achieved.]
• Approval or acceptance: [Status.]
• Evidence: [Supporting record.]
• Remaining work: [Next action.]

3. Results and relevant measures

• [Measure]: [Actual result] versus [Target or previous-period result].
• [Measure]: [Actual result] versus [Target or previous-period result].
• Time spent, if relevant: [Tracked hours within this reporting period].
• What the figures mean: [One sentence explaining the practical result.]

4. Work still in progress

• [Item]: [Current state], [remaining action], [owner], [target date].
• [Item]: [Current state], [remaining action], [owner], [target date].

5. Blockers, risks, and changes

• Issue: [What happened.]
• Impact: [What work, deadline, or outcome it affects.]
• Action taken: [What has already been done.]
• Next action: [What must happen next.]
• Owner and date: [Person responsible and deadline.]

Scope or priority changes: [What changed, when it changed, and who agreed to it. Write “None” if applicable.]

6. Priorities for next month

• [Priority]: [Expected result], [owner], [target date].
• [Priority]: [Expected result], [owner], [target date].
• [Priority]: [Expected result], [owner], [target date].

7. Decisions or support required

• [Decision or resource needed]: [Person responsible], [needed by], [consequence of delay].

Next update: [Date or reporting schedule.]

How to Choose the Overall Status

Use a status that describes the outlook, rather than how busy the month felt.

• On track: The remaining work can reasonably meet the agreed target with the current plan.
• At risk: A deadline or outcome may be missed unless a specific issue is resolved.
• Blocked: An essential next step cannot proceed until a dependency is resolved.

A report can contain several completed deliverables and still be at risk. Progress and delivery confidence answer different questions.

If different work areas have different statuses, state that in the summary. Avoid using one reassuring label to hide a blocked priority.

Monthly Progress Report Example

The following example is fictional. The person, project, dates, hours, and results are illustrative.

Monthly Progress Report

Project: Website refresh for a fictional consulting business

Reporting period: September 1-30, 2026

Prepared by: Alex, freelance developer

Prepared on: October 1, 2026

Overall status: At risk

1. Executive summary

Four of the five planned deliverables were submitted during September, and three received client approval. The homepage, services page, and contact form are approved. The about page is ready for review, while the final handover remains unfinished because it depends on that approval. The original September 30 completion target was missed; October 7 is the proposed revised target, subject to feedback arriving by October 2.

Action needed: The client project owner should approve the about page or provide one consolidated feedback list by October 2.

2. Planned work versus actual progress

Priority 1: Homepage

• Planned: Complete and submit the responsive homepage.
• Actual: Submitted September 10.
• Approval: Approved by the client September 12.
• Evidence: Staging version and dated approval comment.
• Remaining work: None within the agreed scope.

Priority 2: Services page

• Planned: Complete the page using the supplied service descriptions.
• Actual: Submitted September 19, including the additional FAQ section.
• Approval: Approved September 22.
• Evidence: Staging version and client confirmation.
• Remaining work: None within the revised scope.

Priority 3: Contact form

• Planned: Implement and test the agreed form.
• Actual: Form implemented; the agreed submission and notification checks passed.
• Approval: Approved September 24.
• Evidence: Test notes and client confirmation.
• Remaining work: None within the agreed scope.

Priority 4: About page

• Planned: Complete the page and obtain approval during September.
• Actual: Submitted September 26.
• Approval: Awaiting client feedback as of September 30.
• Evidence: Submitted staging version.
• Remaining work: Apply any agreed corrections and obtain approval.

Priority 5: Final handover

• Planned: Complete the handover by September 30.
• Actual: Not completed.
• Acceptance: Not applicable yet.
• Evidence: Open handover task and dependency note.
• Remaining work: Final checks, handover notes, and walkthrough after about-page approval.

3. Results and relevant measures

• Planned deliverables: 5.
• Deliverables submitted during September: 4.
• Deliverables approved during September: 3.
• Estimated effort for September: 36 hours.
• Recorded effort for September: 39 hours.
• Effort difference: 3 hours above the estimate, corresponding to the added FAQ work.

These figures describe September’s agreed delivery list and recorded effort. They do not represent a percentage of the entire project completed or a confirmed billable total.

4. Work still in progress

• About page: Awaiting client feedback. Client project owner to respond by October 2.
• Final handover: Awaiting about-page approval. Alex to complete by October 7 if feedback arrives as requested.

5. Blockers, risks, and changes

• Issue: About-page approval was not received during September.
• Impact: The final handover could not be completed by the original target.
• Action taken: The page was submitted September 26, with a reminder sent September 29.
• Next action: Obtain approval or a consolidated feedback list.
• Owner and date: Client project owner, October 2.

Scope change: An FAQ section was requested and approved September 18. It added 3 recorded hours and was included in the services-page delivery.

6. Priorities for October

• Client project owner: Approve the about page or provide feedback by October 2.
• Alex: Complete agreed corrections by October 5.
• Alex: Complete final checks and handover by October 7, subject to the approval dependency.

7. Decisions or support required

The client project owner needs to confirm the about-page content and the proposed October 7 completion date. If feedback arrives after October 2, the handover date will need to be agreed again.

Next update: October 5, or earlier if approval is received.

Why This Example is Useful to the Reader

The report gives the client a clear decision without making them reconstruct the project from a task list.

It identifies:

• What was submitted.
• What was approved.
• What remains open.
• Why the original target was missed.
• Who needs to act.
• How that action affects the revised target.

It also keeps the effort numbers separate from approval status. Spending more hours does not prove that a deliverable is accepted.

If you want these details available before report-writing day, use SelfManager.ai to capture dated tasks, tracked time, and decision comments as the work happens.

What to Include for a Manager Versus a Client

Use the same structure, but adjust the level of detail to the reader’s decisions.

For a manager

Focus on progress against agreed priorities, coordination needs, and where support would change the outcome.

Include work that matters to the team even when it did not produce a visible deliverable. An investigation, a resolved dependency, or a documented decision can be worth reporting if you explain its consequence.

For example: “Identified the cause of failed notifications and agreed the fix with engineering” is more useful than “Spent time investigating notifications.”

For a client

Focus on deliverables, acceptance, agreed changes, and actions the client must take.

Distinguish “implemented,” “submitted for review,” and “approved.” Those states often determine whether the next phase can begin.

If you report hours, use the relevant project records and clarify the period. Tracked effort, approved billable time, and an invoiced amount are different figures.

How to Prepare the Report from Your Work Records

The difficult part is often finding the information rather than writing the sentences.

Start with these records:

• The priorities agreed at the beginning of the month.
• Tasks and deliverables completed during the reporting period.
• Approval messages and decision notes.
• Open work and documented blockers.
• Time entries, if effort is relevant.
• Approved scope changes.

Then group the evidence by result. Ten small tasks that supported one deliverable usually belong under that deliverable, rather than appearing as ten separate achievements.

Keep a clear reporting cutoff. If approval arrives October 2, it was not a September approval. You can add a dated note about the later development without rewriting what was true at September 30.

A SelfManager.ai Workflow for Monthly Progress Reports

SelfManager.ai organizes work around dates and tables, with tasks, comments, and time tracking. That gives you a place to preserve the details a monthly report needs.

1. Organize the daily work by client or work area

Use consistently named tables for the work you want to report on, such as “Client website” or “Product development.”

Within each date, record meaningful tasks: “Submit about page for approval” is more useful for reporting than “Website work.”

2. Record outcomes and decisions in comments

After a meaningful change, leave a short factual comment.

For example: “Client approved the services page today. FAQ section is included in the approved scope.”

Use comments to distinguish completion from acceptance and to explain dependencies. If speaking is easier, capture a voice note, check the transcription, and correct names or dates. Recordings can be up to 30 minutes.

3. Track time while doing the work

Enable task time tracking where you need effort figures. Treat the resulting entries as source records to check, rather than assuming every logged minute is billable.

For the fictional website project, you would separate the original page work from the added FAQ work so the difference is explainable.

4. Use Instant AI Review for the reporting period

Instant AI Review can cover a month or a custom range of up to 90 days. Use the relevant period to generate a structured starting point, then follow up to focus the draft on the client or project being reported.

Keep the output within the chosen reporting scope. A report about one client should not absorb achievements from unrelated work.

5. Ask for a report using your chosen structure

You can use a prompt like this:

Draft a monthly progress report for [manager/client] covering [start date] through [end date], using only records related to [project].

Include an executive summary, planned versus actual progress, deliverables submitted, approvals explicitly recorded, unfinished work, blockers, scope changes, and next actions.

Separate completion from approval. Use recorded time only where relevant. Do not invent targets, approval dates, causes of delays, or percentages. Mark missing information as “not recorded.”

Suggest owners and dates only when clearly labeled as proposals. Keep the tone factual and concise.

6. Check the draft before sharing

Check the period, counts, dates, time totals, approval states, and action owners against the original records.

Confirm proposed commitments with the people responsible. AI can suggest a next step; it cannot establish that someone has agreed to deliver it.

Copy the checked report into the format your manager or client expects.

For the following month, AI Plan can help turn agreed priorities into dated tasks across up to 31 days. Review and approve the plan before committing it.

Common Monthly Progress Report Mistakes

Listing activity without an outcome

“Worked on the proposal” does not explain progress.

“Completed the first draft and sent it for internal approval” tells the reader what changed and what happens next.

Giving a completion percentage without a definition

A statement such as “80% complete” needs a clear basis.

Four of five monthly deliverables submitted is a useful count. It does not mean the remaining deliverable requires only 20% of the effort, or that the whole project is 80% finished.

Leaving the request buried at the bottom

If the reader needs to approve something, state the request in the executive summary and repeat it in the decisions section.

Include an owner and a date. “Waiting on feedback” leaves too much work for the reader.

Mixing this month’s results with later events

Report what happened inside the stated period. Label subsequent developments separately.

The prepared-on date and reporting cutoff are different dates for a reason.

A Final Check Before Sending

Read the report as if you were the recipient.

Can you identify the main result, the unfinished work, and the decision you need to make without opening another document?

Before sending, confirm:

• The reporting period is explicit.
• Results are supported by records.
• Submission and approval are distinguished.
• Numbers use a consistent scope.
• Blockers explain their effect.
• Next actions have owners and realistic dates.
• Proposed dates are labeled as proposed.

Try SelfManager.ai free for 7 days, with no card required, if you want your daily task records, time entries, and comments to support the next monthly report.

Frequently Asked Questions

What is a monthly progress report?

A monthly progress report summarizes work completed or advanced during a defined month. It explains progress against the plan, unfinished work, blockers, relevant measures, and the decisions or actions needed next.

What should a monthly progress report include?

Include the reporting period, an executive summary, planned versus actual progress, relevant results, open work, blockers, scope changes, next priorities, and requests for decisions or support. Add hours or other measures when they help the reader assess the work.

How long should a monthly progress report be?

Use the shortest version that gives the reader enough information to make decisions. A single-project report may fit on one page. Several workstreams may need a longer summary with supporting detail kept separately.

Should I include every completed task?

Usually, group tasks under outcomes or deliverables. Include individual tasks when they explain a significant result, unresolved issue, or decision. A full activity log can remain a supporting record.

Can AI write a monthly progress report?

AI can draft a report from relevant task records, time entries, and comments. A person should check dates, counts, approval states, missing context, and proposed commitments before sharing it. SelfManager.ai’s Instant AI Review supports periods of up to 90 days, including a month.

Is a monthly progress report the same as a monthly personal review?

No. A progress report is written for a manager, client, or stakeholder who needs to understand delivery and act on it. A personal review focuses on your own reflection and habits. They can use the same work records, but serve different readers.