> For the complete documentation index, see [llms.txt](https://help.brieftech.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brieftech.ai/how-to-guides/bundle/prepare-records-of-appeal-bundle.md).

# Prepare Records of Appeal for the Singapore & Malaysian Courts

Take a matter from upload to a filing-ready Record of Appeal for the Singapore or Malaysian courts, split into volumes and paginated per volume.

First, sort your documents into **one folder per volume** — I, II, III or IV for Singapore; **Part / Bahagian** A, B, C or D for Malaysia — on your computer **before** you upload. That folder structure sets how the index and the finished bundle are grouped.

## Step 1 — Create the matter

*On the **Matters** screen.*

1. Click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-f8cf6402521f2ea220af941844d9bda08c7ab3ad%2Fbtn-create-new-matter.svg?alt=media" alt="Create New Matter" data-size="line"> in the top-right corner, then enter the matter details. The new matter opens on the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-30913153ebd9cc9194606c644922feb649ae10a5%2Ftab-files.svg?alt=media" alt="Files tab" data-size="line"> tab.

## Step 2 — Upload and check the documents

*In the* <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-30913153ebd9cc9194606c644922feb649ae10a5%2Ftab-files.svg?alt=media" alt="Files tab" data-size="line"> *tab.*

1. Drag your volume/Part folders into the upload zone. <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-8fb0db73f10e5ba0926bea47de89141576f6bf4f%2Fbtn-select-files.svg?alt=media" alt="Select files" data-size="line"> picks individual files only; once the matter has documents, **Upload → Upload Folder** is also available. See [Upload documents](/how-to-guides/upload/upload-documents.md).
2. Check the file list for error or warning icons, and hover an icon to read its message. See [Document processing and errors](/reference/document-processing-and-errors.md).
3. If a document's text is wrong or garbled — usually because it arrived with its own low-quality text that BriefTech kept (**Skipped Text**) — right-click and choose <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-ab33defb36f835e4c16641923c72f5798a3ce962%2Fbtn-force-ocr.svg?alt=media" alt="Force OCR" data-size="line"> to re-read every page from scratch. The option appears only when *every* selected document is eligible, so clear a mixed selection first.
4. If a document shows a processing error, right-click and choose <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-d0e6b89a4a252f16acc7ad2ee31373e54f789ddd%2Fbtn-reprocess-selection.svg?alt=media" alt="Re-process Selection" data-size="line">. A persistent error usually means the file is corrupt or unsupported — contact BriefTech support. An error document still takes one page in the bundle, so move it to the Bin (tick it, bin icon) before you go on; it stays recoverable there. See [Reprocess a failed document](/how-to-guides/process/reprocess-failed-document.md).

## Step 3 — Review and edit the index fields

*In the* <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-8f18f06a78c4d0bf6e51eac54ec7d3e5d2cdb8a2%2Ftab-review.svg?alt=media" alt="Review tab" data-size="line"> *tab.*

1. Switch to the Review tab and wait for the **Document Description** and **Document Date** to be generated automatically. A spinner shows a document is still being processed. See [Document metadata fields](/reference/document-metadata-fields.md).
2. Double-click the **Document Date** field to type a date, or to pick one BriefTech found in the document (the list appears only when a document yielded more than one). Press Enter to confirm.
3. Double-click the **Document Description** field to edit it. Press Enter to confirm. An edited field turns blue.

## Step 4 — Refine descriptions

*In the* <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-8f18f06a78c4d0bf6e51eac54ec7d3e5d2cdb8a2%2Ftab-review.svg?alt=media" alt="Review tab" data-size="line"> *tab.*

To bring multiple descriptions into a consistent style in one go, use <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-7ca852ba9ed8e5cd335486f6f5aafe2a31996043%2Fbtn-refine-descriptions.svg?alt=media" alt="Refine Descriptions" data-size="line"> above the **Original File Name** column. See [Refine descriptions using your own edits as examples](/how-to-guides/review/refine-descriptions-from-examples.md).

1. Manually edit at least one description into the style you want — two or three consistent examples give BriefTech more to work from. Edited descriptions turn blue and become your reference rows.
2. Tick your reference rows together with the remaining documents you want to follow that style. The button stays greyed out until your selection holds both at least one edited row and at least one un-edited row.
3. Click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-7ca852ba9ed8e5cd335486f6f5aafe2a31996043%2Fbtn-refine-descriptions.svg?alt=media" alt="Refine Descriptions" data-size="line">.

## Step 5 — Translate a description (optional)

*In the* <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-8f18f06a78c4d0bf6e51eac54ec7d3e5d2cdb8a2%2Ftab-review.svg?alt=media" alt="Review tab" data-size="line"> *tab.*

To translate one or more Document Descriptions into another language:

1. Tick the checkbox on each document whose description you want to translate.
2. Open the **Tools** menu in the toolbar and choose <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-20cca8ba1ddb37b74ff6547b14b9cf50d7e7cb95%2Fbtn-translate-description.svg?alt=media" alt="Translate description…" data-size="line">.
3. Pick a language and confirm.

To translate a single row, hover its **Document Description** cell and click the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-17c9d403849250e5f95b2b7fa28c719dd8d2ba70%2Ficon-translate.svg?alt=media" alt="translate" data-size="line"> icon. If the language you need isn't listed, contact BriefTech support. See [Translate document descriptions](/how-to-guides/review/translate-document-descriptions.md).

## Step 6 — Use the file name as the description (optional)

*In the* <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-8f18f06a78c4d0bf6e51eac54ec7d3e5d2cdb8a2%2Ftab-review.svg?alt=media" alt="Review tab" data-size="line"> *tab.*

To use a document's file name as its Document Description, hover the **Document Description** cell and click the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-a23ba3c3cf3b8904c67137563291fac7395f3893%2Fbtn-use-filename-as-description.svg?alt=media" alt="Use file name as description" data-size="line"> icon.

To revert, double-click the cell to edit or click Regenerate.

## Step 7 — Verify edits against the source document

*In the* <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-8f18f06a78c4d0bf6e51eac54ec7d3e5d2cdb8a2%2Ftab-review.svg?alt=media" alt="Review tab" data-size="line"> *tab.*

1. Click anywhere on the row to open a side-panel view of the document without leaving the Review tab.
2. A large document opens with a **Click to preview** overlay — click it to load.
3. Drag the splitter to widen the pane, or collapse it with the chevron.

See [The preview pane](/reference/preview-pane.md).

## Step 8 — Add or remove documents

*In the* <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-8f18f06a78c4d0bf6e51eac54ec7d3e5d2cdb8a2%2Ftab-review.svg?alt=media" alt="Review tab" data-size="line"> */* <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-30913153ebd9cc9194606c644922feb649ae10a5%2Ftab-files.svg?alt=media" alt="Files tab" data-size="line"> *tab.*

* **Remove** — tick the checkbox next to a row, then click the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-1be3df96ec310ea3302e70fd81129f7dcb9378ef%2Fbtn-move-to-bin.svg?alt=media" alt="Move to bin" data-size="line"> bin icon in the toolbar (hovering shows **Move (N) to bin**), and confirm. Documents in the Bin stay recoverable until you delete them from there.
* **Add from the Review tab** — drag the new files onto the folder in the left-hand folder panel where they belong; the folder highlights as you drag over it, and dropping there adds them straight into that folder. (Dropping onto the document list instead adds them without assigning a folder.) The files are added and processed without affecting documents already processed.
* **Add from the Files tab** — return to the Files tab and drag the additional files or folders onto the file table, or use **Upload → Upload Folder**.
* **Find recent uploads** — sort by the **Uploaded** column using its header. See [Upload monitor](/reference/upload-monitor.md).

## Step 9 — Generate the index and split into volumes

*In the* <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-320692e120077fab01f6944df1edd4eec4881a4c%2Ftab-index.svg?alt=media" alt="Index tab" data-size="line"> *tab.*

1. Click the Index tab to see the generated index table.
2. Click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-b912cd1830c2b96fcb2e3a555cd9d809382cf685%2Fbtn-apply-preset.svg?alt=media" alt="Apply preset" data-size="line"> (top-right) → **Apply bundle/index preset**, then choose the preset for your court:

   |                      | Singapore                 | Malaysia               |
   | -------------------- | ------------------------- | ---------------------- |
   | **Preset**           | Record of Appeals (SG)    | Records of Appeal (MY) |
   | **Groups into**      | Volumes                   | Parts (Bahagian)       |
   | **Volume labels**    | Roman — I, II, III…       | Letters — A, B, C…     |
   | **Pages per volume** | 300                       | 200                    |
   | **Page stamp**       | `I RA 1` (Roman-prefixed) | bare `1, 2, 3`         |

   The preset sets your index columns, turns on **Senior Volumes**, and applies that jurisdiction's volume settings automatically. See [Document Index presets](/reference/index-presets.md).
3. To divide the index to match your folders, open <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-b912cd1830c2b96fcb2e3a555cd9d809382cf685%2Fbtn-apply-preset.svg?alt=media" alt="Apply preset" data-size="line"> again → **Generate index headings** → <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-ad0d339819047bc66b01be597a57c8ba2b51d2d7%2Fbtn-group-by-folder.svg?alt=media" alt="Group by folder" data-size="line">. BriefTech creates a heading per folder and labels each following the preset — *Index to Volume I / II / III* for Singapore, *Index to Volume A / B / C* for Malaysia. (For Malaysia, BriefTech labels each Part as a **Volume** — *Volume A* is *Part A*.)
4. Check the order before you go on. BriefTech keeps neither your folder order nor your file order: documents inside each heading are re-sorted by document date, then file name. If a volume/Part must follow a different order, drag the rows into place — see [Reorder documents and add structure](/how-to-guides/index/reorder-documents-add-structure.md) and [Manage headings in the Document Index](/how-to-guides/index/manage-index-headings.md).
5. Switch the mode toggle to <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-6fa665239290710351c4bd5664b5462cc2c59fea%2Fchip-preview-mode.svg?alt=media" alt="Preview" data-size="line"> to see the index as it will appear in the finished bundle, with volume splits applied. Switch back to <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-6646858009b6553c36fb5e1b7dbb8255e69ea8b2%2Fchip-edit-mode.svg?alt=media" alt="Edit" data-size="line"> to make further changes.

**Add a sub-index (optional).** If a document in your Record of Appeal is itself a bundle — an affidavit with exhibits, or a Bundle of Documents — you can add a sub-index so the main index shows what's inside it. Hover the document's row, then click the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-6e7d4ebfce7a47a504d3408172583f987a93bd78%2Ficon-description.svg?alt=media" alt="Edit subindex" data-size="line"> icon on its **Description** cell to open the **Edit Subindex** dialog, where you can generate the entries from the PDF or add them by hand. See [Add or edit sub-index entries](/how-to-guides/index/add-edit-sub-index-entries.md).

## Step 10 — Add the cover page and volume settings

*In the right-hand **Create Bundle** panel of the* <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-320692e120077fab01f6944df1edd4eec4881a4c%2Ftab-index.svg?alt=media" alt="Index tab" data-size="line"> *tab.*

1. Click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-18aade7469e7cdfedfa27099287f4625db64a04b%2Fbtn-create-bundle-toolbar.svg?alt=media" alt="Create Bundle" data-size="line"> in the Index toolbar to open the bundle panel on the right. Its sections start collapsed and behave as an accordion; expand each as you reach it.
2. Prepare a cover page template as a DOCX file, using the variables from the Taxonomy & Syntax Guide where required — see [Template syntax](/reference/template-syntax.md).
3. Expand **Cover Page**, then under **Cover Page Template** click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-aace63e532b017fb1bef72685458cc008cf1508f%2Fbtn-upload-template.svg?alt=media" alt="Upload" data-size="line"> and select your template file. (If a template is already set, the button reads **Replace**.)
4. Set the number of blank pages to insert before the index in each volume, if required for your filing.
5. Expand **Volumes Settings**. **Max Pages Per Volume** is already set by the preset you applied in Step 9; change it only if your filing requires a different limit. See [Document Index presets](/reference/index-presets.md).
6. Use **Volume Split Strategy** and, when set to **Auto (smart split)**, **Auto Split Threshold (pages)** to control where a document that would straddle a boundary is pushed to the next sub-volume rather than split mid-document. See [Court bundle settings](/reference/court-bundle-settings.md) and [Split a bundle into volumes](/how-to-guides/index/split-into-volumes.md).
7. If required for filing, set **Scaling mode** to **Normalize to A4 by orientation** so non-A4 pages are resized. (Leave it on **Keep original page size** to keep pages as they are.)
8. Expand **Pagination**. The preset already applies your jurisdiction's page stamp, with numbering restarting at 1 in each volume.
   * **Stamp page numbers on** lists the page types that carry a stamp. Remove any one to leave that section unstamped — those pages are still counted.
   * Adjust the font size, colour and position of the stamps if your filing requires it.

## Step 11 — Create and download the bundle

*In the* <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-320692e120077fab01f6944df1edd4eec4881a4c%2Ftab-index.svg?alt=media" alt="Index tab" data-size="line"> *tab.*

1. When you're done, click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-9b8d448dbc3a5f29cf3b425479c7ab574e9969ad%2Fbtn-create-bundle.svg?alt=media" alt="Create Bundle" data-size="line">. To build only some volumes, first fill in **Volumes to assemble** just above the button — e.g. `1,2,5-7`; leave it blank to build every volume. Up to three confirmations may follow — always in this order, and each only when it applies.
2. **Processing issues.** If a warning dialog lists documents with issues, click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-bbff6c32497cde9d3297b45db292f7a2bddd04d6%2Fbtn-cancel.svg?alt=media" alt="Cancel" data-size="line"> to fix them first, or **Create Bundle Anyway** to proceed. Each affected file becomes a one-page placeholder:
   * **Password-protected** — a stamped page naming the file. See [Unlock a password-protected file](/how-to-guides/process/unlock-password-protected-file.md).
   * **Too large to process, or no PDF produced** — a blank page. Blank placeholders are counted and paginated like any other page, so fix them before filing.
3. **Credits.** If any documents haven't been charged yet, you'll be asked to confirm the credit deduction; if they were all charged earlier — by Force OCR, say — no confirmation appears.
4. **Existing bundle files detected.** If this matter already has a generated bundle, BriefTech warns that a new one overwrites the previous results. Click **Proceed** to replace, or **Cancel** to keep them.
5. BriefTech starts building and opens a job-log window showing progress — you can close it; the bundle keeps building. A **Bundles created successfully** message appears when it finishes. See [Background Jobs](/reference/background-jobs.md).
6. Once generated, download the bundle under the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-9b8d448dbc3a5f29cf3b425479c7ab574e9969ad%2Fbtn-create-bundle.svg?alt=media" alt="Create Bundle" data-size="line"> button. BriefTech produces one PDF per volume and a **Complete Bundle (ZIP)** containing all of them. You can regenerate at any time after further edits. See [Regenerate a court bundle after making changes](/how-to-guides/bundle/regenerate-court-bundle.md).

Your Record of Appeal is now filing-ready: the volumes divided from your own folders, your jurisdiction's columns, page limits and stamp applied by the preset, cover pages in place, and a paginated PDF for each volume. **BriefTech builds the bundle from the way you organise your documents** — the folders you sorted at the start are what shaped everything downstream.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Prepare Your First Record of Appeal (Singapore)</strong></td><td>The guided tutorial, on a practice matter.</td><td><a href="/get-started/prepare-record-of-appeal-singapore.md">Prepare Your First Record of Appeal (Singapore)</a></td></tr><tr><td><strong>Document Index presets</strong></td><td>The authoritative Singapore (SG) and Malaysia (MY) preset settings.</td><td><a href="/reference/index-presets.md">Document Index presets</a></td></tr><tr><td><strong>Generate a paginated court bundle</strong></td><td>The generic paginated-bundle how-to.</td><td><a href="/how-to-guides/bundle/generate-paginated-bundle.md">Generate a paginated court bundle</a></td></tr><tr><td><strong>Court bundle settings</strong></td><td>The full set of bundle settings and their defaults.</td><td><a href="/reference/court-bundle-settings.md">Court bundle settings</a></td></tr><tr><td><strong>Template syntax</strong></td><td>All tokens for the cover page, page stamp, file name and volume header.</td><td><a href="/reference/template-syntax.md">Template syntax</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.brieftech.ai/how-to-guides/bundle/prepare-records-of-appeal-bundle.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
