Beyond spreadsheets
Keep the rules your team relies on while reducing repeated entry and manual handoffs around a spreadsheet.
Start a projectKeep the useful rules
A spreadsheet can be a good place to calculate, explore and share information. Replacing one makes sense when a specific workflow needs more control: who can change a field, which status can come next, or what must be checked before a job moves on.
The starting point is the workbook's actual use. Formulas, lookup tables, manual corrections and notes can all contain business rules. We check whether existing software or a connection can support those rules before building a new tool. Jacky Pham owns the agreed project through delivery and handover, from Snoogz's Port Coquitlam base and remotely.
A small trial import
This example starts with five imported rows. One repeats a job ID; another has no owner. Importing every row without checking would create two records for the same job and leave one job unassigned.
Check the imported rows
Synthetic job records, shown before review and after correction. These are fixed views of the sample data.
5 source rows. The repeated job and missing owner are kept visible.
| Source row | Job ID | Work | Owner | State |
|---|---|---|---|---|
| 1 | J-101 | Label storage shelves | Alex | New |
| 2 | J-102 | Replace meeting-room cable | Sam | In progress |
| 3 | J-102 | Replace meeting-room cable | Sam | In progress |
| 4 | J-103 | Check lobby display | — | New |
| 5 | J-104 | Archive completed job | Alex | Done |
5 input rows = 3 ready + 2 held for review.
| Source row | Job ID | Work | Owner | State | Check |
|---|---|---|---|---|---|
| 1 | J-101 | Label storage shelves | Alex | New | ReadyReady for the trial import |
| 2 | J-102 | Replace meeting-room cable | Sam | In progress | ReadyReady for the trial import |
| 3 | J-102 | Replace meeting-room cable | Sam | In progress | HeldDuplicate job ID; matches source row 2 |
| 4 | J-103 | Check lobby display | — | New | HeldMissing owner |
| 5 | J-104 | Archive completed job | Alex | Done | ReadyReady for the trial import |
Duplicate IDs and missing owners are held for review. Every source row remains visible.
4 unique records + 1 excluded duplicate = 5 source rows accounted for. 0 unresolved checks.
| Source row | Job ID | Work | Owner | State |
|---|---|---|---|---|
| 1 | J-101 | Label storage shelves | Alex | New |
| 2 | J-102 | Replace meeting-room cable | Sam | In progress |
| 4 | J-103 | Check lobby display | Sam | New |
| 5 | J-104 | Archive completed job | Alex | Done |
Source row 3 (J-102) is an exact duplicate of row 2. It is excluded from this output and remains in the raw sample.
J-103 now has Sam as its owner, an explicit choice for this example.
Download either version to compare the records. The raw file retains the excluded duplicate.
That count is only one check. We also compare job IDs, owners and statuses with the intended output. An import can have the right row count and still put the wrong information in a field.
Check before switching
A trial import should use a copy of the data. We map columns, identify record IDs and define how blank values, duplicates and old statuses are handled. Rows that need a decision stay visible rather than disappearing into an error total.
After correction, staff can compare representative jobs and reports against the current workbook. We agree on the checks that must pass, who signs them off and when the old workflow stops accepting updates. If both systems are used during review, one needs to remain the authoritative record so edits do not drift apart.
The switch also needs a recovery plan. Keep a known starting copy, record what was imported and decide how to return to the previous workflow if the agreed checks fail. The details depend on how much new work arrives during the move.
Decide who can change what
A shared application can assign work, validate fields and record status changes, but those rules have to be specified. For the sample tracker, we would decide who assigns an owner, whether a completed job can reopen and who can correct an old record.
We also identify the exceptions. A job may have no owner yet, a duplicate may turn out to be a separate visit, or a field may be blank for a valid reason. Staff need a way to resolve those cases without inventing a workaround outside the tool.
Keep a way out
Exports, field definitions and instructions for running the tool belong in the scope. An export should contain enough context to understand the records outside the application, with agreed identifiers and formats.
Before building, we discuss repository and account access, hosting, backups and maintenance. If another system needs the records, we can assess an automation or integration. Replacing the workbook and connecting the resulting tool are related tasks with separate requirements.
Before we start
Do we have to stop using Excel?
No. You may keep it for analysis, occasional calculations or exports while moving one operational workflow into an application. We decide where the authoritative records live and how other copies are used.
Can you review the workflow first?
Yes. A standalone assessment can clarify the rules, data and system connections before an implementation is quoted. A well-defined fix may be ready for a direct quote instead. The cost and scope guide sets out the assessment options and starting prices.
Will every formula carry over?
Each formula or script needs to be understood and checked against expected results. Some logic may belong in the application, some may stay in a workbook, and some may need to change. A file conversion alone does not decide that.
What happens to older records?
We agree on which records to import, which to retain as an archive and how people will access them. Migration scope includes cleanup and checking, not just moving columns.
Can we change the rules later?
Yes, through further scoped work. Clear field definitions, review examples and change history help another developer understand the existing behavior before altering it. The cost and scope guide explains how to separate the first release from later changes.
Start a project
Tell me which workflow or system needs attention. Five short questions help outline a review, project or embedded engagement you can discuss by email.
Start a project Review your brief, then continue in email.Snoogz Software is based in Canada and uses Google Workspace for email. These services may process your information outside your country. Please avoid sensitive personal information. Read our privacy notice.