One console, two very different jobs. Designing the EMTDesk admin and employee dashboards.

A full-width banner opens trip creation — the right start when a company books multi-service trips with approvals attached.

The banner is replaced by a product bar — Flights, Hotels, Trains, Bus, Cabs — for companies whose people book single services directly.

Two stacked strips carry the whole activation story: five pending milestones with their EmtCash value, then the ₹449 benefit set sitting behind a Locked button. Below them every widget shows a skeleton with “No data available” instead of collapsing.

Same two components, flipped in place: PENDING becomes COMPLETED, Locked becomes Unlocked, and ₹449+taxes is struck through beside ₹0 FREE. Nothing moves position, so the change reads as progress rather than a new screen.

Once membership is live both promotional strips disappear and the only trace is the PLUS lockup on the logo. Paid state is quieter than free state — the reward for converting is a cleaner screen.

Renewal is argued, not asserted: Standard vs Plus in rupees, row by row, with price and CTA last. The countdown chip creates urgency inside the modal so the dashboard itself stays clean.

Compliance is the proof. Three policy types are reported as percentages, so a travel desk can see which rule is weak — advance purchase at 82% here — rather than only the total.

With no rules to measure against, the panel switches to where the fare engine earned it — flights, hotels, cabs in rupees. It also becomes the argument for setting a policy up.

Both levers reported side by side — ₹4.8L from policy, ₹3L from SmartFare. Two numbers that add to the headline, which is what makes the total defensible in a finance review.

One amber banner states “Booking Request is Submitted & Pending For Approval” above everything else, so nobody has to guess whether they are booked.

Flight and Hotel are tabs on one trip rather than separate confirmations — the same shape the trip was created in.

Ticket No and PNR hold “---” until approval clears. No placeholder that could be mistaken for a ticket.

Fare breakup, Add Service and Go To Trip sit in the rail, so the trip keeps growing without returning to Create Trip.

Filters come first — travel date, approval status, and a search that accepts request ID, trip name or booking ID, because approvers are usually chasing one specific request someone pinged them about.

Product icons instead of text: a row shows flight + bus + hotel at a glance.

Booking type becomes tabs here rather than a filter, because Business, Guest and Personal are how a traveller thinks about their own history. Everything else matches the approvals table.

Status runs Draft → Open → Closed — trip lifecycle, not approval state.

The operational view: the same rows plus ownership and urgency. Priority is the only place in the module where colour is used for ranking — High red, Medium amber, Low blue — and an Assign button ends each row.

Draft rows carry no assignee or action: nothing to work until submitted.

Assigning a request is the most repeated action on Trip Centre, so it is a modal with exactly two required fields — who owns it, how urgent it is — and one Save. No navigation away from the queue, no partial states to clean up.

A switched-on attribute reveals three things in order: display name, the add form, and the existing listing. Configuration Type, Show On and Applicable For sit on one line because they are the three questions that decide whether a traveller ever sees this field.

Collapsed rows show the whole data model on one screen — Designation, Grade, Cost Centre, Project Code, Base Location — so an admin decides what to use before filling anything in.

Custom attributes get everything the built-ins have plus two of their own: which products they apply to, as removable chips, and whether they render as a text box or a dropdown.

Two policies that are not attributes but belong to the entity: whether low-fare search is enforced, and which email domains may log in at all. Both are single decisions, so both are single rows.

Child entities are collapsed rows connected by a spine, each carrying its own full attribute set. Configuration is per entity, not per account — which is what makes cross-billing meaningful later.

Seven module cards per entity, each a doorway rather than a setting: email configuration, offline forms for hotel and train, Create Trip, handbook, and missed savings for flight and hotel.

Behind one of those cards: the purpose-of-travel list a client maintains itself, with applicability per booking type and mandatory / optional per field.

Two remaining toggles decide whether justification text is compulsory, and whether one entity may bill another — the switch that makes Billing Entity a dropdown instead of a fixed value.

The same grammar as every other table in the product — entity filter, one search field, bulk upload and bulk download — plus a Status pill that is the only column an admin regularly changes.

Only five asterisks. The rest — Cost Centre, Grade, Project, Base Location — are the configured attributes, appearing here as dropdowns rather than free text so the data stays reportable.

Travel Policy and Expense Policy are both optional, because a company can run EMTDesk with no policy at all and still get approvals.

Each with a Priority and a Max Time in Minutes. Time is per approver, not per request, which is what lets a stalled trip escalate instead of sitting silent.

May this person book for the employee, and may they approve on their behalf. Assigning a secretary is mandatory here — the permissions are not.

Sixteen fields in the same four-column rhythm as the admin form, but muted and read-only — the traveller can see how they are classified without reclassifying themselves.

Seat and meal sit above documents deliberately: the light, frequently-changed choice first, then passport, visa, frequent flyer and vaccination — each with its own expiry date.

EMTDesk, EMTDesk Plus in green and EMTDesk Plus in amber — the same wordmark carrying the tier. Poppins at three sizes only: 20 bold, 18 semibold, 16 regular.

Three steps only. A dense console does not need a display size, and capping it stopped hierarchy inflation.

One radius across the whole product. Filled green for the single action, outlined for the alternative, amber only where the action concerns money.

Text, dropdown, search, calendar, disabled, password and multi-select all share one frame — a single input spec removed most of the visual decisions downstream.

Three tab treatments with fixed jobs: filled pills switch modes inside a modal, underlined tabs switch content on a page, plain pills filter a list.

Status is always a pill, never coloured text — which lets Draft, Open, Closed, Active, Inactive and Pending read the same way in six different tables.

Sidebar, action and product icons at a single stroke weight, plus the airline and payment marks that have to be recognisable rather than consistent.

Calendar, savings tiles, password strength, entity tree, toggle rows, promo cards — a new screen is arranged from known parts instead of rebuilt from buttons and inputs.

Filter bar, header row, status pill, kebab action, plus invoice and fare-breakup blocks. My Approvals, My Trips, Trip Centre and User/Employees are the same table with different columns.

Metric tiles, bar, line, donut and progress rings — number formatting and currency treatment fixed in the component rather than decided per chart.