What is Knowella? A product tour

Templates are the forms your teams fill in

Everything people complete in Knowella starts as a template. Take one from the Template Library and adjust it, or build your own from scratch — drag fields onto a canvas, set which answers are required, add conditional follow-ups so a failed check asks for a photo and a corrective action. No code, and no waiting on a vendor to change a form for you. That last part is the real argument for building rather than buying: the day your process changes, the form changes with it.

Schedule sets the cadence once

A form on its own is a document. A form on a schedule is a programme. Set the cadence once — daily, weekly, per shift, per facility — and every occurrence is created, assigned to the right person and tracked, whether or not anyone remembers it is due. Missed occurrences stay visible as missed rather than quietly disappearing, which is the difference between a record that satisfies an auditor and one that does not.

My To-Do is what the front line opens

Supervisors and operators do not browse the platform; they open one screen. <b>My To-Do</b> is their forms and their due times, on a phone at the line. Nobody has to be taught the whole product to take part in it — the person doing the check sees the check, and that is all.

Submissions carry the work onward

Everything completed lands in <b>Submissions</b>, and the workflow takes it from there: review, approval, and a corrective action where one is needed. A finding does not stop at being recorded — it becomes an assigned piece of work with an owner and a due date, and it stays open until someone closes it. This is where a form stops being paperwork and starts being a control.

• Review — The completed record goes to whoever is accountable for it.
• Approval — A person signs off, and the approval is part of the record.
• Corrective action — A failure opens assigned follow-up work, tracked to closure.

Analytics reads your live records

Analytics is not a separate reporting exercise — it reads the records as they land: completion rates, open actions, and which facility is drifting. Every template gets its own report the moment it has data, so a new form is measurable from its first submission rather than after someone builds a dashboard for it. <b>My Analytics</b> holds the boards you assemble yourself, or the one Ella builds when you describe what you want to see in a sentence.

Ella sits in the top bar of every screen

Ella is how you talk to your own data. She is in the top bar wherever you are, she already knows your facilities, your templates and your records, and you ask in plain language — no query syntax, no report builder. She answers with the finding first, then does the work: drafting the corrective action, assigning it, putting the re-check on the schedule. When a job belongs to a specialist she hands it to the rest of the roster rather than attempting it herself.

The specialists behind her

Ella orchestrates; the named agents each own a lane of real work. Every one of them stops at a draft and waits for a person, which is the point — the agent removes the typing and the chasing, not the judgement.

• KnowRFP — Takes a lane spreadsheet and returns a priced, branded proposal — normalising the file, rating every lane, and drafting the document for your approval.
• KnowDoc AI — Handles inbound paperwork: splits a PDF packet, reads and validates every document, flags the exceptions, and lines up billing ready for you to approve.
• KnowLogistics — Covers the freight lifecycle — intake, cover, run, reconcile — planning orders, tendering carriers, watching loads and keeping your systems in sync.
• AI Ergo — Reads a task video posture frame by frame and returns RULA, REBA and NIOSH scores, the angles it measured, and a drafted corrective action.

Company Settings is the whole administrative surface

Four tabs, and they are the reason the rest of the product can stay simple. <b>Facilities</b> is every site you operate, each with its own admin, users and templates. <b>Users</b> are invited by email, straight into the right facility. <b>Roles</b> decide who can build, who can assign and who can approve — the permission model that makes human approval meaningful rather than decorative. <b>Plans</b> is one subscription, priced per user, with the AI modules as add-ons you switch on when you want them.

• Facilities — Every site you operate, with its own admin and templates.
• Users — Invited by email, into the facility they belong to.
• Roles — Who can build, who can assign, who can approve.
• Plans — One subscription priced per user; AI modules are add-ons.

Configure it, run it, let the agents close the loop

That is the shape of the platform, and the order matters. You configure it — templates, schedules, facilities, roles — because you know your operation better than any implementation consultant will. It runs on the cadence you set, and the front line only ever sees their own list. Then the agents close the loop: they read what came in, draft what should happen next, and hand it to a person to approve. Nothing reaches the outside world without that approval, which is what makes it safe to let them do the busywork.