How Nonprofits Can Write Better Project Needs

Many nonprofit project requests fail because they ask for help in vague terms. “We need volunteers” may be true, but it does not tell a person where to go, what to bring, how long it takes, or what success looks like.

A better project need turns care into action. It gives a donor, volunteer, or partner enough information to say yes without a long email chain.

Write the task like a work order

Use a title that can be understood at a glance. “Paint pantry shelves” is stronger than “facility support.” “Move donated desks into classroom” is stronger than “operations help.”

A good title includes the verb and the object:

• Build three raised beds
• Sort donated office supplies
• Install shade cloth over garden work area
• Label tool library inventory
• Move shelving into the training room

People decide quickly. A clear task lets them know whether they can help.

Include the site details people actually need

Every project need should include the address or general location, indoor or outdoor setting, parking notes, accessibility details, time window, supervisor name, and safety requirements.

If the site is not ready for public volunteers, say so. Some tasks are better for trained crews, staff, or partners with equipment.

Use this structure:

1. What work will happen?
2. Where will it happen?
3. When should people arrive and leave?
4. Who is responsible on site?
5. What should volunteers bring?
6. What will be provided?
7. What safety limits matter?

Separate people needs from resource needs

A good project request separates people needs from resource needs. If the project requires gloves, paint trays, a hand truck, mulch, shelving, a truck, or shade tents, list those items separately from the volunteer roles.

This gives donors a way to help even when they cannot attend the workday. It also keeps volunteers from arriving with the wrong assumptions.

Example:

• People needed: 8 volunteers for two hours, 1 site lead, 1 person able to lift 40 pounds
• Materials needed: 12 bags of soil, 3 shovels, 2 wheelbarrows, work gloves, water cooler
• Site constraints: outdoor work, no restroom on site, parking on east side only

Define completion before people arrive

A project should have a finish line. “Clear ten raised beds and stack all removed material by the north gate” is easier to manage than “clean up the garden.”

Completion notes help the supervisor sign off on volunteer hours and help the next crew understand what remains.

Good completion language sounds like this:

• All donated chairs are sorted into keep, repair, and recycle groups.
• The tool shelf is labeled and every checkout item has a matching inventory number.
• Mulch is spread two inches deep around the marked beds.
• The classroom is reset, swept, and ready for Monday training.

Make the request honest

Do not make a project sound easier than it is. If the work is hot, heavy, muddy, repetitive, loud, or emotionally sensitive, write that down. Volunteers can handle hard work when they are prepared for it.

Honesty also protects the nonprofit. A person who cannot safely lift, use blades, work in heat, or handle strong smells should be able to choose another role before arriving.

Add evidence without turning it into a grant report

Photos, rough counts, and simple maps can make a request easier to understand. You do not need a polished packet. You need enough context to prevent the wrong help from showing up.

Useful evidence includes:

• One wide photo of the work area
• A photo of materials already on site
• A simple sketch of where items should move
• Count of beds, shelves, boxes, pallets, or rooms
• Notes about water, electricity, gates, docks, or storage

Use a repeatable listing format

Shared World’s Resource Exchange is designed for this kind of clarity. The goal is not more listings. The goal is better matches between real needs and people who can meet them.

Use the same format every time. The easier your requests are to scan, the faster donors and volunteers can trust them.

Write for the person deciding in 30 seconds

Most people do not read a project listing like a grant reviewer. They scan it while deciding whether they can help. A strong listing answers the first decision quickly:

• Is this near me?
• Can I do the work?
• Do I have the time?
• Is it safe for me?
• Do I need special tools or training?
• Will the work actually matter?

Put those answers near the top. Do not bury the basic facts below mission language. Mission matters, but a volunteer cannot act on mission alone.

Use one main ask per listing

When a listing asks for volunteers, a truck, mulch, shelving, social media help, and grant research in one block, it becomes hard to answer. Split large needs into separate listings or clearly marked sections.

For example:

• Volunteer need: 10 people to spread mulch on Saturday.
• Resource need: 20 cubic yards of mulch delivered by Friday.
• Equipment need: 2 wheelbarrows and 6 hard rakes.
• Skilled need: 1 person with irrigation repair experience.

This lets a donor with mulch help without attending the workday. It lets a volunteer sign up even if materials are still being sourced. It also makes the project easier for Shared World to match.

Make safety and accessibility normal

Safety details should not feel like fine print. They help people choose the right role. A listing should name heat, lifting, uneven ground, stairs, dust, noise, chemicals, blades, power tools, vehicle movement, emotional sensitivity, and any background-check or age requirements.

Accessibility details matter too:

• Is there accessible parking?
• Is the route to the task area paved or uneven?
• Are seated roles available?
• Are restrooms available?
• Is shade available?
• Can someone help with check-in, labels, calls, or records instead of lifting?

Good accessibility notes widen participation. They also reduce awkward conversations on arrival.

Give donors the condition standard

Material donors need standards. If a nonprofit says “we need office supplies,” donors may send anything. If the listing says “unopened copy paper, working clipboards, labeled binders, clean bins with lids, no loose mixed boxes,” the match improves.

Each resource request should include:

1. Accepted condition.
2. Quantity needed.
3. Delivery or pickup limits.
4. Storage deadline.
5. What will be declined.
6. Photos if a specific size or type matters.

This is not being picky. It protects nonprofit time.

Show the chain of use

People give more confidently when they understand where the help goes. A project need should explain the chain from contribution to outcome.

Weak: “We need shelving.”

Stronger: “We need four metal shelving units so donated school supplies can be sorted by grade level before the August distribution. Shelving must be freestanding, clean, and no wider than 36 inches because the storage room has a narrow aisle.”

That one paragraph tells a donor what kind of shelving fits, why it matters, and what problem it solves.

Keep the tone factual and human

Do not over-sell. Do not guilt people. Do not write like a press release. The listing should feel like a competent person telling the truth.

Use direct sentences:

• “This is outdoor work in heat.”
• “The site has no restroom.”
• “We can train beginners.”
• “We cannot accept broken furniture.”
• “Court-related service participants must bring their required paperwork.”
• “The finish line is 30 labeled storage bins.”

Clear is more respectful than inspirational padding.

Sources and further reading

• Points of Light: Volunteer engagement resources
• Points of Light: Volunteer engagement resources
• CDC: Social connection
• EPA: Sustainable Materials Management Basics
• Independent Sector: Value of volunteer time