One operator
The method cannot be delegated, so the business cannot take on more work than one person can process.
For laboratory and analytical businesses whose calculation now lives in a workbook only one person can safely operate. We rebuild that method as a product: the same arithmetic, the same grading bands, the same wording, checked value for value against the workbook it came from. The report is generated behind it, from the readings.
The problem a workbook becomes
By the time it is load bearing, it is carrying more risk than anyone intended. The arithmetic is almost always correct. What fails is everything around it: a formula only one person understands well enough to extend, hidden columns nobody dares delete, constants last reasoned about by someone who has left, and a grading threshold that exists in three places and agrees in two.
One operator
The method cannot be delegated, so the business cannot take on more work than one person can process.
No record of why
A number in a cell carries no trace of the reading it came from or whether it was corrected.
Reporting by hand
The result is retyped into a document, where it can diverge from the calculation behind it.
The method, held once, in software, with the reasoning visible and every answer traceable back to the reading that produced it.
The calculation engine
Every formula rebuilt as one engine with one definition of each quantity, and intermediate values shown.
Grading bands as data
Thresholds, band names and band wording stored as values that can be read, versioned and dated.
Readings as they arrive
Typed in batches, pasted as a block, or imported from the file the instrument writes.
The report, generated
Produced from the same stored values the grading used, so report and calculation cannot disagree.
Auditability, built in
Every stored value carries where it came from, when, and under which version of the method.
More than one operator
Roles, review and sign off are part of the product, so a second person can run the method and a third check it.
Each reading keeps its sample identity, its position in the run, who entered it, and the photograph of the display if one was taken. A correction is a new value with a reason, never an overwrite. A band edit happens in one place and is dated, and results already issued keep the bands in force when they were issued. A job reopened a year later answers the question of how a number was reached from the record, rather than by reconstruction. The method stops being a person and becomes a capability the business owns.
Verification
The source file is opened and read, then the rebuilt engine is compared to it value for value. The comparison is a command that fails rather than an opinion that reassures. That is a check of the rebuild against your own file, and it is narrower than a regulatory sign-off.
The source file is the specification
The workbook is the input, read cell by cell, not summarized in a meeting and rebuilt from notes.
Constants are read out, not retyped
Thresholds, coefficients and band boundaries are extracted from the file itself.
Value for value comparison
Every worked example in the workbook is run through the new engine and the two answers diffed to the digit.
The check is runnable, and it fails
The comparison returns a failure when any value disagrees, and runs again on every change to the method.
Disagreements are resolved
Where the workbook contradicts itself, the conflict is reported and settled by the method owner.
The wording travels with the numbers
Band text, qualifiers and standing notes are taken verbatim from the source rather than rewritten.
Roles and connections
A bench, a reviewer, an owner and a client, each needing a different view of the same job.
The bench analyst
One job: the sample set, the readings to enter, and what the engine returns as each value lands.
The reviewer or method owner
The path from reading to result, the corrections made, and the sign off that releases a report.
The owner
Throughput, what is waiting on review, and which methods have changed since the last release.
The client contact
The finished report and nothing else, delivered the way the laboratory already delivers it.
Systems already carrying the work are integrated rather than displaced, and a connection is not called finished until it has read a real record out of the live system.
Instrument output files
Read from the folder the instrument writes to, in the format it writes.
Sample intake and client records
Jobs arrive with client, site and sample identity attached.
Document storage
Issued reports filed where the laboratory already keeps them, under its own naming.
Email and accounting
Delivery recorded against the job, completed jobs reconciled to invoicing.
Scope and delivery
A fixed scope, settled in two conversations, the source workbook read before anything is proposed.
The first call reads the method as it stands: who operates it, what the workbook does, where it is fragile, what the report has to look like, and what a job costs in time today. The workbook is handed over and read in full before the second conversation.
The second call is the plan and a working mockup of the real screens, in the real design, with every field, band and action the finished product will carry. The verification approach is agreed there too: which worked examples become the comparison set, and what counts as agreement.
A method is intellectual property and client results are confidential. Both are treated that way.
Installed, not rented
The product runs on your own machines with a local working copy, so a lost connection does not stop a run.
Your hosting account
The server, database and file storage sit under the laboratory's own account, credentials held by its owner.
The method stays yours
The engine, the constants and the report templates are not reused for anyone else.
Confidential engagements
Client work is described by sector only, and no laboratory is named on this site.
No claim is made on your behalf
The software states what it calculated and what it was verified against, and nothing beyond that.
Export on any day
Jobs, readings, results and reports come back out readable, on request.
The first call will tell you what the rebuilt method has to match. Then how to start: call (252) 666-7217 or email [email protected].