PflichtPilot FAQ

PflichtPilot is an evidence continuity system for recurring documentation-relevant duties. The focus is not task administration, but whether it remains provable over time what was performed, documented as proof, and archived.

PflichtPilot is developed in close alignment with real operational use cases. The early access phase allows companies to use the system in practice and contribute structured feedback while core documentation quality remains stable.

In audits or liability-related reviews, isolated files are rarely enough. Structured documentation keeps duty context, timing, and proof connected, which improves clarity over longer time periods. The core logic is described on How PflichtPilot works, and key terms are collected in the glossary.

PflichtPilot is not a to-do app. It does not organize personal task lists, but documentation-relevant duties with proof and archiving over time. The key point is not whether something was marked done, but whether it can later be presented as reliable evidence.

Typical examples include operator obligations, maintenance duties, recurring inspections, safety checks, and compliance-related records. You can see practical examples in duty documentation, inspection obligation documentation, and maintenance proof documentation.

For operators, companies, and service providers that need duty documentation to remain traceable over time, especially where audits, insurer requests, or internal reviews may occur.

Recurring duties are tracked as connected iterations. This keeps each cycle linked to the corresponding proof and makes long-term documentation continuity easier to demonstrate. Related examples are covered in inspection obligations and maintenance proof documentation.

Audit readiness comes from continuity, not from isolated files. Each recurring duty needs a clear link between due context, attached proof, and documented closure of that specific iteration. A practical baseline is an operator obligations checklist combined with structured maintenance documentation. PflichtPilot supports this chain so records remain understandable and defensible years later.

No. PflichtPilot is not a general task or productivity manager. It is designed for duty documentation that must remain traceable and presentable in audits, inspections, or liability-relevant reviews. Planning workflows can be handled in separate tools if needed.

PflichtPilot is not a calendar or reminder system. It structures due dates, archiving events, and duty progression so documentation-relevant processes remain traceable. The focus is proof, archiving, and chronological evidence chains — not personal reminder logic or calendar workflows.

In recurring duties, the current iteration is documented and then closed in a controlled way. The next iteration continues from that same duty chain. This preserves chronological continuity and avoids fragmented records over long periods.

Yes. The key is transparent labeling that an iteration was archived without proof. This does not hide evidence gaps; it makes them visible and traceable for later clarification.

Yes. Recurring schedules can be ended deliberately. The history remains available, but no further iteration is continued. This keeps active and closed duty chains clearly separated.

The principle is: Duty → Proof → Archive → Next iteration. Each recurring cycle remains connected to the previous one. Over time this creates a readable evidence chain instead of disconnected file collections.

Proof is supporting material linked to a specific duty iteration, for example a record, photo, PDF, or confirmation document. The critical part is not the file alone, but its clear assignment to the correct duty context and timeline.

Yes. Structured exports support clear presentation of duty history in audit and evidence scenarios. The practical benefit is chronological clarity instead of last-minute document reconstruction.

No. PflichtPilot supports documentation structure and traceability, but does not replace legal review or professional assessment.