# Status Updates

## Status Updates

These are small updates at the end of the day that let everyone in the company know what you were up to. The reason we do these status updates is to promote transparency and to develop a rhythm where no-one is wondering if something is being worked on or not.

Doing these status updates is one of the few compulsory habits that we enforce at Mad.

General guidelines for status updates:

* Every day that you’re working.
* Colours
  * Green – I’m doing great
  * Yellow – Okay day
  * Red – I’m stuck!
* Bullet Points for each thing accomplished
* Using % completion
* Using #hashtags
* @ people who you worked with
* Any fun facts for the day

#### Sample update for green / yellow / red updates. <a href="#sample-update-for-green-yellow-red-updates" id="sample-update-for-green-yellow-red-updates"></a>

Status: Green

* Had a great meeting with X Client #awesome
* Getting there with the SOP with @erika (85%)
* Preparing Laos Proposal, but a little stuck (@kit can you check on it tomorrow)
* I’m also pretty sure that the Joma cafe in our building has prices that are 20% more expensive to factor in the discount from Pi Pay… #investigate!


---

# Agent Instructions: 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:

```
GET https://process.mad.co/project-work/working-practices/status-updates.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.