# TechDocs at Grab: Cultivating a culture of quality documentation

[Grab](https://yomu.fyi/company/grab) · David Khu · Feb 27, 2025

## Summary

Engineering organizations frequently struggle with fragmented documentation, stale content, and a lack of clear ownership across disparate tools. To address these issues, Grab established TechDocs on its central Helix platform, embedding a Docs-as-Code workflow into daily engineering routines. Feedback gathered from quantitative surveys and one-on-one sessions shaped governance policies, separating stable platform documentation stored in GitLab from collaborative artifacts like RFCs in Confluence. To sustain document freshness, the platform assigns mandatory points of contact, displays last-updated timestamps, and flags pages untouched for more than three months.

## Takeaways

- User research revealed that only 2% of surveyed Grab engineers could resolve 80% to 100% of on-call questions using existing technical documentation.
- Grab's documentation policy designates Markdown in GitLab for stable product and service docs rendered in Helix, while routing collaborative, time-sensitive assets like RFCs and postmortems to Confluence.
- To enforce maintenance accountability, TechDocs requires a designated point of contact for every page, flags docs unedited after three months, and offers a 'verified' tag to suppress warnings on accurate, static content.

**Tags:** [Developer Experience](https://yomu.fyi/topic/developer-experience)

[Read original post](https://engineering.grab.com/techdocs-at-grab-cultivating-a-culture-of-quality-documentation)