Feature
Every resolution becomes a verifiable document
A resolution is only worth something if you can still prove it two years later – to the general meeting, the auditor or a new board. Beschlussmanager produces that proof itself.
What the PDF contains
- The motion in the wording that was voted on
- Committee, organisation and the voting rule with its quorum
- The eligible voters and every vote cast, with timestamps
- The outcome, stated separately for majority and quorum
- The start and end of the voting period
- The SHA-256 checksum over the generated document
The PDF is generated on the server from stored data, not from an editable document. It is not written by hand and therefore cannot drift from what happened.
What the checksum does and does not do
A SHA-256 hash is taken over every generated PDF: a string that changes completely as soon as a single byte of the content changes.
It can show: this file is exactly the one Beschlussmanager produced at the time. It has not been altered since.
It cannot show: that a particular person signed. That requires a qualified electronic signature under eIDAS. We therefore never call the checksum a “signature” or the resolution “court-proof” – we could not keep those promises.
Verify it yourself
shasum -a 256 resolution.pdf
On Windows: certutil -hashfile resolution.pdf SHA256.
The value must match the one recorded in Beschlussmanager.
Audit trail
Appended, never overwritten
Alongside the PDF runs a log that records every step: creating, editing, opening, each vote, each comment, each email sent, closing – with a timestamp and the person acting.
Entries are only ever added. There is no function to change or remove an entry, not even for the organisation's administrators.
What it is not: a certification under German GoBD rules. We call it a complete audit trail and not “audit-proof”, because that term carries specific further requirements.
From the application
The record as it comes out
A document that stays readable without Beschlussmanager: motion, rule, outcome, every vote and the audit trail.
Common questions
Is this an electronic signature?
No. A SHA-256 checksum is a fingerprint of the document content: change a single character and the checksum changes. It therefore shows integrity. A qualified electronic signature under eIDAS also attests the identity of the signatory – a checksum does not do that, and we do not claim it does.
How do I verify the checksum myself?
With any standard tool. On macOS and Linux: shasum -a 256 resolution.pdf. On Windows: certutil -hashfile resolution.pdf SHA256. If the value matches the one recorded in Beschlussmanager, the file is unchanged.
What is in the audit trail?
Who created, changed, opened and closed the resolution, every vote cast, every comment and every notification sent – each with a timestamp. Entries are appended, never overwritten or deleted.
Can we archive the PDF ourselves?
Yes, and we recommend it. The PDF can be downloaded at any time and filed in your own resolution book, so you do not depend on Beschlussmanager still being around in ten years.
Ready for the first resolution?
We set up your organisation and get back to you within one working day. No payment details, no contract as a first step.