PEOPLE

Everyone you work with.
One record each.

People is not an employee directory with extras bolted on. It is the shared record of every person your company deals with, and every capability you add writes to it rather than starting a directory of its own.

See Cordango in action → How a person record grows →
EMPLOYEE CONTRACTOR CONTACT APPLICANT ONE PERSON RECORD Lena Kraus ONE PROFILE ONE HISTORY FIG.00 — 4 RELATIONSHIPS · 1 RECORD
FIG.01

An HR system only knows the people you employ.

— the problem

Most companies work with far more people than they employ. Customer contacts, subcontractors, freelancers, applicants, partner staff. The HR system covers a fraction of that, so everything else ends up in a CRM, a spreadsheet or somebody’s head.

That is why offboarding is hard. When someone leaves you have to remember every system that mentions them, and the ones nobody owns are the ones you miss.

  • ALL Employees, contacts, contractors, applicants and partners in one place
  • ONE One record per person, whatever their relationship to you
  • TEAM Real reporting lines and teams, not a flat list
  • OFF One place to end access when someone leaves
People · the usual stateAny company
# where does a person live? > Lena Kraus ? HR system → employee · start date · manager ? CRM → a contact at a customer, entered twice ? project tool → a name typed into an assignment ? contractor sheet → rate, availability, no link to anything ✗ she left four places to remember · three of them missed
FIG.02

The person record grows as you add capabilities.

You are not buying a Cordango version of one HR suite. You are starting with a people foundation that can take on the parts of HR, resource planning and contractor management you actually need.

FOUNDATION
Person
Name and contactOrganizationTeamRoleManagerRelationshipActivity
+ PTO & Absencetime
RequestsApproval statusUpcoming absenceWho is out
+ Projectsdelivery
AssignmentsWorkloadResponsibilitiesDelivery history
+ 360 Feedbackdevelopment
CyclesParticipantsSubmitted feedbackReview history
+ Skillscapability
SkillsCertificationsExpiry dates
+ Equipmentassets
Assigned devicesIssue dateReturn status
+ Recruitinghiring
ApplicationsInterview historyOffer status
Add absence and the person gains requests. Add projects and the same person gains workload. It is one record getting richer, not six systems to reconcile.
FIG.03

Not every person on your books is an employee.

A contractor needs a rate, an availability window and a project assignment. A customer contact needs a company, a role and a history of what you discussed. An applicant needs a pipeline stage. None of those fit an employee file, and all of them are people you work with.

Cordango keeps them on one foundation with different relationships, so a contractor who becomes an employee is the same record with a changed relationship, not a fresh row and a lost history.

  • REACH Access follows your team structure, and it flows down, never up
  • FIELD Field-level permissions, so a salary is not visible to a project lead
  • LOG Field-level history on the record, without modelling an audit entity

How this works for companies →

People · four relationshipsCordango GmbH
# the same foundation, different relationships ✔ Mara Lindqvist employee · delivery team · on the Aurora build ✔ Jonas Beck contractor · day rate · available from March ✔ Dr. Anke Roth contact at Nordwind · signs off the contract ✔ Sami Haddad applicant · second interview Thursday → one people foundation one permission model · one history
FIG.04

Shape it around your company.

The parts of working with people that every company shares arrive built. The parts that make you different, you change.

DATA

Fields and terminology

Track what you actually track. If your consultancy needs a security clearance date and a chargeable rate on the same record, add both.

TYPES

Relationship types

Define who counts as what. A working student, a subcontractor and a partner consultant are different relationships with different rules.

RULES

Process and approvals

Who approves an absence request, who confirms a start date, what has to be true before someone gets access.

VIEW

Screens per role

A manager sees the team and the absence calendar. The person sees their own file. HR sees the employment detail. One record.

NEXT

See it with your own org chart.

Bring the way your company is actually structured, including the contractors and the partner staff. We will show you what it looks like when all of them sit on one foundation.

See Cordango in action → The platform underneath →

About 30 minutes, on a real company platform