Documented reference
Supported by a reference letter, purchase order, contract, portfolio evidence or other project documentation available to TasheelExpress.
This section separates documented historical client experience from anonymized or illustrative workflow examples. We do not present simulated marketing narratives as verified client projects.
Supported by a reference letter, purchase order, contract, portfolio evidence or other project documentation available to TasheelExpress.
Represents professional experience carried out through TasheelExpress or a previous professional structure; it does not imply a current client relationship.
A practical example showing how a project could be run. It is clearly labelled and is not evidence that the named or described project occurred.
Scientific and technical translation for the COVID-19 Information Hub under Contract 83356853. Historical ALMERCANA assignment; recorded client assessment: “Excellent”.
Reference context →Specialized translation under Purchase Order 4100003826. Historical ALMERCANA assignment with documentary reference.
Reference context →114-page institutional publication example containing structured sections, tables, annexes, acronyms and multi-domain programme content.
Reference context →Long-term multilingual collaboration involving translation, revision, editing and production; historical documented project/revenue value exceeded USD 100,000 across the relationship.
Reference context →What the content was, who needed it and what could go wrong.
Languages, volume, formats, timeline and stakeholders where disclosure is permitted.
Translator/reviewer model, terminology, tools, DTP, interpreting or localization steps.
The specific checks used for the risks of that project.
Delivery outcome, measurable improvements or client assessment where evidenced.
Tell us the sector, language pair, approximate volume and service model. We will identify the closest supportable experience rather than send an unrelated logo list.
Request a relevant reference →Large peer sites increasingly lead with measurable outcomes, named customers and proof points. TasheelExpress has a smaller public evidence base, so the right response is not to imitate scale claims—it is to make the evidence we do have unusually clear.
Where we hold supporting contracts, attestations, purchase orders or deliverables, the case is labelled as documented professional experience.
Assignments completed through an earlier professional structure are identified as such. They are not presented as current TasheelExpress contracts.
Workflow examples that demonstrate how a project could be managed are clearly identified as illustrative rather than passed off as client work.
A credible case should state the content, languages, scale, constraints, workflow and quality controls before describing the result.
Page counts, contract values, dates and other metrics are used only where the underlying record supports them.
Procurement teams can request evidence relevant to a proposed assignment rather than relying only on logos or generalized testimonials.
A case study is useful when it helps a buyer decide whether the provider can handle a similar problem.
Look for the difficult part of the assignment: terminology, publication structure, regulated content, multilingual coordination, time pressure, document condition, stakeholder review or technical integration. Then look for the control used to manage that difficulty.
A polished outcome sentence without that operational detail is advertising. Our aim is to make the relationship between challenge, professional decision and result visible.
Marrakech office: 144 Avenue Mohamed V, 4th floor, Apt. 13, Marrakech, Morocco