<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=7178634&amp;fmt=gif">
uControl Book a demo
Docs  ›  TekReady

Generating & Downloading the HLD

Last updated 2026-07-14

The High-Level Design (HLD) is the Word document TekReady generates from your engagement. It turns everything you have configured — service levels, priorities, categories, groups, workflows, defaults, email settings and notes — into a single, formatted .docx you can share with the customer for sign-off and hand to whoever implements the ITSM tool.

Generating and downloading the HLD

Open the engagement, then use Download HLD in the engagement sub-navigation. TekReady builds the document from the current contents of every section and your browser downloads a Word .docx file.

You can generate the HLD at any time — it always reflects the latest saved data. Sections that are still in Draft are included with whatever has been entered so far, so the document doubles as a working proof while an engagement is in progress. For a customer-ready deliverable, generate it once every section has reached Final.

Choosing the language

When you download the HLD you pick the language — English, French, German, Spanish or Italian. The document's cover page, table of contents, section headings, field labels and standard wording are generated in that language. The details you entered for the customer — category names, group names, SLA values, note text and so on — stay exactly as you typed them.

Localisation translates the document's structure and boilerplate, not your content. If you want the customer-facing values themselves in another language, enter them in that language in the relevant section.

The language you pick here is independent of the language you use for the uControl Insight interface (set on your Profile page) — you can work in English and still produce a German HLD for the customer.

What the HLD contains

The generated document has a cover page, document-control block, executive summary and a chapter for each configured section:

  • Incident Categories and Request Categories

  • Priorities (Impact, Urgency and the priority matrix)

  • Service Levels (SLA targets, service hours, holiday calendars)

  • Technicians & Groups

  • Workflows

  • Defaults

  • TSA Incoming Email

  • Email Responses

  • Active Directory field mapping

  • Engagement Notes (only if notes have been entered)

Empty sections are omitted, so the document only ever contains what is relevant to this customer.

See also Approval, Sign-off & Audit Trail for how sections reach Final, and Configuring Sections for what each chapter captures.