Every weld, tied to the drawing it came from.
WeldHawk is for fabrication shops working to ISO 3834 and EN 1090. Pin welds on the PDF drawing. Link each one to its procedure, its welder, its parent material heats, the consumable batch and the equipment set. When the drawing goes to the next revision, the map goes with it.
Sign-in is by a link sent to your work email. There is no password to forget or to share around the shop.
- Procedure
- WPS-014 / WPQR-221
- Welder
- J. Reid — stamp 12
- Parent 1
- Heat 5548211 — S355J2
- Parent 2
- Heat 5548219 — S355J2
- Consumable
- Batch K7734 — G3Si1
- Equipment
- Set 04 — cal. due 14/11
Illustrative. Every field is a link to the record it names, and the record carries its own certificate.
The record book, built as the work is done
Not a folder of scans assembled at handover. The traceability is entered against the weld at the time, and the documents come out of it.
Weld map on the drawing
Click the PDF to drop an auto-numbered pin, drag it to reposition. Pins are held as a proportion of the page, so they stay on the joint through zoom and rotation.
Traceability against the pin
Weld type, size, process and status, the WPS and its supporting WPQR, the welder, the parent heats — parent 1, parent 2 and backing — the consumable batches and the equipment.
Revisions that carry forward
A new revision copies the weld map onto the new sheet and records where each weld came from. The superseded revision is left exactly as it was.
Standards and specifications
The documents a job is built to, held per workspace with the edition and revision pinned, so a project keeps citing what it was contracted to.
Inspection and test plans
The signing-party grid, with activity codes, hold points, sign-off and issue to the client as a PDF by email.
Snags and NCRs
Raised against the project with a priority, photographs, and an owner who can be one of your own staff or someone outside the business. Tracked from open to closed.
The project register
Every weld on the job in one table, on your letterhead, laid out to print as an A4 landscape record with a client approval block.
Certificates, gathered automatically
The project document page collects every certificate the project actually depends on — procedures, welder approvals, mill certificates, consumable certificates, calibration — from the records themselves.
Dates that catch up with you
Welder approvals, qualifications, consumable and material certificates and equipment calibration all carry dates. Anything expired or due inside thirty days is counted on the dashboard.
Rev B does not mean starting the map again
Creating a revision copies the welds onto the new sheet: the weld numbers, type and size, the WPS, the welder, the welded-on date, the status, the notes and the pin position. Each carried weld records the weld it came from and is flagged for review, so the pins get checked against the new sheet rather than assumed.
What carries, and what does not
Material heats, consumable batches and equipment are not carried across — they belong to the weld that was actually made, and a new sheet is a new piece of work. They are entered against the new revision. Better to say so here than to have you find it on a Friday afternoon.
The old revision stays readable
Superseding does not overwrite. The previous revision keeps its own weld map and its own records, because that is what was built at the time and that is what the record book has to show.
Nothing is deleted
Welds and library records are archived rather than removed, and the audit trail keeps who changed what and when. An auditor asking how a number changed gets an answer.
The model transcribes. WeldHawk does the arithmetic.
AI is used where it is genuinely good — reading a scan and typing it out — and kept away from anything that amounts to a judgement about the work.
Title blocks
Upload a drawing and it reads the drawing number, the title and the revision into the form, each box marked as read from the drawing. What you type always wins. On a revision the number is never taken from the model.
Weld symbols
It proposes pins from the symbols on the sheet, with a type, a size and a position. You see the list and accept it before anything is written. A detection the model cannot point to on the drawing is discarded rather than shown.
Spreadsheet columns
On an import it proposes which of your columns is which. It sees the headers and a few sample rows, never the whole file, and you confirm the mapping before a row is written.
Carbon equivalent, calculated rather than believed
A mill certificate is transcribed by the model — heat number, grade, specification, EN 10204 certificate type, the analysis element by element and the mechanicals. It is told to transcribe and not to evaluate. WeldHawk then works out the numbers itself, in code.
Three formulas, from the declared analysis
- CEV (IIW) C + Mn/6 + (Cr+Mo+V)/5 + (Ni+Cu)/15
- CET C + (Mn+Mo)/10 + (Cr+Cu)/20 + Ni/40
- Pcm C + Si/30 + (Mn+Cu+Cr)/20 + Ni/60 + Mo/15 + V/10 + 5B
Where an element is not declared on the certificate, it says so rather than quietly reporting the result as if it were zero. For austenitic stainless it withholds all three and explains why, instead of printing a number that means nothing. The CEV printed on the certificate is compared with the calculated one, and a disagreement is raised.
- Carbon equivalent is 0.482, above the 0.47 maximum for S355J2.
- Nb is not declared on the certificate, so it could not be checked.
Illustrative. WeldHawk flags; it does not approve material. The verdict reads Issues found or No limits exceeded, and where no limits are held for the grade it says plainly that the certificate has not been checked. The decision stays with your responsible welding coordinator.
Limits are currently held for S275JR, S355J2, S355K2, P265GH, 304L and 316L, with their material numbers as aliases. Chemistry, mechanicals and the CEV ceiling are checked; where the certificate cites a different product standard, the mechanicals are skipped and the fact is recorded.
Operations down, signing parties across
The grid your client expects to receive, built in the app rather than in a spreadsheet that gets emailed around and forked.
| Operation | Fabricator | Client | Third party |
|---|---|---|---|
| Material verification | A1 | R1 (CQM) | N/A |
| Fit-up before welding | A1 | H (PE) | W2 |
| Welding to WPS | A1 | S | W2 |
| Final documentation | R1 | AP (CQM) | N/A |
Illustrative. A1 and A2 for full and sample inspection, W1 and W2 for witness, R1 and R2 for review, S for surveillance, H for a hold point and AP for submission for approval, each with the responsible party in brackets.
Hold points are counted, not just coloured
H and AP are marked as blocking, and the header tells you how many hold points nobody has signed and how far through the sign-offs the plan is.
Signing is its own permission
Sign off is separate from edit. Writing a plan and certifying that work was witnessed are different authorities, and a quality system that conflates them is one an auditor will query.
Issued as a PDF, by email
A4 landscape with a repeating header and the code legend. Signed cells print with the name and the date; unsigned cells print ruled for hand-signing. Send it to the client from the app and every recipient is recorded in the audit trail.
Your existing registers, imported
Most shops arrive with spreadsheets. Equipment, consumable batches and material heats can be brought in from Excel or CSV — those three record types, up to 5,000 rows a file.
It finds the header row
Registers rarely start on row 1. WeldHawk looks for the header rather than assuming, so a sheet with a logo and a title block above the table works.
You approve the mapping
The model proposes which column is which and says why. You confirm it before anything is written.
A bad cell does not fail the file
Dates are read UK-order. A cell that cannot be understood is reported against its row, and the rest of the import proceeds.
Four steps, in the order a job actually runs
- 1
Build the library
Welders and their approval ranges, WPS and supporting WPQR, material heats, consumable batches, equipment and calibration dates. Import the registers you already keep.
- 2
Open the project
Client, execution class and status, the standards and client specifications it is built to, and the drawings as PDFs.
- 3
Map the welds
Click the drawing to drop a pin. Link the procedure, the welder, the heats, the consumable batch and the equipment. Read the symbols with AI first if it saves time.
- 4
Issue the records
The weld register on your letterhead, the ITP signed and sent to the client, and the certificates the job depends on gathered on one page.
Who can do what, decided by you
Permissions are not a fixed set of job titles. Every module carries its own actions — view, add, edit, archive, and sign off where the module allows it — and you tick them per role.
Roles you define
Five starting points ship with the product — Administrator, Welding engineer, Material controller, Inspector and Read only — to use as they are or copy and adjust. Read only is the one to give an auditor.
New features arrive switched off
A role created before a feature existed does not silently gain it when the product grows. Administrators are the deliberate exception.
Your workspace is your own
Each workspace is a separate tenant, isolated in Postgres by row-level security that is forced rather than merely enabled — it applies to the database owner too — and any tenant-scoped query that arrives without a workspace is refused outright rather than run.
A seat is a login, not a person on the shop floor
Forty welders need a record — stamp, approval range, expiry — and not one of them needs an account. In WeldHawk a person and a login are two different things, and only the login costs anything.
How the seat count works
Billing is per seat, and the seat count is simply the number of people in the workspace who can sign in. Welders, inspectors and staff who exist as records — because their qualifications and stamps have to be on file — cost nothing. Forty welders on the system and four people who actually sign in is four seats.
The quantity follows your headcount rather than being edited separately: add a colleague and the subscription follows. It cannot drift out of step with reality, which is the usual way a per-seat bill goes wrong. Card details, invoices and cancellation are handled through Stripe, and the invoice list in the app is read live from there rather than mirrored.
Two plans
- Core
- For a single fabrication shop. The weld map, the register, snags and NCRs, the production programme, and AI reading of drawings and certificates.
- Pro
- For multi-site. Everything in Core, a higher ceiling on people and projects, and your own logo and colour on the documents you issue.
Workspaces are set up for you rather than self-service, so the plan and the first administrator are in place before anyone signs in.
Already have a workspace?
Sign in with your work email. We send a link; there is no password.