Cleargrain DocsSpreadsheets · Instructions · ResearchStart a project
Menu
Need help using this site?

You do not need technical words to get started. Describe what is difficult and what you want to make easier. You can send a short inquiry without an account.

  1. Browse services and prices, or go straight to tell me what you need.
  2. Examples include a real public-data cleanup and clearly labeled fictional work. You can read them without downloading anything.
  3. Use Client Login for private requests, files and project review. Start with the no-account inquiry form; no files are needed.

Have a complex or technical project? Describe it here. The listed packages are starting points. Larger spreadsheets are welcome; feasibility, size and complexity are reviewed before agreeing a custom scope and price.

What do the file types and technical terms mean?
PDF
A document you can read in a browser or PDF reader.
XLSX
An Excel workbook. Open it in a spreadsheet app to inspect the full example.
CSV
A plain spreadsheet file. Open it in a spreadsheet app to see rows and columns.
TXT
A plain-text checklist or template. Open it in a text editor or copy its text.
SOP or procedure
Step-by-step instructions for a task.
CRM
An app used to organize customer or contact records.
Workflow
The steps that move a task from start to finish.

To download a file, select its download link. It may open in your browser or appear in Downloads. If the browser asks, choose where to save it. A download is not a project order.

Real public data · A complete worked example

A service-request queue you can actually review

3,840 requests become a 115-request review queue and a category/borough report. 25 closing dates earlier than opening dates are kept for review instead of contaminating elapsed-time statistics.

Download the prepared workbook (.xlsx)See the before-and-after

Independent public-data demonstration · Not paid client work · Source and limits below

3,840Source requests
115Not closed in snapshot
25Closing dates before opening datesNot used as negative completion times
3,725Valid closed timings

This is a downloaded status snapshot dated 8 October 2026, not a live backlog. A source status or elapsed age does not prove a deadline was missed.

The practical question

Which requests are still not closed in the downloaded snapshot, and which closed requests have completion times we can calculate from the recorded dates?

The prepared workbook keeps a route back to the original records and includes the checks and open questions. It is a worked example you can inspect, not a claim of client savings or a live operational system.

  • Review queue
  • Team workload

What the work involved

From the source files to a usable result.

  1. Use a complete, clearly defined cohort

    All DOT requests created September 1–7, 2025, ordered by created time and request ID; no address, location or contact fields downloaded.

  2. Separate status from dates

    A closure timestamp does not override a Pending or Assigned status. Source status remains visible.

  3. Make elapsed-time statistics defensible

    Calculate duration only for closed requests whose closure does not precede creation, with New York daylight-saving offsets applied before subtraction.

  4. Build a usable review queue

    Not-closed requests are sorted oldest first, with a fixed snapshot date and a category/borough workload report.

  5. Keep unknowns explicit

    Unspecified boroughs and unknown channels stay missing; the original value remains inspectable.

Follow actual records

What changed, and why it matters.

The two columns show the same information before and after. New calculations, group labels and questions appear separately beneath them. “[blank]” marks an empty field; the explanation says why. The full source records and the complete change log are included in the downloads.

Example 1

A closing date earlier than its opening date is flagged

Before · source information

Request number
66026371
Created
2025-09-02T07:53:00.000
Closure date
2025-09-01T07:49:00.000

After · prepared information

Request number
66026371
Created
2025-09-02T07:53:00.000
Closure date
2025-09-01T07:49:00.000

What changed or was added: An impossible sequence is not quietly converted into a negative completion time.

Added to make the record useful

Hours to close
[blank]
Question to check
Closure predates creation; duration excluded; Non-closed status has a closure date; status retained

Example 2

Status wins over an isolated date

Before · source information

Request number
66026371
Status
Pending
Closure date
2025-09-01 07:49:00

After · prepared information

Request number
66026371
Status
Pending
Closure date
2025-09-01 07:49:00

What changed or was added: A Pending or Assigned request is not labelled finished simply because a date exists.

Added to make the record useful

Review group
Not closed in snapshot
Hours to close
[blank]

Example 3

Valid timestamps become comparable elapsed hours

Before · source information

Request number
66006215
Created
2025-09-01T00:24:27.000
Closure date
2025-09-02T10:20:00.000

After · prepared information

Request number
66006215
Created
2025-09-01T00:24:27.000
Closure date
2025-09-02T10:20:00.000

What changed or was added: A duration is added only after status and chronology checks.

Added to make the record useful

Hours to close
33.926

Example 4

Unknown geography does not become a guess

Before · source information

Request number
66005377
Borough
Unspecified

After · prepared information

Request number
66005377
Borough
[blank]

What changed or was added: The row stays in the workload count without being assigned to a made-up borough.

Added to make the record useful

Group used in the report
Unspecified

Example 5

Open work becomes a dated queue

Before · source information

Request number
66030838
Created
2025-09-01 00:20:54
Status
Pending

After · prepared information

Request number
66030838
Created
2025-09-01 00:20:54
Status
Pending

What changed or was added: The oldest not-closed records can be reviewed; age is not presented as an SLA breach.

Added to make the record useful

Age in days on the snapshot date
401.985
Snapshot date (New York time)
2026-10-08 00:00

Checks you can inspect

Every selected record is accounted for.

CheckResult
Original records3,840
Prepared records3,840
Records removed0
Distinct request numbers3,840
Requests marked Closed3,725
Requests not marked Closed115
Requests included in the report3,840
Backwards date pairs kept for checking25
Closed requests with valid timing3,725
Daylight saving adjusted closed rows130
Logged transformations13,620

These checks verify the preparation and grouping rules. They do not certify the underlying source, prove a business outcome or settle the questions listed for review.

Open the complete deliverables

Originals, prepared work and supporting checks.

Start with the prepared workbook. Compare it with the original workbook, or use the CSV files to inspect every row in another spreadsheet app.

The files contain public source data and independently prepared analysis. Native Microsoft Excel testing has not been performed.

Use the result in context

What this example does and does not establish.

  • All NYC DOT requests created September 1–7, 2025 in the downloaded snapshot; not all agencies or a representative service-quality sample.
  • Source downloaded October 8, 2026. Status is a snapshot and may later change; this is not a live operational system.
  • Source timestamps are NYC local wall-clock values. Completion times localize America/New_York and convert to UTC before subtraction, including daylight-saving changes. No ambiguous or nonexistent transition timestamp occurs in this selection.
  • Closed means the source says Closed, not independently verified resolution. Not-closed age is elapsed calendar time, not a promised deadline or SLA breach.
  • Medians include only valid closed timings. The report shows the number excluded, and keeps all requests in workload denominators.

Source & reuse

Public evidence, clearly credited.

NYC Open Data: 311 Service Requests from 2020 to Present. Source: NYC Open Data, NYC311/Department of Transportation, downloaded 8 October 2026. Filtered and transformed independently; no City endorsement.

NYC Open Data unrestricted reuse statement; portal Terms of Use apply

Source portal terms of use

Prepared for this demonstration from the source downloaded 2026-10-08. Source details, transformations and limitations are included in the files.

Have work like this?

Larger files and more involved reports are welcome. The $125 spreadsheet starter is one defined offer; other work is quoted by size and complexity after review.

Ask about a project like thisBrowse the other examples
Help opening these files

Select a file link to open or download it. Check your browser’s downloads list or your device’s Downloads folder.

PDF: read it in your browser. XLSX or CSV: open it in a spreadsheet app. TXT: open it as plain text. You can read the example on this page without downloading anything.

If a file does not open, tell us the file name and what happened. Do not send private data in your first message.

Have a task in mind?

Start with the result you need.

Tell me what you need