Why the iPad Has Become the Default Archive for Grief Research
Grief research is messy. Your data sits across interview transcripts, coded field notes, participant consent forms, and your own reflexive memos. Every single one of these lives in a different folder, or used to, before people started consolidating onto the iPad. The workflow is not glamorous, but it does work if you commit to a system early rather than retrofitting one after you have accumulated months of fragmented files. I run a small qualitative archive focused on bereavement outcomes. What follows is how I actually manage it day to day. I do not pretend this is elegant.
Academic Journal iPad For Grief
That phrase came from a student asking how to keep a single source of truth between her notes and her draft. The short answer is: you do not. What you actually get is a working ecosystem that is occasionally coherent, often sync-conflicted, and always worth the friction. Start by committing to one app for raw field notes and one for structured academic writing. If you try to do both in one place you will lose your citation trail. My setup has been Obsidian for research notes and Word for drafting. Obsidian handles tagging, linking, and backlinks. Word handles peer review and submission formatting. The friction between them is the point. Create a flat hierarchy inside your main folder. Flat means a parent folder for your study and subfolders for each phase. Do not nest deeper than three levels. I learned this after my third month when a backup of a backup of a backup made it impossible to tell which version of a transcript was the final edited file. Use these subfolders:
The numbers enforce order. You can sort alphabetically without second-guessing yourself. I use the Notes app for quick captures during interviews and for transcribing raw quotes in real time. The advantage is that the search function is fast and the handwriting input converts cleanly when I sketch code relationships. For heavier work I switch to Obsidian on the same device. Handwriting and typed notes live separately on purpose. Mixing them in one document breaks the search flow within minutes. When I am coding, I import audio from Zoom or a digital recorder directly into Obsidian as a new note, attach the .m4a file, and insert timestamped quotes. I keep a single codebook note that links to each code using bidirectional links. This takes longer than one might think. The import step alone adds about four to six minutes per hour of audio because of file naming and metadata insertion.
Get the Full Details
Sync and Backup Strategy
iCloud is fine for everyday sync but it will not rescue you from a corruption event. My backup routine uses a local Time Machine drive plus an external SSD that I rotate monthly. I also maintain a separate cloud backup in a different provider so that if one sync service glitches I still have a clean copy. The cost is roughly two dollars a month for secondary cloud storage and the time to verify file counts every Friday. Verify file counts. It sounds trivial. It saved me when a syncing error replaced my entire 03_Analysis folder with an empty placeholder. I caught it because I compared the number of notes in Obsidian against the folder size in Finder.
Version Control Without Losing Your Mind
Use date-stamped filenames for every draft. Format it as YYYYMMDD_StudyTag_Version. Example: 20240812_GriefStudy_V1. This makes sorting reliable and prevents the accidental overwrite that happens when you forget to save before closing an app. When you move a draft forward, duplicate it rather than rename in place. Duplicates keep a fallback even when you make a bad edit. Zotero is the cleanest option if you want to keep references and PDFs together. Export your library regularly to a local folder. Zotero syncs through Zotero Server, not iCloud, and trying to push a large PDF library through iCloud will slow your workflow down noticeably. I keep Zotero on the iPad but store the actual PDF archive on my desktop. The iPad acts as a read interface; the desktop does the heavy lifting. I once spent three weeks dealing with a sync conflict where a participant's coded extract disappeared from Obsidian but remained in the backed-up folder. The root cause was a naming collision: I had copied a note from one project into another without updating its filename. Obsidian treated the duplicate as the same file and then silently dropped one copy during a background sync. The workaround was simple and ugly. I started using a project prefix on every filename, like GRIEF_INT_001 rather than just INT_001. I also run a quick script that scans for duplicate basenames and alerts me before I finish a coding session.
Once your notes are coded, move the analysis forward into Word. Copy the relevant extracts in batches. Do not paste everything at once. Pasting one themed cluster at a time keeps the Word document manageable and reduces formatting drift. Keep a separate spreadsheet for a coding matrix. It will save you when a reviewer asks for the evidence behind a claim. The spreadsheet columns I use are participant ID, theme, quote excerpt, page or timestamp, and analytical memo. That last column is essential. Without it, you lose the interpretive link between the raw data and your argument.
Pitfalls That Are Not Obvious
Handwriting recognition is not a reliable method for coding. You will miss nuances and you will spend more time correcting transcription errors than you gain from the speed of pen. Typed notes are slower to produce but far more searchable. Use handwriting only for sketches and code relationships. Keep text in the main body of your notes. iCloud sync delays can make it look like you have lost work when you have not. Wait ten minutes and refresh before you panic. Most apparent losses are sync lag. Exporting a large Obsidian vault to another program is painful. Keep your vault in a single, well-organized folder and do not embed large media files inside the notes themselves. Put media in the attachments subfolder and reference it with relative links. This keeps the export step from becoming a multi-hour chore.
What the iPad Does Not Solve
The iPad is not a replacement for a serious qualitative analysis program if you plan to submit to journals that require rigorous audit trails. Tools like NVivo or ATLAS.ti still handle large-scale code hierarchies and audit exports more cleanly. If your project stays under fifty participants and your coding is mostly thematic, the iPad workflow is sufficient. If you scale up, you will outgrow the manual linking process quickly. Another limitation is that collaboration on the iPad is awkward. If you are working with co-authors, shared documents on the iPad tend to fragment across devices. Use a shared cloud folder for co-authored drafts and reserve the iPad for individual note-taking and coding.
A Practical Checklist
Before you start a study, commit to the folder structure, install Zotero and Obsidian, and test your sync between the iPad and your desktop. Run a pilot with five transcripts through the entire pipeline. Measure how long the import, coding, and export steps take. If the pilot takes longer than two hours per transcript, simplify your workflow rather than add tools. The goal is a sustainable process, not a feature-complete one. This workflow is not a luxury. It is a constraint that forces discipline. Grief research moves fast emotionally and slow technically. Keeping the two sides separate in a structured way is the only thing that prevents burnout and lost data. I have seen both happen to people who thought they could wing it.
