Principles

What Gewerkton never does

A lot gets promised in construction. Here the limits are part of the product. A tool that records every event on a construction site could easily turn into surveillance of the people working there. This page says where we draw the line and how that line is anchored.

Send an objection The five limits

The subject

The building, not the workforce

What gets recorded is what was built: component, room, trade, deadline. Who said or did something is in the file, because a mapping without an author would be worthless. A picture of a person over time does not come out of it.

The five limits

The anchor

Not promised, but built in

The evaluation of people is not switched off by house rule but anchored as a permanent contract test. Anyone who wanted to build it in would have to break that test, and that shows. The self restraint is generated from executable checks of the codebase, not from a text module.

The five limits

After hours

After hours it stays quiet

Outside working hours nobody asks. No reminder, no callback, no silent follow up: the tool stops when the shift stops.

01The five limits

The five limits

Five limits that stand in the interface and not only in this text, in all 27 languages. The state is beta 2026; general availability is planned for 2027.

No evaluation of people

No location history per person, no evaluation of personal time spans, no work rankings. Presence is recorded by day, without time windows.

Quiet after hours

After the shift ends the tool rests. No notification, no query, no follow up.

Camera exclusion zones

Break room, container and changing room can be kept as exclusion zones. No recording is created there, not even by accident.

Data mirror

Every person sees what is stored about them. The mirror counts only their own records in their own organizations.

Sparse audit trail

The audit trail carries identifiers, counters and states. Plain text, names and paths are not in it.

This page describes product decisions, not a legal position. It says nothing about approval, official recognition or legal effect. What stands here is built or anchored as a check; where something is missing, we say so on the line page concerned.

02Trust register

Trust register

Evidence over rank: every step from the spoken word to approval stays traceable, while a suggestion never takes effect on its own.

01Capture

02Structure

03Prove

FIDICVOBJCTAIAConsensusDocs

FIDIC, AIA, ConsensusDocs, JCT, VOB and custom frameworks are versioned. Chops, hanko, dojang and company stamps are recorded only as technical confirmations, with no claim of special legal effect.

A continuous evidence chain

Conversation, transcript, suggestion and human decision form a continuous chronology that is never silently overwritten.

Fair to both sides

Before evidence protects client and contractor alike. Companies can challenge scorecards; site management records the decision.

03Language

Rendered daywork report containing German, Chinese, Japanese, Korean, Thai and Hindi text

Reports in every script

Embedded Noto fonts render Chinese, Japanese, Korean, Thai and Devanagari correctly in PDF reports.

Objections welcome

If one of these limits does not hold on your site, or one is missing, write to us. We take the objections into the beta.

Send an objection