An interactive display checklist for school IT

What should school IT verify before purchase?

Verify the exact configuration, the school’s required applications, the full connection path and who owns updates and support. A product family name or Android version does not answer those questions.

This is an evidence-request and acceptance checklist. It does not assert that a Penthia configuration supports a particular network protocol, identity system, management platform or certification. Check an item only when you have a documented answer or a completed test.

No email gate. Checkmarks stay only in this page session; print your record before closing it. Do not enter credentials or student information.

Identify the quoted equipment

• Exact model, size, memory and storage are identified in the quote.
• Software, licenses, computing modules and optional accessories are itemized.
• Required exact-brand/model certification documents have been obtained or the requirement remains unresolved.
• Panel dimensions, weight and compatible mount/stand documentation are available.

Resolve network and account requirements

• IT has defined network authentication, filtering and segmentation requirements.
• The vendor has documented supported network and casting behavior for this configuration.
• A school-approved test account can access required applications.
• User sign-out, saved-file cleanup and sharing permissions have been tested.
• Update and management responsibilities are assigned without assuming unsupported MDM compatibility.

Ask IT to define required authentication, segmentation, filtering and account controls. Ask the vendor for exact supported behavior and public documentation. Do not open firewall ports based on a generic casting tutorial or assume a management name means compatibility with the school’s system.

Test a teacher’s complete lesson

• The intended teacher laptop provides a readable picture and the expected sound.
• Touch reaches the correct device and works in the actual lesson application.
• Annotation can be saved and reopened in an approved destination.
• Wireless sharing and handover work on the actual school network if required.
• The smallest lesson content is readable from the farthest and side seats.

Record failures as specifically as successes. “Picture works, touch does not return to the laptop” identifies a different problem from “the application cannot sign in.” Use the connection checklist to separate paths.

Assign deployment and service ownership

• Delivery, unloading, assembly and installation responsibilities are explicitly agreed.
• Warranty and support terms have been reviewed with the exact quote.
• The school knows how to report a fault and distinguish display, computer and cable issues.
• A pilot configuration and its unresolved issues have been recorded before rollout.

The existing Penthia warranty and support page explains the published policy. The purchase quote should identify any additional agreed services. This checklist does not add a new support guarantee.

Keep an acceptance record

For each test, record the configuration, date, tester, expected behavior, observed result and unresolved issue. Use school-approved private storage for those records. The public checklist is not a place to publish asset identifiers, account details or sensitive network information.

Approve a pilot configuration before standardizing a larger order. If certification is required by procurement, exact-brand/model evidence is a gate—not a feature to infer from another company’s hardware platform. Send Penthia your requirements without including secrets.