ZenithronOpen workspace ↗

Zenithron Handbook / Signatures, paper reports and PDFs

Assigned engineers and permitted reviewers

Signatures, paper reports and PDFs

Finish a report with a traceable confirmation.

What to do

  1. In a draft report, open Service details, times and tools. Expand Edit service details and record the service type, reported problem and device outcome. Describe the actual findings; do not infer a successful outcome from a completed visit.
  2. Expand Add travel or work time, choose the type and enter the start, end, description and reason. Times use your local browser time zone and must be in the past, end after they start and not overlap within this report. Use Correct time or Remove time for a correction, with a reason.
  3. Expand Add tool used, search the register, select an active tool and record its use date and reason. Review the captured model, serial number and calibration status. A tool may be recorded once per date. Remove and re-add an incorrect selection before preparing the report.
  4. Save and review the report, service details, time entries and tool evidence before Prepare report for customer review. Preparation freezes these saved details into the version presented to the customer.
  5. Review the saved report content, actual quantities and reference numbers before requesting confirmation. Complete the visit prerequisites shown by the form.
  6. For digital confirmation, enter the signer’s name and follow the signature/declaration steps. If a signature cannot be obtained, use only the supported exception workflow with an honest reason.
  7. For an already signed paper report, expand Import a signed paper report. Save an accurate transcription, upload the paper original and record its original number/date as required.
  8. Wait for the original to pass scanning, then verify the paper evidence and transcription through the form. The paper route avoids demanding a second customer signature for the same report.
  9. After finalization, download the protected PDF when available. For a correction to finalized content, use the supported new-version/addendum process; do not edit an issued document silently.
  10. Complete and save the attached service checklist before preparing the report. Required steps need a result; Fail and Not applicable need an explanation. The prepared version and PDF retain those exact results.
  11. In Change history, History author filters all recorded changes, My recorded changes or System actions within this record. The latest-change summary and older/newer pages follow the chosen filter. Changing the filter returns to its first page. My recorded changes uses your current signed-in identity; it does not show changes whose personal attribution was removed. Assignment and the customer signatory remain separate.
  12. Start the visit when work begins. Save the report text, checklist and actual work separately. End the visit when the work is finished, then review and prepare the saved report for the customer.
  13. Preparing freezes a version; it does not sign it. Record the customer's acknowledgement or the genuine signature exception. The coordinator closes the service case separately; billing and invoices remain separate.
  14. If a save or visit end is unconfirmed, confirm that same action again. Do not enter a second action. A real concurrent change requires comparing the saved report; it is never overwritten automatically.
  15. Before preparing a new report version, billing staff records the customer PO in the existing actual-work section. Preparation freezes that reference for customer review and the PDF. An empty new value is explicit; a historical version without this field stays unchanged.

Before you continue

A drawn signature is not presented as a qualified electronic signature.

The saved PDF is the issued evidence for its version. Later customer or equipment corrections do not rewrite those stored bytes.

Travel and work intervals document this visit. They do not automatically create labour quantities, customer charges, stock movements or invoices. PDF time entries are explicitly shown in UTC.

A tool entry captures the register details when it is added. A later register correction does not silently update that entry or an issued report. Unknown or overdue calibration dates are displayed honestly and must be assessed under your company procedures.

Time, material and measurement corrections require an amendment. The original report, PDF and signature stay unchanged; the amended version needs a new customer acknowledgement.

Existing internal handovers require another review after this amendment. Previously prepared exports stay unchanged and cannot represent the corrected version.

Billing has already been queued. This report cannot be corrected automatically; a separate reviewed adjustment process is required.

Open Change history in a case, work order, visit, report or quotation to see the latest recorded author, time and status change. Expand it for reasons and older pages. The assigned technician and customer signatory are separate from the change author. Automatic actions show System; an initiator may be recorded separately. Missing historical names or status values remain unknown. Check the displayed time zone; Show UTC switches the view without changing the stored instant.

Unconfirmed report text stays only in this open page when you go back and forward. Reloading or closing the browser loses it. Saved drafts stay on the server. Save or explicitly discard before leaving; discarding never deletes a saved report.

A signature exception is recorded. Billing is still blocked; the billing team must review the exception and the applicable policy.

A current draft blocks case closure, including an amendment draft. Older frozen versions do not block it. A recorded signature exception does not add a new signature requirement for closure; billing remains subject to its existing checks.

Read the solution, then record only the work and results actually observed in the report and checklist. Nothing is copied or marked as resolved automatically. Feedback belongs to this solution revision and does not prove repair success.

Refresh to check the current publication and source. Save or discard an open form first. Retry an unconfirmed save unchanged; discarding does not undo a confirmed save.

A finding needs a later successful inspection of the same point, device, customer and template version at a different visit. Choose its report revision as evidence. Customer publication is a separate explicit action.

Changing the operational PO later does not change a prepared or signed version. Use the existing amendment and review process when the next version must show a different PO. A PO reference does not verify identity or turn service acknowledgement into order or contract acceptance.

Signature process review is an unsaved, inactive planning aid. Explicitly choose on-site service acknowledgement at the technician device or business document acceptance. The report version shown is not automatically an offer, buyer PO, order confirmation, maintenance contract or service contract.

No new signing request, personal evidence, IP/user agent, invitation or delivery is created by this review. Document policy, exact version/attachments/terms, country/form requirements, signer verification/authority, purpose/legal basis/transparency/access and finite retention must be decided before a new flow can activate.

Questions and troubleshooting

Why is a document download blocked?

A successful scan and current access permission are required. Pending, rejected or unavailable scanning keeps protected originals blocked. Contact the responsible operator if the status does not recover; do not bypass quarantine.

Why did finalization fail?

Check required fields, visit status, confirmation evidence and the displayed error. PDF generation failures must be resolved before treating the report as finalized.

Why can I no longer change service details?

These fields are editable only while the report is a draft and you have permission for that visit. A prepared or finalized version is protected against silent changes.

Why did saving show a version conflict?

Another change saved a newer report revision. Keep a copy of your unsaved text, reload, review the latest saved content and apply the intended correction again.

Browse all topics · Resolve a problem