Lineage
Your clan genealogy, kept as a living register — sourced, searchable and open to descendants.
Lineage records generations and branches from your founding ancestor, cites every entry back to its source, and decides who counts as a clansman by rules you set. Descendants find their place on a public genealogy site and claim it.
- Generation · Branch
- generations and branches
- Simplified ⇄ Traditional
- surname matching
- 0
- living people shown to the public
What you're doing today
The paper register, the spreadsheet nobody quite trusts, the phone calls asking a question the record could have answered.
A genealogy only the compiler can read
Years of work live in one committee member's handwriting, or in one person's memory of where things are.
No way to prove where an entry came from
A name in the book with no citation back to its source is a claim, not a record.
Descendants who don't know where to look
Someone descended from the clan has no way to search for their own place in it.
族谱 — the printed genealogy book
- 世
- 房
- 名讳
- 配偶
- 子女
- 出处
- 世
- 第十八世
- 房
- 二房
- 名讳
- 锦堂
- 配偶
- 黄氏
- 子女
- 文彬、文华
- 出处
- 族谱 卷三 · 页 42
Each person keeps a citation back to the page of the book they came from.
How it works
From your existing register to a record your team and your community can both rely on.
Enter what the book already has
Generations, branches and unions come in from your existing genealogy book, each with a citation to its page.
Set the rule for who counts
Eligibility for clan membership or benefits is written once as a policy, not decided case by case.
Descendants search and find their line
The public genealogy site lets anyone search a name and follow their ancestors upward.
A claim, verified by email
A descendant asks to be linked to their place in the tree; verification happens before it's confirmed.
What it does
A closer look at the capabilities behind the register — grouped by what they're for.
Generations and branches
Generation and branch, recorded properly
People are placed by generation and branch, with unions and descent recorded from the founding ancestor forward.
A visual line to the founding ancestor
Follow any person's ancestry upward, generation by generation.
Simplified/traditional surname matching
A surname typed in simplified characters is found under its traditional form too, so a search never depends on which script the visitor uses.
Sourced and reproducible
Every entry cited
Each person ties back to the genealogy book, page or document that names them, so a claim about descent is never just a claim.
Eligibility, decided by rule
Determinations are recorded, so the same person gets the same answer every time the policy is applied.
Import from what you already have
Bring in existing genealogy records to speed up entering a book that's already compiled.
Public, but not exposing
Living people masked by default
Only the deceased, and the generational structure around them, are shown on the public site.
A claim, verified before it's linked
Descendants submit a claim to their place in the tree, checked by email before it counts.
One register, one truth
The genealogy committee works from the same data the public site reads — there's no second copy to fall out of step.
Its public site
A genealogy descendants can search
yourclan.zupu.bizcare.myDescendants search by name, follow a person's ancestors and submit a claim to their place, verified by email. Living people never appear.
- Search ancestors
- Follow a line
- Claim a place
- Living people hidden
Your own 族谱 site, your own domain
yourclan.zupu.bizcare.my is ready as soon as Lineage is switched on. Bring a domain you already own — zupu.yourclan.org.my — and the certificate is handled for you.
- Ancestor pages and the claim form work the same on either address
- No hosting or renewal on your side
Ready today
Bring your own
Behind the scenes for your team
The day-to-day workflows a register alone doesn't cover.
Reviewing a claim
A descendant's claim to a position in the tree sits with staff for verification before it's linked.
Setting eligibility policy
Write the rule once — by generation, branch or descent — and every determination against it is recorded for later reference.
Correcting the record
An entry can be amended as new information comes in, with the correction and its source both on file.
Reports and getting your data out
What a committee meeting or an accountant asks for, without a spreadsheet in between.
A citation for every entry
Anyone reviewing the genealogy can see exactly which page or document backs it.
API access for the committee's own tools
Read the tree through the REST and GraphQL APIs if your genealogy committee wants to build something on top of it.
An activity log on every entry
Additions and corrections are kept on the record, so the history of the genealogy itself is not lost.
Built to be trusted with the records that matter
The same protections that run under every module in BizCARE CRM, applied here.
PDPA consent on record
Consent is captured at the moment someone applies or registers, and the answer stays on that record — a living descendant's contact details is shown only where a staff member's role allows it.
Roles & field permissions
Roles decide which modules and records a person reaches; field permissions go further — who sees a living descendant's contact details and who does not is a setting your organisation controls.
Audit trail
Who changed what, and when, is kept on the record itself, ready for a committee meeting or an audit to review.
English & Chinese
Staff switch the interface language at any time, and most public pages read in both; Chinese names are kept exactly as entered, with no romanisation.
Who it's for
Clan associations
A genealogy committee's work kept as a register the whole clan can use.
Ancestral halls
Ancestral halls that want the descent behind every tablet written down.
Families compiling a genealogy
A book in progress, kept as records instead of loose pages.
Questions about this module
More module-specific answers sit in the full FAQ below.
Will living relatives appear on the public site?
No. Living people are masked by default; only the deceased and the generational structure around them are shown publicly.
How does someone prove they belong to the clan?
Eligibility is decided by a policy your committee sets once — by generation, branch or descent — and the same person gets the same answer every time it's applied.
Can we bring in a genealogy we already have in a book?
Yes — enter it directly, or talk to us about importing from records you already hold, with citations kept intact.
What if a descendant claims the wrong ancestor?
A claim is verified by email and reviewed by staff before it's linked; nothing on the tree changes until then.
Does a simplified-character search find a traditional-character entry?
Yes — surname matching works across simplified and traditional characters, so both forms of the same surname are treated as one name.
Works well with
Membership
Your member roll, your association's website and its join form — kept as one.
See the moduleMemorial Registry
Every niche, tablet and urn — registered once, findable by every family.
See the moduleOutreach
Reach members where they already read — on WhatsApp, paced and properly consented.
See the moduleBring your paper ledger. We'll show you.
Tell us how your organisation keeps its records today — whatever kind of organisation it is — and we will walk you through the CRM and the modules that fit.