Tell us what the project or asset needs.
Provide the core technical context and FORMĚS can route the enquiry toward the relevant engineering, inspection, asset, project, digital or manpower capability.
- Capability
- —
- Category
- —
- Need
- —
- Stage
- —
- Sector
- —
- Engagement
- —
A useful first brief does not need to be long—but it should answer the right questions.
Tell us what decision or outcome is needed, what evidence already exists and what constraints matter. FORMĚS can then determine whether the next step is engineering review, investigation, inspection, project support, digital coordination, asset assessment or technical resourcing.
- 01The technical problem, decision or acceptance question that must be resolved
- 02What scope or output you expect: assessment, review, inspection, report, design input, personnel or other support
- 03Available drawings, specifications, reports, test data, models or field evidence
- 04Applicable standards, acceptance criteria, client requirements or contractual basis where known
- 05Sector, project / asset stage and the parties or interfaces involved
- 06Location, access, shutdown, operating, HSE or confidentiality constraints
- 07Required timing, mobilization date, submission deadline or decision milestone
- 08Tender / RFQ / procurement reference where applicable
Share only what is appropriate at first contact.
Initial enquiries should contain the information necessary to understand the requirement. Sensitive project documents or restricted information can be exchanged later through an appropriate controlled channel when required.
- 01Do not include confidential project documents in the initial form
- 02Controlled follow-up for sensitive information
- 03Scope-specific routing
- 04Project information handled for the intended business purpose
Give us enough context to route the requirement correctly.
The first submission is intentionally concise. Sensitive drawings, reports, tender documents or restricted information can be exchanged later through a controlled channel.