Fieldnote reports captured events and researcher annotations. It does not infer emotion, intent, demographics, accessibility status, design quality or causation.
Before a session
- Create a Fieldnote Study data asset.
- Enter a stable study name and one research question.
- Add ordered tasks with a stable ID, participant prompt, observable success definition and sensible suggested time limit.
- Decide which task outcomes and researcher observations the study needs. This version records task timing and notes, not player paths or screenshots.
- Use pseudonymous participant labels. Do not enter names, email addresses, passwords, payment data or private chat content.
Fieldnote rejects incomplete plans, duplicate task IDs and fields outside its documented limits.
Run the session
Connect your project to the Fieldnote Session Subsystem using Blueprint or C++. Your integration supplies the outcomes and observations; Fieldnote does not detect them automatically.
- Start a session with the accepted plan, pseudonymous participant label and build label.
- Start each task when the participant begins it.
- Record Succeeded, Failed, Abandoned or Not Observed.
- Add concise timestamped observations, friction points, questions, positive moments, defects or researcher notes.
- End the session cleanly.
Each accepted change is checkpointed locally. If a checkpoint cannot be written, the operation reports an error and rolls back its in-memory change. Handle that result in your integration before proceeding.
Recover an interrupted session
The Fieldnote workspace identifies sessions that did not end cleanly. Your Blueprint or C++ integration can resume a saved incomplete session through ResumeInterruptedSession. Recovery adds an explicit marker. Existing timestamps remain intact and subsequent evidence continues from the last recorded task or marker time.
Review and export
An accepted export creates a self-contained folder under Saved/Fieldnote/Exports/<session-id>/ containing an offline HTML report, task CSV, marker CSV and versioned JSON evidence file. Review every file before sharing it. Fieldnote does not upload the files automatically.
Potential formula-like text is prefixed with an apostrophe in CSV exports. Import CSV text columns as text; spreadsheet save/reopen behaviour can vary. Use session.fieldnote.json for the original recorded text.
Privacy and retention
The project owner controls access, retention and deletion. Document those rules before a study begins. Fieldnote does not provide recruitment, participant consent management, video conferencing, biometric analysis or cloud device management.
Current compatibility boundary
Fieldnote 1.0.0 supports Unreal Engine 5.8 on Windows in the editor and in Win64 Development playtest builds.
Need help?
Read the Fieldnote support guidance. Never send passwords, payment data or unredacted participant information.