{"id":3976,"date":"2026-03-10T22:07:24","date_gmt":"2026-03-11T02:07:24","guid":{"rendered":"https:\/\/www.airsupervision.com\/wp-r\/docs\/general-knowledge\/ramp-out-in-pads\/the-signature-pad\/"},"modified":"2026-03-22T09:35:19","modified_gmt":"2026-03-22T13:35:19","slug":"the-signature-pad","status":"publish","type":"docs","link":"https:\/\/www.airsupervision.com\/wp-r\/docs\/general-knowledge\/ramp-out-in-pads\/the-signature-pad\/","title":{"rendered":"The signature PAD"},"content":{"rendered":"\n

This guide explains how front-end users use the shared Flight record Signature PAD<\/strong> for outbound flight-record acknowledgement. In practical terms, this page is the checkpoint used just before a record can continue through the normal workflow. It is not a planning screen and it is not a dispatch management page. Its purpose is narrower: show the activity that is waiting, let the right people review it, make sure important warnings are visible at the moment of acknowledgement, and capture the approval the organization requires.<\/p>\n\n\n\n

The page is intentionally simple because it is usually used on a shared tablet or mobile device. The goal is speed without losing control. You are not expected to re-enter the whole record here. You are expected to confirm that the record, the aircraft or resource status, and the signers are correct before the record moves forward.<\/p>\n\n\n\n

<\/p>\n\n\n\n

What This Page Is For<\/strong><\/h2>\n\n\n\n

Use this page when a flight record or activity is waiting for PAD acknowledgement before departure or before the outbound part of the workflow is considered complete. Depending on the activity type and your organization settings, the PAD may collect:<\/p>\n\n\n\n

    \n
  • an Instructor<\/strong> and Student<\/strong> acknowledgement<\/li>\n\n\n\n
  • a Pilot in Command<\/strong> acknowledgement plus a Supervisor or delegate<\/strong> approval<\/li>\n\n\n\n
  • a single Member<\/strong> acknowledgement<\/li>\n<\/ul>\n\n\n\n

    The page also shows any configured agreement text, optional alert text, resource identification, and open squawks. Those elements are there for a reason. They make the user stop long enough to confirm the right activity is being acknowledged on the right device, with the right people, against the right aircraft or resource status.<\/p>\n\n\n\n

    Before You Start<\/strong><\/h2>\n\n\n\n

    Before opening an item, make sure the right people are physically at the device and that you know which record you are about to acknowledge. This matters because the PAD saves an approval on a live flight record, not on a draft copy.<\/p>\n\n\n\n

    As a quick check, you should normally be able to confirm:<\/p>\n\n\n\n

      \n
    • which activity needs acknowledgement<\/li>\n\n\n\n
    • who should sign on the PAD<\/li>\n\n\n\n
    • whether a second approval is expected<\/li>\n\n\n\n
    • whether the aircraft or resource has open squawks that must be reviewed first<\/li>\n<\/ul>\n\n\n\n

      If something already feels wrong before you open the item, do not use the PAD just to “clear” the record. The page is meant to confirm the real situation, not to bypass it.<\/p>\n\n\n\n

      First-Time Device Authorization<\/strong><\/h2>\n\n\n\n

      If the tablet or mobile device has not yet been authorized as a PAD, the list does not open normally. Instead, the page shows a message saying the device is not an authorized signature PAD and offers a Connect<\/strong> button.<\/p>\n\n\n\n

      <\/p>\n\n\n\n

      Tap Connect<\/strong> to open the PAD sync page. On that page you will see:<\/p>\n\n\n\n

        \n
      • an Access code<\/strong> field<\/li>\n\n\n\n
      • a Device name<\/strong> field<\/li>\n\n\n\n
      • the device Fingerprint<\/strong><\/li>\n\n\n\n
      • a Connect !<\/strong> button<\/li>\n<\/ul>\n\n\n\n

        <\/p>\n\n\n\n

        The access code must come from a flight record responsible. The device name helps staff recognize the PAD later. The fingerprint is the device identification value used during authorization. This step exists to prevent an unknown tablet or phone from acting like an approval device.<\/p>\n\n\n\n

        After a successful connection, the page returns to the waiting list. If authorization fails, ask flight records staff for a new access code or for help removing an old PAD registration.<\/p>\n\n\n\n

        Using the Waiting List<\/strong><\/h2>\n\n\n\n

        Once the device is authorized, the first page shows the company name and a Refresh<\/strong> button. The main area is a live list of activities waiting for PAD action.<\/p>\n\n\n\n

        <\/p>\n\n\n\n

        The list is fed live by the system, so items can appear or disappear while the PAD is open. Use Refresh<\/strong> when:<\/p>\n\n\n\n

          \n
        • you are expecting a new item<\/li>\n\n\n\n
        • someone has just finished another action elsewhere<\/li>\n\n\n\n
        • the list looks outdated<\/li>\n\n\n\n
        • the connection was interrupted and you want to force a reload<\/li>\n<\/ul>\n\n\n\n

          Each list row is there to help you recognize the correct record before opening it. Depending on the record, the row can summarize the activity type, people involved, lesson or route information, or related resource information.<\/p>\n\n\n\n

          <\/p>\n\n\n\n

          Tap the correct row to continue.<\/p>\n\n\n\n

          Why this matters: the PAD does not ask you to re-confirm every identity at the final save step. That is why the list exists as the first filter. It helps you avoid opening and signing the wrong activity.<\/p>\n\n\n\n

          Optional Agreement Page<\/strong><\/h2>\n\n\n\n

          Some organizations configure an agreement text before the signature page. If your setup uses it, tapping a waiting-list item opens an agreement page first. Read the text and then tap I agree and I’m ready to acknowledge<\/strong>.<\/p>\n\n\n\n

          <\/p>\n\n\n\n

          This button does not save the record yet. It only confirms that you have read the agreement and are ready to move to the actual acknowledgement step. The purpose is legal and procedural: the organization can require users to read a specific statement before any signature or approval is accepted.<\/p>\n\n\n\n

          Optional Alert Page<\/strong><\/h2>\n\n\n\n

          After the agreement page, some activity types may show a separate alert page with a Continue<\/strong> button.<\/p>\n\n\n\n

          <\/p>\n\n\n\n

          This alert is different from the agreement text. The agreement is a standing acknowledgement statement. The alert is a situational warning for the current activity type. Read it before continuing because it is meant to draw attention to something the signer should actively notice before approval.<\/p>\n\n\n\n

          What You See On The Signature Page<\/strong><\/h2>\n\n\n\n

          The signature page is built as a review-and-acknowledge screen. It is designed to show the essential facts without overwhelming the user.<\/p>\n\n\n\n

          Exercises section<\/h3>\n\n\n\n

          If the activity includes exercises, they appear at the top of the page in a compact grid.<\/p>\n\n\n\n

          <\/p>\n\n\n\n

          This section helps the signer confirm the training context. If no exercises are attached, the section is hidden. That keeps the page short and avoids showing empty placeholders.<\/p>\n\n\n\n

          Details section<\/h3>\n\n\n\n

          The details cards summarize the record and can include:<\/p>\n\n\n\n

          Field<\/th>What it helps you confirm<\/th><\/tr><\/thead>
          Activity type<\/td>Whether you are acknowledging the right kind of activity<\/td><\/tr>
          Lesson<\/td>Which lesson or training content the record belongs to<\/td><\/tr>
          N. Pax<\/td>The passenger count when relevant<\/td><\/tr>
          From \/ To<\/td>The route or local-flight context<\/td><\/tr>
          Resource type<\/td>What kind of aircraft or resource is involved<\/td><\/tr>
          Registration<\/td>Which specific aircraft or resource record is attached<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

          <\/p>\n\n\n\n

          This summary exists so the signer can catch a mismatch before approving. If the lesson, route, or registration is obviously wrong, stop there and return to the list instead of signing the record.<\/p>\n\n\n\n

          Resource status area<\/h3>\n\n\n\n

          Below the details, the page can show a resource-status section. Depending on the activity, it may include:<\/p>\n\n\n\n

            \n
          • a resource QR code<\/li>\n\n\n\n
          • the actual total time value shown beside that code<\/li>\n\n\n\n
          • open squawks or maintenance warnings<\/li>\n<\/ul>\n\n\n\n

            <\/p>\n\n\n\n

            The QR code and resource information help confirm that the right aircraft or resource is attached. The open squawks are more important operationally: they are shown at the exact moment of acknowledgement so the signer cannot miss active warnings, grounded conditions, postponements, or maintenance windows.<\/p>\n\n\n\n

            Each squawk card can show:<\/p>\n\n\n\n

              \n
            • a status such as Warning<\/strong> or Grounded<\/strong><\/li>\n\n\n\n
            • how long the condition remains relevant<\/li>\n\n\n\n
            • the main description<\/li>\n\n\n\n
            • a postponed-until date when applicable<\/li>\n\n\n\n
            • a maintenance window value when applicable<\/li>\n\n\n\n
            • an additional expiry or follow-up note<\/li>\n<\/ul>\n\n\n\n

              <\/p>\n\n\n\n

              Read these carefully. They are not decorative notices. They exist so the person giving acknowledgement can do it with awareness of the current resource condition.<\/p>\n\n\n\n

              Understanding The Signature Blocks<\/strong><\/h2>\n\n\n\n

              The lower part of the page contains one or two signature blocks. The labels change with the activity type.<\/p>\n\n\n\n

              Activity situation<\/th>Block labels normally shown<\/th><\/tr><\/thead>
              Training or ground activity<\/td>Instructor<\/strong> and Student<\/strong><\/td><\/tr>
              Renting, internal, or solo-style approval flow<\/td>Pilot in Command<\/strong> and Sup or delegate<\/strong><\/td><\/tr>
              Single-member activity<\/td>Member<\/strong> only<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

              <\/p>\n\n\n\n

              This role-based layout matters because the PAD is not just collecting “two signatures.” It is collecting the right acknowledgement from the right role. The labels tell users what the system expects from that specific record.<\/p>\n\n\n\n

              Photos, Saved Approvals, And PIN Status<\/strong><\/h2>\n\n\n\n

              Each signature block includes a photo area and a name area when the system can identify the person or role. If a signature or approval was already saved earlier, the PAD shows that saved result instead of an empty pad.<\/p>\n\n\n\n

              You may see:<\/p>\n\n\n\n

                \n
              • a handwritten signature image already displayed<\/li>\n\n\n\n
              • a person name with no need to sign again<\/li>\n\n\n\n
              • a PIN<\/strong> indicator instead of a handwritten supervisor signature<\/li>\n<\/ul>\n\n\n\n

                <\/p>\n\n\n\n

                This is important because the page is designed to avoid duplicate approval. If the approval is already on file, the PAD shows it back to you instead of forcing a second entry.<\/p>\n\n\n\n

                In some cases the Agree and Register<\/strong> button does not appear at all once the required approvals are already present. When that happens, the page is acting as a review screen rather than an input screen.<\/p>\n\n\n\n

                Red Or Greyed Signature Cards<\/strong><\/h2>\n\n\n\n

                Sometimes a signature card is shown in a blocked style instead of the usual light card. When that happens, the card is clickable. Selecting it opens a Missing or Expired<\/strong> popup listing the blocking requirements.<\/p>\n\n\n\n

                <\/p>\n\n\n\n

                This behavior exists to stop users from signing blindly when the related person has a missing or expired requirement. The PAD still shows the person, but it also makes the restriction obvious and lets the user read the exact blocking items without leaving the page.<\/p>\n\n\n\n

                How To Sign On The PAD<\/strong><\/h2>\n\n\n\n

                When a signature box is empty and active, sign directly inside the box with your finger or stylus.<\/p>\n\n\n\n

                <\/p>\n\n\n\n

                Take a moment to sign cleanly inside the box. The page is meant to be quick, but it still stores an actual approval image. A clear signature is easier to verify later if the record is reviewed.<\/p>\n\n\n\n

                Good practice:<\/p>\n\n\n\n

                  \n
                • verify the activity summary before signing<\/li>\n\n\n\n
                • read any alert or squawk information first<\/li>\n\n\n\n
                • sign once, clearly, rather than using very short marks<\/li>\n<\/ul>\n\n\n\n

                  When A Supervisor Or Delegate Must Be Chosen<\/strong><\/h2>\n\n\n\n

                  On some Pilot in Command \/ Sup or delegate<\/strong> workflows, the second block shows a search field instead of a pre-filled person. In that case, start typing the supervisor or delegate name.<\/p>\n\n\n\n

                  <\/p>\n\n\n\n

                  The suggestion list starts only after enough text is entered. In practice, that means you usually need at least three characters before matches appear.<\/p>\n\n\n\n

                  <\/p>\n\n\n\n

                  Tap the correct name from the suggestions. The page then fills the chosen name and updates the photo area.<\/p>\n\n\n\n

                  <\/p>\n\n\n\n

                  This lookup step exists so the approval is attached to the correct person record instead of a typed free-text name. It reduces ambiguity and helps preserve traceability later.<\/p>\n\n\n\n

                  When PIN Approval Is Used<\/strong><\/h2>\n\n\n\n

                  Some organizations use a PIN-based supervisor flow instead of, or in addition to, a handwritten supervisor signature. When that option is active, the second approval area may show a PIN field such as Enter PIN<\/strong> or or PIN…<\/strong><\/p>\n\n\n\n

                  <\/p>\n\n\n\n

                  In other organizations, the PAD may hide the second handwritten approval area and let the system handle the supervisor PIN flow after the pilot in command signs and saves. If that is how your setup works, do not be surprised if the page only shows the pilot block even though a second approval exists in the workflow.<\/p>\n\n\n\n

                  The reason for this design is operational control. A PIN approval is treated differently from a handwritten signature, so the interface adapts to the organization rule instead of forcing one method everywhere.<\/p>\n\n\n\n

                  Saving The Acknowledgement<\/strong><\/h2>\n\n\n\n

                  When the page is ready, tap Agree and Register<\/strong>.<\/p>\n\n\n\n

                  <\/p>\n\n\n\n

                  What happens next depends on the record:<\/p>\n\n\n\n

                    \n
                  • the PAD saves the handwritten signature you entered<\/li>\n\n\n\n
                  • the PAD keeps any already-saved signature or PIN approval visible in the record<\/li>\n\n\n\n
                  • a supervisor PIN request may continue through the organization workflow when that rule is active<\/li>\n\n\n\n
                  • the waiting list may refresh automatically after the record no longer needs PAD action<\/li>\n<\/ul>\n\n\n\n

                    Why the save step matters: the signature box alone is not the final action. Drawing in the box prepares the approval. Agree and Register<\/strong> is the step that actually sends it into the live workflow.<\/p>\n\n\n\n

                    What If You Try To Save With Nothing Entered?<\/strong><\/h2>\n\n\n\n

                    On screens where the PAD is expecting a direct signature entry, leaving every approval blank can trigger the message:<\/p>\n\n\n

                    \n\n\n

                    ERR05-At least one signature is required.<\/p>\n\n\n<\/div>\n\n\n

                    <\/p>\n\n\n\n

                    That rule exists to prevent accidental empty submissions, such as tapping the save button before anyone has actually signed.<\/p>\n\n\n\n

                    Back Buttons And Navigation<\/strong><\/h2>\n\n\n\n

                    The Back<\/strong> buttons let you return to the previous step:<\/p>\n\n\n\n

                      \n
                    • from the agreement page back to the waiting list<\/li>\n\n\n\n
                    • from the alert page back to the agreement page<\/li>\n\n\n\n
                    • from the signature page back to the agreement page or waiting list, depending on how the item was opened<\/li>\n<\/ul>\n\n\n\n

                      Use Back when you realize you opened the wrong item or need to re-check something before approval. Back is a review action only. It does not save the acknowledgement by itself.<\/p>\n\n\n\n

                      Common Situations Users Should Understand<\/strong><\/h2>\n\n\n\n

                      The list is empty<\/h3>\n\n\n\n

                      If no items are waiting, the list simply remains empty. That usually means there is nothing on hold for PAD acknowledgement right now.<\/p>\n\n\n\n

                      The item disappears<\/h3>\n\n\n\n

                      Because the page is live, an item may disappear if another user or another process completes the required action first. Refresh the list and reopen only if the record is still waiting.<\/p>\n\n\n\n

                      The page says the device is not allowed<\/h3>\n\n\n\n

                      This means the tablet or phone is not registered as an authorized PAD. Use the connection step with a valid access code from flight records staff.<\/p>\n\n\n\n

                      The page shows a connection or server popup<\/h3>\n\n\n\n

                      The PAD relies on a live connection. If that connection drops, the page can show a connection or server error popup. In that case:<\/p>\n\n\n\n

                        \n
                      1. close the popup<\/li>\n\n\n\n
                      2. use Refresh<\/strong><\/li>\n\n\n\n
                      3. if needed, reload the page<\/li>\n\n\n\n
                      4. contact flight records staff if the problem continues<\/li>\n<\/ol>\n\n\n\n

                        <\/p>\n\n\n\n

                        Quick Review Before You Tap Agree and Register<\/strong><\/h2>\n\n\n\n

                        Before saving, make sure all of the following are true:<\/p>\n\n\n\n

                          \n
                        • you opened the correct record from the waiting list<\/li>\n\n\n\n
                        • the people shown on the PAD are the right people<\/li>\n\n\n\n
                        • the activity summary matches what is actually being acknowledged<\/li>\n\n\n\n
                        • any alert or open squawk information has been read<\/li>\n\n\n\n
                        • the required handwritten signature, selected supervisor, or PIN step has been completed for your setup<\/li>\n<\/ul>\n\n\n\n

                          That final review is the whole reason this page exists. The PAD is the last controlled pause before the record continues, so it is meant to combine speed with deliberate confirmation rather than silent background processing.<\/p>\n","protected":false},"featured_media":0,"parent":3971,"menu_order":0,"template":"","doc_tag":[],"_links":{"self":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/3976"}],"collection":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/types\/docs"}],"version-history":[{"count":5,"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/3976\/revisions"}],"predecessor-version":[{"id":4087,"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/3976\/revisions\/4087"}],"up":[{"embeddable":true,"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/3971"}],"next":[{"title":"The Ramp In PAD","link":"https:\/\/www.airsupervision.com\/wp-r\/docs\/general-knowledge\/ramp-out-in-pads\/the-ramp-in-pad\/","href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/3972"}],"wp:attachment":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/media?parent=3976"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/doc_tag?post=3976"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}