A repeatable board-pack lifecycle: prepare, release, update and close

Use this lifecycle as an operating example for one meeting or pack cycle, not as a universal governance timetable. Each organisation should apply its own constitution, policies, meeting calendar, legal obligations and professional advice.

Dossira Board Room currently supports organising prepared files and sharing them with registered members or controlled external recipients. It is not yet a complete board-management or board-record system.

1. Define the meeting and responsibilities

Start with a bounded meeting or pack cycle. Record the board or committee name, meeting date and the person responsible for distributing the current pack in the organisation’s established governance system.

Agree the operating responsibilities before files are shared:

• Board administrator or secretary: coordinates the timetable, organises the prepared material and manages access.
• Chair: confirms the organisation’s process for agenda and pack readiness.
• Executive contributor: provides prepared papers through the organisation’s agreed internal process.
• Director, observer or adviser: receives only the material appropriate to their participation.

These are professional responsibilities, not predefined Dossira permission levels. Board-specific Chair, Director, Secretary and Observer roles are not implemented. Use registered organisation members or controlled external shares according to the access that is actually supported.

2. Prepare the draft pack

Prepare and review draft papers in the organisation’s existing tools. Add material to the Board Room when it is ready for the participants who can access that room or share.

A simple operating structure might be:

• 01 Current board pack for the file participants should use;
• 02 Supporting papers for prepared appendices or separate papers intended for the same audience;
• 03 Previous releases for clearly named earlier files when the organisation needs to retain them in the room.

Do not assume that folders create different access levels. Granular agenda-section or per-document permissions for registered members are not implemented. If an external recipient should receive only a subset, create a separate deliberate share for that subset and use confirmed-email access when it should be tied to a named address.

3. Release the current pack

In this example, release means that the operator has clearly identified the prepared pack, provided the intended access and told participants that it is ready. Dossira does not currently provide a pack-release, publication or authoritative-version state.

Before sending the notification:

1. Confirm that 01 Current board pack contains the file participants should use.
2. Give the file a clear meeting date and version identifier.
3. Confirm the intended registered members or controlled external recipients.
4. Set an expiry when an external share should be time-limited.
5. Notify participants through the organisation’s normal communication channel.

The organisation should choose its own release timetable. For example, its board calendar may set a target number of days before the meeting, but that timing is an internal operating choice rather than a universal rule.

4. Issue a revised pack when necessary

If the pack changes, upload the revision with a clear filename and move or rename the earlier file so it cannot be mistaken for the current pack. Keep previous versions as separately named files or in the organisation’s established records system when retention is required.

Dossira does not yet present a complete or authoritative version chain and does not automatically notify participants that the pack has changed. State what changed, identify the current filename and notify participants through the normal communication channel. Direct them back to the controlled room or share instead of circulating another parallel email attachment.

Revoke and reissue a share if its recipient or scope must change. Revocation prevents future access through that share; it cannot retrieve a file already downloaded or copied.

5. Record decisions or acknowledgements in the established system

Dossira does not currently provide customer-facing comments, pack acknowledgements, approvals or decision records. Do not treat file access as confirmation that a director reviewed or accepted a particular version.

Use the organisation’s established governance process to record attendance, declarations, acknowledgements, minutes, resolutions and actions. If an authorised member later uploads an approved document produced by that process, describe it as a copy of the record created elsewhere—not as a decision or approval recorded by Dossira.

6. Close the meeting record

Complete the organisation’s formal meeting record in the system and procedure approved for that purpose. Users can download files available to them, but Dossira does not provide a room-closing state, a read-only sealed state or a complete export containing activity, acknowledgements and decisions.

As an operating checklist:

• confirm which pack and supporting papers belong in the organisation’s final record;
• download the available files that must be retained elsewhere;
• retain minutes, resolutions, acknowledgements and actions in the established governance system;
• expire or revoke external shares that should no longer provide future access;
• record any follow-up outside Dossira.

This process does not create a complete Dossira meeting-record export or establish that copies previously downloaded by participants no longer exist.

7. Prepare the next meeting

A built-in duplicate-meeting workflow, recurring Board Room template and room-specific creation defaults are not implemented in the current private preview. Do not rely on the product to copy the previous meeting into the next one.

Instead, keep the organisation’s approved folder convention, naming rules and operating checklist in its established procedure. Apply that convention manually when setting up the next meeting or pack cycle, adding only the participants and prepared material needed for that meeting.

Explore the Board Room

Explore the Board Room to review the current distribution workflow, participant model and capability boundaries before requesting early access.