M·01
Projects, phases and schedule
Phases, milestones, deadlines and budget. Delays show up on the list.
source · Opis modułu Konik Structure
Projects and construction sites in one systemEvery project under control. From the first drawing to handover._
Konik Structure runs a project where the work happens: on site, in the design office and with the client. Phases, schedule, budget, subcontractors and documents sit in one place. Crews log their work by phone, and every handover has a protocol. The project manager sees a delay before the client calls.
Stage 01 · Chaos01 / 03
02 · Problem · Diagnosis
The schedule lives in a spreadsheet. The site lives in group chats.
Drawings travel by email in several versions, and site decisions get lost in people's phones. We start with four questions that we also ask in the Diagnosis.
What you see
A subcontractor works from an old drawing. Crew hours and fuel receipts don't match what happened on site. The client report gets stitched together from several files late in the evening.
How it feels
You hear about a delay from the client. At handover nobody remembers who reported a defect or when it was fixed.
How it should be
Every phase has a deadline, a budget and one person accountable for it. Every document has a version and an author, and every handover has a protocol.
[ 4 Diagnosis questions ]S · P · I · N
- SituationWhere do you keep the schedule, the drawings and your subcontractor contracts today?
- ProblemHow do you know a crew is working from the current version of the drawings?
- ImpactWhat does a phase cost you when it slips two weeks because nobody spotted a subcontractor running late?
- NeedWhat would change if the client got progress reports straight from the system and you saw delays first?
When I run several projects at once and my people are out in the field, I want to have phases, documents, crews and handovers in one place, so that I see delays first and hand over each project with complete paperwork.
You are not buying a drawing tool or another spreadsheet. You are buying one place where a project has its deadlines, people, documents and proof of handover.
01 · Chaos02 · Integration
Stage 02 · Integration02 / 03
03 · How it works · Flow
From project setup to the client report. At every step you know who does it.
This is how Konik Structure works. The system tracks deadlines, versions and reminders. People decide on phases, changes and handovers.
Project and phases
HumanThe project manager sets up the project: phases, milestones, schedule and budget. Each phase has a person accountable for it.
Roles in RACI
HumanFor each phase you record who does the work, who is accountable, who to consult and who to inform. A phase without an accountable person shows up as a gap.
Subcontractors and suppliers
HumanEach subcontractor has a scope, deadlines, a contract and settlements. They see only their project and their part of the work.
Versioned documents
SystemDrawings, approvals and permits are in one place. Every change saves a new version with the author and date.
Field crews
HumanA worker scans a QR code with their phone to start work, check out equipment or log refuelling. Site photos go straight into the project.
Deadline tracking
SystemThe system compares progress with the schedule and sends reminders. The project manager sees a late phase on the list before it turns into a problem.
Phase handover
HumanA handover has a protocol, photos and a snag list. Each defect gets an owner and a deadline, and a signature closes the phase.
Client report
SystemThe progress report is built from project data: phases, deadlines, budget, handovers and photos. The client sees it in their own view.
Clients and subcontractors see only their own project and scope. A person approves every document change, handover and phase closure.
04 · Modules
What Konik Structure does.
Everything runs in Konik CRM, on the same data as your clients, contracts, tasks and company documents.
M·02
Subcontractors and suppliers
Scopes, deadlines, contracts and settlements. Each party sees only its own part.
source · Opis modułu Konik Structure
M·03
Project documents
Drawings, approvals and permits with version history and the author of every change.
source · Opis modułu Konik Structure
M·04
Handovers and snags
Phase handover protocol, photos, a snag list with owners and deadlines, and a signature.
source · Opis modułu Konik Structure
M·05
Field crews
Working time, equipment and fuel logged by QR code, plus site photos straight from the phone.
source · Opis modułu Konik Structure
M·06
Roles, RACI and permissions
Project and company structure: who does the work, who is accountable and who sees what in Konik CRM.
source · Opis modułu Konik Structure
M·07
Client report
Progress, deadlines, budget and handovers in one report, built from project data.
source · Opis modułu Konik Structure
05 · Rules · System limits
Rules the system enforces.
On a construction project, disputes start with who saw what and who approved what. These rules keep that clear.
Z·01
Everyone sees their own scope
The client sees their project. A subcontractor sees their scope. Permissions are set by the person responsible in your company.
source · Opis modułu Konik Structure
Z·02
Version and author on every change
Each change to the documents saves a new version. Earlier versions stay available.
source · Opis modułu Konik Structure
Z·03
Handover only with a protocol
A signed protocol closes a phase. Snags on the list have an owner and a deadline, so nothing gets lost between handovers.
source · Opis modułu Konik Structure
Z·04
A gap instead of a guess
When a phase has no accountable person, the system flags it for a decision. It never assigns anyone on its own.
source · Opis modułu Konik Structure
02 · Integration03 · Awakening
06 · Proof · Case studies
We publish case studies with data and client consent.
Konik Structure case studies will appear here once a client agrees to publication, with the period and the source of every figure.
In every Konik System implementation we map roles and responsibilities in RACI in Konik Structure together with the client.
07 · Pricing · Net
Prices are in the Stable. Scope is set in the Diagnosis.
Prices for all Konik System products, net and gross, are listed in the Stable. In the Diagnosis we look at how many projects you run and who works in the field, then you get the scope in writing.
- The scope of your Konik Structure implementation is set out after the Diagnosis, in the Implementation Card.
- Project data, documents and photos belong to you.
Offer for businesses (B2B). Prices in the Stable are shown net and gross (23% VAT). The price list is for information only and is not an offer within the meaning of Article 66 § 1 of the Polish Civil Code. The contract is binding.source · Stajnia Konik System
All systems and the Complete system on one page, with prices from, in EUR.
08 · FAQ · Final objections
Questions people ask before they decide.
With a Konik System Diagnosis: a conversation, a review of your processes and systems, classification of your AI systems under the EU AI Act and a report with recommendations. The report says which projects and crews to start with.
Yes. Each gets an account with access to their own project and scope. The client sees progress and reports. A subcontractor sees their tasks, deadlines and documents.
With their phone. A worker scans the QR code on a vehicle, a machine or the site and logs the start of work, an equipment checkout or refuelling. Site photos go in the same place.
It runs inside Konik CRM. Projects sit with the client record, tasks go to people on your team and documents go to the company's shared file store.
On servers in the European Union or on your own server. Sign-in is protected by two-factor authentication, and each person sees only what they have permission to see.
A person with the right permission, whom you choose. The system saves versions, sends reminders and builds reports, but it never closes a phase or a handover by itself.
09 · Diagnosis · One decision
Let's start with a Diagnosis.
Leave your details. We will call you back within one working day and set a date for the Diagnosis: a conversation, a review of your processes and systems, and a written report.