The dashboard gives a live snapshot of your plant's QC health — total active samples, expiry alerts, recent transactions, and calibration due counts — via KPI cards and interactive charts.

Register a new QC sample into the system by filling in batch details, storage location, and expiry information. Generates a printable label with QR code.

Find any sample in your plant's inventory using free-text search, batch ID lookup, or filter by storage location, status, or expiry range.

Record when samples are taken out from storage for testing and when they are returned. Every transaction is timestamped and linked to the user who performed it.

Full audit trail of all sample take-outs and returns. Filter by date range, batch ID, user, or transaction type. Export as Excel for compliance reporting.

A live dashboard of all samples sorted by expiry date. Colour-coded rows immediately highlight which batches need attention — from Expired to Safe.

Archive of all batches that have been expired or removed from active inventory, with full audit trail including who removed them and when.

Interactive charts showing sample trends, storage utilization by rack/bin, transaction volume over time, and expiry distribution across your plant.

The main equipment register showing every instrument in your plant with its current calibration status. Status is automatically calculated from the due date.

Full history of all calibration events per instrument — shows who performed each calibration, when, certificate reference, and any notes added.

A chronological log of all updates made to any equipment record — tracks both calibration updates and due date changes, with user attribution for every entry.

Charts showing calibration status distribution (pie/bar), upcoming due dates by month, and historical calibration completion rates across equipment categories.

The main register lists all active (Draft + Open) walkabout observations for your plant. Raise new observations, assign action persons, and track progress through the lifecycle.

All closed walkabout observations with full audit trail — close date, CAPA notes, reopen count, and all comments/attachments. Paginated 20 per page.

Personal view showing every open walkabout observation where you are the assigned Action Person. Paginated 20 per page. Your personal to-do list for CAPA completion.

Complete audit log of every state change, comment, attachment upload, and edit across all walkabout observations — with user name and timestamp for each action.

Charts showing observation trends over time, status distribution, top areas with repeat observations, average close times, and department-wise breakdown.

Manage the pest control team for your plant — list team members with their roles (Internal/External contractor), contact details, and assignment status.

12-month schedule of planned pest control activities — fogging, spraying, baiting — for every area of your plant. Shows planned vs. completed activities with status tracking.

Visual heatmap of your plant layout showing device placement and current pest pressure level by location. Four heatmap views available, each colour-coded by activity intensity.

Master register of all pest control devices in your plant — fly catchers (previously "insect killers"), rodent bait stations, glue traps, and spider pads. Each device has a unique code, type, and location coordinates for the heatmap.

Enter fortnightly or monthly readings for every pest device in the plant. Five device types have their own input format: Insect Internal, Insect External, Rodent Bait (Outer), Rodent Glue (Inner), and Spider Pad.

Log every chemical spray application — chemical name, quantity used, target area, applicator, and date. Linked to the Pest Chemical Master for chemical details.

The planned spray schedule for the year — which areas get treated, with what, and how often. Spray Tracking then records what actually happened against this plan, so you can show planned-versus-done to an auditor.

Dedicated planning and service logging for lizard control, kept separate from general spraying because it runs on its own schedule and method.

A full audit trail for the module — every device, reading, spray, chemical and meeting change, with who made it, when, and what it was before.

Schedule pest control review meetings, record attendance, and manage Minutes of Meeting (MOM) with action items, owners, and due dates.

Pest control document repository — upload and manage SDS sheets, contracts, compliance certificates, inspection reports, and any other regulatory documents.

Generate comprehensive pest control reports — monthly readings summaries, trend analysis, infestation level reports, and compliance documentation — all exported as clean A4 PDFs.

Master list of all pesticides and chemicals approved for use at your plant. Each entry stores name, active ingredient, dilution ratio, target pest, regulatory registration number, and safety notes.

The kiosk-style entry screen where any employee submits an improvement idea. Each submission gets a unique, permanent card number and starts in the Open state.

The management board for all cards raised at your plant. Move each card through its lifecycle and record who did what at every stage.

Every card you have raised, with its current status — so a submitter can follow their own idea through to implementation without asking an admin.

Dashboards summarising card activity for the plant — totals by status, cards by zone and working place, implementation rate, and cumulative savings from implemented ideas.

Per-plant configuration for the module, across three tabs:

A complete audit trail of every create, edit, status change, reward, delete and restore in the module — who did it, when, and exactly what changed from what to what.

Checklists is the bank — every checklist at your plant with its category, scope, status, version and the builder that made it. There are now two ways to author one, and they write into the same bank, so versions, runs, history, audit and PDF work identically behind either:

Either way a checklist is organised into sections, each holding a list of questions. A Standard or Custom pill appears wherever a checklist is named, so you always know which editor owns it.

A checklist is built once and then assigned to the modules it belongs to. Every module now carries the same Checklist Configuration screen, showing the checks that landed there — so a check written for the gate is found at the gate, not hunted for in a list of two hundred.

The execution screen operators use to carry out an inspection, designed as a single scrollable form that works well on mobile devices.

Your personal inbox of checks that are due. When a schedule generates runs, everyone on the recipient list sees them here — this is where an operator starts their day.

Named, reusable sets of people at your plant — "Shift A Operators", "QA Team", "Line 3 Leads". Build the group once and target it from any schedule instead of re-picking individuals every time.

Set a check up once and let it run itself. A schedule generates the runs, assigns them to the right people, and emails them — every day, week, month or quarter, without anyone remembering to start it.

A shared tablet or panel PC mounted at a physical place on the floor, so operators run their checks where the work happens instead of walking to a desk. A Station is registered once and permanently bound to a place — a plant, an area, a work center, a specific machine, or a gate.

A dashboard of every completed (and in-progress) run at your plant, with its overall pass/fail result, the template and version used, and who ran it and when.

Register a visitor once and reuse them anywhere in the company — no re-typing at each plant.

Raise, approve and manage visit requests. Each pass gets a unique UGPN-YYYY-NNNNNNNN number and a QR code.

A party of people, or the same person for a run of days, without any new concepts to learn at the gate.

Who is inside the plant right now — for the daily count, and for the head count at the assembly point.

The visitor master is shared so nobody re-types the same person — but sharing a list is not the same as sharing the right to change it.

Visitor Management is built to be run from a phone at the barrier, not only from a desk.

Two hands-free ways to check visitors in and out at the gate.

Reporting and the master data behind the module.

The state of the yard on one screen — how many trucks are expected, arrived, in transit, loading, unloading, done and gone today.

Register a truck as it reaches the gate — or before it arrives, as an expected delivery. Every entry gets a unique number, TE-YYYY-NNNNNN, sequential per company per year.

One card per truck, and the card is where the day is actually run. The action buttons change with the stage the truck is at, and the next one due blinks.

Where the truck parks, and what it weighed before and after.

A truck inspection is an ordinary checklist, built in the Checklist module like every other check. What Fleet adds is when it is demanded — you write rules, and the rules block the ladder.

What was ordered against what turned up, and the record of everything anyone did.

Fleet is off for everybody until it is granted. Nobody gains a new module simply because it was installed.

Define the physical storage infrastructure for samples — add Plants, Racks per plant, and Bins per rack. This structure is what all sample location dropdowns use throughout the system.

Manage the organisational hierarchy used for data scoping — Companies → Countries → States → Plants → Departments — plus the shop-floor asset tree inside each plant. Every piece of data in the system belongs somewhere in this structure.

Add, edit, deactivate users and assign their access level, module permissions, and plant/department. User Roles are also managed here (moved from Master Data in v1.3.0).

Licensing control for each customer company — how long their subscription runs and how many users they may create, overall and per role.

Make the app look like the customer's own. Turn branding on for a company and its users see that company's identity after they log in.

Per-plant, per-module behaviour — the knobs that let two plants on the same system run their processes differently. This page lives in the sidebar under Checklists, but it configures more than checklists, which is why it is documented here with the other admin screens.

The authentication and account trail for compliance: logins, logouts, failed attempts, password changes, and account create / edit / deactivate events, with who and when.

Configure enterprise Single Sign-On (OIDC) per company. Once configured, users with a matching email domain are automatically redirected to your identity provider (Okta, Azure AD, Google).

Configure label printer settings — POS thermal printer connection details, label dimensions (width, height in mm), and QR code size. Supports both A4 and ESC/POS thermal formats.

SMTP settings for system email notifications — walkabout alerts, calibration reminders, and meeting invites. Configure sender address, SMTP host, port, and authentication credentials.

In addition to the access level, each user's visibility of the four main modules (Sample Management, Equipment Calibration, Quality Walkabout, Pest Control) is individually controlled via Module Access settings in User Management.