Review AMP Diff

Open a parsed AMP revision, understand the diff panel, read change summaries, and inspect individual task differences before approval.

Module: Tech Library · 6 steps · camo_engineer admin

Open a Revision
1 Navigate to the Revision

Go to Tech Library → AMP. In the revisions list, find a revision with status PARSED or PENDING_APPROVAL and click the row.

The detail page opens at /tech-library/amp/{id}. The diff panel is visible only for revisions in PARSED or PENDING_APPROVAL status.

The first time anyone views a PARSED revision, the system automatically generates the diff and transitions the status to PENDING_APPROVAL.
AMP revision info card with status badge and View PDF link
2 Read the Info Card

The info card at the top displays key metadata:

FieldDescription
Revision NoThe revision identifier.
ModelAircraft model this AMP applies to.
Effective DateWhen the revision takes effect.
StatusCurrent status badge (colour-coded).
Tasks ExtractedNumber of tasks the parser found in the PDF.
PDF File“View PDF” link — opens the uploaded document in a new tab.
UploadedDate and time the revision was uploaded.
RemarksOptional notes from the uploader.
Understand the Diff Panel
3 Read the Summary Badges

At the top-right of the diff panel, four summary badges show the number of tasks in each category:

  • New — tasks in the AMP that do not exist in the current task card database.
  • Changed — tasks that exist in both, but with differences in interval, description, or type.
  • Removed — tasks in the database that are no longer in this AMP revision.
  • Unchanged — tasks that match exactly between the AMP and the database.

Use these counts for a quick assessment of how many changes the new revision introduces.

Diff panel with summary badges showing New, Changed, Removed, Unchanged counts
4 Inspect the Diff Table

The diff table lists every task with these columns:

ColumnContent
Task NoThe task identifier from the AMP (monospace, bold).
ATA ChATA chapter number (monospace).
DescriptionTask description. Changed tasks show the old value with strikethrough.
HoursInterval in flight hours. Changed values show old with strikethrough.
CyclesInterval in landing cycles.
DaysInterval in calendar days.
TypeTask type (e.g. routine, non-routine).
StatusColour-coded badge: New (green), Changed (amber), Removed (red), Unchanged (transparent).

Each row is colour-tinted to match its status — green background for new, amber for changed, red for removed, and transparent for unchanged.

Admin users see an additional checkbox column on the left. This is used to select items for approval. Non-admin users see a read-only diff.
5 Understand Change Types

Each diff item falls into one of four categories:

TypeWhat It MeansOn Approval
New Task exists in the uploaded AMP but not in the task card database. A new task card is created with the AMP’s values.
Changed Task exists in both, but intervals, description, or type differ. The existing task card is updated with the AMP’s new values.
Removed Task exists in the database but is missing from this AMP revision. The existing task card is deactivated (soft-deleted).
Unchanged Task matches exactly — no action needed. No change.
Only New, Changed, and Removed items are “actionable”. Unchanged items are shown for reference only and cannot be selected for approval.
6 Review Extracted Tasks & Raw Text

Below the diff panel, two additional sections help verify parsing quality:

SectionContent
Extracted Tasks A full table of every task parsed from the PDF: Task No, ATA Ch, Description, Hours, Cycles, Days, Type. Use this to spot-check the parser output.
Raw Extracted Text Collapsible section showing the verbatim text extracted from the PDF. Click the summary to expand. Useful for debugging when tasks are not parsed correctly.

If the extracted tasks table is empty, the PDF may contain scanned images instead of selectable text. Re-upload a text-based PDF for accurate parsing.

Extracted tasks table showing parsed maintenance tasks