Practical tools for specific problems.
Each of these is a custom engagement shaped by an on-site audit. The descriptions below are illustrative, not client work.
Web, mobile and compatible smart glasses are delivery options where they fit the work. We choose the interface around your team, environment and existing systems.
AI workflow automation
The same order, invoice or job gets typed into three places by hand.
The problem
An order arrives by email and gets keyed into a spreadsheet, then into accounting, then into a schedule. Every hand-off is a chance for a typo, a delay or a missed step, and the people doing it have better things to do.
What we might build
- Connections to the systems you already use, where they allow it.
- Steps that read incoming information, prepare the next action and show it for approval.
- An exception queue for anything incomplete, unusual or outside agreed rules.
- A log of what was proposed, who approved it, and what ran.
How the workflow runs
- Existing systemsInbox, spreadsheets, line-of-business tools
- Proposed actionFields extracted and a step prepared
- ApprovalPerson decidesA person approves, edits or rejects
- Execute & logThe step runs and is recorded
- Exception queuePerson decidesAnything unclear waits for a person
Human oversight
Nothing consequential runs silently. Approval points are agreed up front, and the level of automation can grow only as the team builds confidence in the results.
What the audit checks first
- Which systems have usable APIs or exports, and which do not.
- The quality and consistency of the data that flows between them.
- Where hand-offs happen between people, teams and organisations.
- Which steps genuinely need a person, and which are just copying.
Computer & photo vision
What passes depends on who is looking, how busy the shift is, and the light that day.
The problem
Visual checks depend on who is looking, how tired they are and how busy the line is. The same scratch, gap or missing part gets caught one shift and missed the next, and there is rarely a record of what was seen or why it passed.
What we might build
- A capture setup suited to your space: a fixed camera, a mounted tablet, or phones your team already carry.
- Detection tuned to the specific conditions you define, such as a visible defect, a missing component or an incorrect count.
- A review screen where people confirm or dismiss each flag quickly, with the image in front of them.
- A record of decisions that can feed reporting, rework or supplier conversations.
How the workflow runs
- CaptureFixed camera, tablet or phone photo
- FlagModel highlights a defined condition
- ReviewPerson decidesA person confirms or dismisses the flag
- RecordDecision, image and context are logged
Human oversight
Flags are prompts for review, not verdicts. A person decides what happens next, and their decisions are recorded so the system can be checked and improved over time. Accuracy is not assumed; it is measured against your own examples.
What the audit checks first
- The real conditions: lighting, camera position, motion, dust, glare and shift-to-shift variation.
- Representative examples of good and problem items, gathered from your actual work.
- What counts as a defect or condition, defined with the people who inspect today.
- How results would be validated before anyone relies on them.
Digital audits & inspections
Findings go on a clipboard. The fix depends on someone remembering to chase it.
The problem
Paper forms get filled in, filed and forgotten. Findings live on a clipboard, photos live on someone’s phone, and the follow-up depends on a person remembering to chase it. When it is time to show what was found and fixed, the trail is incomplete.
What we might build
- Checklists that mirror your inspection types, with the steps your team already follows.
- Photo capture and notes attached directly to each finding.
- Corrective actions with owners, due dates and reminders, visible until closed.
- Sign-off by the right person and a clean record you can pull up when you need it.
How the workflow runs
- ChecklistGuided steps for the inspection type
- FindingsPhotos and notes attached at the point of capture
- Corrective actionAssigned to an owner with a due date
- Sign-offPerson decidesA responsible person closes it out
Human oversight
The tool supports your compliance work; it does not guarantee compliance. Your standards, your inspectors and your sign-off remain the authority. The software makes the trail clearer and the follow-up harder to lose.
What the audit checks first
- Which standards, policies or customer requirements the inspections relate to.
- Who inspects, who fixes, and who signs off, including contractors.
- Connectivity where inspections happen: barns, basements, boats, remote sites.
- How records need to be kept, retained and shared today.
AI knowledge hubs
The answer is in a binder, a PDF, or one person’s memory, and nobody is sure which version is current.
The problem
The answer exists, somewhere. It is in a binder in the shop, a PDF on a shared drive, or the head of the person who has been there longest. New staff ask around, experienced staff get interrupted, and nobody is quite sure which version of the procedure is current.
What we might build
- A searchable hub over the SOPs, manuals and reference documents you approve for inclusion.
- Answers that link to the exact document and section they came from, so people can read the original.
- Access permissions that follow your existing roles, so people only see what they should.
- A simple way for document owners to add, replace or retire sources as procedures change.
How the workflow runs
- AskA team member asks in plain language
- RetrieveOnly approved sources they are permitted to see
- AnswerA short answer with a citation to the source
- VerifyPerson decidesThe person checks the cited passage before acting
Human oversight
The hub points to sources; it does not replace them. Answers are framed as a starting point with a citation, and the person doing the work reads the source before acting. A design objective is that when no approved source covers a question, the hub says so instead of guessing. That behaviour is validated in testing against your own questions before rollout, not assumed.
What the audit checks first
- Which documents are actually approved, and who owns each one.
- How current those documents are and how revisions are handled today.
- Who should be able to see what, across roles, sites and departments.
- The real questions people ask in a week, collected on site.
Not sure which one fits? That is what the audit is for.
A call or an in-person coffee is the easiest first step. We talk through the work, the people doing it and whether an audit is the right next step.