HelloForms
Research · free template

Observation Log Form

Structured field notes: what was observed, when, how often and what the observer inferred.

A ready-to-use research & data collection form for small teams who need a reliable intake process: 17 questions, 3 pages, 3 conditional rules.

Questions
17
Pages
3
Layouts
classic
Conditional rules
3
Preview it in the gallery

Searches this template answers

Also filed under

Live preview and test console

This is the real form. Answer it to test the 2 conditional rules — nothing is sent or stored.

Page 1 of 3 — Observation setup

Observation log

Every question on this page is currently visible.

Compliance checklist

Ready to publish
  • Payment items priced — passingEvery payment question charges a real amount, so a submission always records a payment.
  • Conditional logic resolves — passingEvery rule points at a question or page that exists in this template.
  • Legal text not required — passingThis template collects neither health nor regulated financial information.
  • Question labels unique — passingLogic and exports address questions by label, so duplicates are ambiguous.

What happens after submit: nothing is stored in this preview. On your own copy, every response triggers an instant email notification and lands in your response dashboard, ready to export or forward.

Happy with it? Take a copy into your workspace — every question, rule and setting comes with it.

Who this template is for

Observation Log Form is built for small teams who need a reliable intake process who need to collect the same complete information from everyone.

  • Small teams who need a reliable intake process working in research & data collection.
  • Teams who need to collect the same complete information from everyone without writing code or paying for a custom build.
  • Anyone replacing chasing missing details over email with one structured record per enquiry.
  • Respondents are the people you send it to — the form asks them 17 questions across 3 screens.

Why this form is useful

It removes the cost of chasing missing details over email and turns each submission into a record your team can act on immediately.

  • 9 questions are required, so submissions arrive complete instead of needing a follow-up email.
  • It accepts a document or photo upload as evidence.
  • It pins the request to a specific date.
  • It allows multiple selections without free text.
  • It captures a numeric value you can filter and sort on.
  • Conditional logic hides 3 questions until they are relevant — shorter forms convert better than long ones.
  • Splitting the form across 3 pages keeps each screen short and shows respondents how much is left.
  • Every response is stored, searchable and exportable, so nothing depends on one person's inbox.

How to use this template

From copy to live form is a few minutes of work, and every step is reversible.

  1. 1Press “Use this template” — a fresh copy of Observation Log Form lands in your workspace, ready to edit.
  2. 2Rename or delete any question, and change what is required. Nothing here is fixed.
  3. 3Open Notifications and add the email addresses that should be alerted on each submission; add an auto-reply to the respondent if the form collects an email address.
  4. 4Check the upload limits on the file question so respondents can attach what you actually need.
  5. 5Publish it, then either share the link directly or paste the embed snippet into your site — the embedded form resizes to fit and loads no marketing or advertising trackers.
  6. 6Watch responses land in Submissions, where you can filter, label and export them to CSV or PDF.

Logic and conditions blueprint

Exactly how this form behaves as it is answered — 3 conditional rules ship with it.

  • Features advanced show logic: if “Did your presence appear to change what people did?” is Yes, the form dynamically exposes “How did your presence change things?”. Otherwise that question never appears.
  • Features advanced show logic: if “Was anything observed that needs escalating?” is Yes, the form dynamically exposes “What needs escalating?”. Otherwise that question never appears.
  • Features conditional validation: if “Was anything observed that needs escalating?” is Yes, “What needs escalating?” becomes mandatory before the form can be sent.
  • All 3 rules are editable in the Logic tab, and the built-in checker warns about rules that contradict each other.

About this template

Observation produces useful data only when every observer records the same things in the same way, and this log exists to enforce that. Each entry is one observation window rather than a whole session, so frequencies mean something: the observer records where they were, the start and end time, how many people were present and whether the observation was overt or covert. Behaviours are logged as counts against a fixed list, which is what makes two observers comparable, and there is a separate free-text box for anything the list did not anticipate. The most important structural choice is the split between description and interpretation: one box for what was seen and heard in plain language, a second, clearly labelled box for what the observer thinks it meant. Keeping them apart is what allows a supervisor to challenge an inference without discarding the observation. A photo or sketch can be attached where the physical setting matters, and a flag marks any entry where the observer's presence visibly changed behaviour, since that is a limitation you will need to report rather than hide.

What this form asks

Every question is editable — rename it, make it optional, or delete it entirely.

Page 1 — Observation setup

  • Observer namerequired
  • Site or settingrequired
  • Daterequired
  • Window start timerequired
  • Window end timerequired
  • Observation typerequired
  • Approximate number of people present

Page 2 — What happened

  • Behaviours observed in this window
  • Count — asked for help
  • Count — left before being served
  • Description — what did you see and hear?required
  • Photo or sketch of the setting

Page 3 — Interpretation

  • Interpretation — what do you think it meant?
  • Did your presence appear to change what people did?required
  • How did your presence change things?
  • Was anything observed that needs escalating?required
  • What needs escalating?

17 questions in total.

How the form changes as it's filled in

This template ships with 3 conditional rules, grouped into 3 behaviours driven by 2 questions. Everything below is already set up — edit or delete any rule once the template is in your workspace.

Driven by “Did your presence appear to change what people did?”

  • Reveals questions

    If “Did your presence appear to change what people did?” is Yes, the form reveals “How did your presence change things?”.

Driven by “Was anything observed that needs escalating?”

  • Reveals questions

    If “Was anything observed that needs escalating?” is Yes, the form reveals “What needs escalating?”.

  • Makes answers required

    If “Was anything observed that needs escalating?” is Yes, “What needs escalating?” becomes required before the form can be submitted.

Set it up step by step

  1. 1

    Define the behaviours first

    Write a one-line definition for each behaviour on the list and share it with every observer before fieldwork.

  2. 2

    Log one window per entry

    Submit a separate entry for each observation window so counts stay comparable.

  3. 3

    Separate seeing from thinking

    Descriptions go in the description box; anything starting 'they seemed' belongs in interpretation.

  4. 4

    Check agreement early

    Have two observers log the same window on day one and compare before the rest of the fieldwork runs.

  5. 5

    Export and aggregate

    Download all entries and sum counts by site and time band rather than by observer.

Mistakes to avoid

  • Writing interpretations in the description box, so nobody can tell later what was actually seen.
  • Logging a whole session as one entry instead of timed intervals.
  • Changing the definition of a behaviour part-way through fieldwork.

What it pairs with

Most teams don't run this form on its own. These are the forms and systems it sits next to.

What to do with the responses

Combine the logs from every observer, check inter-observer agreement on the coded behaviours, and only then summarise frequencies.

Works in this layout

Browse classic templates

Forms that overlap this one

These pages cover the same subject ground as the observation log form, matched on the words people actually search for.

Frequently asked questions

Overt or covert observation — which should I use?

Overt unless a research ethics committee has approved otherwise. Covert observation of identifiable people raises consent problems this form cannot solve for you.

How long should an observation window be?

Ten to twenty minutes is typical. Long enough to see a pattern, short enough that counts stay accurate.

Why separate description from interpretation?

Because a reader six months later cannot unpick them. Descriptions can be re-analysed; interpretations can only be trusted or discarded.

Can several observers use the same form?

Yes, and they should — the observer name field is what lets you check agreement between them.

Is the Observation Log Form template free to use?

Yes. You can preview and test Observation Log Form on this page without an account, and take a copy into your own HelloForms workspace on the free plan. There is nothing to install and no card required to publish it.

What does the Observation Log Form template ask for?

It asks 17 questions across 3 pages, 9 of which are required. Every question is listed in full further down this page, and each one can be renamed, reordered, made optional or deleted after you copy the template.

Can I edit the Observation Log Form form after copying it?

Yes — the copy is entirely yours. Change wording, add or remove questions, switch between the classic layout, restyle it to match your brand, and set who gets notified on each submission.

How does the conditional logic in this research & data collection form work?

3 conditional rules ship with the template: Features advanced show logic: if “Did your presence appear to change what people did?” is Yes, the form dynamically exposes “How did your presence change things?”. Otherwise that question never appears. Features advanced show logic: if “Was anything observed that needs escalating?” is Yes, the form dynamically exposes “What needs escalating?”. Otherwise that question never appears. Features conditional validation: if “Was anything observed that needs escalating?” is Yes, “What needs escalating?” becomes mandatory before the form can be sent. All rules are editable in the Logic tab.

Where do responses to the Observation Log Form form go?

Submissions land in your workspace under Submissions, where you can search, filter, label and export them to CSV or PDF. You can also email a notification to your team on every submission and send the respondent an auto-reply.

Can I embed the Observation Log Form form on my own website?

Yes. Publish the form and paste the embed snippet into any page or share the direct link. The embedded form resizes to fit its container and loads no advertising or marketing trackers inside the iframe.

Can respondents upload files?

Yes. This template includes a file upload question, so respondents can attach documents or photos with their answers. You can adjust the accepted file types and size limits on that question.

Related templates

More forms teams pair with the observation log form.

Related categories

All Research & Data Collection templates