A shift covered, a visit delivered, a job signed off, a load received, an inspection passed: these are outcomes, and the record is built from them exactly as it is from a shipped release. This page names them in each industry's own words, maps each to the event to report, and says who independently confirms it. It is rendered from the live catalog at /api/v1/outcome-templates, so it cannot drift from what the API serves.
An outcome counts as verified only when the third party named below confirms it. Not when your system recorded it, not when the worker says so, and not because you set a flag: your own record is not a witness. Everything else is still worth reporting; it simply counts as self-reported until someone else stands behind it. That single rule is why a Credda record means something when it moves to the next employer, and it is the same rule in every industry on this page.
The formula is identical for every kind of work. There is no per-trade calibration, no adjustment by sector, and nothing weighted by the prestige of an employer or a school: read it yourself at /api/v1/scoring/model.
Four kinds of third party, described so you can tell which one you have. They are descriptive only: the formula does not read them and no witness type is weighted above another. What varies is how hard each is for either side to influence.
A body with no stake in the job: a code inspector or authority having jurisdiction, a title/escrow agent, a state-mandated visit-verification record, a safety inspector, a certifying board. The hardest witness for either party to influence.
The party the work was done for, or who took delivery of it: a homeowner, a patient, a client, a consignee, a family. They know first-hand whether it happened.
The responsible party where the work happened, who is not the worker: a shift or site manager, a charge nurse, a dispatcher, a production manager, a reviewer. Distinct from the worker by construction; a worker can never be their own supervisor here.
A processor or marketplace that independently recorded a payer other than the worker. Money moving from a third party is evidence someone else was involved, never, on its own, evidence that the work was good.
On-time delivery is a large share of the score, and it is worked out from two fields and nothing else. Report that a shift was completed without them and it can count as completed, never as completed on time, which is usually the whole point. Each row in the tables below says what those two timestamps are for that outcome.
| dueDate | When the outcome was DUE: the booked shift start, the appointment time, the end of the delivery window, the agreed completion date. Timeliness is a large share of the deterministic score and is derived from this against completedAt. Report an outcome without these two and it can only ever count as completed, never as completed on time. |
| completedAt | When it ACTUALLY happened: the clock-in, the signed proof of delivery, the release of the vehicle, the sign-off, the settlement. For a negative outcome where nothing was delivered, leave this unset; the due date alone says what was missed. |
| stakeLevel | How much this outcome should weigh: LOW, MEDIUM (the default) or HIGH. Advisory. Automatically imported activity is capped below HIGH so an integration cannot manufacture high-stake evidence. |
| transactionValue | The value of the work, in whatever units you already use. Optional. Credda stores no currency and converts nothing; it is a relative weight, not an amount of money. |
| isVerified | Whether the named third-party witness confirmed this outcome. Never set it true because your own system recorded the job; your own record is not a witness. It becomes true when the witness acts: POST /confirmations, POST /references, or a per-record verifiedBy on ingest. Self-reported outcomes are still worth recording; they simply do not count as verified evidence. |
| metadata | Your own reference: work order, job number, visit id, load number, call sheet. Stored as given and never scored. It is what lets you reconcile a Credda event back to the record in your own system. |
Every industry here tracks failure numbers, and several of the most-watched ones describe something the worker did not do. Recording those against a person makes the record measure somebody else's action, and they have no way to answer it. Credda cannot see why a booking was missed, which is exactly why this is stated rather than assumed.
Copy a row straight into POST /api/v1/events. Where a confirmation channel mentions a scheduling, field-service or practice system, that is your software, named so it is clear the confirmation fits work you already do: Credda does not connect to it, and nothing on this page is an integration you have to buy. Not listed? The vocabulary is the same; pick the closest row.
Practices tracking whether scheduled care was delivered reliably. ?industry=dental_clinical
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Appointment completed as scheduled The clinician saw the patient at the booked time and completed the planned care. |
CONTRACT_FULFILLED MEDIUM stake |
The practice (front-desk/practice manager) or the patient supervisor_or_reviewer Confirm via the post-visit SMS/email the PMS already sends, or a manager sign-off in the console. |
dueDate = the booked appointment time; completedAt = when the clinician actually started the appointment. |
|
Procedure delivered to plan A specific procedure (e.g. a crown, a lab case) was delivered on time and to the agreed plan. |
TRANSACTION_COMPLETED HIGH stake |
The receiving party (patient, or the practice for a lab case) customer_or_client Confirmed by the counterparty who received the work, via a confirmation link. |
dueDate = the date the procedure or lab case was promised for; completedAt = the date it was actually delivered and seated/handed over. |
|
Unfilled shift / no-show A clinician or assistant did not show for a booked shift, disrupting scheduled care. |
CONTRACT_BREACHED MEDIUM stake |
The practice manager supervisor_or_reviewer Recorded by the practice; the worker is notified and can dispute. |
dueDate = the booked shift start; leave completedAt unset; nothing was delivered. |
Plumbing, electrical, HVAC, handyman and field-service companies. ?industry=trades_home_services
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Job completed and signed off The tradesperson completed the job and the customer signed off on the work. |
CONTRACT_FULFILLED HIGH stake |
The customer customer_or_client Confirm on the post-job SMS the field-service tool (Jobber/ServiceTitan/Housecall Pro) already sends. |
dueDate = the arrival window or promised completion date given to the customer; completedAt = when the customer signed off on site. |
|
Invoiced work paid The customer paid the invoice for completed work. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying customer (as recorded by the payment/marketplace processor) payment_or_marketplace Auto-verified when a third-party processor/marketplace records the payer as someone other than the worker. |
dueDate = the invoice due date; completedAt = the settlement date the processor recorded. |
|
Callback for defective work The customer required a return visit because the original work was defective. |
CONTRACT_BREACHED MEDIUM stake |
The customer customer_or_client Recorded against the job; the worker can dispute. |
dueDate = the original job date the work should have held from; leave completedAt unset. |
Electricians, plumbers, HVAC and other licensed trades where work is permitted and inspected. ?industry=skilled_trades_licensed
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Permitted work passed inspection Permitted work was completed and passed an independent code inspection. |
REVIEW_VERIFIED HIGH stake |
The code inspector / authority having jurisdiction (independent of the worker) independent_authority Confirmed from the inspection result recorded by the independent inspector/authority, the strongest witness available in the licensed trades. |
dueDate = the date the permit or contract required the work to be ready for inspection; completedAt = the recorded inspection date. |
|
Job completed and signed off The licensed tradesperson completed the job and the customer signed off. |
CONTRACT_FULFILLED HIGH stake |
The customer customer_or_client Confirm on the post-job link the field-service tool sends. |
dueDate = the agreed completion date; completedAt = when the customer signed off. |
|
Invoiced work paid The customer paid the invoice for completed licensed work. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying customer (as recorded by the processor) payment_or_marketplace Auto-verified when a third-party processor records the payer as someone other than the worker. |
dueDate = the invoice due date; completedAt = the settlement date the processor recorded. |
|
Failed inspection / code violation Permitted work failed an independent inspection for a code violation. |
CONTRACT_BREACHED MEDIUM stake |
The code inspector / authority having jurisdiction independent_authority Recorded from the failed inspection result; the worker can dispute. |
dueDate = the date the work was required to be code-compliant; leave completedAt unset. |
Technicians and shops repairing cars, fleets and heavy vehicles, where the industry already measures comebacks. ?industry=automotive_repair
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Repair order completed The repair was completed and the vehicle released to the customer. |
CONTRACT_FULFILLED HIGH stake |
The customer who collected the vehicle customer_or_client Confirm on the post-service link the shop management system already sends, or a service-advisor sign-off in the console. |
dueDate = the promised-ready time given to the customer; completedAt = when the vehicle was actually released. |
|
Repair order paid The customer or fleet account paid for the completed repair. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying customer or fleet account (as recorded by the processor) payment_or_marketplace Auto-verified when a third-party processor records the payer as someone other than the worker. |
dueDate = the invoice due date; completedAt = the settlement date the processor recorded. |
|
Work passed safety / emissions inspection The vehicle passed an independent statutory safety or emissions inspection after the work. |
REVIEW_VERIFIED MEDIUM stake |
The licensed inspection station or state inspector (independent of the shop) independent_authority Confirmed from the inspection result recorded by the independent inspector. |
dueDate = the date the vehicle was required to be ready for inspection; completedAt = the recorded inspection date. |
|
Comeback / repeat repair The vehicle came back for the same fault; the original repair did not hold. The industry’s own term is a "comeback". |
CONTRACT_BREACHED MEDIUM stake |
The customer who returned the vehicle customer_or_client Recorded against the original repair order; the worker is notified and can dispute. |
dueDate = the date of the original repair the work should have held from; leave completedAt unset. |
Caregivers, home-health aides and personal-care assistants delivering scheduled visits in someone’s home. ?industry=home_care_personal_care
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Scheduled visit delivered The caregiver arrived and delivered the scheduled visit on the care plan. |
CONTRACT_FULFILLED MEDIUM stake |
The electronic visit verification (EVV) record the agency is required to capture, or the client/family the visit was for independent_authority Confirmed from the EVV clock-in/clock-out the agency already captures for Medicaid-funded personal-care and home-health visits; an independently timestamped visit record is among the strongest witnesses in care work. The client or family can also confirm directly via a confirmation link. |
dueDate = the scheduled visit start on the care plan; completedAt = the EVV clock-in the agency recorded. |
|
Care period invoiced and paid A funded period of care was delivered and settled by the payer. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying agency or payer (as recorded by the processor) payment_or_marketplace Auto-verified when a third-party processor records the payer as someone other than the worker. |
dueDate = the end of the funded care period; completedAt = the settlement date the processor recorded. |
|
Client / family reference confirmed A client or their family confirmed the caregiver delivered care reliably. |
REVIEW_VERIFIED MEDIUM stake |
The client or their family customer_or_client Requested via a reference link the client or family responds to. |
dueDate = the end of the care period being confirmed; completedAt = the date the reference was given. |
|
Missed visit A scheduled visit was not delivered and the caregiver arranged no cover. The industry’s own term is a "missed visit". |
CONTRACT_BREACHED MEDIUM stake |
The scheduling coordinator or care manager at the agency supervisor_or_reviewer Recorded by the agency; the worker is notified and can dispute. A visit the AGENCY rescheduled, or the client cancelled, is not the worker’s outcome; see the catalog’s notTheWorkersOutcome list. |
dueDate = the scheduled visit start; leave completedAt unset; no visit was delivered. |
Nurses, techs, therapists and allied-health workers across shifts and visits. ?industry=healthcare_clinical
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Clinical shift completed The worker showed up on time and completed the full booked clinical shift. |
CONTRACT_FULFILLED MEDIUM stake |
The charge nurse or unit/staffing manager supervisor_or_reviewer Confirmed from the clock-in/clock-out the staffing tool records, with a charge-nurse or manager sign-off. |
dueDate = the booked shift start; completedAt = the actual clock-in the staffing tool recorded. |
|
Home-health visit delivered A scheduled home-health or therapy visit was delivered and billed as agreed. |
TRANSACTION_COMPLETED MEDIUM stake |
The patient/family or the paying agency customer_or_client Confirmed via the post-visit link the agency sends, or by the paying agency as recorded by the processor. |
dueDate = the scheduled visit time; completedAt = the recorded arrival or visit-verification timestamp. |
|
Supervisor reference confirmed A supervising clinician confirmed the worker performed reliably over an assignment. |
REVIEW_VERIFIED MEDIUM stake |
The supervising clinician or unit manager supervisor_or_reviewer Requested via a reference link the supervisor responds to. |
dueDate = the end of the assignment being confirmed; completedAt = the date the reference was given. |
|
Unfilled shift / no-show The worker did not show for a booked clinical shift, disrupting patient coverage. |
CONTRACT_BREACHED MEDIUM stake |
The unit/staffing manager supervisor_or_reviewer Recorded by the manager; the worker is notified and can dispute. |
dueDate = the booked shift start; leave completedAt unset. |
Veterinarians, vet techs and relief/locum staff covering booked clinic sessions. ?industry=veterinary
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Booked clinic shift covered The relief or permanent worker covered the booked clinic session in full. |
CONTRACT_FULFILLED MEDIUM stake |
The practice manager or lead veterinarian at the clinic supervisor_or_reviewer Confirmed by the practice via a confirmation link, or from the clinic’s own rota sign-off. |
dueDate = the booked session start; completedAt = the actual arrival time the clinic recorded. |
|
Relief booking paid The clinic paid for a completed relief booking. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying clinic (as recorded by the processor or relief marketplace) payment_or_marketplace Auto-verified when a third-party processor or relief marketplace records the payer as someone other than the worker. |
dueDate = the invoice or booking settlement date; completedAt = the settlement date the processor recorded. |
|
Practice reference confirmed A clinic confirmed the worker covered their sessions reliably. |
REVIEW_VERIFIED MEDIUM stake |
The practice manager or lead veterinarian supervisor_or_reviewer Requested via a reference link the practice responds to. |
dueDate = the end of the booking being confirmed; completedAt = the date the reference was given. |
|
Accepted booking dropped The worker did not cover a session they had accepted, leaving the clinic short. |
CONTRACT_BREACHED MEDIUM stake |
The practice manager supervisor_or_reviewer Recorded by the practice; the worker is notified and can dispute. A session the CLINIC cancelled is not the worker’s outcome. |
dueDate = the accepted session start; leave completedAt unset. |
Restaurants, cafés, hotels, catering and event staff. ?industry=hospitality_food
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Shift completed The worker showed up on time and completed the full booked shift. |
CONTRACT_FULFILLED LOW stake |
The shift manager supervisor_or_reviewer Confirmed from the clock-in/clock-out the scheduling tool (Homebase/Deputy/When I Work) already records, with a manager sign-off. |
dueDate = the scheduled shift start; completedAt = the actual clock-in the scheduling tool recorded. |
|
Catering / event delivered A catering or event booking was delivered as agreed. |
TRANSACTION_COMPLETED HIGH stake |
The client who booked it customer_or_client Confirmed by the booking client via a confirmation link. |
dueDate = the contracted service time for the event; completedAt = when service actually began. |
|
No-call / no-show The worker did not show for a booked shift without notice. The industry’s own term is a "no-call/no-show". |
CONTRACT_BREACHED MEDIUM stake |
The shift manager supervisor_or_reviewer Recorded by the manager; the worker is notified and can dispute. |
dueDate = the scheduled shift start; leave completedAt unset. |
Store, counter and contact-centre staff working scheduled shifts. ?industry=retail_customer_service
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Shift completed The worker showed up on time and completed the full scheduled shift. |
CONTRACT_FULFILLED LOW stake |
The store or floor manager supervisor_or_reviewer Confirmed from the clock-in/clock-out the scheduling tool already records, with a manager sign-off. |
dueDate = the scheduled shift start; completedAt = the actual clock-in. |
|
Manager reference confirmed A store manager confirmed the worker covered their shifts reliably over a period. |
REVIEW_VERIFIED LOW stake |
The store or floor manager supervisor_or_reviewer Requested via a reference link the manager responds to. |
dueDate = the end of the period being confirmed; completedAt = the date the reference was given. |
|
No-call / no-show The worker did not show for a scheduled shift without notice. |
CONTRACT_BREACHED MEDIUM stake |
The store or floor manager supervisor_or_reviewer Recorded by the manager; the worker is notified and can dispute. |
dueDate = the scheduled shift start; leave completedAt unset. |
Couriers, drivers, warehouse and last-mile workers. ?industry=logistics_delivery
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Route / deliveries completed The worker completed the assigned route or deliveries on time. |
CONTRACT_FULFILLED MEDIUM stake |
The dispatching operator or the receiving customers supervisor_or_reviewer Confirmed from the dispatch system’s proof-of-delivery, with an operator sign-off. |
dueDate = the end of the promised delivery window; completedAt = the timestamp on the last proof of delivery. |
|
Delivery dispute A delivery was disputed (missing, damaged, or not delivered). |
TRANSACTION_DISPUTED MEDIUM stake |
The receiving customer customer_or_client Raised by the customer; resolution follows the dispute flow. |
dueDate = the promised delivery window; leave completedAt unset if nothing was delivered. |
Truck drivers, owner-operators and carriers moving loads for shippers and brokers. ?industry=transportation_freight
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Load delivered and signed for The load was delivered and the consignee signed the proof of delivery / bill of lading. |
CONTRACT_FULFILLED MEDIUM stake |
The consignee who signed for the load at the receiving facility customer_or_client Confirmed from the signed proof of delivery the receiving facility already produces; a signed BOL is a third-party record of the delivery, not the carrier’s own say-so. |
dueDate = the end of the booked delivery appointment window; completedAt = the timestamp on the signed proof of delivery. |
|
Freight invoice settled The broker or shipper settled the freight invoice for a delivered load. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying broker or shipper (as recorded by the processor or load board) payment_or_marketplace Auto-verified when a third-party processor or load board records the payer as someone other than the driver. |
dueDate = the invoice due date; completedAt = the settlement date the processor recorded. |
|
Broker / shipper reference confirmed A broker or shipper confirmed the carrier ran their loads reliably. |
REVIEW_VERIFIED MEDIUM stake |
The broker or shipper customer_or_client Requested via a reference link the broker or shipper responds to. |
dueDate = the end of the period being confirmed; completedAt = the date the reference was given. |
|
Missed pickup / abandoned load A booked load was not picked up or was abandoned in transit, leaving the shipper uncovered. |
CONTRACT_BREACHED HIGH stake |
The broker or shipper who booked the load customer_or_client Recorded against the load; the driver is notified and can dispute. A load cancelled by the SHIPPER, or a delay from weather, road closure or a facility holding the truck, is not the driver’s outcome. |
dueDate = the booked pickup or delivery appointment; leave completedAt unset. |
Pickers, packers, machine operators and production staff working scheduled shifts on a site. ?industry=warehouse_manufacturing
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Production shift completed The worker showed up on time and worked the full scheduled shift on the line or floor. |
CONTRACT_FULFILLED LOW stake |
The floor supervisor or shift lead at the site supervisor_or_reviewer Confirmed from the badge-in/badge-out or WMS clock record, with a supervisor sign-off. |
dueDate = the scheduled shift start; completedAt = the actual badge-in or clock-in the site recorded. |
|
Output passed quality check The worker’s output passed an independent quality inspection. |
REVIEW_VERIFIED MEDIUM stake |
The QA inspector, who is independent of the production line independent_authority Confirmed from the QA result recorded by the inspector. |
dueDate = the date the batch or run was due to be ready for inspection; completedAt = the recorded inspection date. |
|
Assignment period paid A paid assignment period on site was completed and settled. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying client site or agency (as recorded by the processor) payment_or_marketplace Auto-verified when a third-party processor records the payer as someone other than the worker. |
dueDate = the end of the assignment period; completedAt = the settlement date the processor recorded. |
|
No-call / no-show The worker did not show for a scheduled shift without notice, leaving the line short. |
CONTRACT_BREACHED MEDIUM stake |
The floor supervisor or shift lead supervisor_or_reviewer Recorded by the supervisor; the worker is notified and can dispute. A shift the SITE cancelled or sent the worker home from is not the worker’s outcome. |
dueDate = the scheduled shift start; leave completedAt unset. |
Commercial/residential cleaning and facilities maintenance. ?industry=cleaning_facilities
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Clean completed to standard The scheduled clean was completed and met the checklist standard. |
CONTRACT_FULFILLED LOW stake |
The site contact or property manager customer_or_client Confirmed by the site contact via a confirmation link or manager sign-off. |
dueDate = the scheduled visit start; completedAt = the actual arrival or checklist-completion time. |
|
Redo required The site contact required the clean to be redone. |
CONTRACT_BREACHED LOW stake |
The site contact customer_or_client Recorded against the visit; the worker can dispute. |
dueDate = the original scheduled visit the work should have satisfied; leave completedAt unset. |
Lawn, landscaping, arborist and grounds crews on scheduled routes and contracts. ?industry=landscaping_grounds
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Scheduled visit completed The crew completed the scheduled grounds visit to the agreed scope. |
CONTRACT_FULFILLED LOW stake |
The property manager or homeowner customer_or_client Confirmed by the property contact via the post-visit link the scheduling tool sends. |
dueDate = the scheduled visit date on the route; completedAt = the date the crew actually completed the visit. |
|
Contract period paid A seasonal or monthly maintenance contract period was delivered and paid. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying property owner or manager (as recorded by the processor) payment_or_marketplace Auto-verified when a third-party processor records the payer as someone other than the worker. |
dueDate = the end of the contract period; completedAt = the settlement date the processor recorded. |
|
Property manager reference confirmed A property manager confirmed the crew maintained their sites reliably. |
REVIEW_VERIFIED MEDIUM stake |
The property manager customer_or_client Requested via a reference link the property manager responds to. |
dueDate = the end of the period being confirmed; completedAt = the date the reference was given. |
|
Return visit required The property contact required the crew to return because the visit did not meet the agreed scope. |
CONTRACT_BREACHED LOW stake |
The property manager or homeowner customer_or_client Recorded against the visit; the worker can dispute. A visit missed because of weather or site access is not the worker’s outcome. |
dueDate = the original scheduled visit date; leave completedAt unset. |
Temp/staffing agencies and multi-site shift operators. ?industry=staffing_shift_work
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Placement completed The worker completed a staffed placement/assignment as agreed. |
CONTRACT_FULFILLED MEDIUM stake |
The client site the worker was placed at supervisor_or_reviewer Confirmed by the client site (the marketplace/agency is the witness for the engagement). |
dueDate = the booked shift or assignment start; completedAt = the actual clock-in the client site recorded. |
|
Placement confirmed by the site The client site confirmed the worker completed the placement as booked. |
REVIEW_VERIFIED MEDIUM stake |
The client site supervisor supervisor_or_reviewer Confirmed by the supervisor via a confirmation/reference link. |
dueDate = the end of the placement being confirmed; completedAt = the date the site confirmed it. |
|
Assignment abandoned The worker left a placement early or did not show for an accepted assignment. |
CONTRACT_BREACHED MEDIUM stake |
The client site supervisor_or_reviewer Recorded by the client/agency; the worker is notified and can dispute. A shift the SITE cancelled, or one cancelled inside the agency’s own notice policy, is not the worker’s outcome. |
dueDate = the accepted shift or assignment start; leave completedAt unset. |
Security guards, patrol and event-security professionals working to a site or client contract. ?industry=security_services
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Security shift completed The worker showed up on time and completed the full booked security shift or post. |
CONTRACT_FULFILLED MEDIUM stake |
The site/client supervisor supervisor_or_reviewer Confirmed from the clock-in/clock-out or patrol log, with a site-supervisor sign-off. |
dueDate = the booked post start time; completedAt = the actual clock-in or first patrol-log entry. |
|
Contract period delivered A paid contract period of security coverage was delivered as agreed. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying client (as recorded by the processor) payment_or_marketplace Auto-verified when a third-party processor records the payer as someone other than the worker. |
dueDate = the end of the contract period; completedAt = the settlement date the processor recorded. |
|
Client reference confirmed A client confirmed the worker delivered security coverage reliably. |
REVIEW_VERIFIED MEDIUM stake |
The client site supervisor supervisor_or_reviewer Requested via a reference link the client responds to. |
dueDate = the end of the period being confirmed; completedAt = the date the reference was given. |
|
Post abandoned / no-show The worker abandoned a post or did not show for a booked shift, leaving the site uncovered. |
CONTRACT_BREACHED HIGH stake |
The site/client supervisor supervisor_or_reviewer Recorded by the supervisor; the worker is notified and can dispute. |
dueDate = the booked post start time; leave completedAt unset. |
Stagehands, AV techs, riggers and production crew working to call times on live events. ?industry=events_production
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Call completed The crew member made their call time and worked the full call. |
CONTRACT_FULFILLED MEDIUM stake |
The production manager or stage manager running the call supervisor_or_reviewer Confirmed from the call sheet sign-in, with a production-manager sign-off. |
dueDate = the call time on the schedule; completedAt = the actual sign-in time at the venue. |
|
Event work invoiced and paid A completed event booking was invoiced and settled. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying production company or venue (as recorded by the processor) payment_or_marketplace Auto-verified when a third-party processor records the payer as someone other than the worker. |
dueDate = the invoice due date; completedAt = the settlement date the processor recorded. |
|
Production reference confirmed A production manager confirmed the crew member worked their calls reliably. |
REVIEW_VERIFIED MEDIUM stake |
The production manager supervisor_or_reviewer Requested via a reference link the production manager responds to. |
dueDate = the end of the run being confirmed; completedAt = the date the reference was given. |
|
Missed call The crew member did not make an accepted call, leaving a live event short-crewed. |
CONTRACT_BREACHED HIGH stake |
The production manager or stage manager supervisor_or_reviewer Recorded by the production manager; the worker is notified and can dispute. A call the PRODUCTION cancelled or moved is not the worker’s outcome. |
dueDate = the call time on the schedule; leave completedAt unset. |
Nannies, childminders and early-years workers delivering care to families or centres. ?industry=childcare
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Care period completed The booked care period or shift was delivered as agreed. |
CONTRACT_FULFILLED MEDIUM stake |
The parent/guardian or the centre director customer_or_client Confirmed by the parent or the centre director via a confirmation link. |
dueDate = the booked care start time; completedAt = the actual arrival time. |
|
Care contract term paid A paid contract term of childcare was completed. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying parent/guardian (as recorded by the processor) payment_or_marketplace Auto-verified when a third-party processor records the payer as someone other than the worker. |
dueDate = the end of the contract term; completedAt = the settlement date the processor recorded. |
|
Family reference confirmed A family confirmed the worker delivered care reliably. |
REVIEW_VERIFIED MEDIUM stake |
The parent/guardian customer_or_client Requested via a reference link the family responds to. |
dueDate = the end of the period being confirmed; completedAt = the date the reference was given. |
|
No-show for booked care The worker did not show for booked care without notice. |
CONTRACT_BREACHED MEDIUM stake |
The parent/guardian or centre director customer_or_client Recorded by the family/centre; the worker is notified and can dispute. |
dueDate = the booked care start time; leave completedAt unset. |
Stylists, estheticians, massage therapists, trainers and personal-care professionals. ?industry=beauty_wellness
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Appointment completed The booked appointment was delivered as scheduled. |
CONTRACT_FULFILLED LOW stake |
The client or the salon/studio manager customer_or_client Confirmed via the post-visit link the booking tool sends, or a manager sign-off. |
dueDate = the booked appointment time; completedAt = when the appointment actually started. |
|
Package delivered and paid A paid package or membership block of services was completed. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying client (as recorded by the processor) payment_or_marketplace Auto-verified when a third-party processor records the payer as someone other than the worker. |
dueDate = the date the package was due to be completed by; completedAt = the settlement or final-session date. |
|
Client reference confirmed A repeat client confirmed the professional delivered reliably. |
REVIEW_VERIFIED LOW stake |
The client customer_or_client Requested via a reference link the client responds to. |
dueDate = the end of the period being confirmed; completedAt = the date the reference was given. |
|
No-show for booked appointment The worker did not show for a booked appointment without notice. |
CONTRACT_BREACHED LOW stake |
The salon/studio manager supervisor_or_reviewer Recorded by the manager; the worker is notified and can dispute. A CLIENT who did not show is not the worker’s outcome. |
dueDate = the booked appointment time; leave completedAt unset. |
Tutors, instructors, teaching aides and independent educators. ?industry=education_tutoring
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Sessions delivered as agreed The booked block of lessons or sessions was delivered on schedule. |
CONTRACT_FULFILLED LOW stake |
The student’s parent/guardian or the school/institution customer_or_client Confirmed by the parent or the institution via a confirmation link. |
dueDate = the date the block of sessions was due to be completed by; completedAt = the date the last session was delivered. |
|
Tutoring program paid A paid tutoring package or program was completed. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying parent/guardian or institution payment_or_marketplace Auto-verified when a third-party processor records the payer as someone other than the worker. |
dueDate = the end of the program; completedAt = the settlement date the processor recorded. |
|
Parent / school reference confirmed A parent or school confirmed the educator delivered reliably. |
REVIEW_VERIFIED MEDIUM stake |
The parent/guardian or school contact customer_or_client Requested via a reference link they respond to. |
dueDate = the end of the period being confirmed; completedAt = the date the reference was given. |
|
Booked sessions missed The educator did not deliver booked sessions without notice. |
CONTRACT_BREACHED LOW stake |
The parent/guardian or institution customer_or_client Recorded against the booking; the worker can dispute. A session the STUDENT missed is not the educator’s outcome. |
dueDate = the booked session time; leave completedAt unset. |
Consultants, agencies, freelancers and independent professionals. ?industry=professional_services
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Engagement / deliverable delivered The agreed deliverable or engagement was completed and accepted. |
CONTRACT_FULFILLED HIGH stake |
The client customer_or_client Confirmed by the client via a confirmation link, or by a paid invoice a third-party processor records. |
dueDate = the agreed delivery date in the statement of work; completedAt = the date the client accepted it. |
|
Client reference confirmed A past client confirmed the professional delivered reliably. |
REVIEW_VERIFIED MEDIUM stake |
The past client customer_or_client Requested via a reference link the client responds to. |
dueDate = the end of the engagement being confirmed; completedAt = the date the reference was given. |
Attorneys, paralegals and independent legal professionals. ?industry=legal
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Matter delivered and accepted The agreed legal work on a matter was completed and accepted by the client. |
CONTRACT_FULFILLED HIGH stake |
The client (or the supervising attorney on a staffed matter) customer_or_client Confirmed by the client via a confirmation link, or by the supervising attorney who assigned the work. |
dueDate = the agreed deliverable or filing date; completedAt = the date the work was delivered or filed. |
|
Invoiced legal work paid The client paid the invoice for completed legal work. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying client (as recorded by the processor) payment_or_marketplace Auto-verified when a third-party processor records the payer as someone other than the worker. |
dueDate = the invoice due date; completedAt = the settlement date the processor recorded. |
|
Client reference confirmed A past client confirmed the professional handled their matter reliably. |
REVIEW_VERIFIED MEDIUM stake |
The past client customer_or_client Requested via a reference link the client responds to. |
dueDate = the end of the matter being confirmed; completedAt = the date the reference was given. |
|
Client deadline missed An agreed deliverable or filing deadline on the matter was missed. |
CONTRACT_BREACHED MEDIUM stake |
The client or supervising attorney customer_or_client Recorded against the matter; the worker is notified and can dispute. |
dueDate = the agreed deadline that passed; leave completedAt unset. |
Bookkeepers, accountants, tax preparers and fractional finance professionals. ?industry=finance_accounting
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Engagement delivered The agreed work (a closed set of books, a filed return, a completed audit) was delivered and accepted. |
CONTRACT_FULFILLED HIGH stake |
The client customer_or_client Confirmed by the client via a confirmation link. |
dueDate = the agreed close, filing or delivery date; completedAt = the date it was actually delivered or filed. |
|
Invoiced work paid The client paid the invoice for completed finance/accounting work. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying client (as recorded by the processor) payment_or_marketplace Auto-verified when a third-party processor records the payer as someone other than the worker. |
dueDate = the invoice due date; completedAt = the settlement date the processor recorded. |
|
Client reference confirmed A past client confirmed the professional delivered their finance work reliably. |
REVIEW_VERIFIED MEDIUM stake |
The past client customer_or_client Requested via a reference link the client responds to. |
dueDate = the end of the engagement being confirmed; completedAt = the date the reference was given. |
Designers, writers, photographers, video and other creative professionals. ?industry=creative_design
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Creative project delivered and accepted The agreed creative deliverable was delivered and accepted by the client. |
CONTRACT_FULFILLED HIGH stake |
The client customer_or_client Confirmed by the client via a confirmation link. |
dueDate = the agreed delivery date on the brief; completedAt = the date the client accepted the deliverable. |
|
Milestone paid A client paid for a completed creative milestone or deliverable. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying client (as recorded by the marketplace/processor) payment_or_marketplace Auto-verified when the payer is a third party (marketplace or settled invoice). |
dueDate = the milestone due date; completedAt = the settlement date the processor recorded. |
|
Client reference confirmed A past client confirmed the creative delivered reliably. |
REVIEW_VERIFIED MEDIUM stake |
The past client customer_or_client Requested via a reference link the client responds to. |
dueDate = the end of the project being confirmed; completedAt = the date the reference was given. |
|
Deliverable disputed The client disputed the deliverable (not delivered, or not to the agreed brief). |
TRANSACTION_DISPUTED MEDIUM stake |
The client customer_or_client Raised by the client; resolution follows the dispute flow. |
dueDate = the agreed delivery date; leave completedAt unset if nothing was accepted. |
Non-software engineering: design, drafting and field engineering delivered to a client or project owner. ?industry=engineering
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Design / deliverable accepted The engineering deliverable (drawings, design, report) was delivered and accepted by the client or project owner. |
CONTRACT_FULFILLED HIGH stake |
The client or project owner customer_or_client Confirmed by the client via a confirmation link. |
dueDate = the milestone date in the project programme; completedAt = the date the deliverable was accepted. |
|
Milestone paid A project milestone was paid by the client. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying client (as recorded by the processor) payment_or_marketplace Auto-verified when a third-party processor records the payer as someone other than the worker. |
dueDate = the milestone invoice due date; completedAt = the settlement date the processor recorded. |
|
Work passed inspection The delivered work passed an independent inspection or review. |
REVIEW_VERIFIED MEDIUM stake |
The inspector or authority having jurisdiction independent_authority Confirmed from the inspection result recorded by the independent inspector/authority. |
dueDate = the date the work was due to be ready for inspection; completedAt = the recorded inspection date. |
|
Rework required The client or reviewer required the work to be reworked to meet the agreed spec. |
CONTRACT_BREACHED MEDIUM stake |
The client or reviewer customer_or_client Recorded against the deliverable; the worker can dispute. |
dueDate = the original milestone date the deliverable should have met; leave completedAt unset. |
Independent consultants and advisory firms delivering to a client sponsor. ?industry=consulting
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Engagement delivered The agreed advisory engagement or deliverable was completed and accepted by the client sponsor. |
CONTRACT_FULFILLED HIGH stake |
The client sponsor customer_or_client Confirmed by the sponsor via a confirmation link. |
dueDate = the agreed delivery date in the statement of work; completedAt = the date the sponsor accepted it. |
|
Retainer / milestone paid A retainer period or milestone was paid by the client. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying client (as recorded by the processor) payment_or_marketplace Auto-verified when a third-party processor records the payer as someone other than the worker. |
dueDate = the invoice due date; completedAt = the settlement date the processor recorded. |
|
Client reference confirmed A past client confirmed the consultant delivered reliably. |
REVIEW_VERIFIED MEDIUM stake |
The past client sponsor customer_or_client Requested via a reference link the client responds to. |
dueDate = the end of the engagement being confirmed; completedAt = the date the reference was given. |
Agents, brokers and transaction coordinators taking a deal to close. ?industry=real_estate
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Transaction closed A property transaction closed as agreed. |
TRANSACTION_COMPLETED HIGH stake |
The closing/title/escrow agent (an independent third party) independent_authority Confirmed from the closing recorded by the independent title/escrow agent. |
dueDate = the contract closing date; completedAt = the date the transaction actually closed. |
|
Client engagement delivered The agreed representation (listing sold, buyer placed) was delivered and accepted by the client. |
CONTRACT_FULFILLED MEDIUM stake |
The client (buyer or seller) customer_or_client Confirmed by the client via a confirmation link. |
dueDate = the end of the listing or representation period; completedAt = the date the engagement completed. |
|
Client reference confirmed A past client confirmed the agent handled their transaction reliably. |
REVIEW_VERIFIED MEDIUM stake |
The past client customer_or_client Requested via a reference link the client responds to. |
dueDate = the end of the transaction being confirmed; completedAt = the date the reference was given. |
|
Commission / representation disputed A client disputed the representation or the commission owed. |
TRANSACTION_DISPUTED MEDIUM stake |
The client customer_or_client Raised by the client; resolution follows the dispute flow. |
dueDate = the contract date the dispute relates to; leave completedAt unset. |
The digitally-native case: outcomes already live in your tools. ?industry=software_engineering
| Outcome | Report as | Who confirms it | Timing |
|---|---|---|---|
|
Work delivered and merged Committed work was delivered and accepted (merged/shipped) by someone other than the author. |
CONTRACT_FULFILLED MEDIUM stake |
The reviewer/merger (not the author) supervisor_or_reviewer Auto-derived from the VCS/CI system; a self-merge is never a third-party witness. |
dueDate = the agreed or sprint delivery date; completedAt = the merge/ship timestamp. |
|
Milestone paid A client paid for a completed milestone. |
TRANSACTION_COMPLETED MEDIUM stake |
The paying client (as recorded by the marketplace/processor) payment_or_marketplace Auto-verified when the payer is a third party (marketplace or settled invoice). |
dueDate = the milestone due date; completedAt = the settlement date the processor recorded. |
Report outcomes one at a time, map your own payload shape with POST /api/v1/ingest, or backfill history as CSV with POST /api/v1/imports. A spreadsheet export is a perfectly good integration. Then ask the counterparty to confirm: Credda hosts the page they answer on, so there is nothing to build for the person doing the confirming. The quickstart has the calls.
developers