Business
Smoke control company website versus commissioning software: what belongs where?
Compare the roles of a smoke-control company website, client CRM and specialist test documentation software without confusing marketing with code compliance.
One company can need three different systems
A smoke-control practice has a public-facing business, a sales and scheduling process, and a regulated technical practice. The temptation is to ask one platform to run all three. That sounds efficient until someone expects a website contact form to provide controlled test procedures, legally significant inspection reports or professional certification.
The more useful question is which system owns each record and who is responsible for it? A modest architecture often reduces risk and cost: a clear website for procurement, a CRM for ordinary commercial relationships, and specialist tools for the test process.
What the public website should own
A serious smoke-control site should make it easy to understand services, jurisdictions served, professional roles, project phases and procurement contact. It should help a first-time visitor answer four questions: Is this the correct specialty? Can this firm work on my type of building? Can it work where I am? What information does it need before preparing a proposal?
Typical public material includes service descriptions, anonymized projects, qualification statements verified by the firm, process guidance and request forms. This is durable marketing content. It is not a substitute for engineer-reviewed project documents.
What a client CRM can reasonably hold
Ordinary business records include company contacts, enquiry dates, call notes, next follow-up, proposal status and billing-stage context. A CRM is helpful when different stakeholders reach out about the same property or when a general contractor returns with a second project. It should not silently become the authoritative register of tested devices, calibrated instruments, life-safety sequences or final acceptance reports.
For example, a CRM note might say “proposal requested for pre-occupancy smoke-control testing; technical reviewer to confirm scope.” It should not copy confidential control sequences or produce a compliance conclusion. Store the project document reference and access instructions in the appropriate managed location.
What specialist commissioning or inspection software owns
Depending on the firm and jurisdiction, technical systems may control the approved test plan, system components, device schedules, site observations, instrumentation and calibration evidence, deficiencies, witness sign-offs, report revisions and record retention. These workflows require defined permissions, traceability and professional review. They are outside an ordinary website's promise.
| Question | Website and enquiry layer | Client CRM | Specialist technical system |
|---|---|---|---|
| Which services and markets do we serve? | Primary owner | Reference | Not required |
| Who asked for a quote? | Initial capture | Primary follow-up | Optional project reference |
| Who owns the approved test plan? | Explain process only | Refer to responsible party | Document control |
| What measurement was observed on site? | Never a public claim | Avoid recording values by default | Verified technical record |
| Has the authority accepted the report? | Do not infer | Record confirmed project milestone if appropriate | Official signed/approved record and AHJ process |
A sensible handoff workflow
This is an operating model, not a claim that the three tools are automatically integrated. An integration, if needed, should be specified, tested and approved separately.
- A buyer finds a clear smoke-control testing page and submits a request.
- The office reviews location, system type and project phase, then asks for the approved documentation through the firm's established channel.
- A qualified technical lead defines the contracted scope, independence requirements and access.
- Commercial staff track the proposal and customer communication in the CRM.
- The team executes and records testing in its approved technical process; formal reports follow the relevant review and filing requirements.
- The CRM records only a customer-facing status or follow-up, without duplicating restricted technical evidence.
When is a larger integrated solution worthwhile?
A single discipline practice with occasional projects may be well served by a lean website and established specialist documentation tools. A multi-office inspection organization may need tighter project identity, access controls and handoffs. Before buying an all-in-one package, check whether it genuinely satisfies your technical audit trail and legal obligations rather than merely offering an “inspection” label.
OneStudio provides public website, enquiry and optional business modules. Its features page describes the scope of booking, client records and related workflows. Use those only where they fit your actual service model.
Avoid five claims that create unnecessary risk
Do not say a website automatically certifies systems, guarantees compliance, files every AHJ report, runs integrated smoke-control tests, or replaces professional inspection software. Even if a firm has an internal integration, the claim must describe what was actually built and who is legally responsible.
CTA: make the business layer simpler without weakening technical control
Map every customer-facing step from the first project request to the final commercial follow-up. Explore OneStudio features for that layer, and keep controlled inspection records where qualified professionals manage them.