How DocuAlign Turns Soil Sampling Spreadsheets Into BCA-Compliant Reports
A progressive web app that takes soil sampling values in a controlled format and writes a BCA-compliant report — then a client portal so R.A.K Materials can send a link instead of an inbox full of attachments.
Soil reports live or die on the spreadsheet
R.A.K Materials Consultants produces geotechnical reports that contractors, consultants, and regulators have to be able to read the same way every time. The source material is laboratory and field data: SPT N-values, moisture content, Atterberg limits, particle-size distribution, and the rest of a soil investigation package.
That data arrived in Excel. From there it was pushed into a PDF that had to look like a BCA-compliant report. When the spreadsheet was the layout engine, the report inherited every quirk of the person who last typed into it.
Web Wizards built DocuAlign so the report is generated from a contract, not from a cell range. Staff still work from the numbers they already collect. The app decides how those numbers are stored, validated, and printed.
Why raw Excel values break a BCA report
A soil investigation PDF is not a dump of cells. It is a structured document: headers, borehole logs, summary tables, units, significant figures, and page breaks that have to survive a client review and a submission check.
Raw sampling values do not arrive in that shape. One sheet uses extra decimal places. Another wraps a long borehole ID across two lines. A merged cell shifts a column. Scientific notation appears where a regulator expects a plain number. The PDF generator then does what spreadsheet-fed templates always do: it tries to honour the source, and the layout comes apart.
Those failures are not cosmetic. A misaligned table, a missing unit, or a value that overflows a cell makes the report harder to trust — and slower to issue — even when the laboratory work itself was sound.
Where the old path created risk
Unstable inputSpreadsheets accepted whatever was typed, so the same field could arrive as text, a formula, or a differently rounded number.
Layout inheritanceColumn widths, wrapping, and merged cells travelled into the PDF and broke tables that should have been fixed.
Manual repairStaff spent time fixing the document after generation instead of reviewing the geotechnical content.
Inconsistent reportsTwo jobs with the same test suite could look different depending on who prepared the sheet.
Email deliveryFinished files left as attachments, renamed in transit, and buried in threads the client had to search later.
No single client viewReports, certificates, and supporting files were not sitting together under one labelled job the client could reopen.
A PWA that enforces the contract, then a Node.js engine that prints it
DocuAlign is a progressive web app. Field and laboratory staff can open it on the devices they already use. The interface does not ask them to "design" a report. It asks them to enter, or import, soil sampling values into a schema the organisation controls.
Excel is still welcome as an intake format, because that is how the numbers are captured. What changed is the next step: the sheet is parsed against required fields, units, and value ranges. Anything that would later wreck a table is rejected while the person with the data is still in front of the form.
A Node.js service then writes the PDF from a fixed BCA-facing template. The engine owns typography, column geometry, page breaks, and number formatting. Spreadsheet cosmetics never reach the output. Standardised input in; standardised report out.
How a soil job becomes a report the client can open
- Capture: staff upload the Excel sheet or enter sampling values in the DocuAlign PWA.
- Validate: required fields, units, and numeric formats are checked before anything is generated.
- Normalise: values are stored in one internal shape so the template never has to guess.
- Render: Node.js writes a BCA-compliant PDF from the controlled layout, not from cell formatting.
- Publish: the report is labelled against the job and placed in the client portal.
- Share: R.A.K Materials sends a link. The client opens every document for that job in one place.
Then the documents stop travelling by email
Generating a clean PDF only solves half of the delay. The other half was delivery. Staff attached files, wrote covering notes, and hoped the right person downloaded the right version. Clients replied asking which borehole log belonged to which job, or whether the certificate in last Tuesday's thread was still current.
DocuAlign's client portal removes that round trip. Employees publish the finished pack and send a link. The client opens a portal where reports, certificates, and supporting files are labelled against the job they belong to — not named in whoever last saved the attachment.
The inbox is no longer the document management system. R.A.K Materials keeps a record of what was issued. The client keeps a place they can return to without hunting through forwarded mail.
Better for both sides of the job
For R.A.K MaterialsStaff stop repairing PDF layout after every export, and they stop assembling email packs by hand. Issue the report, send the link, keep an auditable copy.
For their clientsThere is one place to open the current pack. Files are named and grouped, so a consultant does not have to reconstruct the job from a chain of attachments.
For the laboratoryThe PWA makes the expected fields obvious. Invalid values fail early, while the sampling record is still in reach.
For compliance reviewThe PDF is produced from one template, so BCA-facing structure does not drift from job to job.
For version controlReplacing a file in the portal updates what the client sees. It does not create a third PDF with "final_v2" in the filename.
For follow-up workThe next enquiry starts from the labelled pack, not from a search through last month's mail.
Built around the report, not a generic form
DocuAlign is not a file converter with a login screen. The PWA encodes the soil-sampling fields R.A.K Materials actually issues. The Node.js renderer encodes the report those fields must become. The portal encodes how that pack is handed to the people who paid for it.
That is the same approach as CubeSync and WorkGrid: software fitted to a materials-testing operation, rather than a generic workflow the team would have to fight.
What the standardisation actually protects
Field contractsRequired sampling fields are explicit, so a missing borehole reference cannot slip into a generated report.
Numeric rulesUnits and precision are applied in one place, instead of depending on whoever formatted the sheet.
Template lockHeaders, tables, and page geometry belong to the renderer, not to Excel print areas.
Reject-early UXThe PWA tells the operator what failed before a PDF is written, while correction is still cheap.
Job labellingPortal files carry the job identity the client already uses, so packs do not arrive as untitled downloads.
Link-based accessClients receive a location, not a one-off attachment that goes stale the moment a revision is issued.
The result
DocuAlign turns a fragile export path into a controlled pipeline. Soil sampling values still originate in the laboratory's Excel practice, but they no longer dictate how the PDF looks. The Node.js engine prints a BCA-compliant report from a stable template. The portal then gives R.A.K Materials and their clients the same labelled pack, reachable from a link.
The laboratory keeps its data. The report keeps its shape. The client keeps a place to find it.
Still assembling regulated reports from a spreadsheet?
Web Wizards builds the intake, the document engine, and the portal around the reports your clients already expect. Tell us where layout breaks, where email is doing the job of a filing system, and we'll map a cleaner path from source data to signed-off output.