# Bulk archive for completed projects

Draft for engineering. Fictional demonstration material.

## Problem

Project managers need to archive several completed projects at the end of an engagement. The current flow handles one project at a time. In eight observed sessions, archiving ten projects took a median of 2 minutes 20 seconds. Six participants asked for a bulk action.

## Proposed change

Add an Archive selected button to the existing project list. Users select up to 20 projects and confirm the action. This will streamline the workflow and make managing projects more seamless.

## Behaviour

- Enable the button when at least one project is selected.
- On confirmation, submit the selected IDs to the existing bulk archive endpoint. Disable the button while the request is in progress.
- When the request completes, show “Projects archived” and remove archived projects from the active list.
- If any projects fail, show a general error and keep the selection so the user can try again.
- If the request times out, show “Try again” and enable the button.
- The feature must work with a keyboard and announce the result to screen readers.

## Success

During the pilot, project managers should archive ten permitted projects in a median of 45 seconds or less. The interface should accurately report failures and never show a failed project as archived.

## Scope

Use the existing list selection and bulk endpoint. No deletion, bulk unarchive, undo, scheduling, permission changes or selection beyond the current page.

## Delivery

One frontend engineer will build the interaction. The backend engineer will confirm the endpoint behaviour. QA will test single and multiple selections, the loading state and error handling before a pilot with the eight participants.