Upper-Limb Table Software Delivery Acceptance Sheet

Why does KF-SGZ need a configuration-specific record?

The RehabIntl catalog uses KF-SGZ for multiple upper-limb table configurations. The software listing explicitly asks buyers to verify the hardware, software package, language, licence and computer requirements in the quotation. The model code alone does not identify the complete delivered system.

This worksheet is for a clinic or distributor preparing a handover record after agreeing the purchase scope. It does not promise that the product provides reporting, cloud storage, patient accounts or any specific training activity. Include those items only if supported by the supplier's written offer.

Agree the acceptance basis before shipment

Save the accepted quotation revision and itemised configuration. Identify the software package and quoted version or release basis, the licence terms, supplied hardware, required system environment and promised documentation. Agree which checks the supplier will demonstrate and which the facility will perform after setup.

Name the delivery contact and the person authorised to record unresolved items. Agree whether a partial delivery can be recorded separately and how differences will be resolved under the purchase terms. This guide does not create a warranty, service commitment or right to withhold payment.

Copy this blank delivery acceptance sheet

Use one record for the exact KF-SGZ software configuration and retain evidence securely. Do not put passwords, activation keys or patient records in a shared procurement sheet.

Suggested status labels are confirmed, pending clarification, not supplied and not applicable. “Not applicable” requires an explanation tied to the agreed scope; it should not hide a missing promised item.

What should the handover demonstration cover?

After supplier-approved installation, confirm that the delivered package identifies the agreed version and can start in the agreed system environment. Check the quoted interface language and the specific functions named in the order. Record the demonstration reference or relevant manual page rather than writing only “software works”.

If the order includes a computer or accessories, reconcile the supplied items separately from the software licence. If hardware is buyer-supplied, confirm compatibility and responsibility before attributing a problem to the table. Do not assume that a successful launch proves every promised function or licence condition has been met.

Use synthetic demonstration data rather than real patient details. If the quoted system stores or transfers user information, ask for the applicable data-handling documentation and have the facility's responsible team review it before live use. No particular storage or network architecture is assumed here.

Keep future support separate from day-one checks

Record the support contact, update scope, renewal basis and recovery process as contractual questions. Successful activation today does not establish future updates, free renewal or a replacement-computer entitlement. Ask what happens if supplied hardware is replaced and how licence continuity is handled.

For an unresolved difference, identify the quoted requirement, observed result, evidence and supplier response. Agree a follow-up action without marking the item confirmed prematurely. Keep the final handover record aligned with the actual accepted configuration, not with a generic brochure.