Fieldwork Workflow: Record → Backup → ELAN → Archive (Research SOP)

Fieldwork workflow works best when you treat recording, backup, annotation, and archiving as one system. A strong research SOP helps you capture clear audio, protect files with a 3-2-1 backup plan, annotate in ELAN, and archive material so others can find and use it later. This guide gives you an end-to-end process with practical checklists, naming rules, metadata fields, and failure recovery steps.

• Key takeaways
• Use one standard workflow from recording to archive so files stay consistent and easy to manage.
• Record in a stable format, document context at the time of capture, and verify files before leaving the site.
• Follow the 3-2-1 backup rule: 3 copies, 2 media types, 1 copy off-site.
• Set clear file naming and metadata rules before fieldwork starts.
• Build ELAN annotation steps into your SOP so transcription and analysis stay organized.
• Plan for failure recovery before problems happen.

Why a fieldwork workflow matters

A field recording is easy to lose and hard to recreate. Good workflow reduces avoidable risk and saves time later when you transcribe, annotate, share, or archive your data.

Your SOP should answer five questions: what you record, how you name it, where you store it, how you annotate it, and how you preserve it. If your team can answer those questions the same way every time, your project will run better.

Stage 1: Record with clear standards

Set recording standards before anyone enters the field. This avoids mixed formats, missing notes, and audio that is hard to transcribe or annotate.

Recommended recording standards

• Use uncompressed WAV for the master file.
• Record at one project-wide sample rate and bit depth, such as 48 kHz/24-bit, and keep it consistent.
• Use an external microphone when possible.
• Monitor with headphones during a test recording.
• Keep phone or camera recordings as secondary copies, not your only master, unless your project requires mobile-only capture.
• Record a spoken slate at the start: date, location, session ID, speaker code, and recorder name.

What to capture in your field log

• Project name
• Session ID
• Date and local time
• Location
• Researcher name
• Speaker or participant codes
• Language or variety
• Equipment used
• Consent status and restrictions
• Notes on noise, interruptions, and recording conditions

Recording checklist

• Batteries charged and spare power packed
• Storage media formatted and tested
• Recorder clock set correctly
• Microphone tested
• Headphones packed
• Consent materials ready
• Session ID assigned before recording starts
• Test clip recorded and reviewed
• Field log started before the interview or session
• File reviewed after recording ends

Common recording mistakes

• Using different formats across devices
• Relying on automatic gain without checking levels
• Skipping a test recording
• Not documenting who is speaking
• Leaving the site before verifying playback

Stage 2: Back up files with the 3-2-1 rule

Back up files as soon as possible after each session. The 3-2-1 rule means you keep 3 copies of your data on 2 different media types, with 1 copy stored off-site.

The U.S. National Park Service describes 3-2-1 as a practical baseline for digital preservation in its guidance on personal digital archiving: 3 copies, 2 kinds of media, 1 copy offsite. That principle fits fieldwork well because travel, device failure, and theft are all real risks.

A simple 3-2-1 setup for research fieldwork

• Copy 1: Original recording on the recorder or source card
• Copy 2: Working copy on a laptop or external SSD
• Copy 3: Off-site encrypted copy in approved cloud storage or a remote institutional server

Backup SOP steps

• Transfer files immediately after recording or at the end of the day
• Do not delete the source card until you verify at least two additional copies
• Use checksum verification if your team supports it
• Store raw masters as read-only once copied
• Keep working files separate from preservation masters
• Log every transfer in a backup sheet

Backup checklist

• Original file present on source media
• Copy created on local drive
• Copy created off-site
• File size and duration checked
• Random playback spot-check completed
• Checksums created or verified if used
• Transfer logged with date, time, and staff initials
• Source media retained until all checks pass

File naming convention that scales

Choose one naming rule and enforce it. Good names make sorting, annotation, and archiving much easier.

• Use only letters, numbers, hyphens, and underscores
• Avoid spaces and special characters
• Put the most stable identifiers first
• Use ISO-style dates: YYYY-MM-DD
• Keep speaker names out of filenames if privacy matters; use participant codes instead

Example: projA_LOC03_2026-04-18_sess02_spkP01_audio.wav

Related files should share the same base name.

• projA_LOC03_2026-04-18_sess02_spkP01_audio.wav
• projA_LOC03_2026-04-18_sess02_spkP01_notes.txt
• projA_LOC03_2026-04-18_sess02_spkP01.eaf
• projA_LOC03_2026-04-18_sess02_spkP01_metadata.csv

Stage 3: Annotate in ELAN without losing structure

ELAN works best when your project has a fixed annotation plan. Decide your tiers, labels, and export needs before the team starts annotating.

Set up an ELAN template

• Create a template with standard tiers for every session
• Use a clear naming rule for tiers, such as speakerA_utterance, speakerA_translation, and comments
• Define who can add or edit each tier if multiple researchers work on the same files

Suggested ELAN tier structure

• Utterance or transcription tier
• Translation tier
• Morpheme or gloss tier if needed
• Speaker ID tier
• Comments or uncertainty tier
• Consent or restriction note tier if your workflow requires it

Step-by-step ELAN workflow

• Open the verified working copy, not the preservation master
• Create a new .eaf file using your template
• Link the media file and confirm the path works
• Save the .eaf file with the same base name as the recording
• Segment the audio into manageable annotation units
• Add transcription on the main tier
• Add translation, notes, and other dependent tiers
• Mark unclear audio consistently, such as [unclear] or a project-approved tag
• Save often and back up the .eaf file after each session
• Export review files if your team needs plain text or tabular output

ELAN quality checks

• Correct media linked
• Tier names match the project template
• Time alignment checked at the start, middle, and end of the file
• Unclear segments tagged consistently
• Speaker codes match field log and metadata sheet
• .eaf file backed up with the rest of the session materials

When to use outside transcription support

If your team needs help turning recordings into text before annotation, a clean transcript can speed up ELAN work. For projects that need human review, professional transcription services can fit into the workflow before detailed annotation starts.

Stage 4: Archive with metadata that others can understand

Archiving is not just storage. It means preserving files, context, permissions, and documentation so the material stays usable later.

What to archive

• Preservation master audio files
• Access copies if you create them
• ELAN .eaf files
• Field notes and session logs
• Consent records and access restrictions
• Project readme file
• Metadata spreadsheet or database export
• Any transcripts, translations, or caption files

Core metadata fields

• Project title
• Session ID
• File name
• Date created
• Location
• Language
• Participant code
• Collector or recorder
• Equipment
• File format
• Duration
• Consent status
• Access level and restrictions
• Related files
• Notes on processing and annotation status

Archiving checklist

• Master and access files separated
• All related files use the same base name
• Metadata complete for every session
• Readme explains folder structure and abbreviations
• Consent and restriction data stored securely
• Archive package tested before submission
• Long-term storage location documented

Folder structure example

• /project_name/
• /project_name/audio_master/
• /project_name/audio_access/
• /project_name/elan/
• /project_name/notes/
• /project_name/metadata/
• /project_name/consent_restricted/
• /project_name/readme/

If your recordings will be shared as video or public educational media, you may also need closed caption services or subtitles as separate access files.

Failure recovery: what to do when something goes wrong

Failure recovery belongs in the SOP, not in a panic after data loss. Define the response steps now so the team acts fast and consistently.

If files are missing

• Stop writing new data to the source device or card
• Check whether the file was renamed or moved
• Compare the field log, transfer log, and backup sheet
• Look for copies on the recorder, laptop, external drive, and off-site storage
• Document what is missing, when it was last seen, and who handled the transfer

If media is corrupted

• Do not keep opening the file repeatedly on different apps
• Create a bit-level copy or duplicate of the storage media if your team has the skill and tools
• Work only on copies, not the original medium
• Try recovery from the verified backup first
• Log all actions taken

If the ELAN file breaks or loses links

• Check whether the media path changed after files were moved
• Restore the most recent backup of the .eaf file
• Relink media using the same base file naming rule
• Export plain text or tabular snapshots during annotation so work exists in more than one form

If a device is lost or stolen

• Report the loss under your institution's policy
• Revoke access if the device synced to cloud tools
• Confirm whether encrypted backups exist
• Review whether consent terms require participant notification

Failure recovery checklist

• Incident documented
• Original media protected from further writes
• All backup locations checked
• Team lead notified
• Recovery actions logged step by step
• SOP updated after the incident review

Decision rules that make the SOP easier to follow

People follow simple rules better than vague advice. Add clear decision points to your SOP so team members do not have to guess.

• If audio is unique and irreplaceable, make backups before any editing or annotation.
• If consent is limited, store identifying files and recordings separately.
• If a file fails verification, do not delete the source copy.
• If multiple team members annotate, use one ELAN template and one version naming rule.
• If you create derivatives, keep masters untouched and documented.

Common questions

What is the best audio format for fieldwork masters?

Use an uncompressed format such as WAV for the master when possible. It is easier to preserve and process later than a heavily compressed file.

How soon should I back up field recordings?

Back them up as soon as possible after each session. At minimum, do it the same day and before you reuse the card or leave the only secure location available to you.

Should I annotate directly on the master audio file?

No. Keep the preservation master untouched and annotate from a verified working copy.

What should go in a fieldwork filename?

Include the project, date, location or session, and participant or speaker code if needed. Keep the pattern consistent across audio, notes, ELAN files, and metadata.

How many ELAN tiers do I need?

Only the tiers your project will actually use. Start simple, then add more only when they serve a clear research purpose.

What metadata matters most for archiving?

At minimum, record who created the file, when and where it was made, what it contains, what format it uses, and what access limits apply.

What if I only have one device in the field?

Use it, but reduce risk in other ways. Verify files after recording, transfer them quickly, and create your second and third copies as soon as you can.

Final SOP summary

A reliable fieldwork workflow is simple to state: record well, back up fast, annotate in a standard way, and archive with full metadata. The more your team uses the same steps every time, the safer and more useful your research materials become.

If you need transcripts, captions, or related language support as part of that workflow, GoTranscript provides the right solutions, including professional transcription services that can fit naturally into your research process.