CESDEV Guides & Tools
Useful business problems rarely introduce themselves clearly. Start with a symptom, test what can be tested and follow the evidence toward the right level of action.
Two-minute decision aid
Select only statements you have actually observed. This is not a scorecard; it looks for the pattern behind the symptoms and suggests a practical starting point.
Select observed facts, not suspicions. Several connected clues are more meaningful than one isolated issue.
Less-obvious evidence
These are not proof by themselves. They are useful places to look because ordinary reports often hide them.
A product may show positive stock overall while the sellable location is negative and unusable or inbound locations make the total look healthy. Compare quantity by status and location, not only the grand total.
“Call before delivery,” “price held until Friday” or “must arrive before shutdown” often lives in email. If a promise cannot travel with the order, the process depends on memory.
Gross margin can look healthy while slow turns, awkward storage, partial kits, damage risk and handling time quietly consume cash and space.
A connector may be technically documented but still depend on one person's mailbox, authenticator, API key or payment card. Test operational ownership, not just whether it works today.
Removing an item from sale does not remove warranties, replacement parts, historic links, customer documents or tax records. “Inactive” is not the same as finished.
If two people cannot reproduce the same number from the same source, the report contains undocumented decisions—not just formulas.
A cleaner online form can increase manual handling if its values do not match customer, product or delivery records downstream. Measure the whole transaction, not only conversion.
A new case pack, model label, lead-time rule or replacement SKU can distort purchasing and margins long before anyone calls it a systems problem.
A successful backup notification proves that a job ran. It does not prove the right data was included, credentials are available or the business can resume within an acceptable time.
Free external checks
These independent tools can test a narrow question without giving CESDEV access to your systems. Use them as indicators—not as a complete audit or automatic verdict.
Search participating federal, provincial and territorial registries to compare public business identity and status with contracts, invoices and website details.
Open the official registry searchNo result is not proof that a business does not exist; coverage and naming vary by jurisdiction.
Confirm whether a supplier's GST/HST account was registered on the transaction date using its nine-digit number and business name.
Open the CRA verification guideSave the result with the transaction evidence. This tool validates a specific account and date, not the entire supplier.
Check a domain's registrar and available registration data. This can expose a forgotten registrar, unexpected nameserver or unclear renewal path.
Open ICANN LookupPrivacy redaction is normal, and public registration data is not proof of internal ownership or account control.
Check modern standards including HTTPS, DNSSEC, IPv6, DMARC, STARTTLS and related domain and email protections in one place.
Run the independent testsA score is a technical snapshot. Configuration changes should be planned so working mail and websites are not disrupted.
Perform a deeper public analysis of a website's TLS certificate and server configuration when the broader check identifies a concern.
Open the SSL Server TestTest systems you own or are authorized to assess. A strong TLS grade is not a complete security assessment.
Review public HTTP security headers and related browser protections that are easy to miss when a website appears to work normally.
Open HTTP ObservatoryAutomated results need context; adding strict headers without testing can break legitimate site functions.
Compare mobile and desktop performance indicators and see whether real-user field data is available for the tested page.
Test a public pageTest several important pages. A fast homepage says little about forms, search, product pages or checkout.
Identify many accessibility errors and inspect how page structure may affect people using assistive technology.
Run the WAVE testWAVE supports human review; it does not certify accessibility or replace testing with actual users.
Check whether a public page's structured data is eligible for Google-supported enhanced search features.
Test structured dataEligibility does not guarantee display or ranking. Validate the business facts behind the markup too.
Use Canada's baseline cyber controls to challenge overlooked assumptions about account management, backups, incident planning and service-provider risk.
Read the Canadian baseline controlsGuidance helps frame decisions; technical or legal obligations may require qualified specialists.
Make the result useful
A good starting record is small enough to understand and specific enough to reproduce. It turns “something seems wrong” into a question that can be tested.
Example: “The website says 14 available; the sellable warehouse location contains 3.”
Name the report, system, URL, location or document and when it was checked.
Identify the delayed order, lost time, cash exposure, customer risk or decision that cannot be made confidently.
Record what is known, what someone reported and what remains an untested assumption.
When the evidence points somewhere
Use when the symptoms cross people, records, operations and systems or the root cause is still uncertain.
Explore the Baseline Audit →Use when the need is verified and simplifying, configuring or connecting existing tools cannot close the gap.
Explore Development →Use when priorities, documentation and working systems need a controlled rhythm of continued attention.
Explore Care Plans →Check whether CESDEV has already released a focused application that fits the environment and requirement.
Explore Apps →CESDEV Guides & Tools
Useful business problems rarely introduce themselves clearly. Start with a symptom, test what can be tested and follow the evidence toward the right level of action.
Two-minute decision aid
Select only statements you have actually observed. This is not a scorecard; it looks for the pattern behind the symptoms and suggests a practical starting point.
Select observed facts, not suspicions. Several connected clues are more meaningful than one isolated issue.
Less-obvious evidence
These are not proof by themselves. They are useful places to look because ordinary reports often hide them.
A product may show positive stock overall while the sellable location is negative and unusable or inbound locations make the total look healthy. Compare quantity by status and location, not only the grand total.
“Call before delivery,” “price held until Friday” or “must arrive before shutdown” often lives in email. If a promise cannot travel with the order, the process depends on memory.
Gross margin can look healthy while slow turns, awkward storage, partial kits, damage risk and handling time quietly consume cash and space.
A connector may be technically documented but still depend on one person's mailbox, authenticator, API key or payment card. Test operational ownership, not just whether it works today.
Removing an item from sale does not remove warranties, replacement parts, historic links, customer documents or tax records. “Inactive” is not the same as finished.
If two people cannot reproduce the same number from the same source, the report contains undocumented decisions—not just formulas.
A cleaner online form can increase manual handling if its values do not match customer, product or delivery records downstream. Measure the whole transaction, not only conversion.
A new case pack, model label, lead-time rule or replacement SKU can distort purchasing and margins long before anyone calls it a systems problem.
A successful backup notification proves that a job ran. It does not prove the right data was included, credentials are available or the business can resume within an acceptable time.
Free external checks
These independent tools can test a narrow question without giving CESDEV access to your systems. Use them as indicators—not as a complete audit or automatic verdict.
Search participating federal, provincial and territorial registries to compare public business identity and status with contracts, invoices and website details.
Open the official registry searchNo result is not proof that a business does not exist; coverage and naming vary by jurisdiction.
Confirm whether a supplier's GST/HST account was registered on the transaction date using its nine-digit number and business name.
Open the CRA verification guideSave the result with the transaction evidence. This tool validates a specific account and date, not the entire supplier.
Check a domain's registrar and available registration data. This can expose a forgotten registrar, unexpected nameserver or unclear renewal path.
Open ICANN LookupPrivacy redaction is normal, and public registration data is not proof of internal ownership or account control.
Check modern standards including HTTPS, DNSSEC, IPv6, DMARC, STARTTLS and related domain and email protections in one place.
Run the independent testsA score is a technical snapshot. Configuration changes should be planned so working mail and websites are not disrupted.
Perform a deeper public analysis of a website's TLS certificate and server configuration when the broader check identifies a concern.
Open the SSL Server TestTest systems you own or are authorized to assess. A strong TLS grade is not a complete security assessment.
Review public HTTP security headers and related browser protections that are easy to miss when a website appears to work normally.
Open HTTP ObservatoryAutomated results need context; adding strict headers without testing can break legitimate site functions.
Compare mobile and desktop performance indicators and see whether real-user field data is available for the tested page.
Test a public pageTest several important pages. A fast homepage says little about forms, search, product pages or checkout.
Identify many accessibility errors and inspect how page structure may affect people using assistive technology.
Run the WAVE testWAVE supports human review; it does not certify accessibility or replace testing with actual users.
Check whether a public page's structured data is eligible for Google-supported enhanced search features.
Test structured dataEligibility does not guarantee display or ranking. Validate the business facts behind the markup too.
Use Canada's baseline cyber controls to challenge overlooked assumptions about account management, backups, incident planning and service-provider risk.
Read the Canadian baseline controlsGuidance helps frame decisions; technical or legal obligations may require qualified specialists.
Make the result useful
A good starting record is small enough to understand and specific enough to reproduce. It turns “something seems wrong” into a question that can be tested.
Example: “The website says 14 available; the sellable warehouse location contains 3.”
Name the report, system, URL, location or document and when it was checked.
Identify the delayed order, lost time, cash exposure, customer risk or decision that cannot be made confidently.
Record what is known, what someone reported and what remains an untested assumption.
When the evidence points somewhere
Use when the symptoms cross people, records, operations and systems or the root cause is still uncertain.
Explore the Baseline Audit →Use when the need is verified and simplifying, configuring or connecting existing tools cannot close the gap.
Explore Development →Use when priorities, documentation and working systems need a controlled rhythm of continued attention.
Explore Care Plans →Check whether CESDEV has already released a focused application that fits the environment and requirement.
Explore Apps →We use cookies to provide you a better user experience on this website. Cookie Policy