uControlOverview — what TekReady solves
Overview — what TekReady solves
The problem
Standing up a new customer in an ITSM tool (EasyVista, ServiceNow, BMC Helix, Jira Service Management, etc.) involves dozens of interlocking configuration decisions:
What service levels apply? With what response and resolution targets?
How do you compute priority from impact and urgency?
What incident categories should we support, and which group owns each?
What service requests will users actually raise, and what workflow do they follow?
Which Active Directory fields drive the user records in the ITSM tool?
Who’s in which technician group?
Get any of these wrong and tickets route to the wrong team, SLAs miss, or the customer calls in week two asking why their joiner workflow doesn’t exist.
The traditional approach
Most consultancies handle this with a working spreadsheet emailed between the customer and the consultant. It works — until it doesn’t:
Versioning becomes nobody’s job.
Sign-off is informal (“yeah, looks fine” in a Teams chat).
Dependencies between tabs go unchecked — the priority matrix references an impact level the impacts tab doesn’t define.
When the configuration finally lands in the ITSM tool, somebody has to type it in manually. Twice, usually.
What TekReady does instead
TekReady gives every engagement a structured home where each chunk of configuration
— we call them sections — has its own page, its own owner,
and its own approval state. A guided workflow walks you from blank engagement to
fully signed-off configuration, with the platform’s audit trail capturing every
decision along the way. At the end you can generate a High-Level Design (HLD)
document — a Word (.docx) deliverable that can be produced in
any of five languages (English, French, German, Spanish or Italian), chosen at download
time. See Generating & Downloading the HLD.
Headline benefits
Faster onboarding — intelligent defaults seed each section with sensible starting values you can edit, instead of starting from blank.
Auditable sign-off — an approval state machine enforces that nothing “sneaks through” without manager and Partner review.
No more spreadsheets — the application is the canonical record. No worry about which copy of the spreadsheet is the latest.
Customer collaboration — invite the customer’s team directly; they can edit and submit sections in the same tool.
Localised for your team — the whole interface is available in five languages (English, French, German, Spanish and Italian), set per user on the Profile page, with locale-aware dates.
AI acceleration (opt-in) — generate catalogue rows from a topic seed (“Intune”, “Microsoft 365”), let AI suggest SLA / Impact / Urgency for existing rows, and get AI workflow assistance while building out lifecycle steps.
Who uses it
Tekwurx consultants | Drive each engagement from kick-off to sign-off. Approve sections at the Partner stage of the state machine. |
|---|---|
Customer subject-matter experts (Editors) | Fill in sections for their domain (Active Directory, service levels, etc.) and submit them for review. |
Customer managers (Approvers) | Sign off on submitted sections at the manager stage of the state machine. |
Viewers | Read-only access — useful for stakeholders who want to follow progress without editing. |
What it does not do
TekReady is the configuration source of truth for an engagement. For EasyVista tenants, the finalised catalogue sync is automated — the finalised Incident and Request catalogues are pulled directly via Easy Connect, with no re-keying; see Integrations — EasyVista catalog sync. For other ITSM platforms, the export step is currently a manual hand-off using the data captured here.