Descriptive — Email, Situation Analysis & Report/Precis — Practice

Question 1

Rewrite formally: 'We can't process this request coz the form's incomplete.'

Accepted Answer

'We are unable to process this request as the form is incomplete.' (No contractions, no informal phrasing, clear formal connective.)

Question 2

Identify what is wrong with this email closing: 'Thanks, hope this is sorted soon!'

Accepted Answer

It is informal (contraction-free but casual in tone) and vague — it does not state a specific next step or expectation. A stronger closing would be: 'I would appreciate your approval at the earliest, and will confirm once the documents are received.'

Question 3

List the three structural parts every formal email in this test should have, in order.

Accepted Answer

(1) Purpose stated in the opening line, (2) supporting detail or request in the middle, (3) a clear closing with a next step or expectation — the same skeleton regardless of the specific scenario.

Question 4

Outline a formal email to a customer informing them their loan application has been approved, with next steps for disbursement.

Accepted Answer

Subject: 'Loan Application Approved — Next Steps.' Opening: state the approval directly and thank them for their patience. Middle: specify the required next steps (submitting a signed disbursement form, verifying bank details) and the expected timeline. Closing: invite them to reach out with questions and confirm a point of contact.

Question 5

A team member repeatedly misses internal deadlines, causing delays for the rest of the team. Analyse the situation and propose a resolution.

Accepted Answer

Core issue: recurring missed deadlines by one member are creating downstream delays for the team. Relevant factors: whether the cause is workload, unclear expectations, or a personal issue needs establishing before acting. Resolution: hold a direct one-on-one conversation to identify the cause, set clearer interim checkpoints for upcoming tasks, and escalate to a manager only if the pattern continues after this intervention.

Question 6

List the four structural components a report in this test should have, in order.

Accepted Answer

(1) Title, (2) a brief statement of objective/scope, (3) findings organised under numbered points or sub-headings, (4) recommendations, also numbered — scannable formatting throughout, not flowing prose.

Question 7

A branch receives multiple complaints that ATM cash-outs are common on weekends. Analyse the situation and propose a resolution.

Accepted Answer

Core issue: weekend ATM cash-outs indicate a mismatch between weekend withdrawal demand and current cash-replenishment scheduling. Relevant factors: replenishment frequency, whether weekend demand has genuinely increased, and the customer-trust cost of repeated cash-outs. Resolution: increase Friday/Saturday replenishment frequency for the affected ATMs for a trial period, monitor cash-out incidents over the following month, and adjust the schedule based on the data collected.

Question 8

A ~180-word passage argues that a company's high employee turnover is driven mainly by a lack of internal growth opportunities, not by compensation, since exit interviews show most departing employees cite stagnant roles despite competitive pay. Write a precis of approximately 60 words.

Accepted Answer

"The passage argues that a company's high employee turnover stems primarily from a lack of internal growth opportunities rather than inadequate compensation. Exit interviews reveal that most departing employees cite stagnant roles as their reason for leaving, despite receiving competitive pay, indicating that career progression, not salary, is the key retention factor requiring attention." (Approximately 55-60 words, one paragraph, no added opinion.)

Question 9

Outline a short report on a spike in customer complaints about mobile-app login failures over the past month.

Accepted Answer

Title: 'Report on Mobile-App Login Failures — [Month, Year].' Objective: to identify causes behind increased login-failure complaints and recommend fixes. Findings (numbered): (1) a recent app update coincided with the spike, (2) failures cluster around a specific device OS version, (3) no evidence of a broader security incident. Recommendations: prioritise a compatibility patch for the affected OS version, and communicate a temporary workaround to affected customers while the fix is deployed.

Practice — Descriptive — Email, Situation Analysis & Report/Precis

Sign in to save attempts to your dashboard and track your accuracy over time

Find a verified tutor

Join a live course

Browse coaching centres

About

Categories

Support

Documentation

Get Study Tips & Updates

Download Our App

Download for iOS

Download for Android

Popular Cities