What belongs in a nonprofit plan for 2027? Start with approved commitments, funding assumptions, program priorities, staff capacity, systems, and decision dates. Choose a manageable set of actions with owners and resources. Use current evidence to prepare for uncertainty rather than predicting that a new year will automatically bring growth, stability, or better results.
Annual planning is an opportunity to make the work clearer. It can reveal which promises are already funded, which projects depend on decisions, and which responsibilities have quietly accumulated without support. A useful plan gives people a practical sequence rather than another long list of ambitions.
This guide is written in 2026 for planning toward 2027. Resources were reviewed October 26, 2026. It replaces an older prediction-based article with a working method for nonprofit leaders, boards, managers, and professionals. The suggested timing and examples are planning tools, not requirements or forecasts.
Begin with commitments already made
List the services, reports, events, agreements, and organizational responsibilities that must be supported. Identify the people or partners who depend on them and the dates that matter. Separate these commitments from proposed expansion, new ideas, and activities that have not been approved.
Ask each team to describe the work in concrete terms. “Improve engagement” leaves the activity unclear; “review the donor acknowledgment process and assign an owner” identifies a task. Clear descriptions make it easier to compare priorities and estimate the resources required.
Include continuing work that is easy to overlook: supervision, records, maintenance, finance, HR, accessibility, and partner coordination. A plan that lists only new projects can create an unrealistic picture of staff capacity. Existing responsibilities still require time even when they do not appear in a campaign or strategic initiative.
Choose a small number of practical priorities
For each proposed priority, ask which mission need it addresses, what evidence supports it, and what would happen if it were delayed. Compare its value with the work it requires. Avoid approving projects solely because they sound modern, appear in a sector report, or are being discussed by another organization.
Define what completion would look like. A revised process, an approved resource, a trained team, and a launched service are different outputs. If the desired result depends on other people or external conditions, distinguish the action your team can complete from the outcome it hopes to influence.
Keep a visible list of deferred ideas with the reason and review date where appropriate. Deferring a project can be a responsible capacity decision. It is more useful than treating every idea as an active commitment while leaving the team to resolve the conflict informally.
Review funding assumptions before assigning expansion
Separate confirmed revenue from renewals, proposals, and possibilities. Record restrictions, payment timing, delivery costs, and reporting obligations. A grant amount alone does not reveal how much flexibility it creates or whether the organization can support the associated work.
Use the National Council of Nonprofits budgeting resource to frame the review with staff and board. The funding planning guide connects revenue sources with capacity and timing. Apply the concepts to actual agreements and records.
Give cash timing a separate view. An annual budget can look balanced while receipts arrive after obligations are due. Ask finance to identify the relevant restrictions and timing before approving a new commitment. A general economic forecast cannot establish what resources are available for a particular decision.
Build a capacity map before a hiring list
Identify the work, current owner, approximate effort, relevant skills, and support needed. Look for responsibilities covered through informal reassignment, delayed projects, or a single person’s undocumented knowledge. A vacancy can conceal work that is already being performed elsewhere in the team.
Ask whether a gap requires additional staffing, clearer priorities, training, a process change, or a defined external service. Those are different responses. A new title does not automatically solve a problem whose duties and decision authority remain unclear.
If hiring is proposed, describe the role’s first priorities, reporting line, resources, and ongoing costs. Include onboarding and supervision in the plan. Use the job posting checklist before treating the vacancy as ready for publication.
Use a sequence that makes dependencies visible
| Stage | Work to complete | Decision enabled |
|---|---|---|
| Establish the starting point | Reconcile commitments, funding, workload, and systems | Which assumptions need attention? |
| Choose priorities | Compare need, evidence, cost, and capacity | What is approved, deferred, or declined? |
| Assign delivery | Name owners, resources, dependencies, and dates | Can the work begin? |
| Review and adapt | Compare progress and evidence with the plan | What should change next? |
Use your actual fiscal year, program calendar, and governance schedule rather than assuming January is the start of every operating cycle. A calendar-year guide can help organize questions while the organization’s own deadlines determine the timing.
For a hypothetical example, a program expansion may depend on confirmed funding, an available supervisor, and a suitable service location. Show all three prerequisites. Completion of one does not make the project ready. Assign a person to track the remaining conditions before announcing a start date.
Plan technology around a defined workflow
Choose a process that needs attention and describe its inputs, users, output, review, and owner. A new system may support the work, but it also requires setup, training, maintenance, and support. Include those responsibilities in the plan rather than treating purchase or installation as completion.
For AI-assisted work, distinguish drafting, research, access to organizational information, and actions in connected systems. Confirm current capabilities and permissions. Use the nonprofit AI recruiting guide and AI work resource to explore task-level examples.
The NIST AI Risk Management Framework resource offers a broader reference for examining AI-related risks and responsibilities. Review its current materials and status rather than assuming one document answers every organizational question. A small, defined pilot can provide more useful evidence than a broad claim that automation will transform the entire team.
Connect learning with work people will perform
Ask which skills the approved priorities require and where gaps exist. Choose training with relevant content, practice, and feedback. A course should address an identified need rather than serve as a general signal that the organization values development.
Use the nonprofit training guide to compare resources. Include learning time and a practical application step. A supervisor should know what the person is authorized to change and who will review the work afterward.
Do not assume training resolves unclear authority, missing access, or an impossible workload. If the barrier is structural, address that issue directly. A useful learning plan can be part of the response without carrying responsibility for every organizational outcome.
Make board and management responsibilities clear
Identify which decisions belong to management, which require board approval, and which involve other authorized parties. Consult the organization’s governing documents and appropriate expertise. BoardSource’s board responsibilities resource is a starting point for governance learning, not a substitute for the organization’s own rules.
Prepare decision papers that state the question, evidence, alternatives, recommendation, resources, and review date. Separate information items from approval requests. A board packet full of articles does not automatically establish what decision members are being asked to make.
Record approvals and conditions. If a decision is deferred, identify the missing information and responsible person. If a temporary arrangement is approved, state when it will be reconsidered. These records help maintain continuity between meetings and staff changes.
Build scenarios around real uncertainties
Choose alternatives that would change a decision: a delayed payment, an unconfirmed renewal, a later hire, a quoted cost increase, or a partner’s availability. Label the assumption and explain its effect on cash, commitments, workload, and timing.
Avoid arbitrary percentages selected only because they are easy to calculate. A scenario should correspond to a plausible question in the organization’s actual plan. It does not need to predict the future to be useful; it needs to prepare a choice and identify what evidence would trigger review.
Use the funding uncertainty guide when an award or payment requires closer attention. Keep the specific agreement, official notices, and current organizational evidence central to the decision.
Choose measures that inform action
For each priority, define the output, source, owner, period, and decision the measure supports. A completed activity, participant count, service quality indicator, and long-term outcome are different measures. Do not merge them into a single score without a clear method.
Use consistent definitions and avoid double counting. If a measure cannot be reproduced from its source, resolve that before putting it in a board chart. A missing value is not zero, and a few comments are not a representative survey unless the method supports that claim.
The research resource guide can help assess external evidence. Use the latest relevant source while preserving its actual data period. A report published in 2026 may describe an earlier year, and that distinction belongs beside the number.
Communicate the plan in terms people can use
Staff need to understand priorities, responsibilities, decision routes, and the next review. Explain what is approved and what remains proposed. Avoid sharing a scenario as if it were a settled employment or program outcome. Provide a route for questions and update the plan when decisions change.
Partners and funders need accurate information about commitments and requests. Candidates need clear terms for advertised roles. The same planning process can support all three audiences, but each requires different detail. Do not use a broad strategic statement as a substitute for a specific agreement or job description.
Set a review rhythm for 2027
Schedule reviews around the decisions and volatility involved. Cash timing may need closer attention than a long-term projection. Program launches, renewals, vendor agreements, and hiring decisions may each have their own milestones. Assign owners rather than relying on a general instruction to monitor developments.
At each review, ask what changed, what evidence supports it, and which decision needs attention. Retire measures that no longer help. Preserve the version used for important approvals while keeping the active plan current. The plan should guide work and adapt to evidence, not become a document people avoid updating.
Give professionals a role in the next step
Employees can ask how their responsibilities connect with approved priorities, what support is available, and where learning would be useful. Job seekers can explore roles whose duties match their experience and interests. Use the career resources and current listings to investigate actual opportunities.
Employers preparing a vacancy should define the work before choosing a title or channel. A 2027 staffing plan is more useful when it explains responsibilities, supervision, location, compensation information, and resources. Clear scope supports informed applications without promising a particular hiring result.
Prepare the team for your next priorities
Employers can review posting options for a defined vacancy. Job seekers can explore current nonprofit openings and compare individual responsibilities and terms.
Nonprofit planning for 2027 questions
Should every organization start its plan in January?
No. Use the actual fiscal year, program calendar, agreement dates, and governance schedule. The sequence here is a planning tool rather than a required timetable.
What should come before a hiring list?
Map the approved work, current capacity, skills, resources, and supervision. Then assess whether the gap calls for hiring, training, process changes, or another defined response.
How many priorities should we choose?
Choose a manageable set the organization can resource and explain. The right scope depends on commitments and capacity, not a universal number of initiatives.
Should AI adoption be a 2027 goal by itself?
Define the workflow and need first. Evaluate tools through current capabilities, permissions, review responsibilities, costs, and a practical pilot rather than a broad technology promise.
What makes a planning scenario useful?
It connects a specific uncertainty with a decision, owner, evidence trigger, and practical effect. It prepares choices without pretending that the outcome is known.
How do we keep the plan useful after approval?
Assign review dates and owners, update assumptions, record decisions, and communicate changes. Remove stale inputs from the active summary while preserving important approval records.