Solutions · Construction & fit-out

AI consulting & training for construction & fit-outs.

Choosing a starting point and preparing the team. This page places the service mechanics next to the rules that apply in construction & fit-out — without claiming a project we have not done.

Discuss your scenario

Starting point

What construction & fit-out look like before any software

The first question that reaches a construction or fit-out company in the Republic of Moldova is almost never a request for a quote. It is a question about permission: ‘do I need authorisation to replace the windows?’, ‘can I enclose the balcony?’, ‘if it is only interior finishing, is anything needed?’. The law has an exact answer to each one, and it does not depend on the budget of the work, but on what is being affected. Works that do not alter the load-bearing structure, the exterior appearance or the original characteristics may be carried out without an urban planning certificate for design and without a construction permit, and the code lists the cases by name — interior finishing, replacement of joinery while preserving the shape and dimensions of the openings, roof repair without changing the shape and colour solutions, annexes of up to 15 square metres to individual houses on private land, outside protected areas. An automated response that says ‘it depends, call us’ misses exactly the information the law makes available to everyone.

The second reality is that the company does not sell only labour, it also sells a way of working. Design, verification and expert evaluation activities, as well as execution, reconstruction and capital repair, may not be carried out without notifying the National Inspectorate for Technical Supervision and registration in the State Register in the field of construction; in the absence of notification, carrying them out is prohibited. The notification requires, among other things, the statement on the composition of the teams, indicating the certified technical managers by field. The consequence for communication is direct: the status of ‘registered’ and the names of certified specialists are verifiable facts, and any presentation text that suggests them without having them is a statement that an inspection can dismantle.

In practice, the data are scattered between worlds that do not communicate. The request comes by phone or messenger, with photos of the apartment and the exact address. Measurements end up in a notebook and then in a spreadsheet. The estimate is made in an estimation programme. The contract is on paper, with the client’s name, identity document and address. The design documentation circulates as files between designer, verifier and beneficiary. And the public part of the file — the urban planning certificate and the permit — passes obligatorily through the state information system. The same personal data therefore pass through at least five systems, only one of which is designed for them.

The third reality is that, in construction, the file outlives the work. For all constructions falling under the code, the preparation, completion and keeping of the Technical Book of the construction is mandatory for the entire period of existence of the construction. It is prepared in one original copy on paper, which within three months of reception is transferred into electronic form and handed to the owner. It is not a passive archive: the owner completes the operating chapter and the event log, the results of the operational monitoring are entered once per quarter, and inspections are mandatorily recorded in it. The completion of acts of alienation of the construction without the Technical Book is prohibited. An information system that treats the project as ‘closed at reception’ contradicts the way the law counts time here.

Finally, what is public. In an industry perceived as discreet, part of the file is published by law, and anyone building software needs to know exactly which part. Within five working days from issuance, the issuer is obliged to publish on the official website of the local authority the depersonalised extracts from the registers and the depersonalised construction and demolition permits, with free and unrestricted access; if there is no website, on the information board within the authority’s premises. The word that carries the full weight is ‘depersonalised’: the authorised act is public, the person is not. A portfolio website that displays the full address of a private work together with the beneficiary’s name makes public exactly what the law has removed from publication.

A statement and its sources

Regulile

What applies in construction & fit-out, with the article it comes from

Each rule below carries the normative act that imposes it. Verification does not require you to take our word for it.

The permissive act is issued electronically, and one issued otherwise is null

The permissive acts provided for by the code are issued by the competent authorities, mandatorily, in electronic form, through the Automated information system for management and issuance of permissive acts; on paper only at the applicant’s request. The rule has teeth: the urban planning certificate for design that is not issued through this system is null, and the construction permit in which changes or corrections have been made is likewise null. When there are several permits for the same immovable property, the last one issued through the system is deemed valid. For a digital product this means that the source of truth about a file is not the PDF file received by the client, but the record in the state system.

SourceUrban Planning and Construction Code No. 434/2023, art. 2 para. (3), art. 108 para. (5), art. 148 para. (1), art. 152 paras. (2)–(3)

Issuance deadlines are fixed and have a written appeal route in the code

The urban planning certificate for design is issued within 30 days; the building permit is issued within no more than 30 days from the date of registration of the application. The refusal is also communicated within 30 days, in writing, with the reasons and the means of appeal. The Code also provides what the applicant does if the term passes in silence: they send, by registered letter, a notification to the National Anticorruption Centre and the National Technical Supervision Inspectorate, declaring on their own responsibility that they have received neither the act nor the refusal. A system that tracks files must count days from registration, not from submission, and must know what happens on expiry.

SourceUrban Planning and Construction Code No. 434/2023, art. 108 paras. (1), (6) and (7); art. 148 para. (1); art. 157 para. (2)

Issued permits are published in depersonalised form, within five working days

The issuing authority is obliged to register and transmit to the central database of the Register of Permissive Acts all information regarding the permits issued. Within 5 working days from issue, it publishes on the official website of the local public administration authority the depersonalised excerpts from the registers and the depersonalised building and demolition permits, ensuring free and unrestricted access for all persons; in the absence of an official website, these are displayed on the information board within the authority’s premises. Separately, interested persons have passive access through the single government open data portal. The public therefore has the right to the fact, not to the person.

SourceUrban Planning and Construction Code No. 434/2023, art. 159 para. (1) item c) and para. (2)

Construction activity is prohibited without registration in the state register

For design, verification and expert assessment, for execution, reconstruction and capital repair, as well as for the manufacture of construction materials and products, notification of the National Technical Supervision Inspectorate for the purpose of registration in the state register in the field of construction is mandatory; in the absence of notification, carrying out these activities is prohibited. The notification is submitted at least 10 working days before the start of the activity and includes the declaration regarding the composition of the teams, indicating the certified specialists or technical managers by field. It is made once, not for each site, but is repeated when activities are expanded or suspended.

SourceUrban Planning and Construction Code No. 434/2023, art. 10 paras. (2)–(5), (7) and (8)

Acceptance is mandatory, and an unaccepted construction is not used

The acceptance of constructions and related installations is a mandatory action, by which the completion of the works at the designed quality levels is established, and it is carried out by the investor with notification of the National Technical Supervision Inspectorate, which in turn notifies the authority that issued the permit. The use of constructions that have not been accepted is prohibited. For objectives financed from public money, acceptance is carried out in two stages — upon completion of the works and final acceptance — with no more than one year between them, and between the two stages the control body verifies the volume and cost of the works; for private financing, acceptance is carried out in a single stage. The acceptance act is a minutes signed by the commission, by which the investor declares that they accept and take over the construction.

SourceUrban Planning and Construction Code No. 434/2023, art. 192 paras. (2), (3), (6), (9)–(12) and art. 193 paras. (1)–(2)

The technical record is kept for the entire life of the construction and blocks alienation if it is missing

The preparation, completion and keeping of the Technical Record are mandatory throughout the entire existence of the construction. It is prepared by the investor in one original paper copy, transposed into electronic form within 3 months from acceptance and handed over to the owner. Until acceptance, it is kept on site, in a sealed fire-resistant metal cabinet, accessible only to the technical manager and the control bodies; after acceptance, it is kept by the owner, on paper and in electronic form, updated semi-annually during operation. It is prohibited to complete transfer or alienation documents for constructions without the Technical Record prepared and completed in accordance with the code.

SourceUrban Planning and Construction Code No. 434/2023, art. 229 paras. (1)–(2), art. 230 para. (1), art. 240 paras. (2), (3) and (7)

The warranty period is five years and runs from acceptance upon completion of the works

The warranty period is 5 years and starts from the date of acceptance upon completion of the works, including when acceptance is carried out in two stages; it may be shorter only for materials and products whose natural wear indicated by the manufacturer has a shorter term. During the warranty period, the contractor is obliged to remedy at their own expense the deficiencies arising from non-compliance with the design, the technical standards in force on the date of acceptance, or the contractual clauses. If the investor makes no request during the warranty period, the term is deemed to have expired. Any commercial text that promises a “warranty” without saying when it starts and what it covers contradicts a term written in the code.

SourceUrban Planning and Construction Code No. 434/2023, art. 225 paras. (1)–(4) and art. 226 paras. (1)–(5)

The personal data of the beneficiary individual need a legal basis, not just a file

A construction file usually contains the beneficiary’s name, address, identity document and national identification number, the notarised consent of the co-owners and the owner’s written consent. Processing a national identification number, including by collecting or disclosing documents that contain it, is done only in the situations of lawfulness provided by law, and where the basis is legitimate interest, the law requires guarantees called: data minimisation, security, retention periods set according to the nature of the data and the purpose, specific deletion or review periods, and periodic training of the persons carrying out the processing. For a contract there is a separate basis — performance of the contract or pre-contractual measures at the request of the person.

SourceLaw No. 195/2024 on the protection of personal data, art. 6 para. (1) lit. b) and c), art. 53 para. (1) and (2) lit. a)–c); Urban Planning and Construction Code No. 434/2023, art. 148 para. (1) lit. b) and c)

Mecanica

What AI consulting & training does, in concrete terms

The same capabilities that appear on the service page, where each has its own file and back-end line.

We request the primary document for each statement

A register with one statement per line: the primary document, the date, where it is found, whether it is publishable. The document that repeats the statement does not count as a source. Applied to us, the register eliminated three non-existent awards and confirmed three real ones, one of them through an original email found in the archive — a private source, showable on request, which no public search could have produced.

We measure production, not what the documentation says

The verification commands are included in the deliverable, so anyone can repeat them without us. When the document and the measurement do not agree, the measurement is right: while preparing this work, we found an internal document that declared a file about 16% smaller than it was, and an infrastructure diagram that described a server we had moved away from.

We declare what we could NOT measure

In our own accessibility and performance audit, the limitations section comes before the results and lists five things: render indicators the tool did not expose, keyboard activation the automation could not reproduce faithfully, the absence of screen reader tests, the inability to emulate the reduced motion preference, and the lack of field data. The conclusions drawn are marked as deductions, not observations.

We do not claim compliance levels we have not tested

The same audit contains no declared compliance level, because a complete audit requires testing with real screen readers, on real devices, with users — none of that had been done. What it does contain are individual findings, each with the relevant criterion, ordered so the work can be prioritised. Three blockers counted, the rest improvements.

We separate what can be published from what cannot

Technical fact from our own code: publishable, with the line. Actual project status: publishable, with the real reason, not the euphemism. Commercial result — clients, improvement percentages, volumes: not publishable without measurement and the client’s agreement. Comparison of the type “first” or “best”: not publishable without criterion and date. This grid applies before a line is written, not in proofreading.

We check consistency between what you publish and what the code does

The published policy and the implementation must not diverge, and divergence is hard to see from the inside. Examples from our own audit: the page promised IP address anonymisation, but the code sent it in full in a notification; the publicly declared retention period was not enforced by anything. The resulting rule: if a code change alters what is collected, where it goes, or how long it is kept, the published text changes at the same time.

The service, in detail

The data

What every system in the industry addresses

The data classes held by construction & fit-out, with the legal basis for retention where the law provides it.

Authorisation file: The request, the extract from the project documentation, the notarised agreement of the co-owners, the owner’s written agreement, the positive inspection report, the approvals. It is the class with the greatest mix: it contains the personal data of the beneficiary and of third parties (co-owners, neighbours), technical documents protected by copyright and notarised acts. It also has a procedural particularity: the person receiving the request is not entitled to examine the content of the attached acts, refuse receipt or request additional documents — their competence is limited to registration, to noting that the acts are attached and to issuing the confirming certificate.Keep: Unverified as a term. The Code requires that information about issued authorisations be sent to the central database of the Register of Permissive Acts and that the second copy of the urbanism certificate for design be kept in the issuer’s archive, without setting a duration; the archiving term at the issuer depends on archival legislation, which we have not verified.SourceUrban Planning and Construction Code No. 434/2023, art. 108 para. (3), art. 148 para. (1) items a)–g), art. 159 para. (1) item c) and para. (3)
Technical book of the construction: Four chapters: design documentation, execution documentation, reception documentation and documentation on operation, maintenance, repair and monitoring in operation, plus the central register with the summary data sheet and the slips. Chapters A, B and C are finalised before reception; chapter D is completed during operation. It is the class that ties all the others together: the importance category of the structure is entered in it, the results of inspections are recorded in it as mandatory, and its restoration in case of loss or damage is carried out by a certified technical expert engaged by the investor.Keep: Throughout the entire lifespan of the structure, until the demolition authorisation is obtained; on paper and in electronic form, updated semi-annually during operation. After demolition, the owner hands it over for archiving to the local public administration authority, by handover-takeover deed. When completion is done through the state information system, archiving is carried out through that system.SourceUrban Planning and Construction Code No. 434/2023, art. 229 paras. (1)–(4), art. 231 paras. (1)–(4), art. 239 para. (2), art. 240 paras. (3), (5) and (9)
Event log: The living part of the Technical Book, kept by the owner for the duration of operation. The results of monitoring behaviour in operation and the condition of the structure are entered once a quarter, if the special monitoring project does not provide another term; in exceptional events — fires, floods, landslides, earthquakes with an intensity higher than the normative one — the structure is examined, and the results are entered here as well. On transfer of ownership, the new owner records the fact in the transfer contract and in the event log.Keep: The same as the Technical Book it belongs to: the construction’s service life, then archiving with the local authority after demolition.SourceUrban Planning and Construction Code no. 434/2023, art. 240 para. (4) and (8), art. 241 para. (1)–(2)
Data of the natural person beneficiary: Name, address, identity document, national identification number, contact details, sometimes ownership status and family consents. They end up in the authorisation dossier, in the contract, in estimates and — most often — in a messenger, because the discussion started there. They are collected on the basis of a contract or pre-contractual measures at the request of the person, and the national identification number has its own article, with its own safeguards, which are not activated because it is convenient to have it.Keep: Unverified as a fixed term established by an act in the field of construction. It is determined by the operator, based on the nature of the data and the purpose, with specific deletion or review periods, and is declared in the record of processing activities. For documents that are included in the Technical File, its duration applies.SourceLaw No. 195/2024, art. 5 para. (1) lit. e), art. 6 para. (1) lit. b), art. 30 para. (1) lit. f) and art. 53 para. (2) lit. b)
Project documentation and the copyright over it: The explanatory memorandum, plans, facades, colour solutions, the execution organisation project, the specifications. It is not just technical content: the code has a chapter on protecting copyright in project documentation and on its repeated use, and the construction importance category is determined by the designer and entered in all related technical documents. The consequence for a site or an assistant that “shows projects” is that the material has an author with rights, even when the client has paid for the work.Keep: As part of Chapter A in the Technical Book — the lifespan of the construction. As a working file at the design office, the registration notice in the state register requires the declaration of the persons responsible for the record-keeping and archiving of documents, but does not set a duration; the term is established at company level.SourceUrban Planning and Construction Code No. 434/2023, art. 10 para. (4) item a), art. 128 paras. (3)–(4), arts. 142–144, art. 231 para. (2) item a)
Site photographs and photographs of the completed object: The material that feeds any industry presentation. There are two overlapping problems. The first is that the image of an inhabited interior or an identifiable façade can lead to a person, which makes publication a processing activity with its own legal basis. The second is that the law has already chosen the regime for the public side of the dossier: what the public authority publishes is depersonalised. A company that publishes more than the state, about the same work, is not more transparent; it is in a position that it cannot justify.Keep: Unverified as a term. We have not identified an act that fixes the retention period of a construction company’s photographic material. It is established by agreement with the beneficiary, with the term written down, and declared in the record of processing activities.SourceLaw No. 195/2024, art. 5 para. (1) lit. e), art. 6 para. (1) lit. a) and art. 30 para. (1) lit. f); Urban Planning and Construction Code No. 434/2023, art. 159 para. (2)

Limbajul

The words people there use

An agent that says “programming” where the industry says otherwise is immediately heard as foreign. That is why vocabulary goes into configuration, not into the glossary at the end.

Informative / design urbanism certificate: Two different acts, constantly confused. The informative one is optional and is needed in land relations, in alienation, division, parcelling, amalgamation, partition, inheritance or property disputes. The design one is regulatory and is mandatory when the approved general urban plan is more than 10 years old, optional when it is newer; it allows the preparation of the project documentation.
Building permit: The act by which the execution of works is authorised, on the basis of the approved territorial planning and urbanism documentation and the project documentation. It is not “approval of the project” and it is not “the town hall’s consent” — it is a permissive act with content defined by law: location, special execution conditions, the designer, the start date, the execution period and, for public objectives, the value of the works.
Investor, beneficiary, contractor: Three roles that, in everyday speech, merge into “client” and “builder”, but in the code have different obligations. The investor is the one who finances and, as the case may be, carries out; the beneficiary is the one who benefits from the completed and accepted work; the contractor is the one who carries out the work. Acceptance is carried out by the investor; the warranty is owed by the contractor; the Technical Book is drawn up by the investor and kept by the owner or user.
Importance category: The classification of the construction into A (exceptional), B (special), C (normal) or D (low), with the corresponding consequence classes. It is determined by the designer, is only one per construction and is entered in the project documentation, in the building permit, in the Technical Book and in the insurance documents. It is the word that determines who must be present at acceptance and which obligations apply.
Technical book of the construction: It is not “the work file” and it does not close at acceptance. It is the set of documents concerning design, execution, acceptance, operation, maintenance, repair and monitoring during operation, plus post-use, kept for the entire life span of the construction. Its absence legally blocks the alienation of the construction.
Acceptance upon completion of works and final acceptance: Two stages, not two names for the same thing. For objectives financed from public funds, acceptance is carried out in both stages, with at most one year between them, and in between the control body checks the volume and cost of the works. For private financing, acceptance is in a single stage. The warranty period runs, in both cases, from acceptance upon completion of works.
Technical supervisor and site manager: Certified persons, not freely chosen internal roles. The site manager role may be held only by certified persons, and the notice by which a company registers in the state register requires declaring the certified technical supervisors by field. Until acceptance, the technical supervisor is the one who keeps the Technical Book on site.
Permissive act: The category to which the urban planning certificate and the construction and demolition permits belong. The term matters because it brings with it the mandatory electronic regime — issuance through the state information system — and registration in the central database of the Register of Permissive Acts.
Works without a permit: This does not mean “works without rules”. The Code expressly lists what may be carried out without an urban planning certificate for design and without a permit: interior finishing works, replacement of floors and joinery while keeping the shape and dimensions of openings, roof repairs without changing the shape or colour solutions, annexes of up to 15 square metres to individual houses on private land. The general condition is that the load-bearing structure, external appearance or original characteristics are not modified, and the exceptions for monuments and protected areas remain.
Depersonalizat: The word the Code uses for the form in which permits and extracts from registers become public. It is the practical benchmark for any company content about real works: the authorised act is public information, the beneficiary’s identity is not.

Where it breaks down

What goes wrong when construction & fit-out are digitalised in a hurry

The project considered closed at reception

The most common wrong model in construction software is the lifecycle taken over from other industries: offer, contract, execution, handover, archive. In construction, handover does not close anything. The technical record is completed throughout the construction’s entire existence, updated every six months during operation, the event log receives entries once a quarter, and the warranty runs for five years. A system that moves the file into a read-only archive at reception pushes exactly the work the law requires after reception back into files on someone’s desktop.

The portfolio that publishes more than the state publishes

The mechanism is simple and almost universal: someone wants proof, and the most convincing proof seems to be the exact address and the name of the satisfied client. The law has already decided otherwise for the public side of the file — permits and extracts from registers are published in depersonalised form. The result is a strange asymmetry, in which the private company exposes what the authority has removed from exposure, without any basis it can show. The fix costs nothing if done at the start: written consent from the beneficiary, with purpose and term, and a content rule that says what is never published.

The “it depends” answer to a question answered in law

When the client asks whether they need a permit for interior finishing or for replacing windows while keeping the openings, the answer is in the Code, expressly listed. A company that answers “it depends, come to us” loses twice: it loses trust, because the information was public, and it loses the questions that really matter — whether the load-bearing structure is affected, whether the external appearance changes, whether the property is a monument or in a protected area. A well-built assistant gives the full rule and then asks the three questions that move the case from one category to another.

The estimator that becomes, in the client’s eyes, an offer

A price calculator placed on a site produces a number, and the number is remembered. When the real estimate comes, the difference is not read as “the estimate was an estimate”, but as a price change. The mechanism by which it breaks is one of design, not calculation: the result is displayed as a single sum, in a field that looks like a total. The difference is preserved by showing the range, the assumptions that produced it, and what can change it — the category of importance, the real condition found on site, the required approvals.

Documents for the works living in messaging

The photo of the identity card, the scanned plan, the neighbour’s photographed consent — all end up in a messenger because that is where the discussion started. The copies stay there without a deadline, without an access log and on infrastructure that is not the company’s, while the documents they belong to have, some of them, an obligation to be kept for the entire life of the building. This is not fixed by instructions given to the team. It is fixed by a single place where the document is uploaded, with its own gateway, while messaging remains for conversation.

Deadlines counted from the wrong day

The deadlines in the code run from the registration of the application, not from its submission at the counter and not from the moment when the file was considered internally complete. Anyone tracking files in a spreadsheet usually writes the date the envelope was sent. The difference of a few days seems small until the moment it matters: at 30 days due for the certificate or authorisation, at 5 working days for publication of the issued authorisation, at the notice by registered letter that the applicant may send if the deadline passes in silence. A useful system records the registry date, not the dispatch date.

Questions

What someone in construction & fit-out asks before buying software

Can an automated assistant tell the client whether they need authorisation?

It can say what the law says, and that is already a lot. The Code lists by name the works that may be carried out without an urbanism certificate for design and without a building authorisation, provided the general condition is met not to modify the load-bearing structure, external appearance or initial characteristics, and with the exceptions for monuments and protected areas. What an assistant cannot do is qualify a concrete work: whether a wall is or is not load-bearing, whether the façade faces the boulevard, whether the property is in a protection area. That is how the answer is built correctly — the full rule, then the deciding questions, then referral to the person who can establish the facts.

Can you make us a price configurator that gives a quotation on the spot?

We can build an estimator, not a quotation. The difference is not in precision, it is in status: the quotation is part of the technical documentation, and the construction importance category, which determines the required quality level, is established by the designer, not by a form. What works in practice is a tool that gathers the data that matter — the type of work, location, areas, desired deadline, what is being touched in the construction — and hands them over structured to the person who evaluates, with a margin displayed explicitly as an estimate.

Can we publish the works done, with addresses and photos?

Carefully, and the best benchmark is the law itself. The state publishes authorisations and extracts from registers in depersonalised form — the act is public, the person is not. A company that publishes more than the state about the same work ends up in a position it cannot justify. In practice: the type of work, the city or district, the technical solutions and the photographs that do not lead to an identifiable person or dwelling may be published with written consent; the exact address, the beneficiary’s name and the inhabited interiors may not, unless with separate consent, with purpose and term written down.

What evidence can we request or show about the company’s quality?

Those that exist in a register. Design, checking, expert assessment, execution and manufacturing activities cannot be carried out without notifying the National Inspectorate for Technical Supervision and registration in the State Register in the field of construction, and the notification requires declaring the certified specialists and technical responsible persons by field. These are verifiable facts and can be stated. What cannot be stated are certifications, awards or standards that you cannot show with a document — and we do not write them, even if asked.

How long must we keep the documents for a job?

For the documents that go into the Technical Book, the answer is written down: for the entire lifespan of the construction, on paper and in electronic form, updated semi-annually during operation, with transfer for archiving to the local authority after demolition. For the rest — messages, offers, measurements, photos, the contact details of clients who have not signed — we have not found a term fixed by an act, so it is set by the company with justification, written down once and applied automatically. A term written only in a policy and nowhere in the system is not a term.

Who is responsible if the work has a defect after acceptance?

The warranty period is 5 years from acceptance upon completion of the works, including when acceptance is carried out in two stages, and during that period the contractor is obliged to remove at its own expense the shortcomings arising from non-compliance with the design, the regulations in force on the date of acceptance or the contractual clauses. If the technical expertise shows that the defect arose for other reasons, the cost is not charged to the contractor. We do not establish fault and do not build systems that establish it; what we build is the path through which the report reaches the person who decides, documented, with date, description and evidence.

Do we need a data protection officer?

For a private construction company, the obligation is not automatic: it arises when the main activities consist of periodic and systematic monitoring of persons on a large scale, or processing on a large scale of special categories of data or data relating to criminal convictions. An execution company does not, as a rule, fall into either category. That does not exempt you from the rest of the obligations — legal basis, term, security, records of processing activities. If you work as a subcontractor for a public authority, the situation is different: for it the obligation is automatic, and the requirements flow down through the contract.

Where do the data go if we use a language model for requests?

It is established in writing before the first line of code: which fields are allowed to leave the company, to which supplier, on what basis and for how long. The practical rule we apply is that the national identification number and copies of identity documents never leave; what leaves, if anything, is the description of the work, not the person’s identity. In construction this is easy to comply with, because the two can be cleanly separated: the technical description of a work does not need anyone’s name to be useful.

Can we connect our system to the state authorisations system?

We do not have a built integration with the automated information system through which permissive acts are issued and we have not checked whether there is a public interface for it — it is unverified, not "yes, it can be done". What is verified is that the issued acts reach the central database of the Register of permissive acts and that the depersonalised authorisations are published on the local authority’s web page within 5 working days, with free access, plus passive access via the open data portal. A realistic workflow starts from what is public, not from an integration we cannot promise.

Can you help us with the compliance part of the documentation?

No. The verification of project documentation, technical expertise and the management of works are activities reserved for certified construction specialists, who bear disciplinary, civil, contraventional or criminal liability for non-compliance with the quality system. We are not, and cannot be, in that position. What we do is the IT part: ordering the documents, tracking deadlines, structuring the requests and the route by which things reach the certified person with full context.

What we cannot claimWe are not a construction company, we are not registered in the State Register in the field of construction and we do not have any certified construction specialist. We do not design, check or perform expert assessment of project documentation, we do not manage works and we do not take part in acceptance — these are activities reserved by law for certified persons, who bear personal responsibility for them. We do not legally qualify a specific work: if you need to know whether an authorisation is required for a particular case, it is not us who says so, but the issuer or a certified specialist. We do not draw up or complete the Technical Book of the Construction on anyone’s behalf. We do not have a built-in integration with the automated information system through which permissive acts are issued and we have not checked whether there is a public interface for it — it is unverified, not available. We do not hold quality certifications, technical approvals or accreditations in the field of construction and we do not declare them. We have not published our own results in this industry, we cannot cite client names, and we do not have verified market figures for the Republic of Moldova — neither about the volume of construction, nor about prices, nor about demand.

The service, in detail What we actually built All scenarios

The service, appliedWe have not yet delivered exactly this combination. What you read above is the mechanism of our service, verifiable on its page, set alongside the rules that govern construction & fit-outs — each with the article it comes from. What we have actually built sits on the service page and in the portfolio.

Sources 9 sources · verified on 2026-09-07

What would you want to work better?

Tell us about your process. Together we decide what is worth building, what we can connect, and how we check the result.

Let's talk