Use Cases

How a Construction Contractor Manages a Project in PRO-dela: Stages, Costs, and Acceptance

An end-to-end scenario for a construction and renovation contractor: a project as a project with work stages, tasks for crews, material and expense tracking, budget, documents and photo documentation, stage acceptance by the client, and invoicing for completed work.

Updated July 27, 2026
How a Construction Contractor Manages a Project in PRO-dela: Stages, Costs, and Acceptance

A construction or renovation contractor manages each project in PRO-dela as a separate project: with work stages, tasks for crews, material and expense tracking, budget, documents, and client acceptance. This addresses the constant pain point of contract work—when estimates, actual material costs, client correspondence, and work status live in different places, and you can only get a real picture of the project manually.

Below is an end-to-end scenario: how to take a project from measurement and estimate to handover and invoicing, maintaining the link between what was planned, what has been done, and how much it cost. You don't need to implement everything at once—you can start with stages and expenses, and add the rest as you go.

Where control over a project is usually lost

On a project, dozens of small tasks happen simultaneously: measurement, procurement, rough work, engineering, finishing, addressing defects. The foreman keeps everything in their head and in correspondence, materials are recorded in a notebook, and the client learns the status by phone. With one project, it's manageable. With multiple projects, confusion sets in: expenses for one project are recorded against another, client comments get lost, and by the time of handover, no one can quickly show what was done and for how much.

PRO-dela helps not to replace the foreman, but to give the project a common language: what stages, what work on each, who is responsible, how much has been spent on materials, and what has been accepted by the client. Then "how much have we already invested in this project" ceases to be an evening question with a calculator.

Step 1. Project as a project with a scope of work

Each project is created as a separate project. Its scope of work defines the framework: what the project is, the scope of work, constraints, initial conditions, and acceptance criteria. This protects against the classic dispute "we didn't agree on that"—the agreement is documented, not left in the parties' memories.

The scope of work works on three levels—the project as a whole, a specific stage, and an individual work task. The overall project description is not mixed with details of a specific node, which is convenient when different crews work on the project.

Step 2. Break the project into work stages

The project path is broken into stages that follow the real sequence: demolition, rough work, engineering systems, finishing, addressing defects, handover. Each stage has its own tasks, requirements, and files (plans, diagrams, photos), and tasks attached to a stage are embedded in its timeline.

Stages give the client and the crew a clear map instead of a scattered list. The client sees that the project has passed the rough stage and is at engineering, rather than trying to piece it together from phone calls. More about stages in the article "Projects and Stages".

Step 3. Tasks for crews and responsible persons

Work on a stage is organized as tasks: chasing, wiring, laying, installation. The performer—a crew or a specific specialist—is assigned from the project participants, and not necessarily immediately: you can create a task and assign a responsible person later. Large work is broken into subtasks, and a recurring set of operations (a typical stage for similar projects) is saved as a template and expanded in one action.

Priority helps separate what blocks the next stage from what can be done later, but does not reorder tasks automatically. Who has the right to assign a responsible person, change status, and accept work is determined by the participant's role—more in the article "Roles and Team Members".

Step 4. Material and expense tracking by project

Materials and other costs are recorded as expenses against tasks, not in a separate notebook. This is key for a contractor: actual expenses and progress are collected in the project budget statistics, so at any moment you can see how much has been invested in the project and how it compares to the plan.

An estimate of work or stage—in cost—can be recorded in advance and, if necessary, agreed with the client as confirmed. This way, the estimate is no longer a static file at the start but is linked to the actual progress of work. More in the articles "Project Budgets" and "Time and Expense Tracking".

Important: PRO-dela does not replace an estimating program, accounting, bank, or legally significant document flow. It links expenses and work to the project, not to official accounting.

Step 5. Documents and photo documentation next to the work

Plans, diagrams, measurements, before-and-after photos are stored as attachments directly in the relevant task or stage. Files are secure attachments, not public links: access is checked both to the task and to the file's belonging to that task.

This reduces the risk of working with outdated plans and simplifies communication with the client: photo documentation of a stage is next to the work of that stage, not buried in correspondence from three weeks ago. Project documents and reports help gather the project picture in one place.

Step 6. Stage acceptance by the client

Acceptance for a contractor is not a formality but protection against rework "within the same budget." When work on a stage is completed, the performer marks it as finished (finish) and assigns an acceptor—a client representative among the project participants, but not the performer themselves. The client either accepts the result (accept) or rejects it (decline) with a clear comment, returning the work. An erroneous acceptance can be undone via reopen.

Thus, "the crew considers the node ready" and "the client has accepted the node" become different states with a history. Comments are recorded in the system, not spoken orally and forgotten by the next visit.

Step 7. Invoicing based on completed work, not memory

When a stage is accepted, an invoice is generated based on the completed work and recorded expenses, with line items and documents. There is no need to reconstruct from correspondence what was done and for how much over the month—the data is already collected in the project.

For a contractor with multiple projects, this is especially important: each invoice is tied to its project, and budget statistics show the project picture without manual reconciliation. More about invoices in conjunction with projects in the overview article "Platform Capabilities".

Multiple projects and clients simultaneously

When there are multiple projects, separation into projects helps, and if necessary, into companies. A participant sees only the projects they have access to, and a manager does not confuse expenses and work between unrelated lists. If a contractor operates through multiple legal entities, they are separated into different companies with their own participants, roles, and tariffs.

Notifications, including via Telegram when configured, help you learn about completed work or client comments on any project in a timely manner, without calling foremen.

Frequently asked questions

Isn't this too complicated for construction?

You can start small: create a project, break it into a few stages, and track expenses by work. Tasks, documents, estimates, and invoices are added as needed, not on day one.

Will PRO-dela replace an estimating program?

No. The platform does not handle official estimates or accounting. It links expenses, work, and acceptance to the project so you can see at any moment how much has been invested and what has been accepted—it does not replace specialized estimating or accounting software.

How will the client see the project status?

The client is invited to the project with a role that defines their access. They see stages, current materials, photo documentation, and work status, and participate in stage acceptance—instead of a "call the foreman" status.

Can I manage multiple projects simultaneously?

Yes. Each project is a separate project with its own stages, expenses, and documents. Multiple legal entities are separated into different companies. Expenses and work of one project are not mixed with others.

Create your first project

Register in PRO-dela and create a project for the project you are currently working on: break it into stages, create the nearest work as tasks, and start recording material expenses. In a week, you will see whether a unified framework helps keep the project under control without an evening calculator.

Before starting, you can check current tariffs and the overview article "Who PRO-dela is for". Don't try to digitize all projects at once—start with one current project.