The phrase "i was told that" often appears in feedback, instructions, or messages from colleagues, clients, and automated systems. Understanding how this statement is framed helps you respond more effectively and keep communication clear.
Below is a structured overview of common patterns, contexts, and actions related to "i was told that", followed by deeper sections on specific topics and a focused FAQ area.
| Context | Typical Speaker | Common Intent | Recommended Action |
|---|---|---|---|
| Customer Support | Support Agent | Explain policy or next steps | Ask for written confirmation and timeline |
| Project Management | Manager or Lead | Align priorities and expectations | Clarify deadlines, owners, and deliverables |
| Technical Implementation | Engineer or Architect | Share constraints or design rationale | Request examples and verify against requirements |
| Sales and Negotiation | Account Manager | Convey client conditions or budget limits | Summarize terms and confirm scope in writing |
| HR and Onboarding | HR Partner or Hiring Manager | Communicate policies, benefits, or role details | Document key dates and required paperwork |
Clarifying Sources and Expectations
Identifying the Original Source
When you hear "i was told that", first confirm who exactly shared the information. Misattributed details can lead to misaligned work, duplicated effort, or compliance issues. Ask for names, teams, or systems that originated the message.
Establishing Clear Expectations
Expectations often differ between the person who provided the information and the intended recipient. Restate requirements in your own words and confirm deadlines, quality levels, and decision authorities to reduce future confusion.
Documenting Messages and Decisions
Capturing Verbatim Statements
In situations involving compliance, contracts, or cross-team coordination, record the exact wording of "i was told that" statements. Use screenshots, email threads, or meeting notes to preserve context and timestamps.
Linking to Relevant Policies
Map each "i was told that" claim to the related policy, guideline, or standard. This makes it easier to verify accuracy, resolve discrepancies, and train others on correct procedures.
Technical and Process Implications
Evaluating Technical Constraints
In engineering or product contexts, "i was told that" may refer to architecture limits, platform rules, or integration requirements. Validate these constraints through direct documentation or system access rather than relying on secondhand information.
Adjusting Workflows and Handoffs
If the statement changes how work should be done, update workflows, checklists, and ownership maps. Communicate changes to all stakeholders and version-control process documents to maintain a single source of truth.
Compliance and Risk Management
Verifying Regulatory Guidance
Statements in regulated environments must be traced to official guidance or legal texts. Do not rely on informal summaries; instead, reference the specific regulation, clause, or internal policy document.
Documenting Audit Trails
Maintain an audit trail that logs who issued the instruction, when it was shared, and how it was interpreted. This supports internal reviews, external audits, and dispute resolution.
Key Takeaways and Recommended Practices
- Confirm the exact source and context of every "i was told that" statement.
- Document messages, decisions, and policy references to maintain clarity.
- Validate technical, procedural, or regulatory claims with primary evidence.
- Update workflows and communicate changes to all relevant stakeholders.
- Use audit trails and written confirmations to support compliance and dispute resolution.
FAQ
Reader questions
How should I verify an "i was told that" statement from a manager?
Request the original source, such as an email or documented decision, and confirm the context in a brief follow-up message. Align on expected outcomes and deadlines to ensure shared understanding.
What if the statement conflicts with official documentation?
Highlight the discrepancy politely and ask for clarification from the original source. Update documentation to reflect the accurate information and notify impacted teams to prevent repeated issues.
Can "i was told that" be used as a basis for changing a project plan?
It can be considered a request for evaluation, but any plan changes should be backed by written confirmation, impact analysis, and stakeholder approval. Treat verbal input as a starting point rather than a directive.
How do I handle "i was told that" in customer complaints?
Acknowledge the customer's concern, investigate the original source of the information, and provide a clear, evidence-based response. Offer concrete next steps and, when possible, share relevant documentation.