QASWAThe problem
HR leadership runs on the same inbox, calendar and meetings as any executive — plus a question no inbox answers: across every community, which new hires are falling behind on their onboarding, from Day 1 to Day 90? And HR data is where a careless report can expose a person.
What we built
A sibling of the CEO's Chief of Staff for Heritage's HR leadership, running inside the same Microsoft 365 and Azure tenancy. It reads the signed-in leader's own mail, calendar and meetings, and adds HR intelligence: onboarding milestones from the training platform and workforce figures from the HR systems, folded into one row per community.
“Qaswa has delivered five platforms for us across four departments, all running inside our own Azure environment. What stands out is the discipline: every number ties back to the source, and nothing changes in our systems unless one of our people approves it.”
Farhan Khan, CEO, Heritage Communities · 
How it works
- Today: a morning briefing, inbox triage with drafted replies, compose, and an in-app reader
- Talent Tracker: overdue onboarding milestones from Day 1 to Day 90, by community and by stage — with a Monday email to HR leadership
- Meetings: minutes, catch-up and attendance; every AI-extracted item carries a verbatim quote from its source
- Five scheduled email digests — morning, evening, weekly, monthly and the Monday talent report
- Opens as a personal tab in Microsoft Teams
HR data stays aggregate
- No employee name, ID, email, comment or individual risk flag ever leaves the server — HR records are reduced to team and community totals first
- New data endpoints ship with a privacy test that fails if a name or ID appears in the response
- No resident or health data; read-only, aggregate views only
Security and control
- Delegated permissions only: no application roles, and zero secrets on the app registration
- Replies are staged in the person's own Drafts; sending takes an explicit two-step confirmation by the signed-in person, and the assistant itself has no send path
- Scheduled digests go out from Heritage's own verified domain, never in a person's name
- Everything stays inside Heritage's Microsoft 365 and Azure tenancy