Commons / Self-service / 21 October 2026

Prepare, print, retain

A person can use the documents independently or ask someone to help with the paperwork.

The Commons publishes reusable explanations and blank records for free reuse. Its purpose is to reduce unnecessary work in asking for a substantive answer: the opposite of sludge. These materials provide procedural information, not individual legal advice.

1. Start with the requested action

Open the request and explanations in the parent reading directory. Select the credit reporting agency and change the collector and lessor names. Review every paragraph against the actual case. Editing names alone does not complete a dispute.

2. Add the individual record

State what is disputed, why, and what correction or explanation is requested. Label supporting copies with dates and descriptive names. Include the relevant calculations, correspondence and unanswered questions. Keep identification and address-verification material in a separate private attachment.

3. Review and record any help

The person whose case it is reviews the completed request and signs their own name. A helper can record typing, reading, organizing, printing or mailing on the next page. Preparing or sending a document does not by itself authorize signing it for someone else.

4. Print or save the completed version

Use Print / save PDF in the request. Choose the request alone or all explanatory pages. Check the resulting pages, names, attachments and signature spaces. The prebuilt request PDF contains the example names; edits in an open HTML page do not change that download.

5. Send and keep the exact copy

Use the recipient's current submission instructions and address. Keep the completed packet and any signed original; retain the sent copy or scan, attachment list, actual sending date, receipt and responses. Complete the delivery record after sending. Publishing a template on GitHub does not send anyone's dispute.

The assistance record is optional. Keep completed records private and supply authorization material only where appropriate to the recipient and task. This template does not grant power of attorney, establish representation, or guarantee acceptance.

Source context: the CFPB's guidance on submitting a complaint for another consumer calls for identifying the helper and obtaining authorization. That guidance concerns CFPB complaints; it is not a universal signing rule for courts or credit bureaus. Source and scope notes are in the directory README.

Commons / Optional private record

Preparation and assistance record

For credit correspondence. Record what each person actually did. Leave unused sections blank.

Person whose case this is: __________________________________________________

Document / version / date: __________________________________________________

A. Person's review and limited permission

I reviewed the identified document and attachments. They reflect the request I want to make. I permit the named helper to perform only the tasks marked below for this document.

Helper's name: ____________________________________________________________

Tasks: [ ] type / fill fields [ ] read aloud [ ] organize copies [ ] print / scan [ ] send

Limits / permission end date, if any: __________________________________________

Person's own signature: ______________________________ Date: ________________

B. Prepared or assisted by

I provided the assistance described here. This entry identifies my work; it does not substitute my signature for the person's signature or certify every underlying fact.

Work performed: __________________________________________________________

Helper's own signature: ______________________________ Date: ________________

C. If someone signed on the person's behalf

This section records an action under separately established authority. Section A's permission to help does not grant authority to sign. Identify the actual signer and capacity; do not imitate the person's signature.

Actual signer / capacity: ___________________________________________________

Authority document / date / scope: ___________________________________________

Authority copy supplied to recipient, if required: _______________________________

Actual signer's own signature: __________________________ Date: ______________

D. Sent by / delivery record

Sender / recipient: ________________________________________________________

Method / actual date / receipt reference: ______________________________________

Exact copy and attachment list retained at: ____________________________________

Private when completed. This record does not establish the sufficiency of authority or the recipient's acceptance. Responses should go to the person unless separately arranged and authorized.

Commons / Further case areas / 21 October 2026

Foundations, articles and cases

Foundations organize subjects. Reusable articles can connect several foundations, and cases can cite several articles.

Deterrence through administrative burden is one reusable article, often called the sludge document. It explains how unnecessary complexity, repetition, delay or expense can discourage a person from pursuing a substantive answer. Excessive or unjustified procedural friction is often called sludge.

Articles and cases connected by an issue

Unsupported rent acceleration connects Real Estate with procedural burden. Veterans dealing with the VA and people challenging traffic tickets are further case areas in which to examine procedural burden. Each case identifies its requested action, evidence, unanswered questions, steps, costs, dates and downstream consequences. The shared explanation does not replace the rules of the particular process.

Credit reporting and traffic insurance

In the credit case, a reported balance can affect later decisions about a person. In a traffic case, a driving-record entry can affect insurance. The comparison concerns a record's downstream consequences. Credit bureaus maintain and distribute credit records; insurers use risk information in underwriting and pricing. Those are different institutional roles.

Traffic tickets as a proposed sludge case

John Rigler proposes studying traffic-ticket procedures as an example of sludge, including situations where payment and compliance with a diversion process affect insurance consequences. His personal experience challenging tickets is a proposed case source; the jurisdiction, ticket, offer and outcome have not yet been documented here.

A documented mechanism is Arizona's defensive-driving diversion program: eligible completion can lead to dismissal and no driving-record points, with court, state and school charges. Its stated purposes include education, diversion and a sanction. The sludge inquiry asks which burdens are necessary and which discourage a challenge or make a better outcome depend on resources. Preserve the offer, reporting rule, conditions and actual insurer effect.

Veterans and the VA

VA decisions can be studied through the same evidence-and-burden structure. The review path depends on the decision. VA benefit-claim preparation and representation have specific accreditation and appointment rules; this credit-correspondence assistance record does not replace them. VA-accredited VSO assistance is free.

Where foundations intersect

Real Estate and Religion can be separate foundations. A proposed Parsonage Exemption article would connect both. Foundations are broad subjects; articles develop specific issues and may belong to several. A case can cite several articles. Religious exemption is another possible subject that need not derive from the burden article. These are organizational examples, with substantive scope and sources still to be selected.

Primary sources: Arizona Judicial Branch, Defensive Driving FAQ and Cost to Attend School; VA, Decision Reviews and Appeals and Accredited Representative FAQs. Links, access date and scope limits are recorded in the directory README. These are further case areas, not completed individual dossiers.