How to Choose The Right Laboratory Resource Planning Software?

posted by
Adam Lester-George
Content Marketing Manager

Are you thinking about digitalizing your laboratory resource planning & scheduling? Maybe already listing a couple of potential software vendors? Eventually, you want to arrive at a cloud-based, laser-focused enterprise software that makes the end user’s life easier and integrates smoothly with all your other lab management systems. Here are four tips to help you out.

Free User Requirement Specifications Template / URS template resource planning software

Tip 1: Go for ’true’ cloud software

Software consultants that come to your office and install a customized version of their software on your local server (on-premises software) sounds like something from a distant past. By now, everyone seems to agree: the cloud is the future. With all kinds of ‘cloud-based solutions’ sprouting left and right, it’s sometimes easy to forget why we want it in the first place.

So, a quick reminder: you always want to be working with the latest version of the software. Your investment needs to include all future updates and enhancements for years to come. An important requirement: the cloud contains one version of the software used and constantly updated for all clients (=true cloud).

However, not every ‘cloud-based software’ is created equally. Sometimes, every client runs a customized version of the software in their own piece of the cloud. Whenever there is a new software update, custom versions, although technically in the cloud, are at risk of missing the boat. Apart from some bug fixes, the system you use tomorrow is remarkably close to the system you buy today. The longer you’ll use it, the more outdated it becomes.


  • One version of the software is constantly updated for all clients. True cloud means you have a product that is constantly improved based on feedback, not only from you but from all users, all of them facing similar challenges.
  • The system is configurable to match your ways of working (configure in the UI, not in the code).
  • This means you are not just buying the features that software offers today but also buying all future updates.

Tip 2: Don’t buy custom software

Do you remember the feeling of opening a Lego box as a kid? It’s full of blocks of different sizes, in different colors, … With a bit of imagination, you can build a thousand different things. Some software is like a Lego do-it-yourself kit: it contains components and building blocks you can use to build a solution yourself.

In contrast to Lego, in the case of software, the feeling of ‘endless opportunities’ is less appealing. Especially when it needs to solve very specific challenges unique to your situation (e.g., competency-based scheduling, specific constraints, business logic, sample campaigning rules, …). You’re probably already imagining a small army of consultants to first map your processes & needs, and then another army of programmers using the building blocks to program a solution that is not so great.

These ‘do-it-yourself kits’ are often called ‘platforms.’ Just like with Lego: they work great if you’re building a relatively straightforward solution, less so for more complex things, like scheduling people & equipment in a lab context. Choose wisely.

A powerful alternative is a solution specifically created for your ‘niche’ market, like, in the case of Binocs: digital resource planning for laboratories, CGT or resource management offices. It’s built around the best practices, experiences & feedback from dozens of clients that face challenges very similar to yours and can therefore be implemented very quickly.


  • Don’t re-invent the wheel if you don’t need to.
  • Look for software built around a solution that fits your unique challenges.
  • You want to go live in a matter of weeks, not months.

Free User Requirement Specifications Template / URS template resource planning software

Tip 3: Choose laser-focused enterprise software with the end-user in mind

You know what it feels like: you go to a store, you’re comparing a few products, and you’re sold to the one that sounds like the best idea. It’s got the most features, the packaging looks hot and everything seems great. But then you get home, and it doesn’t deliver. It’s not as easy to use as you thought it would be. It has too many features you don’t need. You just bought an “in-store” good product.

Most enterprise software is “in-store” good. That because people who buy enterprise software — IT managers, HR managers, etc. — often focus on configurability, control and the number of features. They see all the bells and whistles from companies such as SAP and IBM and fall for the “one system does it all” sales pitch.

But once the software is in use it becomes apparent that typical enterprise software vendors aren’t mindful of the employees that have to work hours in their system on tasks that should take 5 minutes. It becomes clear that they care about the one-night stand with the managers to sell and forget the long-term relationship with the users.

That’s why it’s important to document all your user requirement specifications, whether they’re functional or non-functional: demand management, capacity management, scheduling & tracking, compliance, integration, scalability… If you don’t know which questions to ask, we’ve got you covered! Simply download our free URS template with more than 70 user requirements specifications.


  • Choose software with the end-user in mind
  • Be wary of enterprise software vendors that pretend to solve a thousand problems.
  • Look for laser-focused software solutions that solve a very particular problem for the end-user, a system that’s great at a limited set of tasks but executes them exceptionally well.

Tip 4: Look beyond API’s & standard interfaces

Laboratories have more and more digital systems in place: LIMS, ELN, ERP/SAP, … Whenever you’re adding new software to the mix, it needs to integrate smoothly (at a bare minimum, you need to be able to import and export all data via APIs).

Setting up interfaces is often a painful process. The typical interface approach uses code & programming to transform data from the sending system, so the receiving system understands. This is a rigid approach as it requires a clear contract and requirements upfront, making it challenging to make changes after the fact. The coding requires quite some time of scarce internal IT resources. Not only to write the initial interface but also to cope with the inevitable changes afterwards.

Look beyond APIs and standard interfaces. Make a realistic assessment of how smoothly the new system can be integrated.


  • Verify the vendor’s approach to how they set up interfaces: can they guarantee it will be a smooth process that doesn’t require a lot of your IT resources?
  • Look for low-code or zero-code low-code approaches.
  • Be careful with ‘standard interfaces’: they are not the solution (click here to read why).

Discover how Binocs fits your use case

Binocs is the leading resource management software in life sciences. Our solution fits many use cases:

Check out how our demand & capacity planning + scheduling software could boost your business lead times, team efficiency and productivity. Or contact us so we can show you Binocs in action.

Nail your operational performance

See Binocs in action

Related articles

  • - by Frederik Jaenen

    Planning Your QC Lab with APS Software: is it a Good Idea?

    Planning production is different from planning a quality control lab. Here are a few things to consider before implementing APS software in a QC lab.
    Read more
  • - by Mathias Lasoen

    Lab Automation: how to make your business case?

    In 2008, a survey on laboratory automation concluded that most lab workers (88%) believed they would rely on lab automation in the future. Yet it’s 2021, and 72% of...
    Read more
  • - by Adam Lester-George

    Resource Scheduling: How Much Lab Automation is Too Much?

    Would you like your lab to be 100% automated? Not so fast! First, let’s take a closer look at lab automation and ask: how much is too much?
    Read more