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

Fieldwork workflow works best when you use one clear path: record carefully, back up the same day, annotate in ELAN with consistent rules, and archive with complete metadata. A simple SOP reduces avoidable loss, keeps your files usable, and makes later transcription, analysis, and sharing much easier.

This guide gives you an end-to-end research SOP with recording standards, a 3-2-1 backup plan, file naming, ELAN steps, archiving, metadata, checklists, and failure recovery. You can adapt it for linguistics, qualitative research, oral history, and other field projects.

Key takeaways

• Use a standard setup before every session: test gear, confirm consent, and record in a quiet space.
• Follow a 3-2-1 backup strategy: 3 copies, 2 media types, 1 off-site copy.
• Apply one file naming system across audio, video, notes, photos, ELAN files, and exports.
• Annotate in ELAN with fixed tier names, time alignment rules, and version control.
• Archive only after you complete metadata, integrity checks, and access decisions.
• Prepare for failure before it happens with a recovery plan for lost files and corrupted media.

Why a fieldwork workflow SOP matters

A fieldwork workflow SOP helps you protect data quality from the first recording to the final archive deposit. It also helps teams work the same way across sites, dates, and researchers.

Without a clear process, small mistakes spread fast. A missing consent note, a vague filename, or one skipped backup can make valuable data hard to trust or impossible to use.

This workflow follows a simple chain: Record → Backup → ELAN → Archive. If you keep that order and use the same rules every time, your project stays organized.

Step 1: Record with clear standards

Good archiving starts in the field. If the recording is weak or the context is missing, no later step can fully fix it.

Set recording standards before you leave

• Choose one primary recorder and one backup recorder.
• Carry extra batteries, power banks, cables, memory cards, headphones, and a paper notebook.
• Set device date and time correctly.
• Decide your standard recording format before the trip.
• Prepare participant IDs, session IDs, and consent forms.

Recommended minimum standards

• Audio: use WAV rather than compressed formats when possible.
• Use a consistent sample rate and bit depth across the project.
• Monitor with headphones for noise, clipping, and mic problems.
• Record a short test and listen back before the full session.
• For video, keep framing stable and capture clear sound first.

If you need detailed file format guidance for long-term preservation, the Library of Congress preservation format guidance is a useful reference. Use one project standard and document it in your protocol.

In-session recording rules

• At the start, speak the session ID, date, location, researcher ID, and participant ID on the recording if appropriate.
• Note language, topic, equipment used, and any unusual conditions.
• Keep the microphone close enough for clear speech.
• Pause only when necessary, and note major interruptions.
• Do not rename files in a rushed way on the device if that increases risk.

Recording checklist

• Consent confirmed and documented.
• Recorder time and date checked.
• Battery and storage space checked.
• Test recording completed and reviewed.
• Primary and backup devices ready.
• Session ID written in notebook.
• Environmental noise assessed.
• Field notes started.

Common recording mistakes

• Using different settings on different days without noting the change.
• Saving only to one device.
• Recording without monitoring audio.
• Using filenames like final, new, or test.
• Forgetting to link notes and consent records to the session ID.

Step 2: Back up the same day with the 3-2-1 rule

Your first backup window is the highest-risk moment in fieldwork. Back up the same day, even if the session seems routine.

What 3-2-1 means

• 3 copies of each file.
• 2 different media types.
• 1 off-site copy.

For example, keep the original on the recorder card until verified, copy files to a laptop, then copy them to an external drive, and add an encrypted cloud or remote institutional copy when allowed.

Practical backup sequence

• Copy files from the recorder to an intake folder on your laptop.
• Do not delete originals from the card yet.
• Verify that files open and play.
• Copy the same files to an external drive.
• Create the off-site copy when internet and ethics rules allow.
• Log the backup date, time, operator, and storage locations.

Use checksums and verification

A copied file is not always a good file. Use checksums or file verification tools so you can confirm that copies match the source.

The US National Archives explains why fixity and file verification matter for digital preservation. Even a simple checksum workflow is better than trusting a visual file count.

Backup checklist

• Original media retained until verification.
• Laptop copy completed.
• External drive copy completed.
• Off-site or remote copy scheduled or completed.
• Files opened and spot-checked.
• Checksums created or verification completed.
• Backup log updated.
• Sensitive data encrypted if required.

File naming SOP

Use one naming pattern for everything. A good filename should tell you what the file is without opening it.

• Pattern: ProjectID_SiteID_ParticipantID_SessionID_YYYYMMDD_ItemType_V##
• Example audio: LANG01_SITEA_P023_S01_20260523_AUD_V01.wav
• Example video: LANG01_SITEA_P023_S01_20260523_VID_V01.mp4
• Example notes: LANG01_SITEA_P023_S01_20260523_NOTES_V01.txt
• Example ELAN: LANG01_SITEA_P023_S01_20260523_ANNOT_V03.eaf

Keep names short, avoid spaces, and use leading zeros. Write the rules in one file called naming-convention.txt and keep it in the project root.

Step 3: Annotate in ELAN with consistent rules

ELAN works best when you standardize your process early. If each researcher creates different tiers and labels, later analysis becomes slow and messy.

Create a project template

• Set standard tier names before annotation begins.
• Decide which tiers are alignable and which are referring tiers.
• Define controlled vocabularies for tags where possible.
• Store the template in a shared project folder.

Suggested ELAN tier structure

• utterance
• transcription
• translation
• speaker
• notes
• gesture or context
• verification

Use names that are clear and stable. Avoid creating near-duplicates such as trans, transcript, and transcription in the same project.

Step-by-step ELAN workflow

• Open the verified source media, not an unverified temporary copy.
• Create a new .eaf file using the standard filename pattern.
• Attach linked media with stable relative paths when possible.
• Add document properties and participant information.
• Create annotations on the main utterance tier first.
• Add transcription and translation tiers next.
• Mark uncertain segments with one agreed symbol or tag.
• Save versioned files at defined milestones.
• Export backups of the .eaf file regularly.

Annotation rules to document

• How to segment speech.
• How to mark overlap, pauses, and inaudible sections.
• How to handle code-switching or mixed language data.
• How to mark uncertain hearing.
• How to indicate reviewer changes.
• When to increase the version number.

ELAN checklist

• Correct media file linked.
• Correct template used.
• Participant and session metadata added.
• Main tiers created consistently.
• Segmentation rules followed.
• Version number updated.
• .eaf backup saved to protected storage.
• Review pass completed or scheduled.

If you need help turning recordings into accurate text before annotation, professional transcription services can support a cleaner research workflow.

Step 4: Archive with metadata, context, and access rules

Archiving is more than storing files in a folder. A usable archive needs context, metadata, rights information, and files prepared for future access.

What to archive

• Original recordings.
• Preservation copies and access copies.
• ELAN .eaf files.
• Transcripts, translations, and notes.
• Consent documentation and access restrictions.
• README files, codebooks, and naming rules.
• Checksums and backup logs.

Minimum metadata to capture

• Project title.
• Session ID and file ID.
• Date and location.
• Researcher name or ID.
• Participant ID.
• Language or languages.
• Equipment used.
• File format and duration.
• Consent status and access limits.
• Related files and version history.

Archive preparation steps

• Create a folder structure that separates raw, working, and archive-ready files.
• Add a README at project and session level.
• Normalize filenames before final deposit.
• Include checksums.
• Confirm that linked ELAN media paths still resolve.
• Create access copies when the preservation file is too large or too sensitive for general use.
• Store rights and restriction information with the files, not only in email.

Archive checklist

• All deliverables present.
• Metadata complete.
• Consent and access rules attached.
• Checksums included.
• Folder structure documented.
• README added.
• ELAN links tested.
• Archive deposit reviewed by a second person if possible.

Failure recovery: what to do when something goes wrong

Recovery works best when you act fast and avoid random fixes. Stop, document the problem, protect the original media, and work from copies whenever possible.

Lost files

• Check the recorder, card, laptop intake folder, recycle bin, and recent transfer locations.
• Review your backup log to find the last confirmed copy.
• Stop writing new data to the affected card or drive.
• Clone the affected media before running recovery tools if you have that option.
• Document what is missing by session ID, file type, and last known location.

Corrupted media

• Do not keep opening the original file repeatedly.
• Test the file on a different device or player.
• Compare file size and checksum against another copy if available.
• Try recovery only on a duplicate, not the original.
• Check whether your backup copy opens cleanly.

Broken ELAN links

• Move media and .eaf files back into the documented folder structure.
• Relink media in ELAN and save a new version.
• Add a note in the version log about the relink action.
• Prefer stable relative paths for future work.

Missing metadata

• Use field notebooks, consent forms, calendars, and device timestamps to rebuild context.
• Mark uncertain values clearly instead of guessing.
• Record who reconstructed the metadata and when.

Failure recovery checklist

• Stop using affected media.
• Create a duplicate before repair attempts.
• Consult backup log.
• Check all known storage locations.
• Record incident details.
• Restore from the newest verified copy.
• Review why the failure happened and update the SOP.

How to implement this SOP in a real project

Keep the workflow simple enough that every team member will follow it in the field. The best SOP is the one people can use under pressure.

Suggested project folder structure

• 01_raw
• 02_verified
• 03_working
• 04_elan
• 05_transcripts
• 06_metadata
• 07_archive_ready
• 08_logs

Team roles to assign

• Recorder owner for each session.
• Backup owner for daily transfer and verification.
• Annotation owner for ELAN files.
• Metadata owner for README and session records.
• Archive owner for final deposit review.

Simple daily routine

• Record the session and complete field notes.
• Transfer files before the day ends.
• Verify copies and update the backup log.
• Rename files using the SOP.
• Create the ELAN file and add basic metadata.
• Flag issues while details are fresh.

If your team needs a faster first pass before ELAN review, automated transcription can help create a draft text layer for internal research workflows.

Common questions

Should I delete files from the recorder after copying them?

No. Keep the original until you verify the copied files and confirm that your backup steps are complete.

Which is more important: better audio or better video?

For most speech-based research, clear audio matters more. If you must choose, protect speech quality first.

When should I create the ELAN file?

Create it soon after backup and verification. Early setup helps you add correct metadata while the session is still fresh.

How many versions of an ELAN file should I keep?

Keep versioned milestone saves, not only one rolling file. At minimum, keep a clean initial version, a working version, and reviewed versions.

What if internet access blocks my off-site backup?

Create the local copies first and log the missing off-site step. Complete the off-site copy as soon as you have a safe connection and permission to upload.

Can I change the file naming format midway through a project?

You can, but it creates confusion and broken links. If you must change it, document the migration and update all related files and logs at the same time.

What should go in a README file?

Include the project name, folder structure, naming convention, contact person, software used, version rules, metadata fields, and access restrictions.

A strong fieldwork workflow protects research value at every stage. If you also need transcripts prepared in a consistent, usable format, GoTranscript provides the right solutions through professional transcription services.