When tracking a cross-stitch work in progress, the most common approach is to reduce the entire project down to a single, changeable number. Whether you drag a digital slider from 0% to 100% or erase and overwrite a percentage penciled in the margin of your pattern, this single number is treated as your project’s progress.
But overwriting that number commits a quiet record-keeping error: it erases the historical narrative of how your piece came together. A project that took six months to complete looks identical to one that took six weeks, and the slow, rewarding rhythm of your stitching is lost. To build a system that supports your hobby long-term, it helps to move away from a single overwritten field and adopt a chronological progress timeline instead.
What a Single Overwritten Number Loses
Reducing your tracking to one static percentage strips away two things that keep crafters motivated and organized. First, a static number tells you where you are, but not how fast you got there — without a history of dates and incremental progress, you can’t tell whether your stitching sped up on weekends, slowed down during busy seasons, or stalled on a dense confetti section. Second, it leaves nothing worth sharing. In the needlework community, sharing progress is a big part of the joy, and “I’m at 45%” is far less engaging than “hit 45% today after finally clearing that dark navy border, took three weeks.”
Whether you use a paper journal, a spreadsheet, or an app, preserving these incremental entries turns a simple chore into an archive of your dedication.
What Belongs in a Progress Entry
To build a reliable timeline, each session or milestone should be logged as its own independent entry rather than overwriting a single field. A useful progress entry includes:
- Date: the calendar day you’re recording the progress
- Progress percentage: your cumulative progress on the project, 0 to 100
- Note (optional): what section you worked on, or anything worth remembering
- Photo (optional): a visual snapshot of the fabric at that date
On paper, this means not writing “Progress: 25%” at the top of a page and erasing it repeatedly, but keeping a small table and adding a new row each session — a date, a percentage, and a short note about what you worked on. This simple habit preserves your history without much extra effort.
Deriving Overall Progress from the Latest Entry Instead of a Second Field
A common design challenge with separate progress entries is deciding how to show the project’s overall progress. If a project’s summary says “45% complete” but the latest dated entry says “55%,” the two numbers are out of sync — a small but real data-drift problem.
The fix is to derive the project’s overall progress from the latest entry automatically, rather than maintaining a second number by hand. The system scans every entry tied to a project, finds the one with the most recent date, and uses that entry’s percentage as the current summary value. The key detail is that this has to be driven by the calendar date of the entry, not the order it was typed in. If you finish a stitching session on Friday but don’t log it until Sunday, backdating the entry to Friday should still work correctly, since the system compares dates rather than entry order.
This same idea translates directly to a spreadsheet. Keep one sheet for your dated progress entries and one summary sheet for your projects; on the summary sheet, a formula that looks up the most recent date for a given project and pulls the matching percentage will keep your overview accurate even if you log sessions late or out of order, without you ever copying a number by hand.
What to Do When There Is No Entry Yet
A related edge case: what should the overall progress show for a brand-new project that has no logged entries yet? The intuitive but wrong answer is to force it to zero. A more resilient rule is to let the last known value hold. When a project is created — say, you’re migrating an ongoing piece from a paper system — you can set a starting percentage manually as a baseline. Once a progress entry exists, the summary syncs to that entry’s value as usual. But if every entry for a project were ever deleted, the summary should simply keep its last known value rather than snapping back to zero, so you don’t lose a manually entered estimate just because the underlying log is empty.
Why a Percentage Timeline Fits Better Than a Checklist
Some tracking approaches try to manage craft progress with a to-do list — cut fabric, stitch border, backstitch details. That works for a craft with discrete, sequential steps, but cross-stitch isn’t structured that way. It’s a continuous, cumulative process of filling in a grid of tiny squares, and everyone approaches it differently: some stitchers work one color across the whole fabric before moving to the next (often called “parking” or working “cross-country”), others go page by page through the pattern, and others jump around at random. A task checklist assumes a sequence that doesn’t really exist here, and it goes stale quickly. A percentage timeline doesn’t care which stitches you made — it just records how much of the grid is done on a given date, which fits any stitching style.
FlossLog’s Approach to the Progress Log
FlossLog treats a work in progress as a living record rather than a single number you overwrite. Every entry holds a date, a progress percentage, an optional note, and an optional photo, and you can scroll through a project’s full history as a chronological timeline. The overall progress shown for a project always syncs to the most recent dated entry, so logging a session late or out of order doesn’t throw off your summary. If you ever delete every entry for a project, FlossLog keeps the last known progress value rather than resetting it to zero.
When you want to share your progress, FlossLog generates a card with your latest photo, current percentage, color count, and days spent stitching, ready to post to whichever social platform you use.
The free tier lets you track unlimited projects and progress logs, with a limit only on the number of unique stash colors (up to 50). A single one-time Pro purchase removes that limit and takes the watermark off share cards. Everything runs on your device, with no account and no subscription.
Download FlossLog on the App Store
Summary
A single, overwritten percentage is a missed opportunity to document your crafting journey. By shifting to a dated progress log, you preserve your stitching pace, build a record worth sharing, and keep an accurate summary even when entries are logged late. Percentages, rather than a rigid checklist, are what actually fit the organic way cross-stitch projects come together.
For a broader look at how these records fit into a full recording system, see our hub article: Notebook, Spreadsheet, or App? Tracking Your DMC Floss Stash and Cross-Stitch Projects
This article organizes information from a recording and organizing perspective. If you notice an error or outdated information, please contact us. Last verified: August 2026
