FORMĚS / TECHNICAL SYSTEM
FORMĚS
Skip to content
EXPTechnical experience

Representative scopes. Confidential relationships protected.

Certain client relationships and project details are subject to confidentiality obligations. Public experience therefore explains technical questions, scope logic, evidence requirements and outputs without identifying confidential parties or facilities.

Evidence model

Enough detail to understand capability. Not enough to compromise confidentiality.

Public scope records are structured around the technical problem and the information needed to solve it. Client names, project names, contract values, exact facilities, identifying dates, quantities and restricted imagery remain excluded unless separately approved for disclosure.

01

Asset / environment

The broad asset class or operating environment, without identifying the facility.

02

Technical question

The condition, project requirement, assurance question or delivery problem that drives the work.

03

Evidence / inputs

The drawings, records, field evidence, tests, interfaces or competency information needed to answer the question.

04

Scope & method

The FORMĚS technical activity appropriate to the question, described at a defensible level.

05

Technical outputs

The review, inspection, assessment, register, recommendation, data package or project-control output expected.

06

Disclosure control

Confidential parties, locations, commercial data and identifying metadata remain withheld unless separately approved.

Complete scope coverage

39 services. 39 technical scenario patterns.

Use the library to understand how each FORMĚS subservice is normally framed: the situation that creates the need, the questions to resolve, useful client inputs, expected outputs and any delivery qualification that matters. These are representative scope patterns, not fabricated project claims.

SCOPE FINDER / 39Find the technical scenario that matches the need.
Search, filter, then open a scope.
Selected scopeDesign Review01 / 39 · Browse
SERVICE INDEXBrowse the complete FORMĚS scope.
Wheel, select or use the index controls.
SCOPE PATTERN / 01Studies, Permitting & Design

Design Review

Structured technical review of design bases, calculations, drawings, specifications and interfaces to identify gaps before they become delivery problems.

Typical scenario

Used when a design needs independent challenge, multidisciplinary coordination, compliance review, constructability input or verification before approval or construction.

Questions to resolve
  • What decision must the review, verification or study support?
  • Which assumptions, disciplines, interfaces or compliance requirements are most critical?
  • What information is available, what is uncertain and what must be resolved before approval or implementation?
Useful evidence / client inputs
  • Design basis, drawings, calculations, specifications and applicable technical criteria
  • Available surveys, studies, models, prior reviews and relevant project correspondence
  • Applicable standards, authority / client requirements, decision deadline and required approval route
Typical technical outputs
  • Review comments / action register
  • Verification memorandum or report
  • Technical recommendations
DECISION LENS

Establish whether the available technical basis is complete, coordinated and reliable enough for the decision that depends on it.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 02Studies, Permitting & Design

Technical Due Diligence & Audit

Evidence-led review of available technical information, asset condition, design assumptions and project controls to expose material technical risks and information gaps.

Typical scenario

Relevant before acquisition, investment, major modification, recovery planning or any decision that depends on the reliability of existing technical information.

Questions to resolve
  • What decision must the review, verification or study support?
  • Which assumptions, disciplines, interfaces or compliance requirements are most critical?
  • What information is available, what is uncertain and what must be resolved before approval or implementation?
Useful evidence / client inputs
  • Design basis, drawings, calculations, specifications and applicable technical criteria
  • Available surveys, studies, models, prior reviews and relevant project correspondence
  • Applicable standards, authority / client requirements, decision deadline and required approval route
Typical technical outputs
  • Due-diligence findings
  • Technical risk / gap register
  • Prioritized follow-up actions
DECISION LENS

Establish whether the available technical basis is complete, coordinated and reliable enough for the decision that depends on it.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 03Studies, Permitting & Design

Technical Assistance

Targeted multidisciplinary engineering support for technical queries, design interfaces, field issues, change decisions and specialist problem solving.

Typical scenario

Used where a project or operating team needs additional engineering judgement without appointing a separate full-scope design consultant.

Questions to resolve
  • What decision must the review, verification or study support?
  • Which assumptions, disciplines, interfaces or compliance requirements are most critical?
  • What information is available, what is uncertain and what must be resolved before approval or implementation?
Useful evidence / client inputs
  • Design basis, drawings, calculations, specifications and applicable technical criteria
  • Available surveys, studies, models, prior reviews and relevant project correspondence
  • Applicable standards, authority / client requirements, decision deadline and required approval route
Typical technical outputs
  • Technical responses / memoranda
  • Engineering recommendations
  • Interface and action closure support
DECISION LENS

Establish whether the available technical basis is complete, coordinated and reliable enough for the decision that depends on it.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 04Studies, Permitting & Design

Geotechnical Studies & Survey

Site and ground-condition investigation support used to establish the geotechnical basis, constraints and uncertainties that affect design and construction decisions.

Typical scenario

Relevant for new development, foundation concerns, earthworks, slope or settlement issues and projects where available ground information is incomplete.

Questions to resolve
  • What decision must the review, verification or study support?
  • Which assumptions, disciplines, interfaces or compliance requirements are most critical?
  • What information is available, what is uncertain and what must be resolved before approval or implementation?
Useful evidence / client inputs
  • Design basis, drawings, calculations, specifications and applicable technical criteria
  • Available surveys, studies, models, prior reviews and relevant project correspondence
  • Applicable standards, authority / client requirements, decision deadline and required approval route
Typical technical outputs
  • Ground / site information basis
  • Geotechnical findings
  • Design and investigation recommendations
DECISION LENS

Establish whether the available technical basis is complete, coordinated and reliable enough for the decision that depends on it.

DELIVERY NOTE

Specialist investigation, survey and laboratory activities may be delivered with qualified partners where project-specific equipment or accreditation is required.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 05Studies, Permitting & Design

Construction Material Analysis & Feasibility

Engineering evaluation of proposed or existing construction materials to understand suitability, performance, constraints and implications for the intended application.

Typical scenario

Used when material selection, deterioration, substitution, compatibility or performance needs to be technically justified before procurement or remedial action.

Questions to resolve
  • What decision must the review, verification or study support?
  • Which assumptions, disciplines, interfaces or compliance requirements are most critical?
  • What information is available, what is uncertain and what must be resolved before approval or implementation?
Useful evidence / client inputs
  • Design basis, drawings, calculations, specifications and applicable technical criteria
  • Available surveys, studies, models, prior reviews and relevant project correspondence
  • Applicable standards, authority / client requirements, decision deadline and required approval route
Typical technical outputs
  • Material suitability assessment
  • Testing / evidence interpretation
  • Technical recommendations
DECISION LENS

Establish whether the available technical basis is complete, coordinated and reliable enough for the decision that depends on it.

DELIVERY NOTE

Laboratory testing may be coordinated through qualified laboratories where accredited testing is required.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 06Studies, Permitting & Design

Supplier Feasibility Assessment

Technical assessment of a supplier, fabricator or specialist vendor against the required capability, quality controls, documentation and delivery expectations.

Typical scenario

Relevant during sourcing, vendor qualification, critical procurement or when supplier capability creates a material project risk.

Questions to resolve
  • What decision must the review, verification or study support?
  • Which assumptions, disciplines, interfaces or compliance requirements are most critical?
  • What information is available, what is uncertain and what must be resolved before approval or implementation?
Useful evidence / client inputs
  • Design basis, drawings, calculations, specifications and applicable technical criteria
  • Available surveys, studies, models, prior reviews and relevant project correspondence
  • Applicable standards, authority / client requirements, decision deadline and required approval route
Typical technical outputs
  • Supplier technical assessment
  • Capability / gap findings
  • Qualification recommendations
DECISION LENS

Establish whether the available technical basis is complete, coordinated and reliable enough for the decision that depends on it.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 07Studies, Permitting & Design

BIM Management

Governance of model standards, coordination, information requirements, issue management and model exchanges so BIM remains usable as an engineering and delivery tool.

Typical scenario

Used on multidisciplinary projects where model quality, coordination, naming, information exchanges or handover requirements need active control.

Questions to resolve
  • What information must become easier to capture, verify, reconcile or retrieve?
  • Who needs to use the information, where is it created and at what project or asset stage?
  • What controlled digital output must exist at handover or for the next engineering decision?
Useful evidence / client inputs
  • Existing drawings, models, registers, inspection forms, photographs and source data
  • Required users, field workflow, information exchanges, approvals and handover requirements
  • Platform constraints, naming / data standards, security expectations and verification rules
Typical technical outputs
  • BIM execution / coordination controls
  • Model review and issue records
  • Controlled information exchanges
DECISION LENS

Design the information flow around the engineering decision, not around technology for its own sake.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 08Facility Management

HVAC Compliance

Technical review of HVAC systems and records against the applicable design intent, operational requirements, maintenance expectations and relevant compliance criteria.

Typical scenario

Relevant where comfort, ventilation, system performance, maintenance condition or compliance of installed HVAC systems is in question.

Questions to resolve
  • What condition, deterioration, failure or performance question must be resolved?
  • What evidence already exists and what investigation can realistically be performed?
  • What decision follows the assessment: continue, repair, monitor, strengthen or investigate further?
Useful evidence / client inputs
  • Asset history, drawings, prior assessments, maintenance information and modification records
  • Observed condition, defects, performance concerns, photographs and available test / monitoring data
  • Access constraints, operating conditions, required confidence level and decision / intervention timing
Typical technical outputs
  • HVAC compliance findings
  • Condition / performance observations
  • Corrective-action recommendations
DECISION LENS

Convert condition evidence into an engineering basis for continued use, intervention, monitoring or further investigation.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 09Facility Management

Facility Management Auditing

Independent review of facilities-management processes, records, maintenance controls, responsibilities, performance measures and technical governance.

Typical scenario

Used by owners or operators who need visibility of whether FM activities are controlled, traceable and aligned with asset requirements.

Questions to resolve
  • What condition, deterioration, failure or performance question must be resolved?
  • What evidence already exists and what investigation can realistically be performed?
  • What decision follows the assessment: continue, repair, monitor, strengthen or investigate further?
Useful evidence / client inputs
  • Asset history, drawings, prior assessments, maintenance information and modification records
  • Observed condition, defects, performance concerns, photographs and available test / monitoring data
  • Access constraints, operating conditions, required confidence level and decision / intervention timing
Typical technical outputs
  • FM audit findings
  • Control / documentation gaps
  • Improvement action plan
DECISION LENS

Convert condition evidence into an engineering basis for continued use, intervention, monitoring or further investigation.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 10Facility Management

Facility Management Monitoring

Ongoing specialist oversight of facilities-management performance, maintenance activity, recurring issues and closure of agreed technical actions.

Typical scenario

Relevant where an owner needs continuing technical visibility rather than a one-off FM audit.

Questions to resolve
  • What condition, deterioration, failure or performance question must be resolved?
  • What evidence already exists and what investigation can realistically be performed?
  • What decision follows the assessment: continue, repair, monitor, strengthen or investigate further?
Useful evidence / client inputs
  • Asset history, drawings, prior assessments, maintenance information and modification records
  • Observed condition, defects, performance concerns, photographs and available test / monitoring data
  • Access constraints, operating conditions, required confidence level and decision / intervention timing
Typical technical outputs
  • Periodic performance review
  • Open-action / issue tracking
  • Technical improvement recommendations
DECISION LENS

Convert condition evidence into an engineering basis for continued use, intervention, monitoring or further investigation.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 11Facility Management

Property Condition Assessment

Systematic assessment of building fabric, structural, MEP and maintainability condition to establish current deficiencies and likely intervention priorities.

Typical scenario

Commonly used for acquisition, portfolio planning, handover, major refurbishment or when maintenance history does not provide a reliable condition picture.

Questions to resolve
  • What condition, deterioration, failure or performance question must be resolved?
  • What evidence already exists and what investigation can realistically be performed?
  • What decision follows the assessment: continue, repair, monitor, strengthen or investigate further?
Useful evidence / client inputs
  • Asset history, drawings, prior assessments, maintenance information and modification records
  • Observed condition, defects, performance concerns, photographs and available test / monitoring data
  • Access constraints, operating conditions, required confidence level and decision / intervention timing
Typical technical outputs
  • Condition assessment report
  • Defect / evidence register
  • Prioritized maintenance or capital actions
DECISION LENS

Convert condition evidence into an engineering basis for continued use, intervention, monitoring or further investigation.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 12Construction

Construction Supervision

Site-based technical oversight of construction activities to verify alignment with approved information, specifications, agreed methods and project-quality requirements.

Typical scenario

Used where the client or project team needs stronger visibility of workmanship, interfaces, technical queries and construction progress.

Questions to resolve
  • Where is delivery losing clarity, control or technical ownership?
  • Which interfaces, workfronts, decisions or actions require active coordination?
  • What must be closed, demonstrated or handed over, and by when?
Useful evidence / client inputs
  • Current scope, programme, workfront status, organization chart and responsibility matrix
  • Open RFIs, technical queries, interface issues, action registers and relevant site constraints
  • Project controls, reporting expectations, milestone dates and required decision cadence
Typical technical outputs
  • Supervision records
  • Technical observations / actions
  • Progress and interface reporting
DECISION LENS

Keep technical intent, interfaces, actions and evidence connected while the project continues to change.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 13Construction

Project Management

Structured management of project scope, interfaces, programme, technical actions, reporting and stakeholder coordination to support controlled delivery.

Typical scenario

Relevant where multidisciplinary work requires an integrated management layer rather than isolated technical inputs.

Questions to resolve
  • Where is delivery losing clarity, control or technical ownership?
  • Which interfaces, workfronts, decisions or actions require active coordination?
  • What must be closed, demonstrated or handed over, and by when?
Useful evidence / client inputs
  • Current scope, programme, workfront status, organization chart and responsibility matrix
  • Open RFIs, technical queries, interface issues, action registers and relevant site constraints
  • Project controls, reporting expectations, milestone dates and required decision cadence
Typical technical outputs
  • Project controls / reporting
  • Risk and action registers
  • Interface and decision coordination
DECISION LENS

Keep technical intent, interfaces, actions and evidence connected while the project continues to change.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 14Construction

Quality Assurance & Quality Control (QA/QC)

Planning and verification of project-quality controls so acceptance criteria, inspections, records, nonconformities and closure remain traceable.

Typical scenario

Used during procurement, fabrication and construction where the project needs a disciplined quality system and objective evidence of conformance.

Questions to resolve
  • What exactly constitutes acceptance for the item, work or process being inspected?
  • Where must objective evidence be created, reviewed, witnessed or held before release?
  • How will deviations, nonconformities, release status and closure remain traceable?
Useful evidence / client inputs
  • Drawings, specifications, ITP / quality requirements, procedures and acceptance criteria
  • Supplier, fabrication or site records together with required witness / hold points
  • Release dates, NCR history, testing requirements, reporting format and qualification requirements
Typical technical outputs
  • Quality plans / ITP support
  • QA/QC records and findings
  • NCR / closure tracking
DECISION LENS

Create a defensible acceptance record that distinguishes observation, nonconformity, release and verified closure.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 15Construction

Material Testing & Consultancy

Selection, coordination and engineering interpretation of material tests to answer a defined question about quality, condition, compliance or performance.

Typical scenario

Relevant when field observations or project requirements cannot be resolved reliably through visual inspection or documentation alone.

Questions to resolve
  • What exactly constitutes acceptance for the item, work or process being inspected?
  • Where must objective evidence be created, reviewed, witnessed or held before release?
  • How will deviations, nonconformities, release status and closure remain traceable?
Useful evidence / client inputs
  • Drawings, specifications, ITP / quality requirements, procedures and acceptance criteria
  • Supplier, fabrication or site records together with required witness / hold points
  • Release dates, NCR history, testing requirements, reporting format and qualification requirements
Typical technical outputs
  • Testing scope / coordination
  • Results interpretation
  • Engineering conclusions and recommendations
DECISION LENS

Create a defensible acceptance record that distinguishes observation, nonconformity, release and verified closure.

DELIVERY NOTE

Testing requiring accredited laboratories or specialist equipment may be performed through qualified partners.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 16Construction

Site & Shop Inspection — 1st, 2nd & 3rd Party

Inspection of site work, fabrication, equipment or materials against defined drawings, specifications, procedures and acceptance requirements.

Typical scenario

Used at source, fabrication shops or construction sites where independent or project-specific verification is required before release, installation or acceptance.

Questions to resolve
  • What exactly constitutes acceptance for the item, work or process being inspected?
  • Where must objective evidence be created, reviewed, witnessed or held before release?
  • How will deviations, nonconformities, release status and closure remain traceable?
Useful evidence / client inputs
  • Drawings, specifications, ITP / quality requirements, procedures and acceptance criteria
  • Supplier, fabrication or site records together with required witness / hold points
  • Release dates, NCR history, testing requirements, reporting format and qualification requirements
Typical technical outputs
  • Inspection reports
  • Witness / hold-point records
  • Observations, nonconformities and release evidence
DECISION LENS

Create a defensible acceptance record that distinguishes observation, nonconformity, release and verified closure.

DELIVERY NOTE

The level of independence and any project-specific qualification requirements are defined by the appointment and applicable contract.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 17Construction

Supply Chain Audit

Technical and quality-focused review of supplier, manufacturer or fabricator controls, records, processes and traceability across the supply chain.

Typical scenario

Relevant for critical suppliers, recurring quality concerns, vendor surveillance or procurement packages with elevated delivery risk.

Questions to resolve
  • What exactly constitutes acceptance for the item, work or process being inspected?
  • Where must objective evidence be created, reviewed, witnessed or held before release?
  • How will deviations, nonconformities, release status and closure remain traceable?
Useful evidence / client inputs
  • Drawings, specifications, ITP / quality requirements, procedures and acceptance criteria
  • Supplier, fabrication or site records together with required witness / hold points
  • Release dates, NCR history, testing requirements, reporting format and qualification requirements
Typical technical outputs
  • Supplier / process audit findings
  • Traceability and control gaps
  • Corrective-action recommendations
DECISION LENS

Create a defensible acceptance record that distinguishes observation, nonconformity, release and verified closure.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 18Construction

As-Built Documentation & Verification

Reconciliation of actual installed or constructed conditions against drawings, models and project records to establish a more reliable as-built information set.

Typical scenario

Used during closeout, handover, brownfield modification or whenever existing records do not reliably represent field conditions.

Questions to resolve
  • What information must become easier to capture, verify, reconcile or retrieve?
  • Who needs to use the information, where is it created and at what project or asset stage?
  • What controlled digital output must exist at handover or for the next engineering decision?
Useful evidence / client inputs
  • Existing drawings, models, registers, inspection forms, photographs and source data
  • Required users, field workflow, information exchanges, approvals and handover requirements
  • Platform constraints, naming / data standards, security expectations and verification rules
Typical technical outputs
  • Verified as-built records
  • Field-to-document discrepancy register
  • Controlled closeout information
DECISION LENS

Design the information flow around the engineering decision, not around technology for its own sake.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 19Construction

Commissioning Support

Technical support for readiness review, test and inspection records, punch-list closure, interface verification and structured transition into operation.

Typical scenario

Relevant when construction completion must be converted into demonstrable operational readiness and a controlled handover record.

Questions to resolve
  • Where is delivery losing clarity, control or technical ownership?
  • Which interfaces, workfronts, decisions or actions require active coordination?
  • What must be closed, demonstrated or handed over, and by when?
Useful evidence / client inputs
  • Current scope, programme, workfront status, organization chart and responsibility matrix
  • Open RFIs, technical queries, interface issues, action registers and relevant site constraints
  • Project controls, reporting expectations, milestone dates and required decision cadence
Typical technical outputs
  • Readiness / completion reviews
  • Punch and action closure support
  • Commissioning / handover records
DECISION LENS

Keep technical intent, interfaces, actions and evidence connected while the project continues to change.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 20Asset Management

Asset Performance Assessment

Evaluation of whether an asset is delivering its required function using condition evidence, operating information, maintenance history and performance indicators.

Typical scenario

Used where condition alone does not explain recurring underperformance, reliability issues or declining service levels.

Questions to resolve
  • What condition, deterioration, failure or performance question must be resolved?
  • What evidence already exists and what investigation can realistically be performed?
  • What decision follows the assessment: continue, repair, monitor, strengthen or investigate further?
Useful evidence / client inputs
  • Asset history, drawings, prior assessments, maintenance information and modification records
  • Observed condition, defects, performance concerns, photographs and available test / monitoring data
  • Access constraints, operating conditions, required confidence level and decision / intervention timing
Typical technical outputs
  • Performance assessment
  • Constraint / degradation findings
  • Improvement priorities
DECISION LENS

Convert condition evidence into an engineering basis for continued use, intervention, monitoring or further investigation.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 21Asset Management

Lifecycle Asset Analysis

Assessment of deterioration, remaining service considerations, intervention timing and long-term technical priorities across an asset lifecycle.

Typical scenario

Relevant for aging assets, capital-planning decisions, rehabilitation programmes and portfolios where interventions must be prioritized over time.

Questions to resolve
  • What condition, deterioration, failure or performance question must be resolved?
  • What evidence already exists and what investigation can realistically be performed?
  • What decision follows the assessment: continue, repair, monitor, strengthen or investigate further?
Useful evidence / client inputs
  • Asset history, drawings, prior assessments, maintenance information and modification records
  • Observed condition, defects, performance concerns, photographs and available test / monitoring data
  • Access constraints, operating conditions, required confidence level and decision / intervention timing
Typical technical outputs
  • Lifecycle assessment
  • Intervention scenarios / priorities
  • Monitoring or renewal recommendations
DECISION LENS

Convert condition evidence into an engineering basis for continued use, intervention, monitoring or further investigation.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 22Asset Management

Compliance Audit

Structured review of technical records, asset conditions or project processes against the applicable contractual, regulatory, standard or procedural requirements.

Typical scenario

Used where management needs a clear evidence-based picture of conformance, gaps and actions rather than an informal review.

Questions to resolve
  • What condition, deterioration, failure or performance question must be resolved?
  • What evidence already exists and what investigation can realistically be performed?
  • What decision follows the assessment: continue, repair, monitor, strengthen or investigate further?
Useful evidence / client inputs
  • Asset history, drawings, prior assessments, maintenance information and modification records
  • Observed condition, defects, performance concerns, photographs and available test / monitoring data
  • Access constraints, operating conditions, required confidence level and decision / intervention timing
Typical technical outputs
  • Compliance matrix / findings
  • Gap and action register
  • Closure recommendations
DECISION LENS

Convert condition evidence into an engineering basis for continued use, intervention, monitoring or further investigation.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 23Asset Management

Seismic Technical Assistance & Audit

Engineering review of seismic design basis, demand, capacity, vulnerabilities and available records to support risk-informed technical decisions.

Typical scenario

Relevant for existing structures, change of use, critical facilities, design review or assets where seismic assumptions need independent verification.

Questions to resolve
  • What condition, deterioration, failure or performance question must be resolved?
  • What evidence already exists and what investigation can realistically be performed?
  • What decision follows the assessment: continue, repair, monitor, strengthen or investigate further?
Useful evidence / client inputs
  • Asset history, drawings, prior assessments, maintenance information and modification records
  • Observed condition, defects, performance concerns, photographs and available test / monitoring data
  • Access constraints, operating conditions, required confidence level and decision / intervention timing
Typical technical outputs
  • Seismic review findings
  • Vulnerability / verification assessment
  • Further analysis or retrofit recommendations
DECISION LENS

Convert condition evidence into an engineering basis for continued use, intervention, monitoring or further investigation.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 24Asset Management

Structural Health Monitoring

Definition and interpretation of monitoring strategies that track structural response, movement or deterioration over time against meaningful technical thresholds.

Typical scenario

Used where one-off inspection cannot provide sufficient confidence and the evolution of structural behaviour needs to be observed.

Questions to resolve
  • What condition, deterioration, failure or performance question must be resolved?
  • What evidence already exists and what investigation can realistically be performed?
  • What decision follows the assessment: continue, repair, monitor, strengthen or investigate further?
Useful evidence / client inputs
  • Asset history, drawings, prior assessments, maintenance information and modification records
  • Observed condition, defects, performance concerns, photographs and available test / monitoring data
  • Access constraints, operating conditions, required confidence level and decision / intervention timing
Typical technical outputs
  • Monitoring strategy / parameters
  • Trend and threshold interpretation
  • Technical alerts / recommendations
DECISION LENS

Convert condition evidence into an engineering basis for continued use, intervention, monitoring or further investigation.

DELIVERY NOTE

Sensors, specialist platforms and monitoring hardware may be integrated with qualified technology partners as appropriate.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 25Asset Management

Structural Integrity Assessment

Engineering assessment of structural condition and capacity using available records, field evidence, testing and analysis appropriate to the question being answered.

Typical scenario

Relevant after deterioration, damage, change of loading, observed distress, aging or where continued safe use needs a defensible technical basis.

Questions to resolve
  • What condition, deterioration, failure or performance question must be resolved?
  • What evidence already exists and what investigation can realistically be performed?
  • What decision follows the assessment: continue, repair, monitor, strengthen or investigate further?
Useful evidence / client inputs
  • Asset history, drawings, prior assessments, maintenance information and modification records
  • Observed condition, defects, performance concerns, photographs and available test / monitoring data
  • Access constraints, operating conditions, required confidence level and decision / intervention timing
Typical technical outputs
  • Integrity assessment report
  • Capacity / condition findings
  • Repair, monitoring or further-investigation recommendations
DECISION LENS

Convert condition evidence into an engineering basis for continued use, intervention, monitoring or further investigation.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 26Asset Management

Asset Condition Assessment

Multidisciplinary condition review that converts observed defects and available records into a structured picture of asset condition and intervention priority.

Typical scenario

Used for maintenance planning, due diligence, rehabilitation programmes and portfolios that need consistent condition intelligence.

Questions to resolve
  • What condition, deterioration, failure or performance question must be resolved?
  • What evidence already exists and what investigation can realistically be performed?
  • What decision follows the assessment: continue, repair, monitor, strengthen or investigate further?
Useful evidence / client inputs
  • Asset history, drawings, prior assessments, maintenance information and modification records
  • Observed condition, defects, performance concerns, photographs and available test / monitoring data
  • Access constraints, operating conditions, required confidence level and decision / intervention timing
Typical technical outputs
  • Condition ratings / findings
  • Defect and evidence register
  • Prioritized technical actions
DECISION LENS

Convert condition evidence into an engineering basis for continued use, intervention, monitoring or further investigation.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 27Asset Management

Failure, Distress & Root-Cause Investigation

Forensic engineering investigation of cracking, deformation, deterioration, malfunction or failure to distinguish symptoms from the underlying cause.

Typical scenario

Relevant when repair decisions would otherwise be based on visible damage alone or when recurring defects indicate a deeper mechanism.

Questions to resolve
  • What condition, deterioration, failure or performance question must be resolved?
  • What evidence already exists and what investigation can realistically be performed?
  • What decision follows the assessment: continue, repair, monitor, strengthen or investigate further?
Useful evidence / client inputs
  • Asset history, drawings, prior assessments, maintenance information and modification records
  • Observed condition, defects, performance concerns, photographs and available test / monitoring data
  • Access constraints, operating conditions, required confidence level and decision / intervention timing
Typical technical outputs
  • Root-cause assessment
  • Evidence / hypothesis evaluation
  • Corrective and follow-up recommendations
DECISION LENS

Convert condition evidence into an engineering basis for continued use, intervention, monitoring or further investigation.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 28Asset Management

Repair, Rehabilitation & Strengthening Recommendations

Development and comparison of technically appropriate intervention options based on the diagnosed condition, cause, required performance and implementation constraints.

Typical scenario

Used after assessment or investigation when the project needs a defensible repair, rehabilitation or strengthening strategy before detailed implementation.

Questions to resolve
  • What condition, deterioration, failure or performance question must be resolved?
  • What evidence already exists and what investigation can realistically be performed?
  • What decision follows the assessment: continue, repair, monitor, strengthen or investigate further?
Useful evidence / client inputs
  • Asset history, drawings, prior assessments, maintenance information and modification records
  • Observed condition, defects, performance concerns, photographs and available test / monitoring data
  • Access constraints, operating conditions, required confidence level and decision / intervention timing
Typical technical outputs
  • Repair / strengthening strategy
  • Option assessment and priorities
  • Implementation recommendations
DECISION LENS

Convert condition evidence into an engineering basis for continued use, intervention, monitoring or further investigation.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 29Project Quality Inspection & Digitalization

Aerial Drone Inspection

Remote visual, photographic or sensor-enabled capture of difficult-access assets to improve coverage, repeatability and evidence available for engineering review.

Typical scenario

Relevant for roofs, façades, towers, infrastructure and large or difficult-access areas where conventional access is inefficient or disruptive.

Questions to resolve
  • What information must become easier to capture, verify, reconcile or retrieve?
  • Who needs to use the information, where is it created and at what project or asset stage?
  • What controlled digital output must exist at handover or for the next engineering decision?
Useful evidence / client inputs
  • Existing drawings, models, registers, inspection forms, photographs and source data
  • Required users, field workflow, information exchanges, approvals and handover requirements
  • Platform constraints, naming / data standards, security expectations and verification rules
Typical technical outputs
  • Aerial inspection imagery / evidence
  • Mapped observations
  • Engineering review inputs
DECISION LENS

Design the information flow around the engineering decision, not around technology for its own sake.

DELIVERY NOTE

Drone operations are subject to applicable permissions, site controls and operator qualification; specialist capture may be partner-supported.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 30Project Quality Inspection & Digitalization

Unmanned Robot Inspection

Use of remote or robotic inspection platforms to collect evidence in constrained, hazardous or difficult-access environments while reducing unnecessary personnel exposure.

Typical scenario

Relevant where conventional access is impractical and the required evidence can be captured through a suitable robotic platform.

Questions to resolve
  • What information must become easier to capture, verify, reconcile or retrieve?
  • Who needs to use the information, where is it created and at what project or asset stage?
  • What controlled digital output must exist at handover or for the next engineering decision?
Useful evidence / client inputs
  • Existing drawings, models, registers, inspection forms, photographs and source data
  • Required users, field workflow, information exchanges, approvals and handover requirements
  • Platform constraints, naming / data standards, security expectations and verification rules
Typical technical outputs
  • Remote inspection evidence
  • Mapped observations / records
  • Engineering assessment inputs
DECISION LENS

Design the information flow around the engineering decision, not around technology for its own sake.

DELIVERY NOTE

Robot platforms and specialist operators may be provided through qualified technology partners according to the inspection environment.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 31Project Quality Inspection & Digitalization

Mixed Reality, AI & VR-Enabled Workflows

Project-specific digital workflows that use visualization, assisted review or immersive interfaces to make complex technical information easier to understand and act on.

Typical scenario

Relevant where field guidance, remote collaboration, model review, training or large information sets benefit from an enhanced digital interface.

Questions to resolve
  • What information must become easier to capture, verify, reconcile or retrieve?
  • Who needs to use the information, where is it created and at what project or asset stage?
  • What controlled digital output must exist at handover or for the next engineering decision?
Useful evidence / client inputs
  • Existing drawings, models, registers, inspection forms, photographs and source data
  • Required users, field workflow, information exchanges, approvals and handover requirements
  • Platform constraints, naming / data standards, security expectations and verification rules
Typical technical outputs
  • Configured digital workflow
  • Visualization / review outputs
  • Structured observations or decision support
DECISION LENS

Design the information flow around the engineering decision, not around technology for its own sake.

DELIVERY NOTE

Technology is selected for the use case; no claim is made that a particular platform or AI method is appropriate for every assignment.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 32Project Quality Inspection & Digitalization

Infrared Imaging

Thermal imaging used as a non-destructive screening method to identify temperature anomalies that can guide focused technical investigation.

Typical scenario

Relevant for building envelope, MEP, electrical, moisture or other condition questions where thermal contrast can reveal otherwise hidden anomalies.

Questions to resolve
  • What information must become easier to capture, verify, reconcile or retrieve?
  • Who needs to use the information, where is it created and at what project or asset stage?
  • What controlled digital output must exist at handover or for the next engineering decision?
Useful evidence / client inputs
  • Existing drawings, models, registers, inspection forms, photographs and source data
  • Required users, field workflow, information exchanges, approvals and handover requirements
  • Platform constraints, naming / data standards, security expectations and verification rules
Typical technical outputs
  • Thermal imagery / anomaly map
  • Inspection observations
  • Recommendations for verification or corrective action
DECISION LENS

Design the information flow around the engineering decision, not around technology for its own sake.

DELIVERY NOTE

Interpretation is tied to the inspection objective and site conditions; specialist equipment or operators may be used where required.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 33Project Quality Inspection & Digitalization

Rugged Field Tablets & Data Synchronization

Configuration of field-data capture so inspections, photographs, observations, checklists and technical records are structured and synchronized instead of remaining fragmented.

Typical scenario

Relevant for distributed field teams, high inspection volumes or projects that need better traceability between site evidence and project information.

Questions to resolve
  • What information must become easier to capture, verify, reconcile or retrieve?
  • Who needs to use the information, where is it created and at what project or asset stage?
  • What controlled digital output must exist at handover or for the next engineering decision?
Useful evidence / client inputs
  • Existing drawings, models, registers, inspection forms, photographs and source data
  • Required users, field workflow, information exchanges, approvals and handover requirements
  • Platform constraints, naming / data standards, security expectations and verification rules
Typical technical outputs
  • Configured field forms / workflows
  • Synchronized inspection records
  • Structured field-data packages
DECISION LENS

Design the information flow around the engineering decision, not around technology for its own sake.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 34Project Quality Inspection & Digitalization

Digital Inspection Workflows

Digitization of inspection planning, checklists, evidence, observations, nonconformities, approvals and closure into a controlled traceable workflow.

Typical scenario

Used where paper, spreadsheets or disconnected records make it difficult to understand inspection status and evidence quality in real time.

Questions to resolve
  • What information must become easier to capture, verify, reconcile or retrieve?
  • Who needs to use the information, where is it created and at what project or asset stage?
  • What controlled digital output must exist at handover or for the next engineering decision?
Useful evidence / client inputs
  • Existing drawings, models, registers, inspection forms, photographs and source data
  • Required users, field workflow, information exchanges, approvals and handover requirements
  • Platform constraints, naming / data standards, security expectations and verification rules
Typical technical outputs
  • Digital inspection workflow
  • Traceable inspection / NCR records
  • Status and closeout reporting
DECISION LENS

Design the information flow around the engineering decision, not around technology for its own sake.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 35Engineering & Technical Manpower Support

Engineering Secondment

Placement of qualified engineering personnel within a client or project organization under defined roles, responsibilities and reporting interfaces.

Typical scenario

Relevant for temporary capacity gaps, specialist needs, peak workload or projects that require embedded engineering support for a defined period.

Questions to resolve
  • Which technical role, discipline or competency is missing?
  • Where will the resource sit in the project organization and who owns technical direction?
  • What outputs, approvals, duration and accountability must remain clear throughout the assignment?
Useful evidence / client inputs
  • Role description, discipline, responsibilities, reporting line and expected deliverables
  • Required competency, certifications / approvals where applicable, location and mobilization date
  • Expected duration, rotation / site conditions, working interfaces and project-specific requirements
Typical technical outputs
  • Role-specific engineering support
  • Assigned technical deliverables
  • Progress / interface reporting
DECISION LENS

Fill a defined technical capacity gap without creating ambiguity in responsibility, competency or output ownership.

DELIVERY NOTE

Mobilization is subject to personnel availability, competency requirements and project-specific qualification criteria.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 36Engineering & Technical Manpower Support

Field Engineering Support

Site-based engineering support that resolves technical queries, design interfaces, constructability issues, field changes and coordination between engineering and execution.

Typical scenario

Relevant during construction, brownfield work, shutdowns or fast-moving site activities where technical decisions cannot wait for disconnected office workflows.

Questions to resolve
  • Which technical role, discipline or competency is missing?
  • Where will the resource sit in the project organization and who owns technical direction?
  • What outputs, approvals, duration and accountability must remain clear throughout the assignment?
Useful evidence / client inputs
  • Role description, discipline, responsibilities, reporting line and expected deliverables
  • Required competency, certifications / approvals where applicable, location and mobilization date
  • Expected duration, rotation / site conditions, working interfaces and project-specific requirements
Typical technical outputs
  • Field engineering responses
  • RFI / technical action support
  • Interface and constructability coordination
DECISION LENS

Fill a defined technical capacity gap without creating ambiguity in responsibility, competency or output ownership.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 37Engineering & Technical Manpower Support

QA/QC & Inspection Personnel

Deployment of qualified quality and inspection personnel to perform defined project QA/QC, surveillance, inspection and documentation responsibilities.

Typical scenario

Relevant for project mobilization, peak inspection demand, shutdowns, supplier surveillance or temporary quality-resource gaps.

Questions to resolve
  • Which technical role, discipline or competency is missing?
  • Where will the resource sit in the project organization and who owns technical direction?
  • What outputs, approvals, duration and accountability must remain clear throughout the assignment?
Useful evidence / client inputs
  • Role description, discipline, responsibilities, reporting line and expected deliverables
  • Required competency, certifications / approvals where applicable, location and mobilization date
  • Expected duration, rotation / site conditions, working interfaces and project-specific requirements
Typical technical outputs
  • Assigned QA/QC / inspection activities
  • Inspection and quality records
  • Progress / issue reporting
DECISION LENS

Fill a defined technical capacity gap without creating ambiguity in responsibility, competency or output ownership.

DELIVERY NOTE

Personnel are nominated subject to role-specific competency, project approval, certification and mobilization requirements where applicable.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 38Engineering & Technical Manpower Support

Discipline Engineering Support

Targeted engineering capacity in the required technical discipline to support design, review, calculations, coordination, field issues or project decisions.

Typical scenario

Used when a project has a defined discipline gap or needs additional engineering capacity without expanding the permanent team.

Questions to resolve
  • Which technical role, discipline or competency is missing?
  • Where will the resource sit in the project organization and who owns technical direction?
  • What outputs, approvals, duration and accountability must remain clear throughout the assignment?
Useful evidence / client inputs
  • Role description, discipline, responsibilities, reporting line and expected deliverables
  • Required competency, certifications / approvals where applicable, location and mobilization date
  • Expected duration, rotation / site conditions, working interfaces and project-specific requirements
Typical technical outputs
  • Discipline-specific technical deliverables
  • Design / review support
  • Technical coordination and responses
DECISION LENS

Fill a defined technical capacity gap without creating ambiguity in responsibility, competency or output ownership.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
SCOPE PATTERN / 39Engineering & Technical Manpower Support

Project Technical Personnel

Project-specific technical resources assigned to defined engineering, coordination, documentation, supervision or support roles within the delivery organization.

Typical scenario

Relevant for mobilization, workload peaks, project recovery or temporary roles that require clear technical accountability and reporting lines.

Questions to resolve
  • Which technical role, discipline or competency is missing?
  • Where will the resource sit in the project organization and who owns technical direction?
  • What outputs, approvals, duration and accountability must remain clear throughout the assignment?
Useful evidence / client inputs
  • Role description, discipline, responsibilities, reporting line and expected deliverables
  • Required competency, certifications / approvals where applicable, location and mobilization date
  • Expected duration, rotation / site conditions, working interfaces and project-specific requirements
Typical technical outputs
  • Role-specific project support
  • Assigned technical records / deliverables
  • Progress and interface reporting
DECISION LENS

Fill a defined technical capacity gap without creating ambiguity in responsibility, competency or output ownership.

DELIVERY NOTE

Availability, competency and project acceptance requirements are confirmed before mobilization.

Use this scope in an enquiryRepresentative scenario pattern — not an identifying project disclosure.
02Controlled credentials

Need a closer match for a tender or prequalification exercise?

The public library explains capability without exposing restricted project information. Where a procurement process requires stronger evidence, FORMĚS can prepare a controlled credentials package aligned to the requested service category, sector and disclosure permissions.

  • 01Relevant experience extracts where disclosure is permitted
  • 02Service and capability statements
  • 03QHSE and governance information
  • 04Organization and delivery information
  • 05Personnel CVs where appropriate
  • 06Tender-specific supporting evidence and clarifications
Request Relevant Credentials
Confidential by design

Technical evidence can be strong without turning client information into marketing material.

Use relevant experience in an enquiry