Issues, defects and release

Follow an issue through to signed release.

KitNDocs keeps the first report, defects, work and release to service connected on the equipment record.

Issues

What was reported

Out of serviceHard landing check

Raised today. Open — nobody has closed it.

Close issueAdd a defectPoint this at a defect

Certificate of serviceability

What this certificate says

Released
Resolved defect and completed inspection
Deferred defects
Minor fabric scuff, permitted to a stated date
Open defects
Cosmetic note with no effect on service

The work

One concern can be followed from report to release.

The team can see what was raised, who checked it, what work was done, and what the certificate covers.

1

Raise the concern

Record what somebody saw, the day they saw it, photos if they help, and whether the equipment must not be used until it is checked.

2

Add a defect

A person records any defects the concern turns out to be. One report can become several, and each stays connected to it.

3

Do the work

The task records the repair, inspection or check. The concern remains visible beside the work it led to.

4

Close the issue

A person says the report is finished. The record says what it became, or that nothing notable was found, under their name and the day.

5

Sign the release

The certificate says what was released, what stays in service under a limit, and what remains open with no effect on service.

Example

A heavy landing starts as a concern.

The harness can be kept out of service while it is checked. If a defect is found, the work and later certificate show the path back to use.

Another outcome

A scuff can have a limit instead of a hard stop.

A defect can permit use until a stated date or reading. The certificate shows that limit beside the signed release.

How an issue ends

Each issue outcome stays on the record.

The first report stays separate from the repair. The closure says who finished it, on what day, and what it became.

It became a defect

The defect carries the current assessment, including whether the equipment stays out of service until work and certification are complete.

Nothing notable was found

The closure still shows that somebody checked and found nothing notable. If the issue stopped use, a certificate releases it.

The issue was raised in error

The error and its reason stay on the record.

Signed release

The signer can see what they are releasing.

Before signing, KitNDocs shows the relevant issues, completed tasks, resolved defects, deferred defects and open defects. The certificate records the signed release.

Released

Issues, tasks and defects this certificate clears.

Deferred defects

Defects that let the equipment stay in service, each to its recorded limit.

Open defects

Known defects that have no effect on service.

Where it stops

KitNDocs records the operator's decision.

  • KitNDocs records the closure a person made. It does not judge the equipment for them.
  • A photo helps the record. It is not the signed maintenance record by itself.
  • Closing a defect is not the same as releasing equipment to service.

Keep proof ready

Read the record on either side of the concern.

See the equipment logbook that holds the issue, then the evidence and certificate that record its outcome.