How PflichtPilot works
PflichtPilot is a system for structured evidence continuity across recurring duties. It does not document tasks, but documentation chains: duty, proof, archiving, and next iteration. The focus is not reminders, but verifiable structure over time.
Visual guide: core principle
Duties in PflichtPilot are managed as traceable chains of iterations.
PflichtPilot – Core principle
Duties are managed as traceable iteration chains with evidence.
Duty
starting point of documentation
Iteration
concrete documented step
Add evidence
photo, document, report, email
Archive iteration
deliberate closure
Next iteration is created
for recurring duties via archiving
Duty lifecycle
A duty is created, then documented with proof, then archived. The next iteration is generated when the current one is archived, so chronology remains clear and traceable. For recurring maintenance cases, maintenance documentation is a typical use case.
Why no reminder logic
PflichtPilot is not a task or reminder application. It is structured around documentation chains: what was documented, when it was documented, and how proof and archiving connect across recurring cycles.
Why export matters
In audits, inspections, or liability reviews, structured output matters. Exported evidence packages make recurring documentation easier to present clearly.