For Environmental Scientist / Sustainability Analysts ·
What you'll accomplish
Your rough notes make sense to you at 1400 and look like code by Monday. A saved Gemini Gem takes those notes and returns them in your firm's field log layout, with every time and reading kept exactly as you wrote it and every gap marked. It adds nothing and interprets nothing. You compare the log with your notes line by line and sign it.
Note: Google is replacing Gems with skills. Per Google's support page, Gems become skills starting in November 2026 for personal Google Accounts and in 2027 for work and school accounts, and existing Gems are recreated as skills automatically. The instructions below work the same way as a skill.
What you'll need
Data caution. Field notes from a real site can carry site names, addresses, client names, well locations tied to a client and photo references. Those stay in the firm's approved systems. This Gem works on invented notes and on notes that use codes and placeholders such as "[Client]", "Site S-01" and "MW-2". Before you paste real notes, check whether your firm and the client approve Gemini for that data. Also check Gemini's activity and data settings for whether chats are kept or used to improve Google's models. If your notes mention photos, strip location data from the photos before they go anywhere outside the firm's systems.
What you should see: A short list of column names you can paste.
What you should see: A form with a name box and an instructions box. It may also offer a place to add knowledge files. Troubleshooting: If you see a Skills area instead of Gems, your account has moved to skills. Create a new skill and paste the same name and instructions.
Turn my rough field notes into a daily field log table with these columns: Time, Location, Activity, Observations, Samples collected, Deviations.
Keep every time, number, reading, sample ID and unit exactly as I wrote it. Do not round, convert or correct anything.
If a column has no information in my notes, write [not in notes] in that cell.
Never add, infer or interpret an observation. Do not describe colors, odors or conditions in new words. Copy my wording.
Do not decide whether anything was a deviation. Put an item in Deviations only if my notes call it one.
Do not explain site conditions, health and safety, or regulatory matters.
After the table, list questions for me: every [not in notes] cell, every unclear abbreviation, and every note that could mean two things.
Label the output "Draft field log for my review".
What you should see: "Field Notes Cleaner" listed under your Gems. Troubleshooting: If the output starts adding sentences of its own, tighten the third and fourth lines of the instructions and save again.
Invented practice notes:
MW-2 purged ~25 min, water clear after 15, slight odor, sample 1140, dup? no; MW-5 dup collected 1305, tubing replaced
What you should see: A table close to this one.
| Time | Location | Activity | Observations | Samples collected | Deviations |
|---|---|---|---|---|---|
| [not in notes] | MW-2 | Purged ~25 min | Water clear after 15. Slight odor. | Sample 1140. Dup? no. | [not in notes] |
| 1305 | MW-5 | Dup collected. Tubing replaced. | [not in notes] | Dup collected 1305 | [not in notes] |
Below the table, expect questions such as: What was the start time for MW-2? Was "15" in "clear after 15" minutes? Were sample IDs assigned for the MW-2 sample and the MW-5 duplicate? Was replacing the tubing a deviation from the work plan, or routine?
Troubleshooting: If the Gem turned "slight odor" into a different description, the instructions need to be tightened. Your field log keeps your wording.