DrawBook: progress pay apps without the spreadsheet tax

작성자

카테고리:

← 피드로
DEV Community · SybilGambleyyu · 2026-07-22 개발(SW)

SybilGambleyyu

Every month, thousands of small general contractors and specialty subs prepare a progress payment application against a schedule of values. The math is not exotic — original contract sum, net change orders, work this period, materials presently stored, retainage, less previous certificates, current payment due — but it is easy to get wrong in a spreadsheet, and wrong numbers delay cash.

The market answer is usually one of two extremes: a full construction ERP or AIA billing suite at a few hundred dollars a month, or a fragile Excel template someone emailed in 2019. There is room in the middle for a tool that does one job well, costs nothing, and does not require you to upload job financials to a vendor.

DrawBook is live

What it does

  • Schedule of values with item numbers, descriptions, and scheduled values (CSV import supported)
  • Change order log that rolls net change into every certificate
  • Payment applications that carry prior draws forward correctly
  • Retainage split between work completed and materials stored
  • % complete entry on each line so you can think like a PM, not a bookkeeper
  • Validation that flags overbilling a line past its scheduled value
  • Printable package (Print → Save as PDF) and CSV export
  • JSON backup / restore so you can move projects between machines

Local-first on purpose

Contract sums, change orders, and draw history are sensitive. DrawBook stores everything in your browser’s localStorage. There is no account, no analytics beacon, and no server-side copy of your jobs. If you clear site data, the projects go with it — so use the backup export for anything you rely on.

Honest limits

DrawBook follows the common schedule-of-values payment application math used on G702/G703-style packages. It is not an official AIA Contract Document and is not affiliated with The American Institute of Architects. If your contract requires licensed AIA forms, buy and use those. Always match retainage and stored-materials treatment to your contract, and have someone who owns the job review the numbers before submission.

It is also not a job-cost system, payroll tool, or lien-waiver manager. Depth on one workflow beats a shallow copy of Procore.

Try the sample project

Open the app and click Sample. You get a fictional tenant build-out with twelve SOV lines, two change orders, and two draws already filled in. Open Application #2 to see prior-work carryforward and current payment due computed live.

Stack

Static HTML, CSS, and ES modules. No build step, no framework, no backend. The calculation engine is pure functions with Node unit tests (npm test). MIT licensed.

If you run a small shop and still rebuild pay apps by hand, try DrawBook on your next period. If something is wrong or missing for real jobs, open an issue on the repo.

원문에서 계속 ↗

코멘트

답글 남기기

이메일 주소는 공개되지 않습니다. 필수 필드는 *로 표시됩니다