Audit Type
State whether the audit is functional or physical, with date, program, configuration item, and audit team.
4.8
on G2
Free Aerospace & Defense Template
Report FCA or PCA results for [configuration item/system]
Use this template to report FCA or PCA results for [configuration item/system].
| Field | Details |
|---|---|
| Category | Aerospace & Defense |
| Owner | [Team or owner] |
| Version | [Version number] |
| Effective Date | [Date] |
| Review Cycle | [Monthly / Quarterly / Annual / Event-based] |
| Status | [Draft / In Review / Approved] |
State whether the audit is functional or physical, with date, program, configuration item, and audit team.
| Item | Details | Owner | Status |
|---|---|---|---|
| [Item or requirement] | [Describe the relevant detail, evidence, or decision] | [Owner] | [Open / Complete] |
| [Item or requirement] | [Describe the relevant detail, evidence, or decision] | [Owner] | [Open / Complete] |
[Add context, assumptions, exceptions, evidence links, screenshots, calculations, or reviewer comments.]
List specifications, drawings, software versions, parts lists, approved changes, and serial effectivity.
| Item | Details | Owner | Status |
|---|---|---|---|
| [Item or requirement] | [Describe the relevant detail, evidence, or decision] | [Owner] | [Open / Complete] |
| [Item or requirement] | [Describe the relevant detail, evidence, or decision] | [Owner] | [Open / Complete] |
[Add context, assumptions, exceptions, evidence links, screenshots, calculations, or reviewer comments.]
Summarize inspected hardware, test records, build records, software media, and acceptance data.
| Item | Details | Owner | Status |
|---|---|---|---|
| [Item or requirement] | [Describe the relevant detail, evidence, or decision] | [Owner] | [Open / Complete] |
| [Item or requirement] | [Describe the relevant detail, evidence, or decision] | [Owner] | [Open / Complete] |
[Add context, assumptions, exceptions, evidence links, screenshots, calculations, or reviewer comments.]
Identify discrepancies, missing records, unauthorized changes, or documentation gaps.
| Item | Details | Owner | Status |
|---|---|---|---|
| [Item or requirement] | [Describe the relevant detail, evidence, or decision] | [Owner] | [Open / Complete] |
| [Item or requirement] | [Describe the relevant detail, evidence, or decision] | [Owner] | [Open / Complete] |
[Add context, assumptions, exceptions, evidence links, screenshots, calculations, or reviewer comments.]
Provide owner, due date, closure evidence, and release impact for each action.
| Item | Details | Owner | Status |
|---|---|---|---|
| [Item or requirement] | [Describe the relevant detail, evidence, or decision] | [Owner] | [Open / Complete] |
| [Item or requirement] | [Describe the relevant detail, evidence, or decision] | [Owner] | [Open / Complete] |
[Add context, assumptions, exceptions, evidence links, screenshots, calculations, or reviewer comments.]
State whether the item conforms to the approved baseline and exceptions.
| Item | Details | Owner | Status |
|---|---|---|---|
| [Item or requirement] | [Describe the relevant detail, evidence, or decision] | [Owner] | [Open / Complete] |
| [Item or requirement] | [Describe the relevant detail, evidence, or decision] | [Owner] | [Open / Complete] |
[Add context, assumptions, exceptions, evidence links, screenshots, calculations, or reviewer comments.]
Recommend release, conditional release, re-audit, or hold. Use configuration management terms and maintain traceability to the baseline.
| Item | Details | Owner | Status |
|---|---|---|---|
| [Item or requirement] | [Describe the relevant detail, evidence, or decision] | [Owner] | [Open / Complete] |
| [Item or requirement] | [Describe the relevant detail, evidence, or decision] | [Owner] | [Open / Complete] |
[Add context, assumptions, exceptions, evidence links, screenshots, calculations, or reviewer comments.]
Template Structure
Use this aerospace & defense template as a starting point, then customize each section to match your internal workflow, evidence, and signoff needs.
State whether the audit is functional or physical, with date, program, configuration item, and audit team.
List specifications, drawings, software versions, parts lists, approved changes, and serial effectivity.
Summarize inspected hardware, test records, build records, software media, and acceptance data.
Identify discrepancies, missing records, unauthorized changes, or documentation gaps.
Provide owner, due date, closure evidence, and release impact for each action.
State whether the item conforms to the approved baseline and exceptions.
Recommend release, conditional release, re-audit, or hold. Use configuration management terms and maintain traceability to the baseline.
Write an aerospace configuration audit report. Structure with these Markdown sections:
State whether the audit is functional or physical, with date, program, configuration item, and audit team.
List specifications, drawings, software versions, parts lists, approved changes, and serial effectivity.
Summarize inspected hardware, test records, build records, software media, and acceptance data.
Identify discrepancies, missing records, unauthorized changes, or documentation gaps.
Provide owner, due date, closure evidence, and release impact for each action.
State whether the item conforms to the approved baseline and exceptions.
Recommend release, conditional release, re-audit, or hold.
Use configuration management terms and maintain traceability to the baseline.
Physical Configuration Audit for Mission Computer MC-3, serial MC3-026, conducted 2026-05-04.
| Finding | Requirement | Release Impact |
|---|---|---|
| Label format uses Rev H template | SPEC-LBL-04 | Conditional |
Hardware conforms to baseline except label template correction.
Conditional release after label replacement and photo evidence upload.
Record a walkthrough, training session, or process demonstration. Docsie AI turns it into structured documentation using this template as the starting framework.
Use the template manually, or let Docsie generate the first draft from source footage.
Define final acceptance testing for [flight hardware/subsystem]
Prepare compliance response for [airworthiness directive/service bulletin]
Control baselines, changes, and traceability for [program/system]
Propose technical, cost, schedule, and risk impacts for [aerospace/defense change]
Assess export control requirements for [technical data/item/transaction]
Document failure investigation and corrective action for [test/field failure]
Template FAQ
Common questions about using and generating a configuration Audit Report.
Q: What is a configuration Audit Report?
A: A configuration Audit Report is a structured document for report fca or pca results for [configuration item/system].
Q: Can I download this configuration Audit Report as Word or PDF?
A: Yes. This page includes free downloads in DOCX, PDF, and Markdown formats so you can edit, share, or import the template into your documentation system.
Q: Can Docsie generate this from a video?
A: Yes. Upload a process walkthrough, training recording, or screen capture to Docsie, then use this template structure to generate a first draft automatically.