The Long Return Institute

Audit request workflow

Before you request a review

Know what a request does—and what it does not authorize.

Current status: closed intake. The request page prepares a draft on your device. There is no way to send an Audit request from this page yet. No review agreement or client queue is created by using it.

Before sending any material

The first contact should describe one item and one review question. Do not send confidential documents, protected cultural knowledge, information about a child, medical or legal case records, identity documents, credentials, or allegations containing private personal details.

If access or permission is uncertain, describe the restriction without disclosing the restricted content. Public availability does not by itself establish permission or appropriate authority for every use. Christopher may narrow, refer, or decline the work.

The agreement before acceptance

The agreement must identify the exact material and version, the review question, included and excluded checks, the reviewer, delivery format, timing, any fee, handling arrangements, and the correction and withdrawal process. A later document version or additional task is not silently included.

No fee schedule or completion-time promise has been adopted for this service in this release. Those decisions must be made before intake opens. No payment information is requested.

Separate permissions

Permission to review is not permission to publish. Private requests, names, documents, and reports will not become public examples by default. A case study or testimonial requires a separate, optional decision.

Material AI assistance also requires a separate decision identifying the proposed provider, what would be shared, its purpose, and applicable handling terms. Declining AI use is not permission to use it anyway; the review must be feasible without it or the work must be declined. No AI service is connected to this page.

Information handling before intake opens

The live intake notice must name the receiving service, who has access, where working records and reports are held, how replies and delivery occur, retention periods, and how to request withdrawal or deletion. Those operating arrangements are not verified by this website build.

The public website will not host the private queue or client files. A “noindex” label is not a privacy control. Downloading a local draft creates a file on your device; clearing the page does not delete that file. Your browser and the hosting service may still handle ordinary page requests, but the closed draft helper sends no entered fields.

Corrections, disagreement, and another review

A report must provide a specific correction contact and identify its version. A requester may challenge a finding or supply evidence of a mistake. Correcting the reviewer’s error is separate from reviewing a revised submission; any new work needs agreement. A stopped review must state what was and was not done.

Method status

The site’s recorded Institute adoption identifies core v0.6-dev, operator package v1.5, and release record v1.0, effective 19 August 2026. Later author-method records identify a released 1.7.1 baseline and a 0.4.0 controlled successor candidate. Those are not interchangeable version numbers or automatic Institute adoptions.

Before accepting work, the service must record which exact Audit packet it will use, a file check that identifies that packet, and the decision selecting it. The method has not been externally validated. Each report must name the method actually used.

Read the Institute adoption record →
Return to request detailsSee the example report →