A container on the bench is not a sample yet.

What is lab management software?

Lab management software runs the operational side of a laboratory: the sample arriving, the acceptance checks that turn it into a workable record, the accession reference it takes, the tests or checks assigned to it, the bench worklist those create, the results recorded against each one, the review that has to happen before anything is issued, the release itself, and the history left behind. It is the record of a sample, not a judgement about what the result means.

What is a laboratory management system, and what does it manage?

Samples and the requests behind them, acceptance and accessioning, storage references, the work assigned to each sample, the bench worklists that work creates, results recorded against the work, review and release by whoever the laboratory authorises, reports issued, the full history of every one of those steps, exceptions that need a person, and who in the laboratory is allowed to see or change each part of it.

What is sample accessioning?

Accessioning is the point where a laboratory formally takes a sample on: it is checked against what was requested, given a unique accession reference, and registered with its type, source, condition and storage location. Before accession a container is just something on the bench. After it, there is a record the laboratory is accountable for — which is why it is a decision somebody makes rather than something that happens on arrival.

Can tests or work be assigned to a sample?

Yes — that is the middle of the record. A sample carries the checks it needs, each with the section or bench that owns it and its own state, so a supervisor can see what is outstanding on a sample and a bench can see what is outstanding on it. What the system does not do is decide which method is scientifically appropriate; that is defined by the laboratory and configured, not inferred.

Can laboratory instruments connect to the system?

Where a real interface exists, yes, and it is scoped rather than assumed. Analysers typically expose a serial or file interface, an ASTM or HL7 message, a vendor API, or middleware sitting between the instrument and the system — and each analyser family is its own piece of interface engineering rather than a setting. We start by identifying the instrument, what it can actually emit, and what somebody has to do at the bench, before anything is promised.

Can lab management software support barcodes and labels?

Sample identifiers, barcodes, QR labels and rack or position references are all normal parts of a laboratory record, and the system holds them. Printing them on your label stock and reading them with your scanners depends on the hardware you actually run, so that part is scoped around those devices. Branditify does not supply laboratory hardware and no printer or scanner is claimed to work until it has been identified.

Can lab software track sample history?

Yes, and it is usually the reason a laboratory replaces its spreadsheets. Every state a sample moved through is kept in order against the sample itself — received, accessioned, assigned, worked, recorded, reviewed, released — with who did it and which references were issued. How much depth that history needs, and how long it is kept, is scoped from what the laboratory actually has to be able to show.

Lab Management System vs LIMS — is there a difference?

In practice, less than the vocabulary suggests. LIMS is the established acronym for Laboratory Information Management System, and Lab Management System is what most buyers actually type. Both describe software built around the sample: receipt, accession, work, results, review, release and history. We use the plainer term on this page and answer to the acronym, because a laboratory searching for one of them means the other.

Lab management vs clinic management — which do we need?

They answer different questions about the same day. A clinic system owns the patient, the appointment and the consultation. A laboratory system owns the sample, the work done to it, the result and the release. A clinical laboratory naturally references a patient or an order — that reference does not make it a clinic system, and running both usually means a request raised in one becomes a sample record in the other rather than being retyped.

Can lab software connect to inventory and procurement?

That is the shape worth building. The laboratory record knows this sample’s work needs a unit of a reagent; the stock system knows how many units exist; the procurement record knows who they are bought from and whether the last order arrived. Each connection is scoped against what the other system can accept, and this record deliberately keeps neither a second stock ledger nor a second set of supplier terms.

Can clients access reports through a portal?

Where a portal is in scope, yes — a controlled view of a request, its state and the report once it has been released. It is a decision rather than a default, because giving outsiders a login changes what every internal screen is allowed to contain, and because nothing internal to the bench should become visible by accident.

What determines the scope of a lab management project?

Mostly four things: how many samples arrive, how many different kinds of work the laboratory runs, whether review and release authority varies by method, and which instruments have to feed the system. Feature lists predict a laboratory build badly; those four predict it well.

Who owns the system and the data after a custom build?

You do. The code, the database and the hosting account are yours, and every sample, result, review and report in it is yours. There is no per-sample charge, nothing meters how much work you run through it, and nothing stops working if a relationship ends.

What should a laboratory digitise first?

Samples and acceptance, then work assignment. A clean record of what arrived and whether it was accepted is what everything else hangs off, and work with a named owner is what makes anything else answerable. Digitising results or reports before those exist just moves the confusion into a nicer screen.

Can old sample and result records migrate from spreadsheets or legacy software?

Usually, and the first job is finding out what the current tools can export rather than assuming. Samples, methods and open work normally move cleanly once duplicates have been decided. Years of raw instrument files and scanned reports depend entirely on what shape they are in and whether that history is worth the work — which is a decision made with you rather than for you.

Custom lab software, or an off-the-shelf LIMS?

Off-the-shelf is the right answer more often than agencies admit, and there are really three options rather than two. A packaged LIMS suits a laboratory whose workflow is standard. A configurable platform — a commercial product you build your own workflows on — covers a great deal of the middle ground without a build. A custom system earns its place when the last part will not configure: an unusual sample or review model, authority that varies by method, instruments nobody supports, or several existing systems that have to stay in step rather than be replaced.

Does every laboratory need custom software?

No. A small laboratory that needs sample tracking, results capture and a history it can show is well served by an established product, and commissioning a build would mean paying for complexity it will never use. Very few laboratories are genuinely unique — most differ in the type, number and flow of samples rather than in the shape of the work. Custom becomes the right answer when real workflow or integration gaps justify it, and that is a judgement worth making before a build starts rather than halfway through one.