About Us
Say what the document asks, then stop.
Documents turned into short steps
Technical documents should come out in language a reader can act on. That conviction sets the scope below, applied here to published guidance on chemical peels, microdermabrasion and dermabrasion, and age spots.
- Rules: what a rule asks of you, stated as a directive you can follow.
- Requirement documents: each requirement reduced to the one thing it asks of the reader.
- Official forms: what each part of a form wants, in the order you meet it.
- Plain-language readings: the same material restated in short sentences.
Every item on this list follows one rule: say what the document asks, then stop.
Why a plain reading helps you act
A plain reading puts the next step first, so you know what to do before you read the details.
Each reading starts from primary documents and strips each requirement down to what it asks of the reader.
Three values follow from that. Be steady, so the tone stays the same from one page to the next. Be short, so a directive fits on one line. Be exact, so a reader can check any line against the original.
Places to look up for local context
Rules and forms are applied somewhere, and the place affects practical details such as travel and scheduling. Check those details for wherever you plan to act.
Three encyclopedia entries cover the area: Eastchester, New York, Westchester County, New York and Bronxville, New York.
Pick one document and begin
Choose the document that is waiting on you. Read its plain-language version, write down the one thing it asks of you, and do that first. Use the contact page if you have a correction or a topic you would like read next.