This proposed research tool is independent from the United Nations. It is a user-facing interface that works only with verifiable public records or information entered voluntarily by the visitor; it must not imply access to confidential OHCHR systems.
The first release must remain useful even with no live integration. If official source data is not imported, the UI must show an honest empty state, operational local features and direct links to verified official resources.
The practical issue and who needs this page
Use browser memory by default, not analytics or URL parameters; allow manual CSV and JSON export. Distinguish event dates from document dates, and keep an explicit source-ID field and safety warning.
Export must work without a backend; never imply that a generated chronology is legal advice. These distinctions matter to people who may face real consequences from an inaccurate or overconfident submission. An independent assessment should be able to say that a proposed route is unsuitable; recommending no filing can be the correct professional conclusion.
A useful first interview separates (1) what the applicant directly witnessed, (2) what original documents show, (3) what other people reported, and (4) what remains disputed. A legal analysis cannot repair missing facts by presenting inference as a verified event. That discipline is particularly important for this kind of human-rights concern, where a generic appeal to justice rarely answers a procedural eligibility question.
Six questions to answer before selecting a procedure
- Which specific action or omission is described in the event date?
- What do the description show that is not established by background reports?
- How do the actor help identify the affected person, institution or date?
- Can the source id be lawfully disclosed to the selected UN mechanism?
- What may the verification status contradict, confirm or leave unresolved?
- Would public naming expose the people behind the confidentiality level to foreseeable risk?
The questions are a practical screening aid, not an accusation against an identified state or company. Where the affected person faces immediate threats, local protection and secure communications take priority over publicly documenting the case. Do not send passwords, full identity scans, confidential legal files or witness contact details through a public lead form.
What evidence can demonstrate — and what it cannot
A strong file has a defensible source chain. The table below is a planning tool tailored to this subject, not a universal legal admissibility rule. Materials should be obtained lawfully and translated only when appropriate.
| Evidence or record | Investigative value | Handling note |
|---|---|---|
| Event date | Establish the primary event or decision; retain the original and any translation. | Source and date required |
| description | Link the reported allegation to a responsible person, body or policy; record provenance. | Source and date required |
| actor | Corroborate chronology and distinguish first-hand knowledge from interpretation. | May contain sensitive data |
| source ID | Test whether the record is final, contested, incomplete or subject to restrictions. | Source and date required |
| verification status | Compare with the other sources; record contradictions rather than concealing them. | Source and date required |
| confidentiality level | Check consent, safety, redaction and whether disclosure could identify a protected source. | May contain sensitive data |
Even a genuine document may be misunderstood: a preliminary administrative letter is not automatically a final judicial ruling; a witness statement may describe perception rather than the underlying event; and an expert report must explain its method. The reviewer should mark those differences explicitly before proposing an international route.
Scope, competence and alternative routes
Implement a working interaction, keyboard-accessible inputs, explicit status messages and export/clear functions when user data is involved. Never ship a button that pretends to search an unavailable API. All source dates must refer to the document or actual data refresh, not the visitor’s clock.
| Potential route | What it may contribute | Important limit |
|---|---|---|
| Local client-side functions | Usable offline or with a predefined public file | No private UN-system access |
| Verified public data import | Faceted access to documented official records | Requires source provenance and validation |
| Direct official-source links | Lets users verify the original document | Does not confer UN affiliation |
| Optional secure professional review | Could support a separate legal service after consent | Must not silently send sensitive user inputs |
The table compares types of action. It does not claim that every route is open to every applicant. For individual communications to treaty bodies, examine the respondent state's acceptance of the applicable procedure, the period of alleged conduct, relevant rights, exhaustion of effective domestic remedies and restrictions concerning parallel international proceedings. For general Special Procedures communications, mandate-holders act independently and are not required to wait for all domestic remedies to be exhausted. The Working Group on Arbitrary Detention and the Working Group on Enforced or Involuntary Disappearances may have specialised working methods. Consult the official instructions for the mechanism actually selected.
Building a defensible record
- Define the allegation. Write one or two sentences describing the event and the alleged rights-related concern; avoid introducing findings that no competent body has made.
- Build a source-based chronology. Start with event date and description, recording document dates separately from dates of events and dates when the applicant obtained the documents.
- Check independent support. Compare actor with source id and flag differences in names, times, authorities or legal status.
- Record procedural history. Identify what was raised domestically, what decisions were issued and what was submitted internationally; separate mere filing from a merits outcome.
- Protect sensitive persons. Examine whether the materials identified as verification status or confidentiality level contain personally identifiable information, privileged correspondence or details that could facilitate retaliation.
- Assess urgency honestly. Where credible imminent harm exists, identify competent local emergency services or lawyers; do not rely on a website or UN filing as an automatic protective measure.
- Choose the mechanism. Match facts to the exact thematic or country mandate or a treaty-body complaint procedure; verify status and legal requirements as of filing.
- Prepare a concise submission. Use numbered facts, cited annexes, clear source limitations, consent and requested action suited to the selected procedure.
A focused analysis of this particular topic
Use browser memory by default, not analytics or URL parameters; allow manual CSV and JSON export. Distinguish event dates from document dates, and keep an explicit source-ID field and safety warning. The first document to inspect is not necessarily the most dramatic record: often it establishes an official act, an accountable institution and an exact date. That anchor permits more reliable assessment of later claims and evidence.
In this analysis, event date can help locate the original contested event. Counsel should ask who created the record, whether it is complete, whether its legal status changed and what a careful reader can reliably conclude from it. description can then be compared to that event. A contradiction is worth explaining, but it is not itself proof of a rights violation without context.
Next, actor and source id should be tested against the same chronology. The purpose is to see whether the account holds together when each document is treated on its own terms. If a record contains hearsay, a summary of another person’s account or an opinion rather than direct observation, identify it as such. Finally, verification status and confidentiality level should be assessed for corroboration and safe disclosure. The resulting evidence map can identify which additional documents are worth seeking lawfully through local counsel or appropriate information requests.
What a careful adviser should not promise
Do not persist the chronology server-side without an approved secure intake system. A responsible scope of work can specify research, fact checking, drafting, translation management, legal coordination or monitoring of published results. It cannot promise that UN experts will accept a submission, send a communication, register a treaty-body case or obtain the requested national outcome. Nor can it imply private influence with UN officials.
Interactive tool: required user experience
The page must contain an actual working interactive module, separate from the narrative explanation. Build the minimum viable feature around human rights case timeline builder, with filters or editable rows that match this page's purpose. Use the existing website's component system and accessible input controls; keyboard operation and mobile behaviour are acceptance criteria.
- Primary interaction: start without user login; users can select or enter the information relevant to UN human rights case timeline builder.
- Source handling: for public research, every displayed result links to its official source and carries a verified ingestion date; show an honest empty state when no verified records are present.
- Privacy: no transmission of user timelines, risk narratives, witness records or submitted names to analytics or third-party LLM APIs.
- State reset: provide visible Clear / Reset and working Export where the interaction creates a user-generated dataset; prefer local browser memory over persistent cloud storage.
- Failure behaviour: show a non-misleading explanation if source data or an optional API is unavailable; link to the official public search rather than generating synthetic records.
- Feedback: label every output as research assistance or document organisation, not legal eligibility, success probability or a UN decision.
| Test case | Expected behaviour | Release gate |
|---|---|---|
| No imported public records | Clear source-unavailable state with official source links | No fake entries or invented identifiers |
| Invalid or incomplete user input | Plain-language inline validation | No silent data loss |
| Mobile keyboard and screen-reader access | Controls labelled and reachable | Accessible without hover-only affordances |
| Personal case data entered | Data stays local unless user explicitly opts into a separately secured service | No analytics leakage |
Questions commonly asked
Is this an official United Nations service?
No. It is an independent research or document-organisation tool. Official UN source links are identified clearly.
Does it have access to confidential case status?
No. It should only use published source records or data the visitor explicitly enters. Do not infer unpublished activity.
Can I use it without creating an account?
The MVP should support essential public research or client-side operations without registration. No sensitive server-side storage is allowed by default.
Does the tool decide legal eligibility?
No. Its role is navigation, evidence readiness or source exploration. Independent professional review is needed for legal conclusions.
How independent assistance may help
An initial screening can produce a short route memo identifying potentially relevant mechanisms, outstanding documents, time-sensitive national options, and precautions concerning public disclosure. If the matter is suitable, a scoped engagement may cover chronology review, annex indexing, legally accurate drafting, independent professional verification and coordination with authorised local advisers. It should be explicit which work is legal representation and which work is factual or research support.
For Human Rights Case Timeline Builder, the final recommendation should be able to answer: what is supported, what remains uncertain, which institution has the power to take a relevant step, and what practical measures must happen outside the UN system. The source record should stay available to the applicant, with clearly identified assumptions and limitations.
Next step: Request an independent case assessment. Provide a short non-sensitive outline first; secure document transfer, confidentiality and representation checks must be arranged separately when necessary.
Related guidance
- Un Submission Case Chronology
- Evidence And Case Documentation
- Evidence Readiness Checker
- How We Work
- Research Centre
Official sources and verification
- OHCHR Special Procedures submission guidance
- OHCHR current thematic mandate list
- OHCHR Special Procedures Communications Database
- UN Treaty Body JURIS database
- OHCHR Universal Human Rights Index data
Editorial verification: Reviewed against the source register on 6 November 2026. Re-check mandate status, applicable working methods, the identity of any mandate-holder, treaty acceptance and disclosure conditions immediately before public release and before preparing a real submission.
UN Human Rights Claims is an independent information and professional-services website. It is not an official UN or OHCHR website and has no privileged access to UN decision makers. Educational content is not personal legal advice.