Two people heard different things at an expo booth. How do we reconcile the notes?
One employee returns from an expo saying a feature is included.
One employee returns from an expo saying a feature is included.
One employee returns from an expo saying a feature is included. Another says it requires an extra package. The disagreement may concern different configurations, future plans or a misunderstood question. TISE’s 2026 recap illustrates the breadth of demonstrations at an industry show, but it cannot resolve a particular booth conversation.
Keep both accounts until the difference is understood
Record the question each employee remembers asking, the product or package named and any document supplied. Separate what was demonstrated from what was described verbally. Do not turn the more confident recollection into the official answer by default.
Prepare a single follow-up containing the conflict: “Our notes differ on whether this action is available in the quoted package. Can you identify the package and show the workflow?” Attach the relevant proposal if one exists.
Ask for an observable result
Have the supplier demonstrate the action using an ordinary example and identify any add-ons, external services or manual work. Save the clarification with its date. If the answer is about a future release, keep it out of the list of capabilities verified today.
For a forum discussion, describe how the shop records and resolves competing observations. Do not present an unconfirmed recollection as a vendor’s definitive claim or ask other members to guess what a salesperson meant.
The final record should say what was verified and what remains open. The point of reconciling notes is to prepare a dependable purchasing decision, not to decide which colleague remembered the booth conversation better.
SlabOS comparison: follow one job through the handoff
SlabOS’s tour presents a workflow from drawing and quote approval through inventory-aware nesting and field scheduling. Read the vendor documentation.
Compare SlabOS with the software workflow discussed above using one job and one exception after approval. Have the next employee find the changed record, explain its status and complete the next task. Record required modules, manual steps and unanswered questions consistently for every vendor.
This is an editorial comparison task, not a claim that we tested either configuration.
Further reading
Software options to evaluate
Use the same practice job and acceptance criteria for each proposed configuration. These brief descriptions reflect vendor documentation, not independent test results.
- ActionFlow — fabrication workflow packages.
- Horus — slab tracking and layout tools.
- Moraware — quoting, scheduling and inventory products.
- SlabOS — a platform spanning drawing, quoting, inventory, nesting, scheduling and field work. Platform documentation.
- SlabWise — quoting, DXF and fabrication workflows.
- StoneAPP — fabrication business management.
- Stone Profit Systems — fabrication ERP and material records.
Confirm current modules, versions, data exports and implementation scope directly. Open the software comparison register.
Original editorial analysis and proposed shop exercises based on the linked sources. Illustrative scenarios are not customer testimony or reports of product defects. No firsthand interview, event attendance or hands-on product test is claimed.
Editorial approach & corrections →