Check safety documents from subcontractors

AI reads subcontractors' worker rosters and certificate copies and finds expired or missing licenses, health checks, and insurance. Staff check requests first.

  • Construction
  • Legal & compliance
  • Operations & orders
  • Runs on your own PCs and servers
  • Use Azure OpenAI, Amazon Bedrock, Google Vertex AI, or an in-house model
  • Its engine is Descarty's open-source Dagu (GPL-3.0)

The problem today

For every subcontractor worker new to a site, staff check the worker roster and certificate copies one by one. Missing an expired certificate or a blank field goes straight to site safety, Subcontractors that don't use dedicated services such as Green Site or Buildee send documents on paper, as PDFs, or in Excel, each in its own format, and checks fall behind as sites multiply.

The workflow in Kitewell

  1. Add submitted rosters and certificate copies to a batch sheetAutomatic
  2. AI reads names, qualifications, expiry dates, health check dates, and insurance enrollmentAI judgment
  3. Extract expired, soon-to-expire, and missing itemsAutomatic
  4. Staff check the results and approve the request to the subcontractorApproval
  5. Send the request and track resubmissionsAutomatic

What AI does

Reads the needed fields from rosters and certificate copies in any format, quoting where each value came from.

Where people decide

Staff judge what is missing and make requests to subcontractors. Registration in systems such as Green Site stays with staff, under each system's terms of use.

Prove Kitewell on your own systems

Try it free for 14 days on your own PC. To see it working first, ask for a 30-minute demo. There is also a one-month onboarding (¥500,000 before tax), where we build your first job together.

What to check when you try this work

  • Whether the needed fields are read correctly from your main subcontractors' formats
  • Whether expiry and completeness rules match your safety procedures
  • How results are handed to the management system you use

How the onboarding runs

  1. Week 1Requirements and success criteria
  2. Weeks 2 to 3Build
  3. Week 4Verify on production screens
  4. Final dayReport

One-month onboarding

Length
One month
Cost
¥500,000 (tax excluded). Your staff build, with the developer beside them
If you go on to a license
The onboarding fee is credited to the first year's contract
Without the onboarding
At Team scale, start on Team monthly (¥14,800 per computer a month, tax excluded), and cancel in any month

You can try it first on your own PC, in the free 14-day trial.

See how the onboarding runs and its terms

Frequently asked questions

Is this needed if we use Green Site or Buildee?
For subcontractors whose documents are created and submitted in those services, use their expiry warnings and checks. This use case suits documents that arrive on paper, as PDFs, or in Excel from subcontractors that don't use them.
Can it enter the results into Green Site automatically?
In this use case, staff enter results into management systems such as Green Site. Whether a tool may operate a system depends on its terms of use, so the PoC checks the terms and automates only what they allow. The results can be exported to Excel or CSV for the entry work.
Do our documents and screens leave the company?
Kitewell runs on your own PCs and servers, and Descarty never receives your business data. You choose the AI model: a cloud API, or an in-house or local model with an OpenAI-compatible API. With an in-house model, no data leaves the company. With a cloud model, what the AI reads is sent to the model's provider.
What if the AI misreads something?
A person checks what the AI produced before the work goes on. In a sheet, every value the AI reads shows the quote it came from, and rows below your confidence threshold go to a person. Reviewers can send work back with notes on what to fix, and who approved what is kept in the run history.
What happens when a screen changes or a run stops?
When a screen changes, the AI reads it again, relearns the step, and carries on. The relearned step is saved, and later runs repeat it. If a run still stops, ask the assistant right there, and it finds the cause and proposes a fix. A proposal is not saved until a person applies it.
What happens to the RPA and systems we use today?
Keep them. Kitewell operates screens the way a person does, so it works with systems that have no API. Move the robots that keep stopping and the work you gave up automating because it needs judgment, and leave fast, fixed processing in your current RPA.
What does it cost?
¥14,800 per computer per month, or ¥148,000 per computer when paid yearly, before tax. A computer costs the same whether it builds or runs. You can try it free for 14 days. The one-month onboarding, where we build your first job together, is ¥500,000 before tax, credited to the first year if you go on.

See this work in a demo

A 30-minute demo shows this workflow running. The 14-day free trial lets you check it on your own systems.