Written to be precise rather than promotional. Most of what exists online about hiring engineers is marketing copy; these are the documents we wanted to hand people and could not find.
Most engineering engagements are decided before anyone starts work, in how precisely the problem was written down. These are the guides on doing that part properly.
The four fields that determine whether you get comparable proposals — governing standard and edition, jurisdiction, the input data that actually exists today, and whether professional sign-off is required — and why everything else is detail by comparison.
The design basis is the document every later argument refers back to. This is a section-by-section breakdown of what belongs in one, with the failure modes that follow from each omission.
An acceptance criterion is only useful if someone who did not do the work can check it. Worked examples of vague criteria rewritten as checkable ones, across calculations, drawings, models and reports.
Coordinated projects fail at the boundaries between disciplines, not inside them. How to make each interface somebody's explicit responsibility rather than an assumption nobody stated.
Pricing model, milestone structure and revision allowance do more to determine how an engagement feels than the hourly rate does.
Fixed price transfers scope risk to the engineer, who prices it — often invisibly. Milestones distribute it. Hourly leaves it with you. A decision framework based on how much of the scope depends on information nobody has yet.
Engineering deliverables sit awkwardly across IP categories: the drawing is a work, the design may be patentable, and the engineer's calculation templates are theirs. What to agree, and what the standard positions actually mean in practice.
The distinction between a revision and a change request is the most commercially significant line in any technical contract. How to draw it clearly at award so neither side is arguing about it at delivery.
Professional indemnity cover, what it does and does not respond to, why liability caps exist, and how to check that a stated cover level is actually current and relevant to your scope.
The hardest problem in buying engineering work: judging a deliverable whose correctness you cannot directly see.
You cannot verify the solve. You can verify almost everything around it, and that is where most real errors live. A structured interrogation of an analysis report that does not require you to rebuild the model.
A drawing set can be checked for completeness, internal consistency and buildability without discipline expertise. What to check, in what order, and when to stop and buy an independent review.
Independent review is the cheapest risk reduction available on significant engineering work, and it is routinely skipped. How to scope one so the reviewer can be useful.
Which code applies, which edition, whose national annex, and who is permitted to certify the result — the questions that decide eligibility before competence is even relevant.
Why 'designed to Eurocode' is an incomplete statement, how national annexes change outcomes, and why the jurisdiction of the asset governs rather than the location of the engineer.
Design assistance, drafting, analysis, independent review and professional sign-off are five separate scopes. Conflating them is the most consequential mistake available on this kind of platform.
Engaging an engineer in another country is normal and often the right call. The failure mode is discovering at approval stage that nothing produced can be submitted. How to avoid that.
Guides for the supply side: proposals, evidence, pricing and protecting yourself with the record.
When proposals are normalised, the differentiator becomes the quality of your stated approach and the credibility of your assumptions. What strong proposals do that weak ones do not.
Clients use profiles to eliminate candidates, not to admire them. Structuring yours around checkable, specific claims — including the boundaries of your competence.
Every fixed price on incomplete information contains a risk premium. Making that premium explicit, or structuring the engagement so it is not needed.
The guides above are opinionated and general. These are the structured references for specifics.
Browse engineers, services and case studies by the design standard the work must satisfy.
Browse by tool, with verified competence where a vendor partnership supplies the check.
Real engagements structured as problem, method, evidence and outcome rather than testimonial.
Technical questions answered by practising engineers, with standards cited where relevant.
The structured intake asks the questions these guides say to answer, so a good brief largely writes itself once you have read the first one.
