> For the complete documentation index, see [llms.txt](https://pair.guides.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pair.guides.gov.sg/pair-staffer/pair-staffer-user-guide.md).

# Pair Staffer User Guide

### Overview

Pair Staffer manages your PQ workflow from start to finish. CC it on a PQ email and it will kick off a case in GatherSG, extract key details from the notice paper, send an AI-generated first draft to the thread, and keep the case updated as replies come in.

> **Access is currently limited to MDDI officers only.** Contact <support@pair.gov.sg> for more information.

***

### How it works

1. Parliament Admin sends the PQ email to the relevant team, CCing Pair Staffer
2. Pair Staffer creates a GatherSG case and extracts key details from the notice paper: MP name, PQ type (oral or written), date of sitting, notice paper number, and order number
3. Pair Staffer auto-replies to everyone with an AI-generated first draft and a link to the GatherSG case
4. Officer reviews the draft, edits as needed, and replies in the same thread while keeping Pair Staffer's unique case address in CC
5. Pair Staffer updates the GatherSG case as the thread progresses

***

### For Parliament Admin

#### Sending a PQ

When forwarding a PQ to your officer, add the following address to the **CC field**:

`staffer@work.pair.gov.sg`

#### What Pair Staffer sends back

<figure><img src="/files/qlQrs0e2IjBmJlcnfvdH" alt=""><figcaption></figcaption></figure>

Everyone on the thread receives an automatic reply including:

* A Word document containing the first draft response to the PQ
* A GatherSG case link and case reference number
* A Pair Assistant link to iterate on the draft in chat

#### Tracking progress in GatherSG

**Finding your case:**

* Click the GatherSG case link in Pair Staffer's auto-reply, or
* Log in to GatherSG and search by case reference number

**Case fields**

Pair Staffer automatically extracts the following from the notice paper when a case is created. Some fields need to be filled in manually.

| Field                    | How it's filled                         |
| ------------------------ | --------------------------------------- |
| MP name                  | Auto-extracted                          |
| PQ type (oral / written) | Auto-extracted                          |
| Date of sitting          | Auto-extracted                          |
| Notice paper number      | Auto-extracted                          |
| Order number             | Auto-extracted                          |
| Division                 | Auto-extracted                          |
| POC                      | Auto-extracted                          |
| Last received by         | Auto-extracted                          |
| POH fronting PQ          | Manual (Defaults to Min/MDDI)           |
| Case Status              | Manual (Defaults to Routed to Division) |

**Comments**

<figure><img src="/files/XcjSp5IYEQm4bReTuQpl" alt=""><figcaption></figcaption></figure>

The Comments tab shows a timestamped record of everything that has happened on the case.

***

### For Officers

#### What you'll receive

<figure><img src="/files/qlQrs0e2IjBmJlcnfvdH" alt=""><figcaption></figcaption></figure>

When a PQ is assigned to you, you'll get an email from Pair Staffer with:

* A Word document containing the first draft response to the PQ
* A GatherSG case link and case reference number
* A Pair Assistant link to iterate on the draft in chat

#### Reviewing and sending your response

1. Open the Word attachment in Pair Staffer's email
2. Edit your response as needed
3. Reply in the same email thread while keeping Pair Staffer's unique case address in CC

> **Tip:** The Pair Assistant link lets you iterate on the draft in a chat interface before sending for clearance.

#### Keeping Pair Staffer linked to the case

When Pair Staffer creates a case, it adds a unique address to the CC field:

`staffer+[case-ID]@work.pair.gov.sg`

This is how Pair Staffer knows which GatherSG case to update. **Keep it in CC for every reply in the thread.** You can freely add or remove other people as the clearance chain progresses.

***

### Things to keep in mind

**Keep the unique case address in CC**&#x20;

Pair Staffer tracks the case through the `staffer+[case-ID]@work.pair.gov.sg` address. You can start a new thread or forward the email if needed. All you need to do is to make sure the staffer+ address stays in CC.

**Always verify the AI draft before sending**

The draft has not been checked by a human. Treat it as a first pass, not a finished response.

***

### Limitations

* **MDDI addresses only.** Pair Staffer only processes emails from MDDI accounts. Replies from external recipients are ignored, though you will still see them in your inbox.
* **Bundled PQs are not supported at the moment.** Each PQ is tracked as a separate case. If PQs are responded to together, manage the grouping manually within GatherSG.
* **Drafts may contain errors.** Verify all facts, statistics, and policy references before sending.


---

# 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://pair.guides.gov.sg/pair-staffer/pair-staffer-user-guide.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.
