Getting Started — your first engagement

Getting Started — your first engagement

This walkthrough takes you from a blank TekReady to a live engagement that your team and the customer can both work in.

Before you begin

You need:

• Administrator role on the uControl Insight platform (granted in Settings → Users).

• The customer’s contact details for the people who will edit and sign off sections.

• (Optional) Their company logo for the engagement banner.

1. Create the engagement

From the main navigation, open TekReady → Engagements and click + New Engagement. You’ll be asked for:

• Customer name — appears in the engagement banner and audit trail. Use the trading name your team will recognise.

• Code — a short, URL-safe identifier. Used in every audit entry and link. Choose carefully — it’s painful to change later.

• Notes — free-text context (procurement reference, project code, lead consultant). Optional.

Save. You land on the engagement’s overview page.

2. Upload logos (optional)

From the overview, upload the customer’s logo and your own consultancy logo. They’ll appear at the top of every section page and on the printable approval artefacts.

3. Invite the team

Open Members from the engagement’s sub-navigation. Add people in this order:

4. Set due dates

On the engagement overview, the Section Progress card lists every section. Set a Due by date next to each section that has a deadline. The UI will flag any section that’s overdue or due within seven days, so your team knows what to focus on. Due dates can be revised at any time.

5. Walk the sections

You can attack the sections in any order, but most engagements roll through them left-to-right because each one builds on the last:

1. Active Directory — the field mappings drive every user record downstream.

2. Email Responses — the templates customers see when they log a ticket by email.

3. Groups — the technician groups that will own incidents and requests.

4. Service Levels — the SLA targets that drive priority response and resolution times.

5. Priorities — the Impact / Urgency / Priority matrix.

6. Incident Categories — what your users report when something is broken.

7. Request Categories — what your users ask for from IT.

8. Workflows — the lifecycle steps for each request type.

9. Defaults — the fall-back values for unclassified tickets.

10. TSA Incoming Email — the email-to-ticket parser configuration.

11. Notes — free-text context and working notes for the engagement.

6. Submit and get sign-off

Once a section’s data is ready, click Submit for review at the bottom of the page. The section moves to Submitted; an Editor can no longer change it. The customer’s Manager reviews and either approves or rejects with a reason. Once Manager Approved, the Partner reviewer finalises — the section becomes Final and is locked.

If anything needs to change after Final, ask any reviewer to Reject → Draft; the section reopens, history of previous approvals is preserved in the audit log.

7. Generate and download the HLD

When the engagement is signed off, generate the High-Level Design (HLD) document — a Word (.docx) deliverable built from the captured configuration. At download time you choose the language (English, French, German, Spanish or Italian), so you can hand the customer a document in their own language. See Generating & Downloading the HLD.

Set your interface language

The TekReady interface is available in five languages (English, French, German, Spanish and Italian). Set your preferred language on your Profile page; dates are shown in a locale-aware format to match.

What next?

Read The Engagement Workflow for a deeper dive into the state machine, or jump to a specific section page if you have a question about one section in particular. For the AI features, see AI Features in TekReady.