From equipment owner to coordinator
Select an instrument and propose a service window. Give the coordinator the reason, access details, and replacement needs required to confirm the arrangement.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Preview with sample data. Sign in to explore or install the app.
Keep proposed information separate from the decision so the form is easy to submit and the service window is genuinely reviewed.
The request number is generated automatically. The owner should not have to guess the final provider or approved service dates.
The review creates a confirmed arrangement, not a certificate or a use authorization.
Choose structured fields for repeated choices and short explanations for the facts that vary.
| Detail | Too vague | Useful for coordination |
|---|---|---|
| Instrument identity | “The pressure gauge” | UTIL-PG-031, serial PG10-91744, at the utilities test bench. |
| Timing | “ASAP” | Proposed service on 15 September; required back by 17 September for the planned test. |
| Access | “Collect from the workshop” | Coordinate with the equipment owner and follow the bench-isolation procedure before collection. |
| Replacement | “We may have a spare” | A replacement is required; confirm the approved range and availability before service. |
| Reason | “Needs checking” | Scheduled calibration, suspected damage, or failed verification, with the relevant explanation. |
Open the confirmed dates and provider arrangement from the request. If another arrangement has since changed the instrument’s current service, recheck it instead of overwriting newer work with an old approval.
Submit the result against the same request. The equipment identity and provider context stay linked while the original certificate and findings are reviewed.
Address incomplete evidence and any failed-result impact, then complete the separate use decision. Keep the request history available to explain what was arranged and what happened.
Your team may need a site contact, access restrictions, available power, or a shutdown reference. Add the relevant fields and decide which ones are mandatory for that service type.
Collection location, packaging, shipping details, and replacement arrangements may matter more. An authorized business administrator can adapt the request and review steps without creating a disconnected form for every provider.
This example uses one instrument per request so identity, timing, results, and later reviews stay unambiguous. For a shipment containing several tools, create the individual requests and record a shared shipment reference in your coordination process. A batch-request form with per-instrument decisions would be an additional configuration, not an included feature.
Yes. Explain the service need and proposed timing; the coordinator selects the provider and confirms the arrangement during review. Do not invent an approved appointment or provider commitment just to complete the requester’s portion of the form.
Ask the coordinator to establish or correct the equipment record first. Check the tag and physical serial rather than selecting a similar model. Using the wrong record would attach the service, certificate, and later decisions to the wrong instrument.
Yes. Choose the reason that reflects the problem, such as suspected damage or failed verification, and explain what happened. Follow your equipment-control procedure for any immediate restriction. A service request is not a technical judgment that the instrument may continue in use while waiting.
Tell the coordinator which constraint changed and arrange correction or a replacement request before service is confirmed. Keep the earlier arrangement explainable in the history. After confirmation, do not silently edit dates and assume the provider has received or accepted the change.
Open New service request, select a sample instrument, and review the proposed dates, priority, access, and replacement fields. Install a copy to submit and review your own requests.
