One wall, two kinds of evidence.
Managers pay for repairs they rarely see. The contractor's photos are a start. When they're thin, someone who wasn't paid to do the work takes a second look.
- Who asks
- The property manager. Each work order gets a Teleport link the contractor submits to.
- Who does the work
- The contractor, hired directly. Teleport doesn't schedule them, pay them or take a cut.
- Who checks it
- Someone nearby, onboarded, with no stake in the contractor. Only sent when the contractor's photos aren't enough.
- Evidence
- The contractor's upload first. Then, if needed, a live Teleport capture from the angles the task lists.
- Who pays
- The manager: $9 to the re-shooter on accept, plus the verification fee. The contractor's invoice is paid by the manager, on the proof. Example figures.
- You get
- Independent proof the job is visibly finished, upgraded from “submitted evidence” to Verified.
Not a flat no. A second look, for nine dollars.
Most work orders clear on the contractor's photos alone. Teleport sends someone only when the evidence can't carry the claim, and the proof says which it was.
Live near rental buildings? Join the contributor waitlist
Unit 3C and Northgate Property are fictional. Prices are illustrative.
Weak evidence becomes strong evidence.
Where the evidence came from decides what the proof can say. The contractor's upload stays on the record. The linked re-shoot is what lifts the claim to Verified.
Each item keeps its own origin in the proof: submitted for the upload, Teleport capture for the re-shoot. High assurance, which adds a person's review, is there for bigger jobs. A $9 drywall patch doesn't need it.
From repair to receipt, in six steps.
The contractor does the job. The manager pays for it. Teleport sits in between and finds out whether it's actually finished.
- 01
Repair done
The contractor patches and paints the wall in unit 3C. That part happens entirely outside Teleport.
- 02
Photos in
The contractor opens the work order's Teleport link and uploads completion photos.
- 03
Too thin
One close-up, no wide shot, the metadata stripped. Not a no: the evidence just can't carry the claim yet.
- 04
Linked re-shoot
A $9 task posts for someone nearby, linked to the first. Re-shoot the wall from three listed angles.
- 05
Checked
Place, window, angles and freshness by rule. One question goes to a model: is it finished as specified?
- 06
Paid + proven
The re-shooter is paid on accept. The manager pays the contractor's invoice on the proof.
Five rules, one question, and what none of them prove.
Only one check asks a model: does this look finished, as the work order describes? A versioned policy, not the model, makes the decision.
| Check | Proves | Doesn't prove | By | Result |
|---|---|---|---|---|
| In unit 3C | Captured inside the building's geofence, with the unit's lockbox code entered at the start. | — | Rule | Passed |
| In the window | Captured during the agreed entry window, by trusted device time, not the phone's clock. | — | Rule | Passed |
| Every angle | Wide, left and right, each with the repair inside the guided frame. | — | Rule | Passed |
| Live, not reused | Captured in the Teleport app, and none of it matches the contractor's upload or any earlier capture. | — | Rule | Passed |
| Only the repair | Anything outside the repair area, like belongings, faces or documents, is covered before delivery. | — | Rule | Passed |
| Finished as specified | Patch flat, primed and painted to match, with no visible seam, as the work order describes. | That it's to code, or anything behind the wall. | Model | Passed |
Re-shoot shows the job isn't finished? The manager and the contractor both see “not accepted”, with the photos and the reason. The re-shooter is still paid for an accurate capture.
§ 05 · Entry and scope
The wall, in the window. Nothing else.
Someone is entering a home or a unit for a third party. The owner, or the tenant if someone lives there, agrees first and picks the window. The re-shooter photographs the repair, not the rooms around it. And the proof says exactly what it is: visibly finished as specified, not done to code.
- Granted by
- The owner, while vacant. The tenant, once occupied.
- Window
- Tue 10:00–12:00, one visit
- Access
- Lockbox code, valid in the window only
- Photos
- The repaired wall. Nothing else in the unit.
- Verified
- Visibly finished as specified
- Not verified
- Code compliance, what's behind the wall
Its hash goes into the proof, and the proof page shows the scope word for word.
What needs care.
A stranger, in someone's unit, checking someone else's work. Each of those needs its own line.
Thin isn't a no
A contractor with a weak photo gets a second look, not a rejection. If the re-shoot shows the job isn't done, they see the photos before anyone holds back pay.
Say what was proven
Visibly finished as specified. Not to code, and not what's behind the wall. That line goes in the proof, on the proof page and in the contract.
Someone's home
An occupied unit needs the tenant's yes and a window they chose. Re-shooters are onboarded at a higher trust tier, and visits are time-boxed.
The wall, not the room
The guided capture frames the repair. Anything else that slips into the frame is covered before the manager sees it.
No stake in the answer
The re-shooter is paid the same whether the wall passes or not, and is never the contractor or their crew.
The invoice stays put
Teleport never pays the contractor or holds their money. The manager's own system pays on a signed decision.
A sign-off the manager can pay on.
One proof for the whole work order: the contractor's upload, the re-shoot that verified it, the scope of the answer and the policy that gave it.
Dollars pay the re-shooter. The contractor's invoice never touches Teleport. Nobody needs $PORT to post a work order or get paid for a re-shoot.
- Task
- Drywall repair · unit 3C
- Requested by
- Property manager
- Work by
- Contractor · outside Teleport
- Checked by
- Human · onboarded, nearby
- Evidence
- Upload → Teleport capture
- Assurance
- Standard → Verified
- Scope
- Visibly finished · not code
- Decision
- Accepted
- Paid
- $9.00 to the re-shooter
STATUS: FINAL
The contractor's invoice: paid by the manager on this proof. Never held by Teleport.
For builders.
A VERIFY_ONLY task the contractor submits to. When the evidence is thin, a linked MARKETPLACE capture with relations.verifiesTaskId. Where each item came from decides the assurance.
PhysicalTaskSpec · the linked re-shootTAP v0.2 · preview, subject to change
{
"schema": "teleport.tap.physical-task",
"version": "0.2.0",
"title": "Re-photograph the drywall repair in unit 3C",
"category": "CAPTURE",
"requester": {
"requesterType": "ORGANIZATION",
"principal": { "principalType": "ORGANIZATION" },
"mandateId": "mdt_northgate_maintenance_v1"
},
"trigger": { "type": "TASK_OUTCOME", "sourceRef": "task_wo_5512_verify:EVIDENCE_INSUFFICIENT" },
"fulfillment": { "mode": "MARKETPLACE" },
"relations": {
"workflowId": "wf_wo_5512",
"verifiesTaskId": "task_wo_5512_verify"
},
"environment": {
"siteRef": "site:northgate_14_unit_3c",
"siteConsentRef": "consent_unit_3c_entry_v1"
},
"actorRequirement": {
"permittedActorTypes": ["HUMAN"],
"minimumTrustTier": "ONBOARDED"
},
"completionConditions": [
{ "type": "LOCATION", "id": "in_unit", "zoneRef": "site:northgate_14_unit_3c",
"relation": "IN", "verificationMethod": "DETERMINISTIC" },
{ "type": "COUNT", "id": "angles", "subjectRef": "capture:guided_angles",
"min": 3, "verificationMethod": "DETERMINISTIC" },
{ "type": "SEMANTIC", "id": "finished_as_specified",
"question": "Is the patch flat, primed and painted to match, with no visible seam, as in work order 5512?",
"verificationMethod": "JEV", "minimumEvidenceOrigin": "TELEPORT_CAPTURE" }
],
"rightsPolicy": { "policyId": "repair-area-only-v1" },
"economics": {
"performerPayUsdCents": 900,
"buyerPriceUsdCents": 1500,
"settlementAssets": ["FIAT"]
},
"popw": { "required": true, "assurancePolicyId": "VERIFIED", "proofTiming": "WORKFLOW" },
"timing": { "expiresInSeconds": 172800, "priority": "NORMAL" }
}What this case uses from TAP v0.2
- Verify-only tasks
- The contractor submits evidence to a task they didn't take from a marketplace (fulfillment.mode = VERIFY_ONLY, submitter = PERFORMER).
- Linked tasks
- The re-shoot points at the task it verifies (relations.verifiesTaskId), so both land in one workflow proof.
- Evidence origin
- Each item records where it came from: THIRD_PARTY_SUBMITTED for the upload, TELEPORT_CAPTURE for the re-shoot.
- Assurance by origin
- Submitted evidence alone tops out at Standard. A Teleport capture of the same claim can reach Verified.
- Verification scope (proposed)
- A required, hashed statement of what the proof asserts and what it doesn't, first raised by the construction case.
Example economics: $15 to the manager per re-shoot, $9 of it to the re-shooter, paid on accept. The rest covers verification and the proof. When the contractor's photos are enough, there's no re-shoot, just the verification fee. Developer docs
Property managers
Pay for repairs you can see.
Send each work order a Teleport link. We're working with design partners across property and facilities.