Storage and Autosave

Swiftscore automatically saves your work as you go, so you can focus on observing, writing, and coaching without worrying about losing progress.

How autosave works

As you type notes, score components, or build out a draft, Swiftscore saves your changes in the background. You don't need to click a save button — your edits are captured shortly after you stop typing or making changes, and again if you've made continuous changes for a longer stretch.

If you navigate away from a page, switch tabs, or your device goes to sleep mid-edit, Swiftscore makes a final attempt to save your latest changes before you leave. This means closing a tab or backgrounding the app on your phone doesn't put your most recent edits at risk.

Draft creation

When you start a new evaluation or coaching conversation, your work is saved as a draft automatically once you've entered enough content for it to be meaningful (a few words or more). As you continue filling out details — like the teacher, framework, components, or date — those updates are captured too, not just the narrative text.

If you save twice in quick succession (for example, by clicking "Save Draft" more than once), Swiftscore is built to prevent that from creating duplicate drafts.

Editing an evaluation

While you're editing an existing evaluation report, changes are saved very quickly — within a fraction of a second of you pausing — so that detailed inline edits aren't lost. Behind the scenes, Swiftscore also runs a second, slightly less frequent save pass as a safety net.

If your edits don't reach the server right away, your data isn't lost: Swiftscore also keeps a local copy of your evaluation while you work, so if a save is delayed or the connection hiccups, your content is preserved and recoverable.

Working notes during an observation

Notes you take in the observation notes editor are saved using the same reliable autosave path as evaluations, so your in-the-moment notes are protected just as well as a full report.

Settings

Changes you make to your profile and account settings are saved automatically a couple of seconds after you stop editing, and are also flushed if you navigate away before that window completes — so a quick settings change followed by leaving the page won't be lost.

AI-assisted prep

Before you start an observation or conversation, Swiftscore can prepare a short briefing pulling in relevant history — past evaluations, ongoing goals, and earlier conversations with that teacher. This is generated and cached for you automatically; there's nothing to save here, it's ready when you open the flow.

Summative aggregation preview

When you're building a summative evaluation, Swiftscore shows you a preview of the formative observations that will be rolled up into it, including the date range and how much content is being aggregated, so you know exactly what's feeding into the summative before you finalize it.

Handling save conflicts

Swiftscore protects against accidentally overwriting someone else's edits. If two people (or two open tabs/devices) try to save changes to the same evaluation at the same time, Swiftscore detects the conflict and lets you know with a clear message:

"Someone else edited this evaluation. Your changes were not saved. Please refresh to load the latest version."

If you see this message, refresh the page to load the latest version before continuing your edits.

When your connection is unstable

If your internet connection drops or becomes unreliable while you're working, Swiftscore will retry saving your changes automatically. If saving keeps failing after repeated attempts, autosave is temporarily paused and you'll see a message letting you know:

"Auto-save temporarily disabled due to connection issues. Your changes are saved locally."

Your work isn't lost in this situation — it's held locally on your device until a connection is reestablished.

Audio recordings

During a live observation, audio is recorded and stored directly on your device while the session is in progress, so brief network interruptions during recording don't put your audio at risk. Your device keeps the recording, related notes, and transcript pieces together as you go. If your browser is in private/incognito mode or runs low on storage, Swiftscore falls back to a temporary in-memory store so recording can continue without interruption. Once your observation session ends, the audio is uploaded and stored securely.

File attachments

When you upload files — like PDFs or images — to an evaluation, Swiftscore stages the upload and only finalizes it once the file is fully and successfully received. If an upload fails partway through, the partial file is cleaned up automatically rather than left behind in a broken state.

Why this matters

Persistence is one of the most heavily tested parts of Swiftscore. Whether you're mid-observation with a flaky connection, juggling multiple tabs, or stepping away from your laptop mid-edit, the autosave system is designed so that your evaluation work, notes, and settings are captured reliably and recovered automatically when something goes wrong.