Date: 5/14/26 11:38 am From: <plants...> Subject: [MBBIRDS] reposted by permission from PenBird, by eBird reviewer Malia DeFelice
We are in the thick of Spring Migration! And here are a few reminders for best practices when using eBird at any time, but certainly at this exciting time of the year.
Our review team has been seeing a higher volume of reports this Spring where reports of rare/unusual birds have been lacking adequate documentation. So hopefully the following will be helpful to mention how and why it is important to know how to document rare and unusual birds.
Everyone who has used eBird to report a rare bird, or birds that are unusual for the time of year, or location, is familiar with the automated prompt requesting more documentation. Just a few reminders about documenting your rare/unusual birds on eBird:
Documenting birds flagged as rare : When you are prompted to provide documentation for a sighting of an unusual or rare bird, identifiable photos and audio are best! If you are lacking good supporting media, please write a description of the bird with the #1 comment to add being a description of the bird. A description of the bird should contain field marks and defining physical or audible characteristics that helped you separate it from similar species. This is the most important element you can add to your checklist record. The bird's behavior, what the bird was doing, where it was seen etc. can add depth to the record, but a description of what the bird looked/sounded like is the most important component. Remember, the rarer the bird, the more important thorough documentation becomes.
Ultimately It is up to the observer to provide their documentation and details of the bird. Comments like "continuing bird" or "seen with so-and-so" are OK where applied within reason, but can only go so far. It is a good practice to learn how to write descriptions. Here is an eBird help file link for those new to writing descriptions:
Remember the effort and care you take to document your sightings is your eBird/Birding legacy! And also maintains data quality for our San Mateo County eBird database.
"Details to be added" "Photos/Audio to be added". When compiling checklists in the field using a smart device, it can be difficult to type detailed notes. For birds flagged for more details, please use comments like "Details to be added" or "Photos/Audio to be added". But use that wording only as a temporary placeholder in your checklist comments. Avoid making those "to be added" comments permanent. Try to write your descriptions of the birds and field marks/notes etc. as soon as you can while the details are still fresh in your mind. Don't wait until a time too far in the future when details are fuzzy at best. Upload your supporting photos and audio as soon as it is convenient, especially if it is an early arrival or a rarity you are documenting.
Merlin Users: Merlin does not provide an absolute ID. Merlin provides an ID Suggestion. If you are using Merlin to identify a bird that gets flagged for more details, please upload your audio recording to your checklist as soon as it is convenient. Leaving a comment "ID"d by Merlin" is not sufficient documentation. Merlin can be accurate, but Merlin can also be very wrong and still needs the human element to review suggested Identifications. It is always best to try to see a vocalizing bird in order to get visual confirmation of the ID when possible.
This information seems worth repeating - thanks, Melia!
