Tassqi
ProductProject managementDelivery guidePrivacyTermsImprint
Product guide

Project management from commitment to acceptance

Tassqi connects owned tasks, dated commitments, decisions, deliverables, evidence, and explicit acceptance. Project managers can inspect what changed and what still needs a decision. Contributors handle their assigned work in My Work.

Last updated: 11 October 2026

By BITS Blackrock IT Solutions LLC, Tassqi's operator in Alexandria, Egypt.

Who Tassqi supports

The project manager needs an explanation before a status call: which commitments changed, who owns the next move, and what evidence supports delivery. Contributors need a clear list of their tasks and decisions, with fewer competing views to interpret.

Workspace roles control access and actions. Viewer and guest access is limited by the permissions and project scope granted to them. An invitation does not make someone a project manager or an administrator.

Start with an outcome, an owner, and a date

Create the project outcome, then record the work as owned tasks. A dated task is a commitment. Board, list, and timeline views show that work; My Work gives each contributor their assigned tasks and open decisions.

When a commitment needs a decision, resolve it as done, choose a new date with a reason, or drop it with a reason. The decision history preserves the explanation. Unanswered decisions can escalate through the configured timing and ownership path.

Connect completed work to an accepted deliverable

A task marked done records a work decision. It does not prove that the result meets the project's acceptance criteria. Deliverables connect the expected result to the relevant work, evidence, submitted revision, and review.

Record evidence for the deliverable, submit the revision for review, and record acceptance or rework. Before closing the project, inspect its closure checks rather than treating a full task board as proof of delivery.

Follow the delivery and acceptance guide for a practical example of that distinction.

Review the recorded facts before reporting

The cockpit brings commitments and open decisions into the PM's review. Project views retain risks, milestones, and decision history. Reports draw on activity recorded in Tassqi, so work happening outside the system still needs to be recorded before it can support an update.

A signal identifies something to investigate. It is not a guarantee of project health, a prediction that every deadline will hold, or a substitute for the reviewer's judgment.

AI is optional

Core project management works without AI. The optional Tass pilot requires workspace activation, configured access, and the relevant budget. AI-created tasks remain drafts until confirmed, and external or irreversible AI actions require approval.

Publishing working rules does not enable automatic follow-ups. Available task rules and commitment escalations have their own configuration.

Start with your first project

Create a Tassqi account, define the outcome, and assign the first commitment. Creating an account does not start a paid subscription. Paid service requires an authorized administrator to accept the price and billing terms.

Check current access and pricing, or sign in to your workspace. Read the privacy policy before adding project information.

© 2026 Tassqi
PrivacyTermsData deletionImprint