{"slug":"change-order-documentation","name":"Change order documentation","category":"Real Estate and Construction","customer":"Construction project administrators","problem":"Scope changes lack clear descriptions and evidence.","value":"For construction project administrators, turn approved site notes, photos and change instructions into reviewed change order record. Address the recurring problem: scope changes lack clear descriptions and evidence. The value hypothesis is a more complete, reviewable deliverable with less repeated preparation; the pilot must establish whether that benefit is real.","format":"Source-based content workspace with editorial delivery","screens":"Key screens: Change register, evidence editor, approval status. Use a project list and editorial calendar beside a document editor. Keep original material and supporting passages in a collapsible side panel. Show outline, draft, review and approved stages. Provide tracked edits, comments, version comparisons and an export preview that reflects the final delivery format. In this product, the first view is change register, followed by evidence editor and approval status.","functionality":"1. Capture change facts. 2. Link site evidence. 3. Draft scope descriptions. 4. Record supplied cost impacts. 5. Preserve approval status. 6. Export review forms.","workflow":"Collect a structured brief and source material, identify unanswered questions, approve an outline, generate a draft, verify claims, gather reviewer edits, approve a final version and export the agreed formats. Start with approved site notes, photos and change instructions and finish with reviewed change order record.","ai":"Extract and organize information, propose structure, draft prose and adapt approved content to audiences. Attach evidence to factual claims. Keep names, dates, amounts and quoted wording linked to their source. Editors resolve ambiguity and approve publication.","inputs":"Approved site notes, photos and change instructions","deliverables":"Reviewed change order record","admin":"Client workspaces, source permissions, editorial assignments, change history, reviewer comments, approval gates, revision allowances and export templates.","mvp":"Begin with construction project administrators and one recurring use case. Build the first two modules: capture change facts; link site evidence. Provide operator assistance for the third module: draft scope descriptions. Deliver reviewed change order record through a manual review queue. Perform other necessary full-scope functions manually during the pilot. Include all applicable access, accuracy and professional-review controls from the start.","expansion":"After paid pilots establish value, automate the remaining modules: record supplied cost impacts; preserve approval status; export review forms. Add one validated source integration, reusable customer configuration and recurring delivery. Expand to additional teams, document formats or languages only after testing the new scope.","usp":"A traceable change narrative tied to instructions and supporting records.","defensibility":"Customer-approved terminology, reusable structures, source libraries and editorial feedback tied to a specific audience and recurring publishing workflow. For this solution, build around a traceable change narrative tied to instructions and supporting records. This advantage requires execution and accumulated customer trust; the base model alone is not a defensible asset.","alternatives":"Writers, editors, agencies, internal document templates and general-purpose chat tools. Differentiate on this specific proposed advantage: a traceable change narrative tied to instructions and supporting records. Test it against the buyer's current method on the same task. Competitor coverage and uniqueness have not been established.","revenue":"Test USD 400-1,500 for a tightly scoped initial content package. Convert repeated work to a monthly retainer with explicit deliverable and revision limits. Specialist review and substantial research are separately scoped. Prices are hypotheses.","costs":"Research and interview time, transcription, model usage, factual verification, subject-matter review, editing and revisions.","integrations":"Property records, construction documents, project photos and supplier quotes. Document storage, word processor export, content management systems and approved publishing channels. Pilot with uploads and downloadable drafts before adding write integrations. These are candidate integration categories, not verified supported connectors.","dependencies":"Document parsing, a source-linked editor, tracked revisions, reviewer workflow and reliable document export. Rich presentation or print output needs format-specific QA.","pilot":"Complete one existing brief using the customer’s actual sources. Record reviewer edits, factual corrections and preparation time. Ask the same buyer to commission a second comparable deliverable. For this solution, use approved site notes, photos and change instructions and evaluate reviewed change order record. Agree success thresholds with the buyer before starting; collect a baseline for documentation completeness, clarification rounds. A positive signal is payment and repeat use with acceptable quality and delivery cost, not a favorable demo reaction alone.","plan30":"Week 1: interview five prospective buyers in this segment: construction project administrators. Ask to see a recent example of the problem and their current process. Week 2: prepare this demonstration using authorized or synthetic material: an evidence-backed sample change order. Week 3: present it through construction administration advisers and seek one narrowly scoped paid pilot. Week 4: review documentation completeness, clarification rounds, total delivery effort and a concrete renewal decision before increasing scope.","metrics":"Documentation completeness, clarification rounds","channels":"Construction administration advisers","leadMagnet":"An evidence-backed sample change order","message":"Change order documentation for construction project administrators. A traceable change narrative tied to instructions and supporting records. Demonstrate the claim through an evidence-backed sample change order.","retention":"Maintain the approved source and voice library, schedule recurring editorial work, and expand into additional formats only after the core deliverable is repeatedly accepted.","controls":"Verify property facts and scope assumptions. Clearly label visual alterations. Professional reviewers retain responsibility for contracts, engineering and legal interpretations. Validate source access and reviewer availability during the pilot. Maintain customer-level access, data deletion controls and a record of final approvals.","crossSector":"Operations; Sales; Writers","fn":["Capture change facts","Link site evidence","Draft scope descriptions","Record supplied cost impacts","Preserve approval status","Export review forms"],"sc":{"opp":7,"pain":6,"feas":7,"now":7},"phases":[{"name":"MVP","scope":"One buyer segment, one recurring use case; first modules: capture change facts; link site evidence. Manual review in the loop.","time":{"days":5,"label":"5 days"},"usd":8500},{"name":"Paid pilot","scope":"Accounts, roles, review states, audit trail and the first integration, hardened for two to three paying pilot customers.","time":{"days":6,"label":"6 days"},"usd":10500},{"name":"Full product","scope":"Remaining modules: record supplied cost impacts; preserve approval status; export review forms. Self-serve onboarding, billing, monitoring and the wider integration set.","time":{"days":10,"label":"10 days"},"usd":14500}],"running":[{"stage":"MVP and paid pilot","note":"about 3 customers","hosting":[30,60],"ai":[70,140],"total":[100,200]},{"stage":"Full product","note":"about 50 customers","hosting":[110,210],"ai":[700,1400],"total":[810,1610]}],"total":33500,"complexity":0.53,"days":21,"shot":true,"demo":true}