Loading page
Joining, commitments, evidence, visibility, resolution, and support.
Choose Programme for assignments, submissions and reviews. Choose Project team for a backlog, board, sprints and dependencies alongside the same tasks, evidence and outcomes. A workspace can contain cohorts of either type; choose the type when creating the cohort.
Yes. Organise and reprioritise backlog items, update their workflow status, and move them between sprints as plans evolve. Planning status is separate from an accepted task's outcome. Moving an item or marking it done on the board does not change a task deadline, submit evidence or record an outcome as delivered.
A dependency shows that one planned item is blocked by another in the same cohort. It makes the order of work visible; it does not automatically extend accepted task deadlines or pause outcome processing. Circular dependencies are rejected.
Open Today inside a cohort for pending invitations, members without tasks, approaching deadlines, evidence awaiting review, open support requests and recorded delivery issues. These are factual work queues, not participant rankings.
Organisers can address all active members, selected members, or members with open tasks. Recipients are fixed when the message is saved. Scheduled announcements publish on the first background processing run on or after the chosen date. Email provider acceptance is separate from a recipient marking a message read or acknowledging it.
Open Support in your cohort. Requests and replies are private to you and authorised programme organisers. Your assigned staff contact is shown where available. Asking for help does not extend a task deadline or pause its outcome.
Yes. Under Tasks, open Draft tasks and task sets. Save and edit organiser-authored drafts, group them by set name, and copy a set from another cohort you manage. Assignment requires active participants and a valid deadline. Draft edits never alter tasks already assigned.
Download an ICS calendar or create a private subscription link on the Calendar page. The link grants access to the programme and task titles visible to you, so share it only with a calendar provider you trust. Replacing or revoking it stops future access, but cannot delete copies already downloaded. Session changes do not change task deadlines.
Resources holds organiser-provided HTTPS links and descriptions, grouped by topic or week. These shared materials are separate from confidential task evidence. Access permissions at the external document or video service still apply.
An organiser creates cohorts, sets capacity and the deadline to join, invites people, creates programme tasks, monitors participation, reviews outcomes, and downloads reports. Settings stay editable while a cohort is a draft. After a participant accepts a task, an organiser can still extend its deadline or correct it before it is due, with a recorded reason.
Organisers create tasks from the cohort's Tasks page and assign them to participants. During the current transition, a cohort may also allow participants to create their own measurable task. Every task states the target, due date, evidence requirement, and whether a verifier must review it.
A participant submits the numeric result requested by the task and the evidence allowed by its accepted terms. That can be a written note, an HTTPS link, or direct private uploads of images, documents, and videos. Evidence stays private and is excluded from cohort exports.
A verifier sees only reviews assigned to them. They decide whether the submitted evidence meets the stated evidence requirement. They do not change the task, advise the participant, or decide a different target.
An organisation creates a cohort and gives you an invitation. Creating an Outcomark account does not itself grant programme membership. Open the invitation while signed into the account you intend to use, review the programme and role, then accept it.
Organisers can change a draft cohort's name, capacity, join deadline, programme dates, and defaults. They can also create and manage future work. Once a task is accepted, an organiser can extend its deadline, or change its wording and target until evidence is submitted, from the task's page. Every change needs a written reason, is recorded with who made it and when, is shown to the participant, and is counted in the programme record. A deadline can only move later, and nothing can change after the deadline has passed.
Yes, if an organiser grants one before the deadline, for example for documented illness or an agreed adjustment. The original deadline and the reason stay on the task's record, and the programme record counts every extension. Once a deadline has passed, the outcome is recorded and cannot be changed.
The task may allow a numeric result, private text, a private HTTPS link, or multiple evidence items including direct private uploads of images, documents, and videos. Files upload to private storage with a short-lived signed capability. Evidence is confidential and is not included in summary exports.
Evidence must be submitted before the displayed deadline; after it, the participant can no longer change anything. The automatic outcome processing service then compares the submitted result with the accepted target and records the result. Where the task requires review and evidence was submitted, the outcome waits for the reviewer's decision, which can be made after the deadline. Processing runs at least once a day, so a result can appear up to a day after the deadline.
Programme tasks and results remain in authorised cohort dashboards and reports according to the accepted audience. Evidence remains confidential. Public record directories and personal public-record pages are unavailable. The one exception is a checkable programme record an organiser chooses to issue, which holds cohort counts only; see below.
On a cohort's Reports page, open the programme record and choose Issue a checkable copy. The counts are frozen as they stand, cannot be edited, and are printed with a check link and a fingerprint. Anyone holding the link sees the same counts and cohort terms held by Outcomark. It contains no names, email addresses, task text, evidence or feedback. Issued copies stop answering if the workspace is deleted.
Yes. Open Tasks and choose Closed. It lists every task of yours that has closed, with the terms you accepted and the outcome recorded, and can be printed or saved as a PDF. Only you can see it; it is not published and has no share link.
The workspace overview shows every opened cohort you run side by side: participants, tasks, and how many are open, delivered, not delivered or closed. It shows counts only, ordered by start date, with no ranking.
A workspace owner can connect one Slack or Teams incoming webhook under Settings. Once a day, when there is anything waiting, it posts per-cohort counts of evidence awaiting review, tasks due within three days with nothing submitted, and tasks past their deadline. It posts no names, email addresses or task text, and nothing is sent to participants.
A cohort is charged once, when you activate it. There is no subscription and nothing to renew or cancel. The first cohort of an organisation is free where it has ten or fewer participants, once per organisation; after that the bands are $400 up to 30 participants, $1,000 up to 120, and $2,400 up to 500. The bands are published at Pricing.
By the number of participants who have joined at the moment you activate, not by the capacity you set. Empty places do not count. If more people join between paying and activating and the cohort moves up a band, activation stops and states the difference. A cohort activated before charging began runs to its end at no charge and is never re-priced.
A cohort is refundable in full at any time before you activate it. It is not refundable afterwards, because activating closes enrolment and locks the roster, which is the point the run is delivered.
The band above 120 participants is invoiced rather than charged to a card. Ask through Contact and choose Procurement or a large programme. Smaller bands are paid by card before activation.
Open Account settings, go to Close account, and confirm the deletion. This is a direct action, not a request for manual approval. It is unavailable while you have an open task, and while you are the only owner of a workspace that other people use; transfer ownership or delete the workspace first. Where closed programme records must stay with the programme, your personal details are removed and the records are kept. The screen explains any blocker immediately. You can use Contact for a separate privacy request.
Activity is an in-app record of important programme events addressed to your account, such as invitation, evidence, and outcome events. It is not an email inbox. If nothing has been recorded for you, the page is empty.
An invitation link shown in Outcomark is ready to share, but it does not prove an email was delivered. Email is sent through Outcomark's email provider, and delivery depends on the recipient's mail server. Automatic outcome processing continues independently of optional messages. Use Contact if processing appears delayed.
Outcomark preserves earlier commitments and outcomes as historical account data, but no longer publishes them through a directory or personal public-record URL. They remain distinct from cohort records and cannot be rewritten to hide an outcome.
Choose Accessibility support on the contact form and describe the barrier or format you need. Do not paste private evidence, invitation tokens, passwords, or recovery links into the message.
No. It does not suggest goals, provide coaching or roadmaps, rank people, or use AI to judge evidence. Programme owners define the rules; Outcomark records and applies them consistently.
Still need help? Contact Outcomark.