Squawk Workflow and Lifecycle

Overview

A squawk is only as useful as the process that follows it. A report filed and then forgotten is almost worse than no report at all — it creates a false sense that the issue is being handled when it is not. Centerline's squawk system is designed to make sure every reported issue stays visible until someone with the authority to close it does so deliberately. Nothing silently disappears.

The squawk lifecycle is intentionally simple: a squawk is either OPEN or CLOSED. This two-state model reflects a clear accountability principle — an issue is either unresolved and demanding attention, or it has been reviewed and formally resolved by someone qualified to make that call. There is no ambiguous middle ground where an issue can quietly fade from view. Every squawk that gets filed stays in the OPEN state until a person with maintenance authority explicitly closes it, records what was done to resolve it, and takes responsibility for that determination.

One refinement exists within the open state: an open squawk can be flagged as Monitoring. A monitoring squawk is still open and still visible everywhere — it is an informational observation the club wants pilots to keep an eye on, rather than a defect demanding a repair. Monitoring is described in its own section below.

This structure prevents the most common failure mode in informal maintenance tracking, which is items that fall through the cracks — reported once, never quite resolved, and not visible enough to create urgency. In Centerline, an open squawk on a grounding issue will remain amber and prominent in the list every single day until it is closed. That visibility is intentional.

The Two Statuses

OPEN

Every squawk starts as OPEN the moment it is filed. OPEN means the issue has been reported and has not been formally resolved. It makes no claim about whether maintenance has looked at it, whether a repair has been scheduled, or how serious the issue is — those details live in the maintenance comments. OPEN simply means: this item is not done.

Open squawks appear with an amber badge. On the squawk list, they sort above closed squawks. Grounding squawks within the open group sort to the very top, because they have the most immediate impact on flight operations.

CLOSED

CLOSED means a person with maintenance authority has reviewed the squawk, taken whatever action was warranted, recorded a resolution describing what was done, and formally resolved the item. Closing a squawk is a deliberate act of accountability — it is not something that happens automatically or by the passage of time.

Closed squawks are hidden by default on the squawk list. They remain permanently in the system and can be viewed at any time by enabling Show closed squawks. The full original report, any attachments, the maintenance comments, and the recorded resolution are all preserved.

The Monitoring Flag

Some squawks are not really defects — they are observations. Oil consumption that is slightly elevated but within limits. A vibration a pilot noticed once that maintenance wants other pilots to watch for. An instrument reading that is being tracked across flights before committing to a repair. Closing these would hide them from the pilots whose feedback is wanted; leaving them as ordinary open squawks makes the maintenance backlog look worse than it is.

The Monitoring checkbox in the edit-squawk dialog handles this case. When maintenance marks an open squawk as Monitoring:

• The squawk stays fully visible — in the squawk list, on the member dashboard's fleet status, everywhere an open squawk appears — with a blue MONITORING badge in place of the amber OPEN badge.
• It stops counting as an open squawk in the executive summary, and it is excluded from the Squawk Cycle Time report entirely. Monitoring items are often long-running by design, and including them would distort the club's days-to-close metrics.
• It can be closed at any time through the normal close workflow, or taken back off monitoring by unchecking the box.

Use Monitoring for awareness items where pilot feedback is welcome. Do not use it to park real defects — a known problem that needs a repair should stay a plain open squawk, where the aging is visible and counted.

Who Can Close a Squawk

Only users with the Maintenance role or the Account Owner role can edit and close squawks. This is an intentional permission boundary. Closing a squawk is a maintenance determination — a statement that the aircraft is airworthy with respect to the reported issue. That decision should only be made by someone with the authority and qualifications to make it.

Any member can file a squawk. Only maintenance-authorized personnel can resolve one.

The Resolution Process

When maintenance personnel work a squawk, the typical flow looks like this:

1. Review the squawk — Open the squawk detail to read the full description, look at any photos or attachments, and understand what the pilot reported.

2. Investigate — Inspect the aircraft, reproduce the issue if possible, and determine the cause and appropriate action.

3. Take action — Perform the repair, make a logbook entry, or make a documented determination (for example, inspected and found within limits, or deferred in accordance with MEL/club policy).

4. Keep the record current while you work — Click the pencil icon to open the edit dialog and use the Maintenance Comments field for interim notes ("awaiting part, ETA Thursday"). These notes are visible to all club members.

5. Close the squawk — In the edit dialog, click the Close Squawk button next to the Update button. A dialog appears asking what was done to resolve this squawk. This resolution is required — a squawk cannot be closed without one. Write a real answer: what you found, what you did, and why the aircraft is airworthy. Click Close Squawk to confirm. The squawk moves to CLOSED status and is removed from the default view.

6. Notifications go out — When a squawk is closed, members who have access to that aircraft and have not muted squawk notifications receive an automatic notification that the issue has been resolved — and the notification email includes your resolution text, so pilots see not just that it was fixed but how.

The resolution is displayed permanently in the squawk's detail view under Resolution, alongside the original description and any maintenance comments.

Reopening a Squawk

If a closed squawk turns out not to be resolved — the symptom returns, or the fix didn't hold — a maintenance-authorized user can reopen it. Open the squawk's edit dialog; where the Close Squawk button normally sits, a closed squawk shows a Reopen button instead. Reopening returns the squawk to OPEN status and it re-enters the default list view.

The previous resolution text is kept for history, so the record shows what was tried the first time. When the squawk is eventually closed again, the new resolution replaces the old one — consider summarizing the history in the maintenance comments if the paper trail matters.

Reopening an existing squawk is usually better than filing a fresh duplicate: it keeps the full history of the issue — original report, attachments, comments, and prior resolution — in one place.

Grounding Squawks and Airworthiness

When a pilot checks Recommend Grounding on a squawk, they are flagging that in their judgment the aircraft should not fly until the issue is reviewed. This is an advisory from the reporting pilot — it is not an automatic system lockout — but it carries real weight and should be treated seriously.

A grounding squawk that is still OPEN means:

• The issue has not been reviewed and resolved by maintenance
• The aircraft should not be dispatched until that review happens
• Anyone viewing the aircraft's squawks will see the red Recommend Grounding badge prominently displayed

When maintenance reviews a grounding squawk, there are two appropriate outcomes. First, they can repair the issue, remove the grounding recommendation if appropriate, and close the squawk with a resolution documenting the repair. Second, if they determine the aircraft is actually airworthy (for example, the reported symptom was within acceptable limits), the resolution they enter when closing should state that determination clearly so that pilots have a record of the decision.

Because the close workflow requires a resolution, a grounding squawk can no longer be closed silently — but a resolution that says "done" is barely better. If another pilot later asks why a previously grounding squawk was closed, the resolution should give them a clear answer.

Maintenance Comments and the Resolution

Squawks carry two kinds of maintenance-authored text, with different jobs:

• Maintenance Comments (labeled Comments in the edit dialog) are the running update channel while a squawk is open — what has been found so far, what is on order, what the plan is. They can be updated at any time.
• The Resolution is entered once, at closing time, through the Close Squawk dialog. It answers: what was done, and why is this item resolved?

Good maintenance comments keep the club informed during the work; a good resolution is the permanent record of how it ended. Both are visible to all organization members in the squawk detail view. Detailed entries in both are a mark of professional maintenance practice and build trust throughout the club.

Editing a Squawk

Maintenance-authorized users can edit any field on an existing squawk. This includes:

• Correcting the occurrence date if it was entered incorrectly
• Updating or clarifying the description
• Adding or removing the grounding recommendation
• Setting or clearing the Monitoring flag
• Updating the maintenance comments
• Adding new attachments (photos of the completed repair, for example)
• Removing outdated or incorrect attachments

Editing a squawk never changes its open/closed status — that only happens through the explicit Close Squawk and Reopen buttons. The ability to edit is not an invitation to rewrite history; it exists to let maintenance keep the record accurate and complete as more information comes in.

Deleting a Squawk

Users with the Maintenance role or Account Owner role can delete a squawk entirely using the trash icon in the edit dialog. Deletion is permanent and should be reserved for cases where a squawk was filed in error — for example, a duplicate report or a test entry. Squawks that represent real issues, even already-resolved ones, should be closed rather than deleted so that the history is preserved.

Tips

• Close squawks promptly after resolution. An open squawk that has already been fixed but not yet closed creates confusion. Other pilots see it and do not know whether it is still a live issue. Close it as soon as the work is done.
• Write resolutions for the next pilot, not for the form. The dialog will not let you close without a resolution, but "fixed" satisfies the form and helps nobody. "Replaced pilot-side intercom cable, verified no static on ground test" takes ten more seconds and answers every future question.
• Use comments during the work, not just at the end. Adding a note like "Awaiting part, estimated completion Thursday" keeps the club informed and reduces the number of people calling to ask about the status.
• Grounding squawks need explicit resolutions. Do not close a grounding squawk without a resolution that explains why the aircraft is now airworthy. That text is the record that justifies the airworthiness determination.
• Use Monitoring instead of letting observations age as defects. If an item is informational and you want pilot feedback, flag it Monitoring — it stays visible without inflating the open-squawk metrics your club's reports track.
• Closed does not mean forgotten. Enable Show closed squawks periodically to review resolution history, look for recurring issues on the same aircraft, or verify that a previously reported problem stayed fixed.