Use a batch note when one incident or observation concerns several members of a group. You write the shared explanation once, then save it for the members who belonged at the incident time.
After saving, each affected member can show the observation in Notes & History even if the group changes later. Use Apply selected batch note from the Extensions menu to save this shared observation. Typing the row prepares it; applying the selected row and checking the result finishes the save.
Record and save a shared incident
Before writing, check Batch membership for the incident date and time. You need to know which stock belonged then. Click Record a batch note → on Batches or Batch membership to open the next unused Batch notes row. Complete an unfinished observation on its original row instead.
When you apply the note, it is saved for the members who belonged at that time. Stock added to the group later does not gain an observation about an earlier incident.
On an unused Batch notes row, enter a unique fixed Note number and choose the Batch number. Enter the real incident date and time, then describe what happened in readable sentences.
Add a recorder name when known, and mark Important if the observation needs priority in Current Stock. Select the completed row.
Choose Extensions → Farmer’s Helper — Development → Stock → Apply selected batch note. The development add-on must be available and authorized in this workbook.
Read Save status before leaving. Then open Notes & History for an affected Stock number and confirm that the shared note appears.
The tool also saves each member’s current location and stage when you apply the note. If you are entering an older incident, these describe the time of saving rather than reconstructing the earlier place or progress. Explain any relevant older context in the note, and do not treat today’s saved place as proof of where the stock was then.
Keep the same Note number when retrying
Give this observation a Note number or short label you have not used for another incident. Keep that number and the original details while saving. If the window closes or the connection fails, return to the same row and read Save status before trying again. Follow the status instructions below to continue or confirm that same save.
Do not copy the observation into another row or give it another number just to retry. Returning to the same row lets the tool finish or confirm that save without treating it as a second incident. Use a new number for a genuinely different observation.
Batch number
Choose the batch whose members were affected. Check who belonged on the incident date and time before applying the note. Members may have different Stock types and quantities; sharing the observation does not turn them into one physical lot.
Happened on
Choose the date the incident actually happened, which may be earlier than today. Use the date cell’s calendar and enter the known Time happened beside it. Together, they let the membership records show who belonged at that point.
Time happened
Enter the local time as accurately as your information allows. If you are unsure which members were affected, resolve that before applying the shared note. Inventing a time could make it appear that the observation definitely concerned stock that may not have belonged then.
Describe the incident
Describe the observation with enough context for a colleague who was not present. Explain what happened, what was affected and any important uncertainty. The shared text should make sense when read later in one member’s individual history.
A note preserves what was observed. If you also hold stock, record a loss or change its stage, enter that decision or work on the relevant page. A later reader can then distinguish the incident from what was done about it.
Recorded by, if known
Choose or enter the person or team making the record when known. The name gives someone a contact for more detail, while remaining a label entered on this record rather than an independent verification of the Google account.
Important
Mark Important if the shared observation should receive priority in Current Stock’s note preview. This makes a significant incident easier to notice while its full text remains in history. It does not put members on hold, fail an assessment or change their quantities.
Read Save status before leaving
Read Save status before leaving or retrying. It tells you whether the shared observation has been saved and whether the row still matches it:
Blank: no Note number is entered on this row. A blank status does not confirm a save.
Not saved: the shared note has not been saved. Complete the details, select the row and use Apply selected batch note.
Pending — Apply again: return to this same row, keeping its original Note number and details, and apply it again to continue the save. If you changed those details, restore the original entries before retrying.
Saved: the shared note is recorded and this row matches it. Repeating the same save does not add another copy.
Saved note — draft differs: the note was saved, but something on this row has since changed. Those edits have not replaced the saved observation; history still keeps the original. Restore the original row if you need to repeat or confirm that save.
Check saved note: the saved result needs review. Stop and check the original row and affected members’ history before another attempt. Do not keep applying or create another number simply to clear the message.
After saving, open Notes & History for an affected Stock number and find the observation, so you know it is available where you will need to read it. For additional information or a later observation, make a new row with a new Note number. That adds another observation; it does not overwrite or correct the earlier shared note. Do not change the number merely to make edited text look like a replacement for the original.