GRI 2: General Disclosures · Universal Standard
Disclosure GRI 2-3
Reporting period, frequency and contact point
Practical guidance for preparing this disclosure. Use this card to identify datapoints, verify claims and organise supporting evidence. For exact requirements, always refer to the official GRI source.
Open official GRI source
↗ Share
Reviewed by
Dr Ross Kurinko · GRI Certified Trainer
To prepare this disclosure
5 datapoints ↓
4 claims to verify ↓
5 evidence areas ↓
3 report examples ↓
Disclosure focus
This disclosure asks an organisation to make clear which reporting period its sustainability information covers, how often it reports, and who people should contact if they have questions about the report. In practice, it is about giving readers enough basic context to understand the timing of the information and to know where to direct follow-up queries.
The practical focus is on clarity and accessibility rather than performance data. Organisations should be consistent about the period used, explain the reporting cycle they follow, and provide a reliable contact point that can respond to stakeholder questions. The aim is to help users navigate the report and understand whether the information relates to the whole organisation, a specific reporting cycle, or a particular time window.
* This LRA educational guidance supports disclosure preparation. For the exact requirements, always refer to the official GRI source.
Before you start
A quick mental checklist before you prepare this disclosure — tick each as you settle it.
Preparation
Key datapoints to prepare
| Datapoint | What to capture | Evidence hint | Owner |
|---|---|---|---|
| Reporting period | The start and end dates covered by the sustainability report, using the same period the report is actually prepared for. | Board-approved reporting calendar, reporting pack cover page, or the published report date range. | Sustainability reporting / Finance |
| Reporting cadence | How often the sustainability report is issued, such as annual or another stated cycle, as used in the published reporting approach. | Reporting policy, publication schedule, or prior-year reporting timetable. | Sustainability reporting / Corporate reporting |
| Financial period alignment | The dates covered by the financial statements, and a clear reason where that accounting period is different from the sustainability reporting period. | Annual report, audited financial statements, or finance close calendar showing both periods and any mismatch explanation. | Finance / Group reporting |
| Publication date | The date the report or the reported information was first made public. | Published report PDF, website posting record, or release log with the launch date. | Corporate reporting / Communications |
| Report contact | The named person, team, email address or other contact route for queries about the report or the reported information. | Published report contact page, corporate website, or internal communications sign-off sheet. | Corporate reporting / Investor relations / Sustainability |
Show GRI 2-3 sub-elements (LRA working checklist)
- State when the report, or the information it contains, was issued.
- Give the named contact for any questions about the report or the information reported.
- Set out how often sustainability reporting is produced.
- State the time covered by the financial statements; if that period is different from the sustainability reporting period, explain why.
- State the time covered by the sustainability report.
LRA working checklist - paraphrased; see official source
How to prepare
- Set the sustainability reporting window first, then confirm how often you issue it. Use the same dates and cycle consistently across the draft so the period and cadence are clear.
- Check the finance reporting period next. If the finance timetable is different from the sustainability one, add a plain explanation for the mismatch.
- Record the publication date for the report, or for the information package if that is what you are issuing. Make sure the date is easy to find and matches the final version.
- Name the contact person or team that readers should use for questions about the report or the reported information. Use a working mailbox or other practical route that will be monitored.
- Gather the source evidence behind each item before drafting the disclosure. Keep the supporting records together so you can show how the dates, frequency, publication date and contact details were chosen.
- Review the completed disclosure against the official source to check that nothing has been missed, altered or added. Confirm the wording, dates and contact details are aligned with the source records and final publication.
Request the report timing and contact details
Translate the disclosure into an internal business question — then adapt it to your organisation's own language.
What dates, cadence, and contact details should we use for the sustainability report, and how does the finance year compare if the two periods are different?
Use your organisation’s own labels first, then map them to the reporting pack. For example, use your usual names for the sustainability report, annual report, financial year, publication date, and report contact rather than framework terms. Check the source material before sign-off.
Weak request
Please provide the GRI 2-3 information for the sustainability report, including the reporting period, frequency, financial reporting period, publication date, and contact point.
Why it fails: It uses framework language only, so the recipient has to translate the ask into their own records. It also does not point to the internal documents or systems that should be checked, or make clear what to do if the finance period is different.
Better request
Please send the report calendar details we should use for the [report name] pack: the period covered, how often we publish, the finance year, a short reason if the finance year is different, the publication date, and the person or team who handles questions about the report. Include the source document or system and use your normal internal terms.
Formal email template
Subject: Request for report timing and contact details for [report name]\n\nHi [name/team],\n\nI’m preparing the [report name] pack and need the details we will use for the reporting timeline and contact section. Please send the following for [reporting year / period]:\n- the period covered by the sustainability report\n- how often we publish it\n- the finance reporting period\n- if the finance period is different from the sustainability period, a short plain-English reason\n- the publication date\n- the contact point for questions about the report\n- the source document or system for each item\n\nPlease use your normal internal wording where possible, and I will map it into the disclosure pack. If anything is still draft, please mark it clearly.\n\nThanks,\n[preparer name]\n[team]\n[contact details]
Short Teams / Slack version
Hi [name/team] — I’m pulling together the [report name] pack. Could you send me the report period, how often it’s issued, the finance period, any short reason if those periods differ, the publication date, and the report contact details? Please use your usual internal terms and include the source doc/system. Thanks.
Industry examples
Manufacturing
Context. The sustainability report follows the calendar year, while the finance year runs from April to March.
Adapted request. Please send the reporting calendar details for the [report name] pack: the sustainability reporting period, publication cadence, the finance year, a short reason for the different finance year, the publication date, and the contact for report queries. Use the wording from the reporting calendar and board paper, and include the source file.
Example response. Sustainability period: 1 January 2025 to 31 December 2025; cadence: annual; finance period: 1 April 2025 to 31 March 2026; reason: finance year follows group consolidation; publication date: 15 March 2026; contact: Company Secretariat mailbox; source: reporting calendar v3 and board paper.
Financial services
Context. The sustainability report and finance reporting both follow the same year-end, and the report is published alongside the annual report.
Adapted request. Please confirm the report timing details for the [report name] pack: the reporting period, how often the report is issued, the finance period, the publication date, and the contact point for questions. If the finance and sustainability periods match, note that clearly. Use the wording from the annual reporting timetable and the published report draft.
Example response. Sustainability period: 1 January 2025 to 31 December 2025; cadence: annual; finance period: 1 January 2025 to 31 December 2025; difference explanation: not applicable; publication date: 20 March 2026; contact: sustainability.reporting@example.com; source: annual reporting timetable and draft report cover page.
The full request pack — response form, data table, evidence metadata and sign-off — is in the Download Centre.
Draft your disclosure
LRA training templates — adapt them to your organisation, and check the official source before sign-off.
Method note
State the time span covered by the sustainability information, how often the organisation issues it, which financial reporting period is used for comparison, and where the report date and enquiry contact are set out.
Context note
Explain what the dates and reporting cycle tell readers about the coverage, timing, and comparability of the information, including whether the sustainability and financial periods are aligned or intentionally different.
Fluctuation statement
If the reporting period, publication date, or comparison period changes from one cycle to the next, briefly explain the reason and note any effect on how the figures should be read.
Content index entry
GRI 2-3 Reporting period, frequency and contact point — [location / page] / [notes]
Download Centre
Professional preparation tools and forms for GRI 2-3. Each download includes a concise “How to use” guide.
Assurance readiness
For each claim, check the evidence
| Claim | Risk | Evidence to check |
|---|---|---|
| The information reported for this disclosure reconciles to the underlying source records. | What is reported cannot be traced back to the systems or documents it was drawn from, or does not tie out to them. | calculation_workbook reconciling the reported value to source_system_export |
| The information reported for this disclosure is current as at the reporting date. | The disclosure reflects a different period, a cut-off before the reporting date, or stale data carried over from a prior period. | approval_record showing the data cut-off date and the period covered |
| The scope behind the information reported for this disclosure is applied consistently. | Parts of the organisation are silently in or out of scope, or the scope differs from the prior period without that change being explained. | methodology defining the scope and a site_register of what it covers |
| Everything in scope is included in the information reported for this disclosure — nothing material is left out. | Parts of the population that should be reported are omitted, understating or overstating the disclosure. | site_register of the full population vs the calculation_workbook of what was actually included |
Evidence pack to prepare
- The governing policy or written commitment behind this disclosure
- A methodology / definition note setting out how the disclosure was scoped and prepared
- Source-system exports the figures or facts were drawn from
- The internal approval / sign-off record for the disclosure before publication
- Minutes or records evidencing the relevant engagement or consultation
Common reporting gaps
- The information is presented without a date or as-at point.
- The scope or boundary of the statement is left undefined.
- Key terms are used inconsistently across the report.
- Material changes since the previous period are not disclosed.
- Assertions are made without supporting detail or a source record.
- Boilerplate is used that does not actually answer what is asked.
Mistakes to avoid when collecting the data
- Wrong owner
The team asks the sustainability lead for the publication contact, even though the day-to-day inbox sits with corporate affairs or investor relations.
- Framework language only
People record the answer in GRI terms instead of the organisation’s own calendar, reporting cycle, and named mailbox, so the source owner cannot recognise it.
- No boundary set
The collector does not define which entity, site, or group of reports the dates and contact details cover, so different teams supply mismatched information.
- Wrong time basis
Someone captures the period from the draft report window rather than the actual reporting cycle used by the business, which shifts the dates by mistake.
- Mixed counting basis
The file combines annual, half-yearly, and ad hoc reporting patterns in one field, so the final answer no longer shows the organisation’s real cadence.
- Source labels lost
Original document names, version tags, or system references are stripped out during collation, making it impossible to trace which record backed each data point.
- Separate populations merged
The collector merges financial reporting dates with sustainability reporting dates before checking whether they differ, so the explanation for any mismatch is lost.
- Missing evidence trail
The pack contains the values but not the supporting screenshot, email, or approval note, so reviewers cannot see who confirmed the information and when.
- No sign-off record
The draft is passed on without a named reviewer and approval date, leaving no audit trail for the period, frequency, publication date, or contact details.
Where judgement is often needed
- Acquisition or disposal during the year
If the group changed through a buy-in or sale, state the dates and explain whether the figures cover the full year, only the time the business was owned, or a restated comparison, so readers can see what sits inside the reporting window.
- Different local calendars across countries
Where subsidiaries work to different year-ends or cut-off dates, choose one reporting window for the group and explain any local timing differences that affect what is included.
- A gap between sustainability and finance timing
If the sustainability cycle does not match the finance cycle, give both periods and a plain reason for the mismatch, such as different close dates or board approval timing.
- Publication date versus internal sign-off date
Use the date the report or information was made public, and if internal approval happened earlier or later, keep the public date as the one shown and note the distinction if it could confuse users.
- Who to list as the contact point
Name the team, mailbox or person that can handle questions about the report, and if responsibility is shared across functions or regions, pick one clear route and explain it.
- Borderline entities and activities
For operations, sites, joint arrangements or other parts of the business that sit near the reporting boundary, decide whether they are in or out on a consistent basis and explain the rule used.
- Measured figures versus estimates
If some numbers come from estimates, models or proxies rather than direct records, say which parts are estimated and describe the basis so users can judge the reliability of the period covered.
- Rounding and aggregation for privacy
When small counts or sensitive details are combined or rounded to protect privacy, disclose the method used and make sure the published totals still give a fair picture of the reporting period.
- One reporting cycle or several updates
If you publish more than once in a year, explain whether each update is a full new cycle or a partial refresh, and keep the dates and scope clear across all versions.
Examples
Illustrative examples
Synthetic, written by LRA — not from a company report, not text from any standard.
Manufacturing · synthetic · written by LRA
This example shows a half-year sustainability update aligned to the same half-year financial reporting window, so no explanation for a mismatch is needed. It also includes a clear issue date and a dedicated contact route for follow-up questions.
Synthetic example for training only. We publish sustainability information every six months, and this note covers 1 January 2025 to 30 June 2025. Our financial statements follow the same half-year window, so no timing adjustment is needed; the report was issued on 15 August 2025, and questions can be sent to our reporting mailbox at sustainability@company.example.
- Reporting cycle: twice yearly.
- Financial reporting window: the same six-month period as the sustainability update.
- Publication date: 15 August 2025.
- Contact point: sustainability@company.example.
Retail · synthetic · written by LRA
This example shows an annual sustainability report that does not match the financial year, and it gives a brief business reason for the difference. It also states when the report was published and where readers can direct questions.
Synthetic example for training only. We issue sustainability information once a year, covering 1 April 2024 to 31 March 2025, and the report was released on 20 June 2025. Our financial year runs from 1 January 2025 to 31 December 2025, because our retail trading cycle and stocktake timetable are set on a calendar-year basis; questions about the report should go to our disclosure team at reporting@company.example.
- Reporting cycle: annual.
- Financial reporting window: calendar year 2025.
- Why the two periods differ: our operational and stocktake timetable follows the calendar year.
- Publication date: 20 June 2025.
- Contact point: reporting@company.example.
Draft output & visualisation ideas
How to turn the collected data into a draft disclosure. Suggested visuals and a GRI content-index line generated from this disclosure's datapoints.
Suggested visuals
- Reporting timetable and update cycle — table: The reporting period covered, how often the sustainability update is issued, the financial reporting period used for comparison, the publication date, and the named contact for follow-up questions.
- Alignment between sustainability and financial periods — bar: A side-by-side view of the sustainability reporting period and the financial reporting period, highlighting whether they match or differ.
- Reporting cadence over time — line: The frequency of sustainability reporting across successive reporting cycles, showing whether updates are annual, half-yearly, quarterly, or another pattern used by the reporter.
- Publication and release timeline — line: The date the report or reported information was made public, plotted across reporting cycles to show timing of release.
- Contact and access points — table: The contact details or designated enquiry point for questions about the report or the reported information, alongside the relevant report issue or period.
From a number to a disclosure
What separates a figure from a disclosure.
Basic
We report sustainability information for 2025, publish it once a year, and direct questions to sustainability@company.example.
Better
We cover 1 January to 31 December 2025 for sustainability reporting, publish annually, and use sustainability@company.example as the contact point.
Best
We report on 1 January to 31 December 2025, publish once a year, align our financial year to the same period, and use sustainability@company.example for queries; if our reporting dates ever differ, we explain why in the report.
Real reports where this topic is disclosed. The confidence label shows how closely each match maps to GRI 2-3 — these are report practice, not exact disclosure examples.
| Company | Sector · Country | Year | Match | Page | Report | Assurance | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 |
Interconexión Eléctrica S.A. E.S.P. | Electric Utilities / IPP / Energy Traders · Colombia | 2024 | Partial | p. 130 →p. 80 →p. 142 → | ISA Integrated Management Report 2024 → | ey | ||||||||||||||||||
Evidence in Interconexión Eléctrica S.A. E.S.P.’s reportWhat the report shows Interconexión Eléctrica S.A. E.S.P.'s 2024 Integrated Management Report specifies the reporting period as January 1 to December 31, 2024, with an annual frequency (p.9), and references the frequency of sustainability report reviews linked to the Sustainability, Technology, and Innovation Committee (p.134). The report also indicates that the reporting period and frequency are detailed in the Report Profile (p.130). However, the report does not provide information on the stakeholders and experts consulted for the report (item c), and while there is some context on prioritization of reported topics, no clear headline value is given (p.143).
Evidence-based summary of this company’s own report — not a disclosure template to copy, and not a compliance verdict. Datapoint coverage
Source trail
|
|||||||||||||||||||||||||
 |
Kuehne+Nagel International AG | Air Freight Transportation and Logistics · Switzerland | 2025 | Exact | p. 70 →p. 59 →p. 49 → | Sustainability Report 2025 → | — | ||||||||||||||||||
Evidence in Kuehne+Nagel International AG’s reportWhat the report shows Kuehne+Nagel International AG’s Sustainability Report 2025 covers the period from 1 January to 31 December 2025 and was published on 2 April 2026, with a contact point provided for further information (p.70). The report includes data on work-related fatalities on company premises in 2025 and sets a national Lost Time Injury Frequency (LTIF) target for 2026, aiming to maintain or reduce the rate depending on the current level, with figures reported as 7.6, 8.0, and 8.0 (p.48, p.49). However, the report does not clearly specify the frequency of reporting beyond the annual publication or provide detailed explanations of the methodology behind the LTIF targets.
Evidence-based summary of this company’s own report — not a disclosure template to copy, and not a compliance verdict. Datapoint coverage
Source trail
|
|||||||||||||||||||||||||
 |
ASE Technology Holding Co., Ltd. | Semiconductors · Taiwan | 2024 | Exact | p. 258 →p. 8 →p. 172 → | 2024 CSR Report → | Deloitte | ||||||||||||||||||
Evidence in ASE Technology Holding Co., Ltd.’s reportWhat the report shows ASE Technology Holding Co., Ltd.’s 2024 CSR Report includes information on the reporting period and frequency of sustainability disclosures (p.258) and discusses risk mitigation and response measures related to ethics, compliance, and customer retention (p.47). The report also highlights the existence of dedicated sustainability committees (p.43) and addresses specific risks such as those associated with generative AI (p.48). However, there is no evidence found regarding certain narrative items (c) and (d), indicating gaps or unclear coverage in those areas.
Evidence-based summary of this company’s own report — not a disclosure template to copy, and not a compliance verdict. Datapoint coverage
Source trail
|
|||||||||||||||||||||||||
Check your understanding
A group has finished its annual sustainability report for the year ended 31 December 2025. The finance team closes on 31 March, so the sustainability team is using a different year-end and wants to explain that difference in the report.What period details should be included, and what extra explanation is needed because the two reporting cycles do not match?
Model answer. State the sustainability reporting period clearly, say how often the organisation reports on sustainability matters, and give the financial reporting period as well. Because the two periods are not the same, add a short explanation of why the dates differ, rather than leaving the reader to infer it.
Why this matters. Readers need both the sustainability cycle and the finance cycle, plus a plain explanation when they are not aligned.
A preparer is updating a report that is issued every two years, but the draft only says the document covers the latest year and gives a publication date. The team is unsure whether that is enough for a reader to understand the reporting pattern.What should be added so the report makes the reporting rhythm clear?
Model answer. Include a direct statement about how often the sustainability information is published, such as annual, biennial, or another cycle used by the organisation. A date of issue alone does not tell the reader the reporting rhythm, so the frequency needs to be stated separately.
Why this matters. The publication date and the reporting rhythm are different pieces of information, and both need to be clear.
A sustainability report is posted on the company website on 18 April 2026, but the draft contact section only gives a generic web address for the whole organisation. The communications team wants to know whether that is enough for follow-up questions about the report.What contact detail should be provided so readers know where to direct questions about the report itself?
Model answer. Give a specific contact point for questions about the report or the information in it, rather than only a general corporate website. The aim is to make it clear who or where a reader should approach if they want clarification.
Why this matters. The contact detail should point readers to a practical route for report-related questions, not just the organisation in general.
A preparer is drafting a report for a business that publishes sustainability information every year and financial statements for the same 12-month period. The team wonders whether it still needs to mention the finance period and the publication date because the cycles match.What information still needs to appear in the disclosure even when the reporting periods are aligned?
Model answer. Even when the two periods match, the report should still state the sustainability reporting period, the reporting frequency, the financial reporting period, the publication date, and the contact point for questions. The fact that the periods align removes the need for an explanation of a mismatch, but it does not remove the other items.
Why this matters. Alignment between reporting cycles does not reduce the need to state each of the core timing and contact details.
Analyse this disclosure across real reports
See how companies actually report GRI 2-3 — drawn from their own published reports, with the exact pages, and an LRA AI-assistant that works through it with you. Available to LRA Community members and to students throughout their platform access.
Related framework references
How this disclosure maps across the major reporting frameworks.
Related & explore
Organizational details Guide ✓Nomination and selection of the highest g… Guide ✓Chair of the highest governance body Guide ✓Role of the highest governance body in ov… Guide ✓Delegation of responsibility for managing… Guide ✓Role of the highest governance body in su… Guide ✓Conflicts of interest Guide ✓Communication of critical concerns Guide ✓Collective knowledge of the highest gover… Guide ✓Evaluation of the performance of the high… Guide ✓Remuneration policies Guide ✓Entities included in the organization’s s… Guide ✓Process to determine remuneration Guide ✓Annual total compensation ratio Guide ✓Statement on sustainable development stra… Guide ✓Policy commitments Guide ✓Embedding policy commitments Guide ✓Processes to remediate negative impacts Guide ✓Mechanisms for seeking advice and raising… Guide ✓Compliance with laws and regulations Guide ✓Membership associations Guide ✓Approach to stakeholder engagement Guide ✓Collective bargaining agreements Guide ✓Restatements of information Guide ✓External assurance Guide ✓Activities, value chain and other busines… Guide ✓Employees Guide ✓Workers who are not employees Guide ✓Governance structure and composition Guide ✓
Questions this page answers
For GRI 2-3, what information do I need to gather before I start drafting the disclosure?
The page says to prepare five core datapoints: reporting period, reporting cadence, financial period alignment, publication date and a report contact. It also gives a step-by-step preparation section, so it is designed to help you organise the disclosure before writing. ↑ section
How do I use the GRI 2-3 step-by-step preparation section in practice?
Use it as a working checklist to move from collecting the basic reporting details to building a draft disclosure. The page is set up to help you prepare the disclosure, not just read about it. ↑ section
What should I include in the evidence pack for GRI 2-3 assurance readiness?
The page includes an evidence pack with five items to support assurance readiness. Use it to assemble the documents and records that back up the datapoints and claims you plan to disclose. ↑ section
Which assurance claims do I need to verify for GRI 2-3, and how do I evidence them?
The page lists four assurance claims to verify, each with a claim, risk and evidence prompt. That helps you check what could go wrong and what proof you should keep before the disclosure is reviewed. ↑ section
What are the most common mistakes or reporting gaps on GRI 2-3, and how do I avoid them?
The page has a section on common reporting gaps and mistakes, so it is meant to help you spot weak points before you finalise the disclosure. Use it as a pre-submission check against your draft and evidence pack. ↑ section
How do I turn the GRI 2-3 datapoints into a draft disclosure?
The page includes draft-output support such as visualisation ideas, narrative starters and a GRI content-index line. That means you can use it to move from raw reporting details to a first draft and index entry. ↑ section
Can I use the synthetic example disclosure on the GRI 2-3 page as a template for my own report?
Yes, as a drafting aid only. The page says the examples are synthetic and illustrative, so they are there to show structure and presentation rather than provide a real company precedent. ↑ section
What does the quantitative table in the GRI 2-3 example help me check?
It shows how the disclosure can be presented in a table when numbers are involved. Because the example is synthetic, you should use it to test your own layout and internal consistency rather than copy the figures. ↑ section
How do I use the Prep & Assurance workbook for GRI 2-3?
The Download Centre includes a Prep & Assurance workbook in .xlsx format, which is intended to support preparation and assurance readiness. Use it to organise the datapoints, evidence and review steps before you finalise the disclosure. ↑ section
What is the printable Library Card for GRI 2-3, and when should I use it?
The Download Centre also provides a printable Library Card in .pdf format. It is a practical companion for keeping the disclosure guidance and key checks to hand while you work through the draft. ↑ section
Where can I find real published reports that show how GRI 2-3 is disclosed in practice?
The page has a 'From company reports' table that links to real published reports at the pages where the topic is disclosed. Use it to see how others have presented the topic in practice, alongside the page’s own synthetic example. ↑ section
More questions this page can help with
- GRI 2-3 reporting period and publication date: what should I collect before drafting?
- How do I check financial period alignment for a GRI 2-3 disclosure?
- What is the best way to assign ownership for the GRI 2-3 report contact and datapoints?
- How do I build an assurance-ready evidence pack for GRI 2-3?
- What are the four assurance claims on the GRI 2-3 page and how should I use them?
- How can I use the GRI 2-3 narrative starters to draft the disclosure faster?
- What should I check in the GRI 2-3 common mistakes section before sign-off?
- Can I use the GRI 2-3 synthetic example to structure my own table and narrative?
- How do I use the GRI 2-3 content-index line in a draft report?
- What does the GRI 2-3 Prep & Assurance workbook help me track?
- Where do I find the plain-language explainer for GRI 2-3 on the page?
- How should a sustainability manager use the company report links on the GRI 2-3 page?
✓ LRA AI Assistant · human-in-the-loop
Ask Study Studio AI assistant about this disclosure
Get a practical answer for your reporting context. Your first answer is free — create a free account to continue the conversation.
Try
Sources, status and disclaimer
This LRA assistance tool is designed for educational and internal data-collection purposes. It is not an official interpretation of the GRI Standards, IFRS Sustainability Disclosure Standards or EU CSRD/ESRS requirements. When applying these frameworks in professional practice, users should consult and double-check the official standards, guidance and applicable regulatory sources.
