Beyond Checklists
Commissioning, maintenance, repair or quality control - many process steps follow a fixed routine, but documentation often lives only in someone's head. Beyond Checklists attaches it automatically to the document: the item, the machine, or the service order. Experience becomes a repeatable process - from a function test before a sale to the full inspection report on a machine after maintenance.
What these checklists do differently
On the document, not beside it
The checklist hangs on the document itself - the item, the machine or the order. No second window, no file anyone has to go looking for first.
Set up without developers
Create a template, set a filter, type the lines. Anyone who can configure Business Central can build a checklist - no AL code.
Binding when it has to be
You decide per template: results may stay open, a warning appears, or release is blocked until they are filled.
Knowledge in someone's head becomes a step in the process
Today the quality of a check depends on who happens to be working the document. With a template it depends on the template - and the document shows at any moment how many items are still open.
Same document, same check
One template, any number of documents. Nobody new has to ask what needs checking - the list is already there when the order is created.
Incomplete work stays put
Miss a mandatory item and release warns or blocks. What nobody could reconstruct afterwards never comes into being.
Still documented after posting
The checklist travels from quote to order and on to the posted document. Whoever asks two years later finds the answer on the document.
One mechanism for the business
Sales, purchasing, service, master data, projects, manufacturing, warehouse and transfers all work the same way. Your people learn one screen - not eight separate ones.
From the first template to the printed report
A checklist starts as a list of lines, attaches itself to the matching documents and gets filled in where your people already work. These are the tools in between.
Templates from lines, not code
Groups, headlines and mandatory, normal and additional lines make up the structure. Preview shows the finished layout before the first checklist exists.
The right datatype per line
Text, code, numbers, dates, times, yes/no, option lists, images and multi-line text. Where a choice belongs there is a dropdown, not a box everyone fills differently.
Lines that write to the document
An Editable Field line shows a document field and writes changes back through Business Central's own validation. If the document rejects a value, the message appears at once.
The template finds the document
Handler and filter decide what a template attaches to - by itself on creation or on demand. The lookup only offers templates whose filter matches this document.
Pricing plans
Common questions
What checklists hang on, what happens at posting and where the photos end up.
Which documents can carry a checklist?
Sales, purchase and service documents, the Service Item Worksheet, master data cards such as customer, item or service item, projects, production orders, warehouse receipts, shipments and transfer orders - more than 40 pages.
Does a checklist really block posting?
It blocks release if you set it up that way. And because posting an unreleased document releases it first, the same check applies there too. Per template you choose between None, Warning and Error.
Where do checklist photos end up?
In the Business Central database by default. Optionally you set up your own Azure Blob container; the editor then loads them through a read-only SAS token. One action moves existing images either way.
Will our people see checklists everywhere?
Only where you have created a template. The FactBox and the action stay hidden until at least one enabled template exists for that area. Check service orders only, and sales documents show nothing of it.
Let's talk about the checks in your process
Which check hangs on which document today, who fills it in and where it gets skipped in daily work - we go through that together before you build the first template.
Walk through your checks with us
Works well together
These apps work together
Beyond Checklists
Give every check a place on the document
Spend 30 days finding out how it feels when the question about the check is answered before anyone gets round to asking it.