CACrown ArchivesThe cinema collection
Menu
Research dossier · People & Ideas

Sukhmani Sadana

Indian writer and actress (b. 1980

Correspondence, annotated notebooks and portrait silhouettes prepared for research
People and ideasInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionJun 1, 2026
Entity authorityQ16832091 ↗
Source-derived summary

Sukhmani Sadana is an Indian writer and actress from Amritsar. She is the editor-in-chief of a digital magazine called F.A.C.E. She played the role of Uttara Bakshi in the TV series Khotey Sikkey that aired on Sony Entertainment Television.

Early life

Sadana attended Welham Girls' School, Dehradun and graduated from Lady Shri Ram College, Delhi University. She also studied at St. Xavier's College, Mumbai, Mumbai.

Career

She worked as a copywriter in Ogilvy, Mumbai writing ads for brands such as Vodafone.

Editorial summary

The public source identifies “Sukhmani Sadana” as indian writer and actress (b. 1980. This brief keeps that definition visible, then builds a research path around Sukhmani, Sadana and Indian.

Editorial reviewA productive starting point for separating a subject’s documented career from later reputation and commemoration. The current 81-word lead offers orientation but no explicit four-digit date, so chronology should not be assumed. The linked authority record independently contributes the date 1980-10-16. Its value is orientation rather than verdict, with Sukhmani, Sadana and Indian providing the first useful test.
Editorial analysis

Why this record matters

A short description can identify a subject without explaining its stakes. For “Sukhmani Sadana”, the useful work is to connect “indian writer and actress (b. 1980” to the records capable of establishing context and consequence.

Evidence profile

Chronology provides the most reliable spine for this subject; interpretation should follow only after identities and dates are secure. The source revision retrieved here is dated Jun 1, 2026. The linked authority identifier is Q16832091. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank.

Critical limits

Later biographies can compress uncertainty and repeat inherited reputations, so apparently settled claims may still require comparison. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Read biographical claims against dates, named institutions and the cited references. Distinguish a subject’s later reputation from evidence produced during their lifetime.

Best used for
  • Establishing names and roles
  • Building a first chronology
  • Locating cited institutions
Verify next

Personal papers, civil or court records, institutional files and the scholarship cited by the source.

Three-step research path

  1. Establish the record: confirm the title “Sukhmani Sadana”, its source revision and the description used here.
  2. Expand the search: follow Sukhmani Sadana primary sources, Sukhmani Sadana archive and Sukhmani research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Sukhmani Sadana”?
  2. Which claims depend on a single source or contested interpretation?
  3. How has the subject’s reputation changed across later accounts?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from “Sukhmani Sadana” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.