1. Patch Management System
  2. Process
  3. Request and receipt review
Process · Request and receipt review

Request and receipt review

Keep service requests and integration event exceptions accountable.

Step by step

  1. Submit a request Request Coordinator

    Request Coordinator records the requester, service, request type and requested date. Due date gives the team a target for the work.

    • Request scoped
    • Updates Service requests, People, Services
  2. Decide on the request Service Owner

    The coordinator and Service Owner review the submission and record Approved or Rejected. An approved request can proceed to fulfilment.

    • Decision recorded
    • Updates Service requests
    ApprovalA person approves before the work moves on.
  3. Record progress Request Coordinator

    Request Coordinator moves approved work to in progress, then enters a completion date and marks Completed when the service request is finished.

    • Work and completion dated
    • Updates Service requests
  4. Review event intake Admin

    Admin examines received integration events by provider, external event ID and received time.

    • Provider event identified
    • Updates Integration receipts
  5. Handle exceptions Admin

    Admin inspects Rejected and Failed receipts, checks the source event and decides what correction is needed before relying on that event.

    • Failed intake examined
    • Updates Integration receipts
Request Coordinator
, Service Owner, Admin, Change Manager, Patch Operator.

Set up Patch Management System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started