14In any establishment with more than twenty workers, the CLT (Consolidação das Leis do Trabalho, Brazil's Labor Code) requires that entry and exit times be recorded; when the work is performed outside the establishment, the working hours appear in the record the employee carries (art. 74, §§ 2 and 3). A construction site is work outside headquarters.
An engineering company with several projects under way therefore has several sources of records, each with its own rhythm, and a single responsibility for all of them. Whoever makes sure those sources reach the company complete, in the same format and on time holds the seat of the site administrator (administrador de obras). C&S Engenharia understands it in a way that runs against the name: the role does not administer a single project.
This text describes the role as C&S Engenharia practices it and how it distinguishes it from the resident engineer, the general coordinator and procurement management. The reading is C&S Engenharia's own, marked as such. None of the standards consulted defines the position; they define the obligations it supports, cited throughout the text.
The name suggests a site manager. C&S Engenharia's practice is different: the site administrator is a support role, in a dotted-line relationship to those who decide. It answers functionally to management (CEO, CFO and COO) for administrative matters, and supports the resident engineer, the general coordinator and procurement management without taking the place of any of them. The technical hierarchy of the project stays entirely with the resident engineer.
The administrator keeps fixed hours at one project, because administration needs a floor where the real routine takes place. But the assignment is the whole portfolio. And a portfolio is not administered by visiting: it is administered through information. The other projects send the data the role needs, and the administrator checks whether it is complete, whether it is consistent and whether it conforms to what the law and the contract require. Where the data does not fit, the administrator asks, in writing, the person responsible for the project.
On separate projects, the same fact comes out in different formats: attendance in a spreadsheet, cash in a notebook, the permit in someone's folder. The sum is manual, late and unreliable. The role creates the standard: what each project sends, in what format, by when, and the checking rule. The gain lies in turning six versions into one comparable series.
| Routine | Without a portfolio-wide standard | With the site administrator |
|---|---|---|
| Attendance and personnel records | Each project records in its own way; the company finds the gap when it has to prove something | Single format, periodic delivery, gap checking |
| Documents of subcontractors and suppliers | Paper scattered across projects | Single register with expiry dates, retained balance and history |
| Licenses, permits and registrations | Each project discovers its own expiry date | Single calendar with renewal started well ahead |
| Site cash | Accounts rendered with different deadlines and categories | Standardized, reconciled accounts, comparable across projects |
| Incidents and open items | Live in the foreman's memory | Single record that management can consult |
The resident engineer receives the administrative routine off their hands and the certainty that whatever depends on paper has been checked; their time stays on the site. The general coordinator receives the consolidated administrative view, so that a borderline decision does not depend on hunting for documents. Procurement management receives the standing of suppliers and subcontractors and the receiving history, so that the next purchase is made with data. The CFO receives the standardized site cash accounts and the retentions owed. The COO receives the comparison between projects. The CEO receives the company's administrative risk picture: what is open, what has been closed, what is falling due.
The dotted line has a practical consequence. The administrator gives orders to no project. The administrator points out, with data, what is out of conformity, and the decision stays with whoever holds the mandate to make it.
The CLT states that, in a subcontract, the subcontractor answers for the obligations of the employment contracts it enters into, but its employees may bring claims against the main contractor, who retains the right of recourse and the retention of amounts owed to the subcontractor (art. 455 and sole paragraph). And Law 8.212/1991 (the Social Security funding law) makes the contracting party of services performed with the assignment of labor jointly liable with the performer for social security obligations, without benefit of order, also with a right of recourse and retention (art. 30, VI).
The defense instruments exist, but they depend on timely data. For all subcontractors on all projects, the site administrator maintains periodic checking of labor and social security compliance, and the retained balance. When the same subcontracted company works on three projects, only a portfolio-wide reading shows the size of the exposure.
Law 6.496/1977 subjects every engineering works or services contract to the Anotação de Responsabilidade Técnica (ART, the technical responsibility record) and provides a fine for the professional or company that lacks it (arts. 1 and 3). Law 5.194/1966 (which regulates the engineering, architecture and agronomy professions) requires companies organized to carry out works to register with the regional councils before starting activities (art. 59).
Issuing the ART is an act of the technical manager, not of the administrator. What falls to the administrator is confirming that it exists for each contract and that the company's registration is current. The same applies to permits and licenses, each with its own validity. A single calendar prevents one project from stopping over an expired document that another project has already renewed.
Small expenses, reimbursements and advances generate many entries. On several projects, this is where traceability is lost. The administrator standardizes the rendering of accounts (same spreadsheet, same deadline, same classification) and delivers it to the CFO reconciled. Comparison between projects shows category deviations that none of them would see alone, and the CFO sees the company's cash flow instead of several loose flows.
The CLT makes it the company's duty to comply with and enforce the occupational safety and medicine standards and to instruct employees through service orders (art. 157). Law 8.213/1991 (the Social Security benefits law) makes the company responsible for protective measures and classifies noncompliance with safety standards as a criminal misdemeanor (art. 19, §§ 1 and 2). NR-18 (Norma Regulamentadora 18, the construction industry safety standard) provides for the risk management program prepared by a qualified professional, with implementation under the organization's responsibility.
Preparation belongs to the specialist and implementation belongs to the organization. Demonstrating that service orders were issued and training was delivered is a matter of archive, and the site administrator keeps the archive of all projects in the same standard. The Civil Code adds the long deadline: the contractor is liable for five years for the soundness and safety of the work (art. 618), and the employer answers for the acts of its employees and agents (art. 932, III). Years after delivery, who did what is a matter of archive.
Law 14.133/2021 (the public procurement law) requires the contract inspector to record all occurrences of the execution in a dedicated register and to inform superiors, in due time, of any situation that exceeds the inspector's competence (art. 117, §§ 1 and 2). A contractor that has on its side an equally organized record of occurrences responds to inspection without improvisation. The site administrator maintains that record, in the same standard across all contracts, public or private.
The example is hypothetical. The assumptions are the author's, chosen to make the arithmetic easy, and do not describe a real project. The mechanism is what matters: an expired document stops the project, and the cost runs every day.
| Item (assumption of the example) | Value |
|---|---|
| Daily cost of keeping the project standing (crew, site, equipment) | R$ 15 thousand |
| Stoppage due to expired license | 3 days |
| Cost of the event | R$ 45 thousand |
| Monthly cost of the site administrator | R$ 16 thousand |
| Interval between events at which the role pays for itself: R$ 45 thousand ÷ R$ 16 thousand | 2.8 months |
By this arithmetic, avoiding a single such event every quarter already covers the cost of the role. Left out are the fines for lack of an ART, the exposure to the joint liability rules and the time the resident engineer no longer spends on paperwork. The calculation is conservative for that reason.
Not in the standards consulted for this article. The law defines obligations, such as the registration of employees, the recording of attendance and the ART. The role is how C&S Engenharia organizes whoever supports those obligations across all projects.
Not necessarily. The role relies on precise information sent by the projects, in the same format and deadline, against which it checks conformity. The fixed hours at one project serve as a reference for reading what arrives from the others.
No. The relationship is one of support, in a dotted line. The resident engineer keeps the technical direction of the project, and the administrator delivers the data and the conformity alert.
The CLT allows the subcontractor's employee to bring a claim against the main contractor (art. 455), and Law 8.212 provides for the contracting party's joint liability for social security obligations (art. 30, VI). Both preserve the right of recourse and the retention of amounts owed to the performer.
Write the scope and the standard for submitting information from the projects. Without them, the role becomes the clerical office of a single site. In real estate development, IncorpBuilding describes the same role within the project lifecycle.
By Raphael Schifino, CVO
← Back to Articles