Superintelligence Prep for Glass Shops: Measures and Special Orders

An AI agent can help a glass shop keep every measurement and special order in one traceable record, flag what is still unverified, and draft the paperwork a supplier needs. It cannot see the opening, and it should not decide the final size. The safe pattern is simple: the agent organizes the record and checks it for gaps, while a cutter confirms each dimension on site or from a verified drawing before any special order is released.

Key takeaways

• Every glass size should live in one record that shows who measured, how, and whether a cutter has verified it.
• The agent can draft orders and check that fields are complete, but it should not release a special order on its own.
• Special orders need fields that generic quoting tools often skip, such as edge work, coatings, tempering and the frame system that sets the deduction.
• Write the approval boundaries down before the first job, including who may change a size after a customer request.
• Start with one repeating job type, such as replacement panes or shower enclosures, and judge the setup by whether it catches errors before the supplier does.

Why measurements are the riskiest data in a glass shop

Glass is cut to a finished size, and a wrong size usually means a remake, a second wait at the supplier, and a customer who has already planned around the installation. The trouble is that measurements arrive from many places: a tape measure on site, a photo a homeowner sent by message, a sketch from a general contractor, or a figure copied from an old job that looked similar. Each of those sources has a different level of reliability, and a shop that records them all as simply a size is quietly mixing them together.

The opening is also not the same thing as the glass. The frame, gasket, glazing bite and clearance decide how much smaller the pane must be than the gap it fills. An agent that receives a width and a height from a phone call has received two numbers, not a glass order. The record must keep those numbers labeled as what they are until someone with the right authority confirms them.

Deciding which readings count as verified is an operating rule for the shop, not something software can infer from the data. That rule should be written, short, and applied the same way by everyone who touches a job.

What a measurement record should hold

A useful record is less elaborate than it sounds. For each job, it should contain the following fields, and an empty field should be visible rather than filled in from memory:

• Job reference, site address and the person who owns the decision
• Each opening dimension, with separate readings for top, middle and bottom where the opening may not be square
• The source of each reading: cutter on site, customer photo, contractor sketch or a previous job
• The frame or hardware system that sets the deduction, identified by the manufacturer's model name
• Glass type, thickness, coating, and any tempering or laminating requirement
• Verification status: unverified, cutter verified, or released to the supplier

The agent's job is to notice a blank field, a reading without a source, or a status that does not match the last change in the job. It should never fill a missing value from a similar job or from what it expects the opening to be. If a field is empty, the record says so, and the job stays in the unverified state until a person resolves it.

Tracking special orders from quote to supplier

Special orders differ from stock replacements in ways that matter for tracking. They may involve custom shapes, specific tints, tempered or laminated build-ups, and supplier lead times that the customer may not fully understand when they accept the quote. A special order is only as reliable as the link between the measurement record and the request that goes to the supplier.

For each special order, the record should show the quote reference and what the customer accepted, the supplier and the supplier's order reference, what the customer asked for and every change to that request, the installation window that was promised and who promised it, and each status change with the person who made it. When a customer changes a width or asks for a different tint, the agent should mark the affected measurement as needing re-verification and hold any draft that depends on it. It should not quietly update the supplier request, because that is the moment a small change becomes an expensive remake.

Supplier terms for custom glass vary, and the shop should store the return and remake terms that apply to each order inside the record. When the customer's acceptance and the supplier's terms are in the same place, a later dispute is a question of fact rather than memory. For a similar pattern in another trade, see how estimates and parts tracking works in an auto repair shop.

Where a cutter must verify before ordering

The decision rule matters more than the software. The following guide is a starting point that the shop owner should adjust and sign off:

• Any dimension taken from a photo, a sketch or a phone call: a cutter verifies on site or from a measured drawing before any order.
• Any opening measured by someone other than the cutter who will cut the glass: the cutter re-measures or formally signs the reading.
• Any change to the frame, hardware, glazing system or wall condition since the last reading: re-verify the affected dimensions.
• Any shape that is not a simple rectangle, such as an arch or a radius corner: a template or cutter confirmation is required.
• Any opening where the top, middle and bottom readings differ: the cutter confirms which reading governs the cut.
• Any special order above a value the owner sets in writing: owner approval before release.
• A standard replacement where the prior record matches the site note and the frame is unchanged: the cutter reviews the record and confirms it, which is faster than a new site visit.

Illustrative scenario: a homeowner emails a width and a height for a shower enclosure and asks for tempered glass as soon as possible. The agent opens the job, marks both readings as unverified because they came from email, and drafts a special order for review without sending it. The cutter visits, finds the top of the opening narrower than the bottom, and records both readings. The order is held, the record shows the change and its source, and the draft is corrected before anything reaches the supplier. Nothing about this required the agent to be clever. It required the record to refuse to treat an email as a measurement.

Treating every agent output as a draft until a named person checks it is consistent with the risk-management approach in the NIST AI Risk Management Framework, and limiting each tool to the access the task needs follows the principle in the OWASP authorization guidance.

How Be Human's managed approach handles this

Be Human starts by defining the memory and tools this shop needs: the measurement fields described above, read access to job and quote records, a draft-only path into the supplier portal, and a written approval boundary that keeps release with a named person. The first engagement also sets an observable success criterion, such as every special order carrying a cutter-verified reading before release. Managed operations then review permissions when staff change, run recurring checks on whether records are complete, and handle incidents if a wrong dimension ever reaches a supplier. The work is remote, available in English and Portuguese, and it supports the cutter's judgment on site rather than replacing it. Anthropic's guidance on building effective agents makes a similar point: clear checkpoints and simple, well-defined steps are easier to trust than open-ended autonomy.

Where to start with one job type

Choose one job type that repeats every week, such as replacement panes for a single frame system. Write the measurement fields and the verification rule for that job only, and run the new record alongside your current process for a short trial. Then compare the cases where the record flagged a gap with the cases where the old process would have produced a remake, and adjust the rule before extending it to other jobs. Keep the first scope narrow so that the approval boundaries are easy to test and easy to explain to the people who use them.

If you are not sure which task in your shop is the right first one to hand to an agent, take the free Be Human AI diagnostic to find it.

Frequently asked questions

Can an AI agent take measurements for a glass job? It cannot measure an opening, and it should not treat a phone call or a photo as a verified reading. Its role is to store each reading with its source, flag gaps, and keep the record consistent across changes. A cutter or a verified drawing remains the source for any size that goes to a supplier.

Which special orders need the most checking? Shapes that are not simple rectangles, tempered or laminated builds, tinted or coated glass, and any job where the frame or wall condition changed after the first reading all need closer review. The record should show why each order is flagged so the reason is visible to the cutter. The decision guide in this article is a good starting point for your own list.

Who should be allowed to release a special order? Name one person, usually the cutter or the shop owner, with written authority to release a special order after verification. The agent can prepare the request and check that it is complete, but it should not have permission to submit to a supplier without that person's approval. Review those permissions whenever staff change.

What should a shop do first? Pick one repeating job type, write its measurement fields and approval rule, and run it alongside the current process for a short trial. Compare the gaps the record caught with the remakes the old process would likely have produced, then adjust the rule before expanding the scope. A narrow first step is easier to test, easier to explain, and easier to trust.

Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.