Understand why the Consulting Technical Hour — HTE — should not be treated as a simple man-hour and how it relates to cost engineering, LPU, deliverable-based measurement, and document traceability.
Check it out!
In technical engineering services, it is still common to compare proposals using simplified reasoning: how many hours were estimated and what is the value of each hour. This logic may work for highly defined operational activities, but it is insufficient to evaluate consulting engineering. For a broader view of the topic, also see the Complete Guide to Consulting Engineering.
The reason is straightforward: a consulting deliverable is not formed only by the visible time spent by one professional. It involves analysis, technical responsibility, review, coordination, records, documentation, traceability, risk, business structure, and the ability to turn technical information into safe decisions for the client.
It is in this context that A3A uses the concept of HTE — Consulting Technical Hour.
HTE should not be treated as a simple man-hour. It represents an equivalent technical unit used to organize composite consulting effort and link technical services to deliverables, acceptance criteria, document governance, and cost engineering. This concept is directly connected to the methodology presented in the whitepaper Consulting Engineering Contracting with Traceability, Governance, and Cost Engineering.
The problem with measuring engineering only by hours
An hour is a unit of time. It measures duration, but by itself it does not measure complexity, responsibility, seniority, risk, document quality, or the technical value of a deliverable.
Two proposals may show the same number of hours and still represent completely different levels of depth. One may include only a meeting and verbal guidance. Another may involve document analysis, standards assessment, a risk matrix, technical meeting, preparation of an opinion, review by the responsible engineer, and formal issuance.
If the client compares only the hourly rate without evaluating what is included in each deliverable, the contracting process becomes vulnerable to distortions. The same problem appears in engineering technical proposal analysis, especially when different proposals are treated as equivalent.
In consulting engineering, the technical effort is not only in the apparent execution. It is also in preparation, analysis, interpretation, responsibility, and the ability to record conclusions in a traceable way.
What is a technical hour?
A technical hour is a reference used to estimate, contract, or measure specialized activities. In many contexts, it represents the time a technical professional dedicates to a given demand.
The problem arises when every technical hour is treated as equivalent, regardless of the nature of the activity.
One hour of field survey, one hour of document review, one hour in a supplier meeting, one hour of risk analysis, one hour of review by the responsible engineer, and one hour of issuing a technical opinion do not have the same impact on responsibility, risk, and value for the client.
That is why, in consulting services, A3A distinguishes a conventional technical hour from HTE.
What is HTE — Consulting Technical Hour?
The Consulting Technical Hour — HTE is an equivalent technical unit used to represent composite consulting effort in engineering services.
It does not correspond only to the time of one allocated person. HTE considers the set of activities, responsibilities, and structures required to produce a reliable, documented technical deliverable that is useful for decision-making.
Depending on the scope, HTE may include:
- technical analysis;
- document interpretation;
- alignment meetings;
- definition of assumptions;
- standards research;
- solution development;
- technical review;
- coordination among disciplines;
- evidence records;
- issuance of reports, opinions, matrices, or documentation;
- quality control;
- technical responsibility;
- document traceability;
- business structure;
- technical and contractual risks;
- indirect costs and process governance.
This distinction is important because it brings contracting closer to cost-engineering logic: the assessment is not limited to time, but includes technical composition, responsibility, and the associated deliverable. The same logic applies to engagements that require an detailed design, because the technical value lies in transforming assumptions into documents that can be contracted, implemented, measured, and verified.
Why HTE is not a man-hour
A man-hour represents, in simplified terms, the working time of one professional. HTE represents a broader consulting unit.
The difference can be summarized as follows:
| Criterion | Man-hour | HTE — Consulting Technical Hour |
| Primary unit | Individual time | Equivalent technical effort |
| Focus | Professional allocation | Consulting technical deliverable |
| Measures complexity? | To a limited extent | Yes, when linked to scope |
| Includes review and responsibility? | Not always | It should |
| Includes traceability? | Not necessarily | Yes |
| Linked to deliverables? | May not be | It should be |
| Suitable for technical consulting? | Only in simple cases | Better suited to consulting demands |
HTE does not eliminate the importance of time. It organizes time within a structure of responsibility, deliverables, and governance.
In other words, a man-hour asks, “How long did someone work?” HTE asks, “What technical effort was required to produce a verifiable consulting deliverable?”
What is embedded in a consulting deliverable
An engineering consulting deliverable may look simple when viewed only through the final document. A technical opinion, technical report, or technical note may be only a few pages long while requiring several internal activities.
Before issuance, it may be necessary to review documents, analyze assumptions, identify risks, compare alternatives, verify standards compliance, validate information with suppliers, discuss interfaces, record limitations, and review the conclusion.
The technical value lies in the quality of the analysis and the responsibility assumed, not merely in the number of pages delivered.
Therefore, when engaging consulting engineering, the client should assess:
- which technical problem will be analyzed;
- which documents will be considered;
- what level of depth is expected;
- which deliverables will be issued;
- who will review the deliverable;
- which acceptance criterion will be used;
- which limitations will be recorded;
- how evidence will be organized;
- how the technical decision will be documented.
When these elements are unclear, the contracting process tends to fall back on poor comparisons by hourly rate or lowest price. This is precisely the risk addressed in the content on lowest total price in engineering contracts.
HTE and cost engineering
HTE connects directly to cost engineering because it allows consulting services to be treated as technical compositions rather than simply raw time.
In cost engineering, an adequate estimate must consider scope, assumptions, productivity, risks, uncertainty, direct costs, indirect costs, organizational structure, contingencies, and responsibility. In consulting services, the logic is similar: the technical price should reflect the nature of the deliverable and the risk assumed.
By using HTE, A3A can organize consulting demands with greater predictability, especially when they are associated with an LPU, a Service Order, or an Integrated Engineering Services Cycle. This reasoning also supports Ongoing Consulting Engineering Services, in which the client needs recurring technical support without turning every demand into an informal request.
This structure avoids two common problems:
1. turning all consulting into a simple hour bank; 2. turning each microactivity into an isolated charge with no deliverable-based view.
HTE must be linked to the purpose of the deliverable. Without that connection, it loses its methodological role and becomes merely another name for an hour.
Relationship among HTE, LPU, and Service Orders
HTE becomes more valuable when connected to contractual-governance instruments.
The LPU — Unit Price List organizes service types, reference units, deliverables, and measurement criteria. It allows recurring or special demands to be classified in advance, reducing subjectivity in contracting.
A Service Order turns a request into a formal scope. It records the objective, context, assumptions, deliverables, schedule, acceptance criteria, and measurement method.
HTE helps represent the technical effort associated with the deliverable.
Together, these elements create a clearer structure:
| Element | Function |
| HTE | Represent equivalent consulting technical effort |
| LPU | Organize services, units, and contracting references |
| Service Order | Formalize the demand, scope, deliverable, and acceptance |
| Deliverable-based measurement | Link execution to a verifiable result |
| Measurement report | Record what was requested, delivered, measured, and accepted |
This organization is especially useful in ongoing consulting engineering services, in which the client needs recurring support but not all demands have the same depth, urgency, or responsibility.
When to use HTE, OS-LPU, or OS-CIC
Not every consulting demand should be handled in the same way.
When a demand is specific, bounded, and linked to a particular LPU item, it can be handled as an OS-LPU. Examples include preliminary analysis, document review, a comparative matrix, a specific technical opinion, or targeted technical support.
When a demand involves several interdependent activities, such as technical due diligence, procurement support, Owner’s Engineering, commissioning, or multidisciplinary technical review, it may be more appropriate to use an OS-CIC — Service Order linked to an Integrated Engineering Services Cycle.
OS-CIC avoids excessive fragmentation and reduces the risk of double-counting effort. Instead of measuring every meeting, analysis, or review separately, the cycle organizes the demand by stages, deliverables, and consolidated acceptance criteria.
This distinction is important to protect both the client and the consulting firm. The client gains predictability and traceability. The consulting firm defines responsibility and avoids undefined scope.
Deliverable-based measurement
In consulting engineering, measurement should be associated with verifiable deliverables whenever possible.
This does not mean ignoring effort. It means recognizing that effort should produce a documented technical result.
A deliverable may be:
- technical opinion;
- analysis report;
- risk matrix;
- comparative proposal matrix;
- technical meeting minutes;
- acceptance checklist;
- due diligence report;
- technical memorandum;
- detailed design;
- measurement report;
- commissioning documentation.
Deliverable-based measurement reduces subjectivity, facilitates auditing, improves communication with procurement and legal teams, and creates a technical history for future decisions.
When HTE is linked to deliverables, the engagement stops being merely a purchase of time and becomes a purchase of verifiable technical production. This also improves technical acceptance in engineering projects, because validation no longer depends only on subjective perception and instead considers documented evidence.
Practical example: technical proposal analysis
Imagine a company receives three proposals for implementing a critical system. The prices differ, the scopes are not described in the same way, and each supplier adopts its own assumptions.
A superficial analysis would compare only price, schedule, and equipment brand. A consulting analysis needs to go further.
It may involve:
- reading the proposals;
- identifying exclusions;
- comparing assumptions;
- analyzing scope compliance;
- checking planned documentation;
- assessing testing and commissioning;
- risk analysis;
- comparative matrix;
- alignment meeting;
- technical recommendation.
The result is not merely the time spent. The result is a safer, documented, and defensible contracting decision.
This is the logic of HTE applied to consulting engineering.
How A3A uses HTE in consulting engineering
A3A uses HTE as part of a consulting-engineering methodology oriented around scope, deliverables, traceability, and technical governance.
This methodology connects to services and solutions such as Ongoing Consulting Engineering Services, Detailed Design, Technical Due Diligence, Owner’s Engineering, Procurement, EPCM, and Design Coordination.
The goal is not to create unnecessary complexity. The goal is to reduce subjectivity, organize responsibilities, and enable private companies, industrial organizations, public agencies, and institutions to engage engineering services with greater clarity.
For recurring demands, HTE helps distinguish ordinary support, special demands, and integrated cycles. For specific demands, it helps estimate effort and responsibility more coherently. In both cases, it must be connected to scope and deliverables.
Relationship with ENGiOS
ENGiOS is A3A’s engineering operating system. It materializes the methodology by organizing demands, documents, proposals, technical knowledge, service orders, indicators, commercial workflows, and AI-assisted processes.
The logic of HTE, LPU, OS-LPU, OS-CIC, deliverable-based measurement, and document traceability depends on records. Without a system, the methodology tends to become scattered across emails, spreadsheets, messages, and isolated documents.
That is why ENGiOS has a strategic role: turning technical knowledge and engineering processes into traceable operations. This view is connected to the whitepaper on Consulting Engineering Contracting with Traceability, Governance, and Cost Engineering.
Recommended complementary content
To explore topics related to contracting, documentation, and technical governance in greater depth, see also:
- Complete Guide to Consulting Engineering;
- Basic Design vs Detailed Design: Differences in Consulting Engineering Contracting;
- RACI Matrix in Engineering Projects;
- Technical Due Diligence Report: Evidence, Risk Matrix, and Action Plan;
- FAT, SAT, and Integrated Testing in Critical Systems;
- Lowest Total Price in Engineering Contracts;
- Technical Report, Technical Note, and Technical Opinion.
Conclusion
HTE is not simply another name for a man-hour. It is an equivalent technical unit for organizing consulting effort in engineering.
When used correctly, HTE helps connect scope, responsibility, cost engineering, LPU, Service Orders, deliverable-based measurement, and acceptance criteria.
This structure makes consulting-engineering contracting less subjective and more traceable. For the client, it means greater clarity about what is being requested, delivered, measured, and accepted. For the consulting firm, it means technical boundaries, governance, and documented responsibility.
In critical environments, this distinction matters. Engaging engineering services is not merely buying hours. It is structuring technical decisions with method, documentation, and responsibility.
Talk to our Engineering Department
If your organization needs to structure recurring engineering demands, review proposals, organize scopes, measure deliverables, or engage consulting support with greater traceability, contact A3A’s Engineering Department.
A3A supports private companies, industrial organizations, public agencies, and institutions in engaging consulting engineering with method, technical governance, cost engineering, and documented accountability.
Technical references
[1] A3A Consulting Engineering. Consulting Engineering Contracting with Traceability, Governance, and Cost Engineering. Available at: https://a3aengenharia.com.br/conteudo/whitepapers/contratacao-engenharia-consultiva-governanca-rastreabilidade/.
[2] AACE International. Cost Estimate Classification System in EPC for Process Industries.
[3] SINAENCO. Roteiro de Preços.
[4] DNIT. Manual de Custos SICRO: Conceitos e Metodologias.
Frequently asked questions
No. A man-hour represents the working time of one professional. HTE — Consulting Technical Hour — is an equivalent technical unit that may include analysis, review, responsibility, documentation, traceability, governance, and deliverables.
Because consulting services should not be assessed only by time spent. They involve technical responsibility, analysis, risk, documentation, and decision-making. HTE helps organize this effort in a more traceable way.
HTE can be used as a reference unit within an LPU — Unit Price List — to organize technical services, scopes, deliverables, and measurement criteria.
OS-LPU is suitable for specific and bounded demands. OS-CIC is suitable for integrated engineering cycles when the demand involves multiple interdependent activities and consolidated deliverables.
No. HTE should support estimating and organizing technical effort, but measurement should be linked, whenever possible, to verifiable deliverables and acceptance criteria.
