SurveyPal with doccheckerDocChecker checks the chain. SurveyPal removes its weakest link.
The quote generates the survey. The surveyor completes it at the window. It flows back and checks itself against the quote, your tolerances applied, before the confirmation is checked against it. One thread of data, quote to confirmation.
The strongest chain is only as good as its scrappiest document.
The quote comes out of software. The confirmation comes out of your supplier's software. And between them sits the survey: a printed sheet with handwriting on it, built by hand, filled by hand, then deciphered and rekeyed back into data by the office before anything can check it. Every manual touch is a door for the 1609-that-was-1906 error.
And here's the cruel part: once a misread number is in the data, the chain doesn't catch it, it confirms it. Every downstream check faithfully agrees with the wrong number, because the wrong number is what the data says.
Connected, the loop closes.
The quote generates the survey
The quote sits in DocChecker; a SurveyPal survey is created from it automatically, nothing to build, ready to assign to a surveyor.
The surveyor completes it at the window
On a phone or tablet, item by item, with regs and your own rules checked on the spot. Done when they walk off the drive.
It flows back and checks itself
The completed survey drops into DocChecker and is compared against the quote, with your thresholds applied. In-tolerance changes pass; one outside tolerance is flagged for a human.
The confirmation closes the chain
The supplier's order confirmation is checked against that survey, the same DocChecker process you trust, now anchored to data that was never handwritten.
Same chain. Same checks. But the survey is data from birth, never handwritten, never interpreted, never rekeyed. The whole job, quote to confirmation, is one consistent thread.
It knows the difference between a change and a problem.
Surveys are supposed to change things, that's why you survey. DocChecker works to your tolerances: a measurement that moved within your threshold passes through and is recorded; one that moved outside it gets flagged for a human check. Your rules, your thresholds, automated only where judgement isn't needed.
1204 mm where the quote said 1200 mm. The survey doing its job. Passed and recorded.
1906 mm where the quote said 1609 mm. Not refinement, a question. Flagged for a human.
You already own the other half.
Every product in The Glazing Hub is included in the one subscription. DocChecker isn't a purchase. It's a switch.
Running DocChecker?
Your chain is strong; its weakest link is the paper survey entering it. Switch SurveyPal on and the survey arrives as data.
Running SurveyPal?
Your surveys are clean data going nowhere. Switch DocChecker on and they start checking your quotes and confirmations for you.
Count what the loop removes.
The building of every survey sheet, the deciphering and rekeying of every completed one, the comparing by eye. Then the sharper number: one misread digit that entered the chain and was confirmed by every check downstream. That's what using SurveyPal and DocChecker together fixes.
Data from birth, never handwritten, never interpreted, never rekeyed.
In-tolerance changes pass. Out-of-tolerance changes get flagged.
One thread, quote to confirmation.
Now run it with your real numbers.
The questions about the loop.
Do we need both DocChecker and SurveyPal?
Both are included in the one Hub subscription, so whichever you run today, the other is already yours. Nothing extra to buy; actions use the credits in your plan.
Does the DocChecker process change?
No, same chain, same checks, same review of flagged items. The only difference is the survey stage: instead of paper entering the chain via rekeying, the survey arrives as data.
Who sets the tolerances?
You do. Your thresholds decide what passes as normal survey refinement and what gets flagged as a question for a human.
What if a surveyor genuinely changes something big on site?
That’s exactly what gets flagged, an out-of-tolerance change surfaces for review and confirmation before anything downstream builds on it. The chain sees it as a decision, not a silent edit.
We quote after surveying, not before. Does Connect fit?
Yes, the loop runs survey-first too: the survey is built on site as data, the quote is checked back against it, and the order confirmation against both.
What does it cost?
Both products and the Connect workflow are included in The Glazing Hub subscription, as every Hub product is. Unlimited users, no per-user fees; you pay for actions through credits in your plan.
Watch the loop close around it.
Twenty minutes on a screen share: your quote in, the survey generated, completed, flowed back and checked. If you're already on the Hub, we'll simply switch it on.
20 minutes · one real job · no hard sell