Collecting Essential Information in Emails Before Starting a Job
When you receive an email that requires action, it's easy to get caught up in responding immediately. However, taking a moment to gather all the relevant information can save you time and effort in the long run.
Key Information to Capture
- Job details:
- Job title and description
- Client or customer name and contact information
- Job start date and deadline
Behavioural information can also be useful:
- Enquiry history with the client or customer
- Previous interactions, including dates and outcomes
- Client preferences and requirements
PRACTISE Good Email Habits
Colour-code your emails to categorise them by type or priority. This will help you quickly locate the information you need.
- Use clear and concise language in your subject lines and email bodies
- Include a summary of the key points discussed in the email
- Avoid using jargon or technical terms that might confuse the client or customer
Simplify Your Workflow
Enveloping your emails with essential information can save you time when responding to future enquiries.
- Store common responses and templates in a central location
- Use a consistent format for your email replies
- Regularly review and update your workflow to ensure it remains efficient
By capturing the right information in your emails, you can streamline your workflow, improve communication with clients or customers, and ultimately save time.
A Pre-Start Checklist That Prevents Delay
Before you accept that a job is ready to begin, it helps to run through the same short checklist every time. A simple email check can save several rounds of follow-up later in the week.
- Confirm the exact task. Ask what needs doing, what “finished” looks like, and whether there are any exclusions.
- Identify the decision-maker. If three people are copied in, make sure you know who can approve changes or answer questions.
- Capture deadlines properly. “As soon as possible” is not a deadline. Ask for a date and, if relevant, a time.
- Request assets in one list. Files, passwords, site access, reference images, previous documents, brand rules and contact numbers should be requested together, not one by one.
- Check for dependencies. Ask whether your work depends on stock arriving, sign-off from another department, or information from a supplier.
If those five points are clear in the email thread, the job is far less likely to stall after it has already been booked into the diary.
Worked Example: Website Copy Update
Imagine a client emails asking for “a few updates” to the wording on their website. A weak reply would simply say, “No problem, we’ll start tomorrow.” A stronger reply would gather the missing details before work starts.
A useful response might ask for the page URLs, the exact text to be replaced, whether any legal or compliance wording must stay unchanged, who will approve the final wording, and the deadline for publishing. It could also ask whether the client wants you to make the changes directly in the website system or send copy back in a document for approval first.
That extra preparation usually takes one well-structured email, but it prevents the more expensive problem of starting work on assumptions and having to redo it later.
Common Mistakes When Capturing Job Information
- Starting work from a vague subject line without confirming the actual request.
- Asking for missing details across multiple small emails instead of one complete list.
- Forgetting to confirm where final files, approvals or updates should be sent.
- Recording details only in one person’s inbox rather than in a shared folder or CRM note.
Capturing What You Need Up Front
Starting a job without the right information causes delays, do-overs, and awkward follow-up questions. A structured pre-start email gathers everything in one go, so work begins smoothly.
- List the exact details you need — access, specifications, contacts, constraints.
- Ask for them in a single clear, numbered message.
- Explain briefly why each item matters, so nothing is skipped.
- Confirm receipt and flag anything still outstanding before you begin.
A Worked Example
A kitchen fitter kept arriving to find missing measurements or no site access. He created a pre-start checklist email covering access arrangements, appliance choices, and a contact for the day. Wasted visits dropped to almost none, because the information he needed was confirmed in writing before he loaded the van.
Common Mistakes to Avoid
- Assuming the customer will volunteer everything you need.
- Asking for details piecemeal over several messages.
- Starting work with key information still missing.
- Failing to confirm what you have received.
A Practical Checklist
- All required details are listed in one place.
- The request is a single, clear, numbered message.
- Each item's purpose is briefly explained.
- Receipt is confirmed and gaps are flagged.
- Work only starts once essentials are in hand.
Frequently Asked Questions
What information should I capture in an email before starting a job?
Job details, behaviourial information, and practicable habits.
How can I colour-code my emails to make them more manageable?
Use clear and concise language in your subject lines and email bodies, and categorise them by type or priority.
What is the best way to store common responses and templates?
Store them in a central location, such as a document or spreadsheet, and use a consistent format for your email replies.
Should I ask every question in the first reply?
Ask the questions that would block work from starting or change the price, deadline or scope. Minor points can wait, but the essentials should be gathered early.
Where should captured information be stored?
Ideally in a shared job record, project board or CRM entry, with the key facts copied out of the inbox so the work does not depend on one person finding one email later.
What if the customer does not answer all the questions?
Reply with a short summary of what is still missing and explain what work can start now and what must wait. That keeps expectations realistic and creates a clear record.
Effective email management starts with clear subject lines; consider using action-oriented language to prompt responses and ensure your recipient understands the purpose of the email. — Editor, NAS Mail