Fictional example: relationships between records, not automatic discovery of every connection.
1. Start with a question, not another list
All company names, people, identifiers, applications and records in this example are fictional. Alder Works wants to understand what must be reviewed when Maya Chen moves from Design to Operations. HR has a person record, IT has a device list, and Finance has a licence allocation. Each list can be accurate while the overall picture remains incomplete.
The operational question is not simply what Maya owns. It is which assignments, access decisions and financial responsibilities need review, who should decide, and which facts are sufficiently current to support that decision.
2. Read the relationship map as a conceptual model
The following text map is an accessible conceptual diagram, not a claim that every illustrated relationship is automatically created or available in Lojycal. Each arrow names a relationship that the fictional team must substantiate.
- Person Maya Chen → is associated with → identity maya.chen.
- Device AW-014 → is assigned to → person Maya Chen.
- Identity maya.chen → has an account in → application Draftspace.
- Licence allocation LIC-027 → covers → the Draftspace account.
- Licence allocation LIC-027 → is charged to → cost centre Design.
- Evidence record EV-108 → documents → a review of that licence allocation and its supporting sources.
3. Separate imported facts from manual entries
Imported data originates in a connected source. In this fictional example, an HR export supplies Maya's department and an identity source supplies account status. Importing establishes provenance, not guaranteed correctness: a source can be stale or its mapping wrong.
Manually entered data is supplied by a person rather than retrieved from that source. A finance administrator enters Design as the licence's cost centre and records the allocation basis. Preserve the entry's author and date where available. Do not present this manual allocation as provider-confirmed billing data.
4. Keep inference, verification and unknowns distinct
Inferred data is a conclusion drawn from relationships rather than an observed source fact. The team might hypothesise that Maya's licence should move to Operations because her department changed. That is a review suggestion, not proof of the correct accounting treatment or a claim of an implemented automatic inference mechanism.
Person-verified data means someone checked a specific assertion against stated evidence at a particular time. Unknown data remains unresolved; a missing observation must not silently become a negative result.
- Verified: the application owner confirms Maya still needs Draftspace and dates the decision.
- Unknown: the available sources do not establish Maya's last meaningful application use.
- Still separate: confirming business need does not verify payment, device possession or effective access.
5. Use Lojycal to support investigation, not assumptions
Lojycal brings inventory, licence, finance, employee workflow and evidence modules into a connected workplace operations platform. Confirm the supported fields, relationships and actions for your plan and workspace before relying on this example as a workflow design.
Supported employee integrations include Personio and BambooHR lookups and writes with preflight confirmation and re-read verification. This does not mean your workspace has a live connection or that every provider supports every action. Permissions, mappings, credentials and organisational roles constrain what can be retrieved or changed.
6. Test the chain before acting on it
For Alder Works, the next step is a scoped review rather than an automatic transfer of every assignment. The licence may remain charged to Design under a shared budget agreement even after Maya moves.
- Select one authorised test case and identify the source of each field.
- Check identifiers and conflicting values before accepting a person-to-account match.
- Assign owners to verify access need and financial allocation separately.
- Inspect how unsupported relationships and unknown values are represented.
- For any approved change, check the resulting source state and retain an appropriately scoped review record.