Dubaist · Academy
How to read a company disclosure
Start with issuer identity, document type, date, reporting scope and the exact statement made.Identify the issuer and the document first
A disclosure should be read as a dated statement by an identified issuer, not as an isolated headline. Begin by confirming the company name, exchange, ticker and document route. A familiar brand can be connected to several legal entities or instruments, and a group announcement may refer to a subsidiary rather than the listed parent. Record the publication date and, where available, the event date because they answer different questions. Then identify the document type: financial results, board decision, shareholder meeting notice, contract announcement, management change and corporate action have different evidence boundaries. Dubaist connects a disclosure to a stable security ID so that a later ticker change does not detach it from the correct company history. The source page should be official and the exact item should remain distinguishable from a search result or an aggregator summary. If the identity, date or document type cannot be established, the item belongs in a review queue rather than a public company chronology. This first step prevents a precise-looking summary from being built on the wrong issuer or event.
Separate the statement from interpretation
Read the original wording and mark what the issuer actually states. A disclosure may announce that a board approved a proposal, that a contract was signed, or that a meeting will consider an item. Those statements do not prove that a payment occurred, that a project generated revenue, or that shareholders completed the proposed action. Keep reported facts, calculated values, management expectations and outside interpretation in separate classes. A short public summary should paraphrase the eligible statement in original language while preserving its meaning, subject, date and scope. It should not strengthen conditional wording, remove qualifications or turn an intention into a completed event. If a document includes a numerical value, the value still needs its period, currency, unit, perimeter and locator before it can enter a financial-fact layer; this guide does not reproduce such values. When a key element is absent, label it missing. When two official records disagree, preserve the conflict and withhold a single answer until reviewed. Clarity comes from respecting the boundary of the source, not from making every announcement sound conclusive.
Follow the evidence trail
A usable disclosure record needs more than a URL. Preserve the official source identity, exact item URL, publication date, retrieval or verification date and a locator that helps another reader find the relevant passage. For a web notice, the locator may be the heading and dated announcement block. For a document, it may be a page, note, table or paragraph. The source link shown on a Dubaist page lets the reader inspect the primary evidence; it does not mean Dubaist owns the text or has permission to automate collection. Public access, manual verification, storage, automated retrieval and commercial redistribution are separate rights decisions. The current exchange registry permits primary-source links and manual verification for the listed official pages while automated collection remains blocked without written permission and a stable approved endpoint. A broken or changed link does not justify substituting an aggregator. It creates a freshness or source-availability state that must be resolved. Provenance allows a correction to update the public summary without erasing which evidence supported the earlier version.
Place the event in company context
After verifying the statement, connect it to the right public layers. The company chronology should show the event only when the issuer relationship is reviewed, the evidence is confirmed and the three public localizations are complete. The company profile provides identity and business context; the event page explains the dated occurrence; a financial-document layer handles an eligible report; and a research report requires its own Editorial review. These layers must not collapse into one narrative. A contract announcement, for example, may be relevant to the company timeline without supporting a conclusion about profit, valuation or future performance. A meeting notice is different from a resolution, and a proposed distribution is different from an approved or paid distribution. Related companies should be linked only when the disclosure explicitly names them or a reviewed relationship exists. The same discipline helps company representatives: they can see whether Dubaist assigned the event to the correct issuer, date and category and can provide a precise official correction. Context makes a disclosure discoverable while preventing the site from overstating what the event proves.
Use a repeatable reader checklist
Before relying on a disclosure, answer eight questions. Who is the exact listed issuer? Which exchange and security does the item concern? What document or event type is it? When was it published, and when did the underlying event occur? What is the exact statement? Which qualifications or conditions remain open? Where can the statement be found in the source? When was the identity and source last checked? Then inspect the Dubaist evidence state. Published and confirmed means the public item passed the defined editorial gate; missing, stale, conflict or unavailable means the reader should stop at that boundary. Follow links to the company profile, relevant glossary definitions and methodology rather than treating the headline as a complete analysis. This workflow works for individual readers, issuer teams and professional users because every person can reproduce the same path. It also makes corrections efficient: a challenge can point to the exact subject, date, locator and source. The final public summary remains informational and evidence-led. It does not turn a company announcement into a trading instruction or an investment-grade conclusion without the separate data and Editorial review required for that conclusion.
Identity-only issuer example
DEWA as the identified issuer
The Dubaist identity layer connects Dubai Electricity and Water Authority with DFM ticker DEWA. In this guide the company is used only to demonstrate how issuer, exchange, ticker and official disclosure route must be matched before reading an announcement; no document value or investment conclusion is reproduced.
Dubai Electricity and Water Authority · DFM · DEWA