Yes. Serialized assets carry service history, condition and assignment; consumables carry quantity, location, minimum and maximum levels and reorder points. A vac truck, a laptop and a case of gloves differ in which fields matter, not in where they live.
Lot number, dose, expiry and storage conditions are held on the stock record, and expiring lots are surfaced before they reach a service point. Movement between warehouse, clinic and vehicle is tracked at the lot level rather than as a bulk quantity.
Whichever way suits the moment. Scan the QR or barcode with a handheld scanner or with the phone people already carry, type the item in manually, or search by SKU, part number, serial or description. All of it works offline — entries and scans queue on the device and sync when a connection returns.
Yes. Assets, locations and stock import from a spreadsheet or an export from your current system. We map to your fields rather than asking you to rename everything to suit ours.
Not the question you had? Ask us directly — you get the people who built it.
Yes. Forms are held on the device, completed offline including photos and signatures, and synced when a connection returns. Nothing is lost if the phone stays offline for days.
Existing PDFs and paper forms are rebuilt in the drag-and-drop builder, usually field for field. You can change the layout later without disturbing historic submissions.
Routing for approval, a work order raised against an asset, a corrective action, time logged to a project, a notification, or a follow-up form. The rules are conditional, so only the relevant path fires.
Visibility follows role and organization. A contractor sees their own submissions, a supervisor sees their crew’s, a compliance lead sees the program.
Not the question you had? Ask us directly — you get the people who built it.
A contractor is onboarded as an organization first — coverage, insurance, prequalification and safety program — and its workers sit underneath it. Compliance is answerable at the company level and at the person level.
The program is uploaded and reviewed by AI against a source of truth you set — your own prequalification standard, the regulation, or the requirement written into the contract. What comes back is where it meets the standard, where it falls short and what is missing entirely, with the clause it was measured against. Your reviewer still makes the call; what gets automated is reading 90 pages to find the three gaps.
Compliance is evaluated continuously against the documents held at organization level and the requirements on the duties their workers hold. The moment something lapses — coverage, a certificate, an acknowledgement — the contractor is notified and a corrective action is created with an owner and a due date. It stays open and visible until the evidence is back in place.
The contractor does, through their own portal access. They upload renewals, add and remove their own workers and see exactly where they stand — so the register stays current without your team chasing certificates by email.
Not the question you had? Ask us directly — you get the people who built it.
Yes. Sections, lessons, prerequisites, quizzes and pass thresholds are built in the platform — including training on how your configuration works, rather than generic product training.
SCORM and xAPI packages, recorded webinars, video and documents.
Yes — authoring a SCORM or xAPI package takes a dedicated authoring tool. Once you provide the learning file, Tansi does the rest: hosting, assignment, prerequisites, tracking, scoring and the completion record. Courses built in Tansi’s own builder need no external tool at all — the authoring requirement applies only to packaged SCORM and xAPI content.
Training attached to a duty is assigned the moment the duty is. Completion, score and expiry are held per person, per module, per date.
Yes. Site-specific orientation is delivered remotely, so a first day on site is not spent in a trailer watching a video.
Not the question you had? Ask us directly — you get the people who built it.
No. It holds the operational side — job board, applications, onboarding, employee records, duties and qualifications — and gives payroll the hours and records it needs.
Document collection, policy acknowledgements, orientation and training, duty assignment and the requirements those duties carry. A new hire arrives set up rather than waiting in a queue.
Yes. The job board is public-facing, and applicants flow into onboarding without anybody re-entering their details.
On the same person record as duties, credentials, training and submitted forms — so the history is one record instead of four systems.
Not the question you had? Ask us directly — you get the people who built it.
Injuries, near misses, property damage, environmental releases, security events and hazards — from a phone at the scene, with photos and location.
Yes. The investigation carries witness statements, evidence, contributing factors and root cause, and corrective actions are raised directly from the findings.
Each action has an owner, a due date and evidence of completion. Open actions stay visible until they are closed, and overdue ones escalate.
Recordability is captured on the incident, and the register holds what a 300 log is built from, with dates and classifications. Filing stays your decision — the platform holds the evidence behind it.
Not the question you had? Ask us directly — you get the people who built it.
The record is created as the work happens — the form, the training completion, the inspection, the corrective action. An audit request becomes a filter over data you already hold rather than three weeks of collection.
Yes, with the audit trail attached: who entered what, when, and what changed afterwards.
Policies and procedures are published in the platform with version control, and the record shows who acknowledged which version, on what date.
Yes. View-only access is granted per module, so an auditor sees exactly what you decide they should see and nothing beyond it — no export of your whole system, and no screen-sharing session where somebody drives on their behalf.
Not the question you had? Ask us directly — you get the people who built it.
AI reads the sheet and builds the register entry from it — product and supplier, hazard classification, pictograms, first aid and handling — rather than somebody retyping a PDF into a spreadsheet. You review what it produced and it goes into the register.
Yes, as an add-on. We can provide access to a library of over 40,000 safety data sheets, so a missing sheet is a search rather than a request to a supplier who may take a week to answer.
Yes, from the same record as the sheet — so the label on the container and the SDS in the register cannot drift apart. Secondary container labels print the same way.
An SDS is assigned to the assets that hold the chemical, the inventory item it is stocked as, and the projects it is used on. Someone working a project opens the sheets for that project rather than scrolling the whole organization’s binder — and it works offline, by QR from the container or the asset.
Every SDS carries a three-year review expiry, flagged before it lapses, so the version in the register is the one your people should actually be working to.
Not the question you had? Ask us directly — you get the people who built it.
You upload two things: your source of truth — your prequalification standard, a regulation, or a contract requirement — and the document being assessed. It extracts and compares the two, then reports where the document meets the standard, where it is partial, and what is missing, with the clause each finding was measured against.
No. It produces a scored findings report; a person accepts, actions or ignores each finding. What is automated is the reading, not the judgement — which is also what keeps the result defensible if somebody later asks why a contractor was approved.
They get a secure link by name and email — no login to create or lose. They answer your requirements and upload evidence, progress saves between visits, and deterministic rules plus AI evidence review score each answer into an overall grade.
Accepted findings become corrective actions with an owner and a due date, tracked to closure like any other action in the platform. Policies can be authored and versioned in the same place, with required signers and e-signature.
You can, and most clients tailor their own. GAPit also ships a library of pre-built compliance programs across jurisdictions that you can import into your framework as a starting point, plus a regulatory knowledge base that flags new or changed law.
Not the question you had? Ask us directly — you get the people who built it.
From the operational record you are already keeping — who was onboarded, who worked where and on what, what training they completed — plus whatever your own intake collects. Nothing is inferred, and nothing is reconstructed from payroll after the fact.
Visibility is controlled by role, because the reporting obligation and the privacy obligation are not the same thing. Someone can be able to run a participation report without being able to open an individual’s record.
Community benefit, local hire, spend by region, hours, training and participation are all reportable, and exports come out in the format the recipient asked for. Where a funder has its own template, the report is configured to match it rather than the other way round.
Yes. Readiness scoring compares your workforce against what a project actually requires, by skill, certification and region, and certification expiry is forecast rather than simply alerted on the day it lapses.
Yes — workforce, contractors and participation plotted by location and region, which is usually the fastest way to answer a question about local hiring or service coverage.
Not the question you had? Ask us directly — you get the people who built it.
Across all of them. Because assets, workforce, contractors, forms, training, incidents, tickets and projects sit on one record, a question like “which certified operators are within 50 miles of this site and clear of overdue actions” is a filter rather than a data project.
It puts the operation on a map. Search for workforce, assets, inventory, contractors or open work by region, site or radius, and see what is where before you dispatch a crew or order stock you already hold somewhere else.
Yes — participation, hours, training and completion, and demographic reporting where you collect it, which is what most funders, grants and program obligations ask for. Who can see those fields is controlled by role, because the reporting requirement and the privacy requirement are not the same thing.
Yes. Save a report, set who receives it and how often, and it goes out without anybody remembering to build it. The recipient does not need to be a heavy user of the platform.
Yes. Every chart drills into the records behind it, and reports export in the format you are asked for rather than the one the software prefers.
Not the question you had? Ask us directly — you get the people who built it.
SMS, email and in-app notification go to an audience defined by role, site, duty, crew or compliance status — so “everyone on the east yard tonight” is a query rather than a phone tree.
No. The audience is built from the operational record, which means it is current by definition.
Delivery and read status is held per recipient, and acknowledgement can be required where it matters.
No. The same engine runs scheduled outreach, campaigns and routine operational notices.
Not the question you had? Ask us directly — you get the people who built it.
Yes. Assignment respects the requirements on the duty, so somebody without a current certification is not quietly scheduled into work they are not cleared to do.
Yes, on the phone, with changes pushed as they happen and availability submitted back.
The same schedule. The distinction that matters is whether the person is cleared, not whose payroll they are on.
Yes. Your workforce and your contractors check in for their shifts and check out at the end, from the phone. A supervisor approves the entries, and approved hours carry to the project and the cost code rather than being re-keyed at the end of the month.
Not the question you had? Ask us directly — you get the people who built it.
Consumption at each location drives minimum and maximum levels and reorder points, so the order is raised against usage rather than against somebody noticing an empty shelf.
Requisition, approval, purchase order, receiving and transfers between locations, with the stock record updated at each step.
Before anything is committed, Tansi checks lot numbers and expiry dates for that product across every location and recommends using what is closest to expiring first. It then offers the choice: a transfer from the location already holding the stock, or a purchase order. The user selects, and the approver approves — so the decision to spend is still a person’s, made with the whole stock position in front of them.
Yes — vendors, catalogues, pricing and the documents that go with them.
Stock is held per location with transfers between them, so a shortage at one site can be filled from another before it turns into a purchase.
Not the question you had? Ask us directly — you get the people who built it.
Yes. PM schedules run on time, meter or condition, and corrective work orders are raised from an inspection defect or a reported fault against the same asset.
Anybody with access, from a phone — and a defect recorded on a form raises one automatically.
Yes, to named people rather than to a queue nobody owns. Tansi also shows you who is carrying the lightest workload at that moment, so work spreads across the crew and utilization stays even instead of landing on whoever is easiest to ask.
Add the external service record to the asset — date, provider, work performed, invoice and any documents that came with it. It sits beside the work your own crews did, so the asset carries one service history for its whole life and the proof travels with it.
Yes. Parts consumed on a work order draw down stock, so maintenance history and inventory stay consistent with each other.
Labour, parts and downtime accumulate on the asset record, which is what turns a repair-or-replace argument into an evidence-based decision.
Not the question you had? Ask us directly — you get the people who built it.
Both. Internal service requests and public-facing intake run through the same queue, with routing, priority and response targets set per request type.
A ticket can raise a work order against an asset or a location, and closes when that work does.
Support is handled in-house. Calls are answered by a person in the United States, escalation runs to engineering and then to leadership, and Severity 1 carries a 15-minute response target around the clock.
Yes, without leaving the platform. Pick one of four priority levels, describe what happened and attach screenshots. The priority you set is what drives the response target, and the ticket goes to our own team rather than into a queue somewhere else.
Yes, with updates posted on the ticket rather than obtained by phoning to ask.
Not the question you had? Ask us directly — you get the people who built it.
Operational rather than sales-first. Contacts, organizations, members and vendors sit on the same platform as the work, so outreach is informed by what actually happened.
Anyone held in your account — your own people, customers, members, vendors or leads — or any segment you can define from them. It works the same way the mass communication module does, so if you can describe the audience, you can send to it.
Yes. Send a quote with attachments, convert an accepted quote into an invoice without rebuilding it, and keep the contract and supporting documents on the same record — so the commercial trail and the operational one are not in two different systems.
Convert it into a project. From that point the same record carries the work — time and billables, the workforce assigned, contractor compliance, forms, assets and cost — so nothing is re-entered at the moment the job actually starts.
Yes, including registration, attendance and follow-up.
It can. The advantage is that the list is the operational record, so nobody exports a spreadsheet and hopes it is still current.
Not the question you had? Ask us directly — you get the people who built it.
A searchable register of organizations — vendors, contractors, members, partners — with their capabilities, certifications and contact points, published to whoever you decide should see it.
Yes, through their own portal access, which keeps the directory current without your team retyping it.
Your choice, field by field. Some clients publish it, some keep it internal, some publish a subset.
Yes. Alongside your own private directory, Tansi runs a free public business directory that any business can sign up to — the point of it being to promote local businesses. When the organization you need is not on your internal list, you can search the public one without leaving the platform.
Directory entries carry the prequalification and insurance status held elsewhere in the platform, so sourcing starts from who is actually eligible.
Not the question you had? Ask us directly — you get the people who built it.
