Programs
Create, edit, archive and delete programs. Each one carries an owner, a start and target date, a written objective, a description, progress, and a health rating. Archiving keeps the record without cluttering the active list.
Features
Every part of a program, in one place
Kharazm holds the whole picture of a program: the plan, the work, the people, the risks, and the update you owe your stakeholders. Everything below is in the product today — nothing on this page is a roadmap item.
4
Access levels, enforced on the server
2
Ways to work: board and list
4
Views of the same work
0
Third-party trackers or analytics
Programs & portfolios
Structure that matches how program work is organized
A program is the unit everyone recognizes — a cross-functional launch, a grant-funded initiative, an operational change, or a learning and development program. Portfolios group related programs so a leader can see a whole area at once.
Portfolios
Group related programs into a portfolio — everything funded by one grant, everything owned by one division, everything running in a single fiscal year. Useful when you report upward and need a roll-up rather than a per-program list.
Multi-tenant workspaces
Each organization is its own workspace and the intended security boundary. A session is scoped to one workspace at a time; server reads and writes use that organization scope, and automated tests cover cross-tenant isolation. If you run programs for several entities, keep a workspace for each.
Work management
Board and list, over the same tasks
Some people think in columns; some people think in rows. Kharazm gives you both views of the same work, so nobody has to keep a private spreadsheet on the side.
Board view
A Kanban board with a column for each status: To do, In progress, Review, Done. Move a task and its status changes for everyone.
List view
The same tasks as a scannable list — better for reviewing priority, status, assignees and due dates together, and for anyone who finds a board hard to read.
Blocked work is explicit
A task can be flagged as blocked. The flag stays visible with the task and is counted in the reports view, so a manager can include it in the next update.
What a task holds
- Status — To do, In progress, Review, Done
- Priority — urgent, high, medium, low
- Assignee — one named owner, or none
- Due date — used to show timing and overdue work
- Labels — your own vocabulary: site, vendor, audience, workstream
- Blocked flag — with the reason kept in the discussion
- Comments — task discussion kept next to the work
Statuses shown in the product as badges: To do In progress Review Done
Planning
Milestones, a timeline, and the shape of your delivery
Programs depend on dates: the kickoff, a decision point, the go-live, the reporting deadline. Kharazm makes those dates visible without asking you to rebuild the plan in another tool.
Milestones
Named dates that matter — policy approval, pilot launch, cutover, audit submission. Milestones sit on the program and appear as diamonds on the timeline, keeping critical dates out of a buried task list.
Timeline view
A Gantt-style due-date view with month gridlines, a marker for today, status-coloured bars and milestone diamonds. Task bar starts and spans are visual estimates because tasks do not yet store start dates, durations or dependencies.
Workflow view
A delivery flow chart with live counts at each stage. It shows where work is piling up — a queue in Review usually means one reviewer is the bottleneck — and each stage links straight into the board so you can act on it.
Risk & health
Review risk against the work that is actually recorded
Program health is a manager's judgment. Kharazm keeps the dates, blocked flags, owners, milestones and RAID register beside that judgment so it can be reviewed rather than treated as an unexplained score.
Delivery evidence
The reports view counts four categories directly from current workspace data. Automatic alerts and forecasts are not part of the current product.
- Overdue — the due date has passed and the task is not done
- Blocked — someone flagged the task as stuck
- Unassigned — nobody owns it
- Open risks and issues — RAID items that have not been resolved
Risks & issues (RAID)
A proper register for the things a task list cannot hold: risks, assumptions, issues and decisions. Each entry has an owner, a due date, and a resolution — and can be reopened if the problem comes back.
This is where "the vendor may not deliver the SCORM package on time" and "we assumed supervisors would release staff for the session" live, so they are still on the record when someone asks in month four.
Explainable program health
Every program carries one of four manager-recorded ratings — On track At risk Off track Not started. The nearby tasks, milestones, reports and RAID log give reviewers context, but Kharazm does not calculate or lock the rating automatically.
Collaboration
Keep the conversation next to the work
Decisions made in email threads are lost by the time you need them. In Kharazm the discussion is attached to the thing being discussed.
Task comments
A chronological discussion on every task, in the style people already know from issue trackers. Ask a question, record why a date moved, or note who approved the content in the place someone will look for it later.
Activity history and search
Recent workspace activity stays visible, and global search finds programs, portfolios, tasks and people. An inbox surface exists, but fresh workspaces do not yet generate notifications automatically.
Global search & keyboard access
Search across the workspace to find a program, a task or a person quickly. The interface is keyboard-accessible throughout, which matters for accessibility obligations in public-sector organizations.
People & access
Four access levels, enforced on the server
Access is not a client-side convenience. Every write goes through one shared rule set that runs on the server, with the actor taken from the signed-in session and never from the request. A viewer who forges a request is rejected.
| What you can do | Viewer | Member | Manager | Admin |
|---|---|---|---|---|
| View programs, tasks, timeline, reports | Yes | Yes | Yes | Yes |
| Use global search | Yes | Yes | Yes | Yes |
| Edit tasks and change task status | No | Yes | Yes | Yes |
| Comment on tasks | No | Yes | Yes | Yes |
| Raise and resolve risks & issues | No | Yes | Yes | Yes |
| Create and delete tasks | No | No | Yes | Yes |
| Edit and archive programs; manage milestones | No | No | Yes | Yes |
| Write and publish weekly stakeholder updates | No | No | Yes | Yes |
| Create and edit portfolios | No | No | Yes | Yes |
| Create and delete programs; delete portfolios | No | No | No | Yes |
| Add, edit and remove people; set access levels; invite by email | No | No | No | Yes |
| See the organization's audit log | No | No | No | Yes |
Access levels are cumulative: admin includes everything a manager can do, manager everything a member can do, and member everything a viewer can do.
Team page with a reporting hierarchy
Record who reports to whom. That structure is not cosmetic — it is how you find out whose team is carrying an unreasonable share of the delivery, and who to escalate to when a task has been blocked for three weeks.
Open tasks by person
See each person's current open-task count beside the reporting hierarchy. It is a simple assignment snapshot, not capacity, effort, availability or utilization forecasting.
Invitations by email
Admins create an invitation with the access level already chosen. When transactional email is configured, the token link is emailed; otherwise the admin can share the generated link securely. Password-reset links also require configured email delivery, work once for one hour, and revoke every existing session when used.
Initial registration is approval-gated. A person who is not signed in can request their first workspace, which an operator reviews. Teammates with an invitation join directly, and an already signed-in user can create an additional workspace without another operator review. Read more on access and pricing.
Reporting & accountability
The weekly update, without the last-minute scramble
Many program teams write updates by hand, pulling numbers out of a spreadsheet and hoping nothing changed since. Kharazm builds a draft from the work itself, then preserves what you publish.
Foundations
What sits under all of it
The parts you should not have to think about, stated plainly.
Tenant isolation
The organization is the security boundary, and cross-tenant isolation is covered by tests.
No browser trackers
No analytics, trackers, ad tech or external fonts run in the browser. The hosted service still uses Fly.io, Neon and optional Resend as disclosed in the privacy policy.
Sessions you can reason about
Opaque tokens stored only as a hash, in an httpOnly SameSite cookie, expiring after 14 days.
Plain language
The interface avoids project-management jargon so non-technical staff can use it without training.
See it against your own programs
Kharazm is early and has no customers yet. If your team runs visible, multi-step programs and owes stakeholders a reliable account of progress, we would like to hear how you work.