The first page of the document DocMake makes from the sample values on this page.
Operations
Project Status Report
The report your stakeholders skim in 60 seconds: one status line up top, a workstream table in the middle, risks called out before they become surprises.
Generate it from your project tracker through the API every Friday, and the format never drifts.
Blanks to fill
| project_name | Project |
| period | Period |
| overall_status | Overall |
| report_reference | Report reference |
| author | Reported by |
| report_date | Reported on |
| summary | Summary |
| risks | What we are watching |
| next_steps | What happens next |
| company_name | Company |
| workstreams[] | One per item, so a row is added for every item in the list |
The data behind the preview
This is the exact JSON that produced the document above. Change the values, POST them to the API, and you get your version back as DOCX or PDF. Lists grow and shrink with your data; the layout adapts.
- 01 Sign up free and duplicate this template into your workspace.
- 02 Adjust the wording and branding in the visual editor.
- 03 Fill it in the app, share it as a form link, or call the API.
{
"company_name": "Kestrel Digital Works",
"report_reference": "PSR-2026-W31",
"project_name": "Depot booking system",
"period": "Week 31, 27 July to 2 August 2026",
"report_date": "3 August 2026",
"author": "Nadia Thornbury, Delivery Lead",
"overall_status": "On track, with the carrier interface watched closely",
"summary": "The booking screens went to the two pilot depots on Wednesday and took 340 bookings in three days with no support calls. The carrier interface is the one piece behind: the test account arrived late and leaves four working days for the end to end run.",
"workstreams": [
{
"workstream": "Booking screens",
"status": "Done",
"notes": "Live at Ashford and Warrington since 29 July. Two wording changes ship this week."
},
{
"workstream": "Carrier interface",
"status": "Behind",
"notes": "Test account opened five days late. End to end run booked for 5 August."
},
{
"workstream": "Reporting",
"status": "On track",
"notes": "Daily volume report checked against the depot counts for three days."
},
{
"workstream": "Training",
"status": "On track",
"notes": "Eleven of fourteen depot leads trained. The last three sit on 6 August."
}
],
"risks": "The carrier interface leaves no room in the plan. If the end to end run on 5 August fails, the go live moves by a week and the depots keep the manual booking sheet, which costs about an hour a day each.",
"next_steps": "Run the carrier interface end to end on 5 August. Train the last three depot leads. Hold the go live decision meeting on 7 August with the depot managers."
}Generate this document via the API
One template plus changing data is the whole point. The list of blanks above is the contract, and every new set of values comes back in the same layout: fill it in the app, hand someone a form link, or POST the JSON and get the file straight back.
The request below carries this page's own values, so it runs as soon as the template exists in your workspace. Swap the values for yours and the response is your document.
curl -X POST https://app.docmake.io/api/v1/render \
-H "Authorization: Bearer $DOCMAKE_API_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
--output project-status-report.pdf \
--data-binary @- <<'JSON'
{
"template_id": "tmpl_your_template_id",
"format": "pdf",
"data": {
"company_name": "Kestrel Digital Works",
"report_reference": "PSR-2026-W31",
"project_name": "Depot booking system",
"period": "Week 31, 27 July to 2 August 2026",
"report_date": "3 August 2026",
"author": "Nadia Thornbury, Delivery Lead",
"overall_status": "On track, with the carrier interface watched closely",
"summary": "The booking screens went to the two pilot depots on Wednesday and took 340 bookings in three days with no support calls. The carrier interface is the one piece behind: the test account arrived late and leaves four working days for the end to end run.",
"workstreams": [
{
"workstream": "Booking screens",
"status": "Done",
"notes": "Live at Ashford and Warrington since 29 July. Two wording changes ship this week."
},
{
"workstream": "Carrier interface",
"status": "Behind",
"notes": "Test account opened five days late. End to end run booked for 5 August."
},
{
"workstream": "Reporting",
"status": "On track",
"notes": "Daily volume report checked against the depot counts for three days."
},
{
"workstream": "Training",
"status": "On track",
"notes": "Eleven of fourteen depot leads trained. The last three sit on 6 August."
}
],
"risks": "The carrier interface leaves no room in the plan. If the end to end run on 5 August fails, the go live moves by a week and the depots keep the manual booking sheet, which costs about an hour a day each.",
"next_steps": "Run the carrier interface end to end on 5 August. Train the last three depot leads. Hold the go live decision meeting on 7 August with the depot managers."
}
}
JSON tmpl_your_template_id is
a stand-in: build this template in the visual editor and copy the id it shows, or create one with POST /api/v1/templates. Keys, formats, strict mode and batches are in the API reference.
Or let an AI assistant do it
The DocMake MCP server lets Claude and other assistants make this document the same way. Install it once:
claude mcp add docmake \
--env DOCMAKE_API_KEY=dm_your_api_key \
-- npx -y @docmake/mcp@latestThen ask for the document in plain words:
Make a PDF from my Project Status Report template with project "Depot booking system" and period "Week 31, 27 July to 2 August 2026".
More operations templates
Change Order
The instructed change, where it came from, what it costs line by line, what it does to the programme, and the contract sum it leaves behind.
View template →Daily Site Report
The day on site in one sheet: weather, crew, plant, work done, deliveries and what held the job up.
View template →Field Service Report
One engineer visit written down: the fault, the time on site, the parts fitted, the tests that proved it and the customer signature.
View template →