Describe your fieldwork and required evidence. Makeform creates a mobile-friendly field notes form with observation prompts, time, location, photos, issue flags, and follow-up ownership.
Route field notes to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a workflow, revise the prompt, or send it to the builder. The structure is an example, not a live AI result.
Audience
Researchers recording site observations
Format
Observation log with media
Prompt size
267 chars
Example form structure
Observation log with media
Researcher, site, date, and visit time
Weather and site conditions
What did you directly observe?
Supporting photos or audio
Follow-up question and owner
Suggested routing tags
Routine observation
Follow-up needed
Urgent issue
Use one submission per observation when photos and owners must stay attached to one issue.
Step 1
Locate
site, asset, area, date, and observer
Step 2
Observe
facts, conditions, readings, and context
Step 3
Document
photos, files, severity, and interpretation
Step 4
Route
owner, due date, status, and handoff
Why structured field notes
A field notes form prompts every observer for location, evidence, severity, and next action, making entries easier to compare and hand off.
Site, area, observer, time, and category keep every note anchored to its context.
Separate direct observation, interpretation, and open questions so reviewers can distinguish evidence from inference.
Issue status, owner, and due date turn an observation into a trackable handoff.
Made for work away from a desk
Choose a scenario, then replace its categories, asset lists, and escalation rules with your team's language.
Log setting, participants or materials present, direct observations, reflective notes, media, and questions for the next visit.
Record the area inspected, condition rating, measurements, access constraints, defects, photos, and recommended corrective action.
Capture trade activity, crew and equipment context, progress, conversations, obstructions, site photos, and items that need coordination.
Connect symptoms, readings, troubleshooting, parts, completed work, unresolved issues, and customer handoff to a specific asset.
Build your field workflow
Capture observations in the field and make each result clear enough for another person to act on.
Describe who is in the field, what they observe, and what the reviewer must decide.
Edit categories, ratings, measurements, and required fields so observers record comparable information.
Run a sample entry, shorten long prompts, and check that evidence fields are fast to complete.
Send submissions to the inbox or a connected workflow for triage and follow-up.
Form vs notebook vs open document
Recurring fieldwork needs consistent identifiers, evidence, and ownership while preserving space for narrative.
Field guide
These six sections preserve the context, evidence, and decisions another person needs.
Visit identity
Stable identifiers make filtering possible and keep each note attached to its subject.
Conditions
Conditions explain why visits differ. Use choices for recurring factors and a note for anything unusual.
Observation
Prompt for concrete details before conclusions. A separate interpretation field keeps the evidence visible.
Classification
Controlled choices make submissions sortable without replacing narrative. Match them to real field decisions.
Supporting evidence
Keep uploads with the note that names their subject. Ask for captions when areas look similar.
Next action
Capture the requested response, owner, and target date separately. Allow a no-follow-up-needed choice.
Related tools
Pair field notes with focused forms when a workflow needs its own questions.
Guide safety checks with ratings, findings, and actions.
Open toolDocument behaviors, hazards, positive observations, and follow-ups.
Open toolCapture property conditions, defects, photos, and work.
Open toolRecord asset condition, readings, defects, and maintenance needs.
Open toolCollect event details, response, attachments, and review notes.
Open toolFAQ
Answers for teams replacing inconsistent field notes.
A field notes form records observations at a site, property, route, or asset. It combines observer, location, time, category, and status with narrative, measurements, media, and follow-up ownership.
Include project, observer, time, site and area, conditions, category, factual description, measurements, attachments, and status. For action items, add severity, recommended response, owner, and due date.
Separate direct observation from interpretation. Record what was seen, heard, counted, or measured, including limitations. Use another field for hypotheses or questions so reviewers can distinguish evidence from inference.
Yes. Publish a link and open it in a phone or laptop browser. Keep required questions focused and test a realistic submission on the device people carry.
Yes. Add uploads for photos, sketches, audio, instrument output, or documents. Ask for a caption so reviewers know which area or finding each attachment supports.
Use one submission per visit when findings share a handoff. Use one per observation when each issue needs separate photos, severity, owner, due date, or resolution status.
Add severity, recommended action, owner, and due date fields. Send submissions to the team inbox or a connected workflow so urgent issues can be separated from routine notes.
Yes. Makeform is unlimited free for creating, editing, publishing, and collecting field notes form submissions. The paid tier removes the Makeform badge.
Make every site observation easier to use.
