How to Build a Weekly Work Plan for a One-Person Nonprofit Office

Quick answer: Build a one-page weekly work plan around the hours you actually have, not the number of requests in your inbox. List fixed commitments first, choose up to three outcomes that matter most, reserve time for unexpected work, and give every active task a next step. At the end of the week, decide what to finish, defer, delegate, or stop.

Being the only paid employee of a nonprofit can mean being the executive director, office manager, event coordinator, membership contact, and board packet assembler in the same afternoon. The problem often is not a lack of effort. It is that the organization has more potential work than one person can safely promise.

This guide provides a capacity-first weekly operating plan. It is not a replacement for an annual strategic plan, staff job description, board calendar, or program budget. The Minnesota Council of Nonprofits' planning principles recommend tying operational plans to priorities, responsibilities, timelines, and the approved budget. The weekly work plan is how a small office translates those commitments into realistic next actions.

Start with your real capacity, not a 40-hour fantasy

Do not start Monday by transferring every unfinished item into a longer list. First estimate what time remains after commitments that cannot move.

For example, a fictional director scheduled for 40 hours might have:

These are illustrative numbers, not a staffing benchmark. An organization with a major festival underway might have much less project time. A quieter week may have more.

Ask what must be covered for the office to function: opening hours, payroll handoffs, constituent service, deadlines from grant agreements, board materials, event safety, and vendor commitments. Mark which items have hard external dates. A flexible article draft and a legally required filing should not compete as equals simply because both appear on a task list.

Do not budget every remaining minute. An office that routinely receives urgent partner calls or unexpected facility problems needs slack. Otherwise a single surprise creates a week of broken promises.

Choose three outcomes instead of fifteen priorities

An outcome is a result you can recognize as done. "Work on memberships" is vague. "Send renewal notices to the 12 members whose renewal dates fall next month" is clear.

Choose one to three outcomes for the week using four questions:

1. Mission: Does it support an agreed organizational or program priority?
2. Deadline: What actually happens if it waits a week?
3. Commitment: Has the organization already promised someone a deliverable?
4. Capacity: Is the task small enough to finish with the time available?

The National Council of Nonprofits' strategic planning guidance emphasizes revisiting priorities as conditions change. In a tiny office, that can happen in a ten-minute review each week.

Three priorities do not mean you complete only three tasks. They mean you know which outcomes cannot be crowded out by easier, louder work.

Separate four kinds of work

This distinction prevents a good idea from silently becoming an urgent assignment.

Copy-ready weekly work plan

Duplicate the following into a shared document or task system. One page is enough for a starting point.

Week of: [Date]
Available project hours: [Number]
Board-approved or contract deadlines: [List]
Unexpected-work reserve: [Number of hours]

Recurring essentials: [Payroll check, event inbox, weekly deposit process, etc.]
Waiting on someone else: [Name / requested item / follow-up date]
Not doing this week: [Deferred work, with reason]
Needs board chair or supervisor decision: [Trade-off or resource request]

A fictional example

A chamber-like community nonprofit has a board meeting next Tuesday, a sponsor logo deadline Friday, and a grant report due in ten days. The director's three outcomes might be: finalize the board packet, close sponsor artwork approvals, and assemble grant expense records. A proposed new networking series goes into the backlog until those commitments are covered. This is a choice about sequencing, not a rejection of new ideas.

Build the week around your energy and dependencies

Reserve two or three blocks for work that requires concentration. If financial reports need a bookkeeper's file, request it early rather than planning to finish the report before the file arrives. If sponsor proofs are needed from a designer, distinguish work you can do from work you are waiting for.

A workable rhythm might be:

• Monday, 20 minutes: Review the calendar, actual capacity, three outcomes, and external deadlines.
• Daily, 10 minutes: Scan urgent messages, update blockers, and adjust only when something truly changed.
• Midweek, 15 minutes: Check whether a commitment is at risk. Tell affected people early.
• Friday, 20 minutes: Record completed outcomes, unresolved work, lessons, and the first step for next week.

Those timings are examples, not an industry standard. The right habit is the one a busy director will actually repeat.

Give interruptions a decision rule

A one-person office will be interrupted. Instead of pretending otherwise, use a simple question when a new request arrives: What should this replace?

A same-day safety issue or a time-sensitive legal/contract obligation can supersede planned work. A nonurgent design preference generally should not. If something new requires four hours, either move another four-hour task or explicitly agree to a different deadline. This makes the cost of changing priorities visible.

Use a short response such as:

Thanks for sending this. I can take it on after [current deadline], or we can move [existing priority] to make room this week. Which outcome should take precedence?

For requests from individual board members, coordinate significant reprioritization through the board chair and the organization's agreed governance channels, rather than quietly accepting competing assignments. BoardSource's description of board chair and chief executive roles distinguishes board oversight from executive management.

Track what is blocked, not just what is finished

Many small-office tasks stall because an external person has not responded. Keep a small waiting-on list with the specific answer needed, owner, date requested, and next follow-up date. Do not repeatedly reread the original email and hope the information arrives.

For example:

This table is a fictional example. It identifies dependencies rather than assigning blame.

When the plan consistently does not fit

A weekly plan is diagnostic. If the director continually works evenings to keep routine obligations afloat, the issue may be staffing, overcommitment, unclear authority, a program that needs simplification, or insufficient board support.

Document the gap with neutral evidence: deliverables due, estimated hours available, recurring interruptions, service risks, and what has been delayed. Bring options to the board chair or authorized supervisor. Options could include reducing a low-impact program, involving a qualified committee for an agreed task, funding contract support, or moving a deadline with a partner. Do not imply that unpaid volunteers can simply absorb regulated or confidential work.

Small nonprofits deserve plans that describe reality. A shorter plan that exposes impossible commitments is more useful than a flawless-looking calendar that nobody can deliver.

A five-minute Friday review

Before ending the week, answer:

1. Which of the three outcomes are complete?
2. Which commitment is at risk, and who needs to know?
3. What is waiting on someone else?
4. Which request displaced planned work?
5. What should not be carried into next week?
6. Does leadership need to approve a trade-off?

Keep this record simple. Over time, repeated bottlenecks can show where procedures, staffing, or expectations need to change.