# When a project is closed, move all its documents to an archive catalog

Set a project's status to Closed on one of its documents, and within minutes every document for that project moves to an archive catalog, each keeping its document type and field values. The same two rules work for employees who leave, expired contracts, closed cases, and any record with an ID and a status.

Product: content-central · Versions: 7.8+ · Audience: catalog-administrator · Time: 1 hour, plus a few minutes per document type · Last verified: 2026-10-30

Canonical: https://help.ademero.com/content-central/workflow/move-all-of-a-projects-documents-when-its-closed

**When you're done, setting Project Status to Closed on one of a project's documents moves every document for that project from your Projects catalog to your Closed Projects catalog within a few minutes, each keeping its own document type and field values.**

The example is a **Projects** catalog for active work and a **Closed Projects** catalog made as a copy of it. The same two rules move an employee's file when they leave, a contract's paperwork when it expires, or a case file when it's closed. The table near the end shows what to swap in.

```plan
scope: global
trigger: Content Field Values › Global-Field Value Updated in the System | Field: Project Status · Field Evaluation: Selected Field Value(s) · Closed
action: Content - Update Shared Fields by Key Field | Key Field: Project Number
rule: "Closed → mark all the project's documents", enabled
```

```plan
scope: global
trigger: Content Query › Content in a Catalog | Catalog: Projects · Query: by Field Value(s) · Field: Project Status · Closed · Process Interval: Every 5 Minutes
action: Content - Change Catalog | Catalog: Closed Projects
rule: "Closed in Projects → Closed Projects", enabled
```

## How the two rules work together

1. Someone sets **Project Status** to `Closed` on one of the project's documents.
2. Rule 1 finds every other document with the same **Project Number** and sets its **Project Status** to `Closed` too ([Update a field on every document that shares an ID](/content-central/workflow/update-a-field-on-every-related-document)).
3. Every five minutes, Rule 2 finds the documents in Projects whose **Project Status** is `Closed` and moves each one to Closed Projects ([Move documents to another catalog automatically](/content-central/workflow/move-documents-to-another-catalog-automatically)).

It takes two rules because the documents Rule 1 updates don't start any workflow of their own. A single "when the status changes, move it" rule would move only the one document someone edited. The scheduled Rule 2 picks up the rest. Each document leaves Projects once it's moved, so Rule 2's search stays small no matter how many projects you close.

## Before you start

- [ ] **Matching document types.** Every document type in Projects has a type with exactly the same name, and the same field names, in Closed Projects. Copying the catalog gives you this ([Duplicate a catalog](/content-central/administration/duplicate-a-catalog-or-workflow)). Recheck any type added or renamed since the copy.
- [ ] **A project number that matches exactly.** Every document for a project carries the same value in one field. `2026-014` and `26-014` are different values, so a document with the second one won't be found.
- [ ] **A test project.** Two or three documents of different types in Projects for a project that isn't real.

> **IMPORTANT:** Matching is by exact name and exact value. A document whose type has no same-named type in Closed Projects is skipped and stays in Projects, with no message on screen. Check both before you rely on the rules.

## Set up the two global fields

Both rules work only with **global fields**: fields defined once and shared by every document type that uses them.

1. Go to **Administration** > **Global Fields** and click **Add Field**. **Name:** `Project Status`. **Type:** `Text`. Turn on **Create drop-down from choices.**, enter `Active` and `Closed` under **Field Entry Choices**, one per line, and click **Create**.

2. Add a second global field the same way for the project number, without choices, unless you already have one.

3. In **Administration** > **Catalogs & Document Types**, select a document type and click **Fields**.
   - If the type already has a project number field, open it, turn on **Use Global Field**, and pick the project number field under **Global Field:**. Its existing values stay with it.
   - Otherwise click **Add Field**, turn on **Use Global Field**, and pick the project number field.
   
   Then add **Project Status** the same way.

4. Repeat step 3 for every document type in **both** catalogs.

> **NOTE:** Linking both catalogs' document types to the same global fields also guarantees the field *names* match, which is what lets the values carry over during the move.

## Build Rule 1: mark all the project's documents

1. Go to **Administration** > **Workflow**, click **Triggers**, then **New Trigger**.

2. **Type:** `Content Field Values` and `Global-Field Value Updated in the System`. **Trigger Name:** `Project Status changed to Closed`.

3. **Field:** `Project Status`. **Field Evaluation:** `Selected Field Value(s)`, then choose `Closed` under **Selected Choices:**.

4. Leave **User Evaluation:** at `All Users and Groups` and click **Save**.

5. Click **Actions**, then **New Action**. **Type:** `Content - Update Shared Fields by Key Field`. **Action Name:** `Mark all the project's documents`. **Key Field:** your project number field. Click **Save**.

6. Click **Rules**, then **New Rule**. **Rule Name:** `Closed → mark all the project's documents`. Leave **Enabled** checked. **Add Trigger:** `Project Status changed to Closed`. **Add Action:** `Mark all the project's documents`. Click **Apply**.

**What you should see:** the rule in the **Rules** list with its **Enabled** switch on.

## Build Rule 2: move them to Closed Projects

1. In **Administration** > **Workflow**, click **Triggers**, then **New Trigger**.

2. **Type:** `Content Query` and `Content in a Catalog`. **Trigger Name:** `Closed documents in Projects`.

3. **Catalog:** `Projects`. **Query:** `by Field Value(s)`. Leave **Return:** at `All Matching Content (Multiple Records)`.

4. **Field Evaluation:** `Selected Field Value(s)`. **Field:** `Project Status`, then choose `Closed` under **Selected Choices:**.

5. **Process Interval:** `Every 5 Minutes`. Leave **Reprocess Matching Records After:** at `1` `Days`. Click **Save**.

*[Screenshot: The Content in a Catalog trigger for Rule 2: Catalog set to Projects, Query by Field Value(s), the Project Status field with Closed selected, Process Interval Every 5 Minutes, and Reprocess Matching Records After 1 Days.]*

6. Click **Actions**, then **New Action**. **Type:** `Content - Change Catalog`. **Action Name:** `Move to Closed Projects`. **Catalog:** `Closed Projects`. Click **Save**.

7. Click **Rules**, then **New Rule**. **Rule Name:** `Closed in Projects → Closed Projects`. Leave **Enabled** checked. **Add Trigger:** `Closed documents in Projects`. **Add Action:** `Move to Closed Projects`. Click **Apply**.

**What you should see:** the trigger in the **Triggers** list with **Event** `Scheduled`, and the rule in the **Rules** list with its **Enabled** switch on.

## File them into the right folders

**Content - Change Catalog** files each document by the destination document type's [folder building](/content-central/administration/folder-and-file-building) pattern. Without one, the documents all land together in the catalog's base folder rather than in a folder per project.

To file each project into its own folder, for example `2026-014`, set this up on **each** document type in Closed Projects. Go to **Administration** > **Catalogs & Document Types**, select the document type, and click **Folder & File Building**:

1. Check **Enable Folder Building**.

2. Under **Folder Building Items**, set **Type:** to `Field`, pick your project number field, and click **Add Item**.

3. Fill in **Folder name when field is empty:** with something easy to find, like `Empty`, and click **Apply**.

> **IMPORTANT:** Folder names come from field values, so documents only land in existing folders when the folder names match the values. Check the **Example:** line against your existing folders. A different spelling makes a new folder beside the old one. Once folder building is on, editing a document's fields later can also move it to the folder its fields now point to.

## Test it

1. Open one of your test project's documents in Projects, change **Project Status** to `Closed`, and save. Change nothing else in the same save.

2. Wait up to five minutes, then look in Closed Projects.

3. Open **View History** on one of the moved documents.

**What you should see:** every test document in Closed Projects with its own document type and field values, nothing left for the test project in Projects, and a history line like `From Catalog [Projects], Document Type [Change Order] to Catalog [Closed Projects], Document Type [Change Order]`.

If a document stayed in Projects, its document type or its project number didn't match. If nothing moves at all, scheduled rules depend on the Workflow Service, so start with [A scheduled workflow didn't run](/content-central/workflow/scheduled-workflow-didnt-run).

## The same recipe for other records

Swap the names and keep everything else:

| Record | Status field and value | Key field | From → to |
| --- | --- | --- | --- |
| An employee who leaves | Employment Status: `Inactive` | Employee ID | Personnel → Separated Employees |
| A contract that ends | Contract Status: `Expired` | Contract Number | Contracts → Expired Contracts |
| A client who leaves | Account Status: `Closed` | Account Number | Clients → Former Clients |
| A case, claim, or matter | Case Status: `Closed` | Case Number | Open Cases → Closed Cases |
| A student who graduates | Enrollment Status: `Graduated` | Student ID | Students → Alumni |
| A lease that ends | Lease Status: `Ended` | Lease Number | Leases → Ended Leases |

## Things to know

| Situation | What happens |
| --- | --- |
| Only the document you edited moved | Either the other documents' project number doesn't match exactly, or Rule 2 moved the edited document before Rule 1 ran. If the numbers match, open the moved document in Closed Projects, set **Project Status** to `Active` and save, then set it to `Closed` and save. Rule 1 runs wherever the document is |
| A document's type has no same-named type in Closed Projects | It stays in Projects. After you add the missing type, it moves once the **Reprocess Matching Records After** time (1 day) has passed |
| A document is filed for the project after it's closed | It stays in Projects until its **Project Status** is set to `Closed` |
| Someone changes another global field in the same save | That value is copied to all of the project's documents too. Change only Project Status in that save |
| The project has documents in other catalogs that use Project Status | If their types also use the project number global field, they're set to Closed as well, but they don't move unless you build a Rule 2 for that catalog |
| Projects uses folder or file building | When Rule 1 updates a document, Projects' pattern is applied first, so it can be refiled or renamed in Projects before it moves |
| You check **View History** on a moved document | The move is normally recorded under an administrator account, because scheduled rules run as one |
| A moved document is set back to `Active` | Nothing moves back. Build the same pair of rules in the other direction if you need that |
| A field exists only in the source document's type | Its value isn't carried over. Matching document types avoid this |

## Variations

| Want this instead | Change this |
| --- | --- |
| Move documents out of more than one catalog | Add a Rule 2 for each catalog pair. Rule 1 already marks the project's documents wherever Project Status is used |
| React only when certain staff change the status | Rule 1 trigger: **User Evaluation:** `Selected Group(s)`, and pick the group |
| Check less often | Rule 2 trigger: **Process Interval:** `Every Hour` or `Every Day` |
| Move only one document at a time, as soon as it's marked | Skip Rule 1, and use a right-away trigger with **Content - Change Catalog** ([guide](/content-central/workflow/move-documents-to-another-catalog-automatically)) |

## Still stuck?

Contact support with the names of both rules, the name of one document that didn't move, and what its **View History** shows.

## What's next

- [Move documents to another catalog automatically](https://help.ademero.com/content-central/workflow/move-documents-to-another-catalog-automatically)
- [Update a field on every document that shares an ID](https://help.ademero.com/content-central/workflow/update-a-field-on-every-related-document)
- [Folder and file building](https://help.ademero.com/content-central/administration/folder-and-file-building)
