Plan a community BioBlitz in a park

Planning a community BioBlitz is mostly a matter of turning a park, a fixed observation window and a group of volunteers into a set of biodiversity records that other people can trust and use. The event day matters, but the plan depends on decisions made weeks earlier: what you want to learn, which parts of the park you can use, who is qualified to identify what, where records go, and how results will be checked before anyone publishes them.

This guide is written for organizers. It covers scoping the event, assigning roles, securing permissions, setting up a records system, running the day safely and reporting results. It does not cover how an individual participant should prepare, beyond the information organizers need to publish.

What your plan needs to accomplish

Before booking anything, write down five things: the purpose of the event, the exact park boundary you will survey, the observation period, the people you intend to invite, and the final output you will deliver. Every later decision, from which specialists you recruit to which app settings you use, follows from these.

Purpose is the decision most organizers skip. The National Park Service's Heartland network, which publishes a method for research-style BioBlitzes in its parks, starts by identifying gaps in what is known about a park's biodiversity, then chooses focus taxa and sites to address them. A community event can borrow that logic even if it is less formal: ask the park operator or local naturalists which groups of organisms or areas are poorly recorded, and let that shape where and what you survey. If the main goal is public engagement rather than filling data gaps, say so, because it changes how much specialist review and how much structure you need.

The final output should also be named in advance. Options include a species list for the park, records shared to a public biodiversity platform, a short report for the park operator, or a feedback report for participants. The community guide produced by Tayside Biodiversity Partnership with East Haven Together in January 2023 treats a feedback report as part of the programme rather than an afterthought.

Limits that shape the event

Observation period: the length of the window sets how many sessions you can run and how much specialist time you need. Reserve time after the window for record entry, identification queries and review, which the Tayside guide includes as part of the programme.
Season and timing: which organisms are active and visible depends on the date. Ask your identification leads which groups are realistic for your chosen date before you commit to focus taxa.
Weather: outdoor sessions need a lightning plan and a sheltered fallback. The National Weather Service recommends a plan that covers monitoring, stopping activities, shelter, emergencies and resuming, with enough time allowed to evacuate.
After-dark sessions: any evening or nighttime activity depends on the park operator confirming access and on a leader agreeing to run it.
Mobility and accessibility: arrival routes, activity routes, toilets and meeting facilities determine which areas can be offered to everyone and where the information hub should go.
Participants: who you invite affects briefing content, the number of volunteers needed for each group and how much identification support you must provide.
Equipment: whatever you supply, and who owns it, determines storage at the hub, return arrangements and what participants must bring themselves.
Budget: the Tayside guide budgets for insurance, venue, equipment, connectivity, refreshments and specialist expenses. Use those categories as a starting checklist, but get current prices and requirements locally.

Choosing an approach

Most park BioBlitzes fall into one of three patterns. The right one depends on your purpose, how many qualified identifiers you can recruit and what the park operator permits.

A specialist-led survey follows the research model described by the NPS Heartland network: an interdisciplinary team, focus taxa and sites, qualified leaders who agree methods, equipment and reporting duties, and park-specific permission before any collecting. It produces the most reliable data but needs the most specialist time and the earliest start on permissions.

An open community observation event invites the public to photograph and record what they find, usually through a platform such as iNaturalist, with a staffed hub for help. It is easier to scale and suits engagement goals, but identification quality depends on the evidence participants capture and on later community and specialist review.

A hybrid runs a small number of leader-guided sessions on focus groups alongside open observing, with all records feeding into the same project. It is often the most practical choice for a city park because it gives specialists a defined role without limiting public participation.

Approach	Best fit	Main tradeoff	Must confirm first
Specialist-led survey	Filling known data gaps for a park operator	High demand for qualified leaders and lead time	Research or collecting permission, leader commitments, approved methods
Open community observation	Public engagement and broad participation	Records need more review; quality varies	Event permission, hub location, connectivity, identification support
Hybrid	Engagement plus some reliable focus-group data	More coordination between sessions and the hub	Session leaders, session-specific access, shared records protocol

Whichever pattern you choose, do not assume that an observation-only event needs no permission. Whether the park requires event approval, and whether any methods count as collecting under its rules, is a question for the park operator.

Setting up the records platform

If you use iNaturalist, its own guidance recommends a Collection project for BioBlitzes. A Collection project shows any observation that matches the place, dates, taxa and other criteria you configure, so participants do not need to add records manually. A Traditional project requires observations to be added to it and can require extra observation fields, which gives more control but adds a step participants can forget. Choose Collection unless you need custom fields, and draw the place boundary to match the area the operator has approved.

Planning sequence

1. Write the purpose, park boundary, observation period, intended participants and final output. Everything below depends on this.
2. Contact the park operator. Ask whether event approval is needed, which areas are off limits, what environmental restrictions apply, whether any collecting is allowed and on what terms, and whether evening access is possible. Do not finalize dates until you have answers.
3. Assign roles: park liaison, event coordinator, volunteer coordinator, identification leads, data lead, accessibility lead and safety coordinator. One person can hold more than one role, but each role needs a named owner.
4. Recruit identification leads for your focus groups and agree with them the methods, equipment and reporting duties each will take on, as the NPS model requires of its leaders.
5. Build a scope matrix (example below) that links each area or session to its focus, leader, approved method, participant group, equipment, access needs and record destination.
6. Draft the budget using the categories above and confirm who pays specialist expenses.
7. Write the data protocol: required fields and evidence, permitted methods, submission destination and deadline, which identifier reviews which groups, how sensitive locations are handled, image and data licenses, and release permissions.
8. Create the platform project with the agreed place, dates and taxa, and test it with a few observations.
9. Walk the site to verify accessible arrival and activity routes, toilets, meeting facilities, weather shelter and phone connectivity at the hub and in survey areas.
10. Write the safety and lightning plan with the safety coordinator, including emergency contacts and how stop and resume decisions will be communicated.
11. Publish confirmed registration details, meeting point, what participants should prepare and the cancellation policy. Publish only what is confirmed.
12. Brief volunteers on roles, methods, equipment, boundaries and emergency contact arrangements, and run an orientation at the start of the event.
13. Run the event with a staffed information hub and expert availability, then follow the reporting sequence below.

Hypothetical example of a scope matrix entry, for illustration only: the north meadow, morning session, focus on pollinating insects, led by a named entomologist, method limited to photographs, open to registered families, nets and identification sheets supplied by the event coordinator, step-free route via the main gate, records to the event's Collection project. A second entry for an evening moth session would stay out of the published programme until the operator confirms after-dark access and a leader agrees to run it.

What participants record, and how you track review

Brief participants on iNaturalist's observation workflow: one organism per observation, with photo or sound evidence, the date and location of the encounter, and an identification if they have one. Planted, captive or cultivated organisms should be flagged as such, which is common in city parks with ornamental beds. Saving an observation and uploading it are separate steps, so set a submission deadline after the event and remind people to sync.

iNaturalist assigns each record a quality grade, Needs ID, Casual or Research Grade, based on platform data-quality rules and community identifications. Research Grade can be reached through community agreement on a species or through documented routes at broader levels. These grades can change after your event as more people add identifications. Keep the platform grade separate from your own organizer review, so a record can be Research Grade on the platform yet still awaiting your specialist's check, or the reverse.

record_id | platform_grade | organizer_review_status | reviewer | query | resolution

Location privacy needs a decision before the event, not after. iNaturalist distinguishes geoprivacy set by the observer from geoprivacy applied automatically to certain taxa, and trusted users can be granted access to hidden coordinates. Obscuring coordinates cannot remove location clues in photographs, descriptions or other records. The NPS model withholds sensitive locations from public outputs; agree with your identification leads and the park operator which species or sites count as sensitive and brief participants accordingly.

Details to confirm before you rely on the plan

Event approval: whether the park operator requires a permit or booking for your event, and any conditions attached.
Collecting and methods: whether any method you plan, such as netting, trapping or taking specimens, needs research or collecting permission. The NPS model obtains park-specific permission before collecting.
Restricted areas: environmental restrictions, protected habitats or seasonal closures within your boundary.
After-dark access: whether the park is open for evening sessions and under what arrangements.
Insurance: whether the operator or venue requires event insurance and what cover is needed. The Tayside guide budgets for it, but requirements differ by location.
Arrival and access: transit options, parking and step-free routes to the meeting point. Check these on a site walk and with the operator rather than from maps alone.
On-site facilities: toilets, meeting space, power and weather shelter, and their opening hours on your date.
Connectivity: phone signal in survey areas and at the hub. Test on site; if it is weak, plan for later uploads and adjust the submission deadline.
Equipment: who owns each item, where it is stored during the event and how it is returned.
Specialist commitments: written confirmation of each identification lead's availability, sessions and post-event review duties.
Data permissions: image and data licenses, and permission to release records and any report to the public.

Revising the plan when conditions change

Thunderstorms: the National Weather Service advises stopping outdoor activity in time to reach shelter and waiting at least 30 minutes after the last thunder before resuming. If a storm takes a large part of the window, shorten sessions rather than extending past the published period. If you do extend, update the dates on your Collection project, since its configured dates control which observations appear.

A specialist withdraws: narrow the focus groups to those you can still review, or keep observing that group but label those records as awaiting specialist review in your report. Do not promise identifications you cannot deliver.

Permission is refused or restricted for an area or method: remove it from the scope matrix and the published programme, and tell any leader whose session depended on it. Redraw the project boundary if the surveyed area shrinks.

An accessible route or facility is unavailable on the day: move the hub or the affected session to an area that meets the same access requirements, and announce the change at the meeting point and through your registration channel.

Reporting results

Receive records by the submission deadline and check them for completeness.
Route identification questions to the assigned specialists and log each query and its resolution.
Date every results snapshot, because platform quality grades and identifications keep changing.
Label preliminary findings as provisional and release confirmed results only after specialist review, as the NPS model does.
State the actual area surveyed, the observation period and the methods used alongside the results.
Withhold sensitive locations from public outputs.
Send the park operator its agreed output and share a feedback report with participants.