CONNECTED TECHNOLOGY. CLEARLY EXPLAINED.
Compatibility evidence worksheet
Record the exact function, device roles, market, versions, source, dates and uncertainty. Keep proposed tests and observed results in a separate linked test record.
Practical resource · By Admin · Version 1.0 · Reviewed 20 October 2026.
Compatibility is a claim about particular functions and configurations. Use this workbook to keep the exact scope visible, from a dated source to an actual test record. It starts blank and assigns no automatic compatibility score or certification.
Download the compatibility evidence worksheet XLSX · v1.0 · 10.0 KiB
Two worksheets, each with 30 prepared rows: Evidence register and Test record. Includes editable cells, evidence/test status choices, filters, frozen headers and date/time formats. No macros or external data connections are included.
Make each claim checkable
Name the function and roles
Record the function you need and each device’s actual role. Include the exact market and hardware/firmware context. A shared protocol name does not by itself establish the function for every configuration.
Keep source and dates together
Record the source URL, its date, your checked date and the precise scope of the claim. Keep a later firmware change, another region or an untested feature visible as a separate uncertainty.
Link a real test record
Use Evidence IDs to connect documentary claims to Test IDs. Keep expected and observed results separate. An unrun test or an empty observed-result cell provides no evidence that a test passed.
From a source to a reviewed observation
1 · Register the claim
On Evidence register, give the record an internal Evidence ID. State the required function, device/role pair, market and versions. Enter the source, source date, checked date and exact supported scope.
2 · Keep uncertainty visible
Use the manual evidence-status choices: Unassessed, Documentation only, Test record linked, Mixed evidence, Needs review or Not applicable. Explain the gap or next check and record an accountable owner role. These labels are not calculated product verdicts.
3 · Record a proposed or actual test
On Test record, use a Test ID and the matching Evidence ID. Describe the exact setup, action, conditions and expected result. Enter the actual observation only when it exists, with UTC observation time, limitations and reviewer role. Leave an unrun test explicitly Not run.
4 · Review the scope before using it
Check that the claim and observed setup refer to the same models, market, versions, roles and function. Keep unsupported extensions unassessed. Revisit the record after an important configuration or software change. Attach longer evidence separately and adjust row heights for long notes.
Keep your own evidence copy
The workbook is a manual local record, with no answer-submission action. Save a copy in a location appropriate for the evidence you enter. Use the same IDs across the two sheets; matching them is your review task.
Check your spreadsheet app
Open a copy in an XLSX-compatible app. Check the status choices, filters, frozen headers and date/time display before adding real records. The observation-time column is labelled UTC; enter the intended UTC time. Microsoft Excel desktop has not been tested for this release.
Version and reuse
Original IoTPapa workbook by Admin, version 1.0, reviewed 20 October 2026. Personal and internal business use with attribution is permitted. It does not run a device test, establish interoperability or certify a product.
Download the current version
Download the compatibility evidence worksheet XLSX · v1.0 · 10.0 KiB
Two worksheets, each with 30 prepared rows: Evidence register and Test record. Includes editable cells, evidence/test status choices, filters, frozen headers and date/time formats. No macros or external data connections are included.
Use evidence in the purchase decision
CONTINUE READING
Read the evidence framework
Distinguish documented features, observed tests and missing evidence.
CONTINUE READING
Complete the purchase checklist
Connect compatibility questions to services, support, privacy and exit.
CONTINUE READING
Read the buying guides
Consider the complete connected system and continuing ownership.