Product Capabilities Explained

How StatusAngel works in practice

StatusAngel is scheduled customer status/progress reporting software. The product is built around a controlled Status File: one working record for a customer-facing job, project, order, build, case, service item, implementation or stakeholder update that needs regular progress reporting.

Main object Status File

Main output Polished email plus PDF snapshot

Reporting rhythm Manual or scheduled sends

Positioning Focused reporting, not heavy PM software

This page is a practical capability reference. It explains what the product can do, what each capability is for, and where StatusAngel deliberately stops.

Create your company account View plans Capability summary

Status Files: the main reporting record

Each Status File holds the current position for one customer-facing or stakeholder-facing piece of work. It can be as light as a short status summary, or detailed enough to support structured progress reporting.

Can represent

customer project, custom build, order or delivery
service job, implementation, repair or maintenance item
client file, case, matter or internal stakeholder update

Core information held

Status File name, summary, customer/client context and external reference
overall status, start date, baseline target date, current forecast date and actual completion date
forecast change reason, expected outcome, acceptance/completion notes and internal notes

Functional logic

The Status File is the live working record. The summary gives the high-level current position in plain language. More detailed rows sit underneath it in the workspace sections: progress, risks, issues, next steps, dependencies, milestones and evidence/images.

A client/customer organisation can be recorded where useful, but it is not mandatory. An external reference can also connect the Status File back to the tenant company’s own job number, order number, case reference or internal system reference. Whether that reference is shown externally depends on the report design and configuration.

Screenshot placeholder REPLACE_WITH_STATUS_FILE_HEADER_SCREENSHOT_URL

Summary, expected outcome and acceptance context

StatusAngel supports simple updates and more structured reporting without forcing a heavy project-management method.

Capability	Purpose	Typical use
Status File summary	Explains the current high-level position.	Executive-style overview for the customer or stakeholder.
Original expected outcome	Records what the work was intended to deliver or achieve.	Creates a clear baseline for later updates and completion context.
Acceptance/completion notes	Captures final delivery context, completion notes or review points.	Useful where the customer needs to understand how the outcome should be read.
Workspace detail	Maintains operational update rows under practical sections.	Progress, next steps, risks, issues, dependencies, milestones and evidence.

Specification note: A team can keep the Status File short when the work is simple, or add more structure where the relationship, risk profile or reporting expectation requires it.

Screenshot placeholder REPLACE_WITH_SUMMARY_OUTCOME_ACCEPTANCE_SCREENSHOT_URL

Practical update sections

The workspace gives teams a consistent place to maintain the details that normally matter in customer progress reporting.

Section	What it explains
Progress During this Reporting Period	What moved forward, what was completed, and what should be explained for the current reporting period.
Risks	Future uncertainties that may affect delivery, timing, cost, quality or expectations.
Issues	Current problems, blockers or escalations that already exist, with practical detail such as impact or mitigation where appropriate.
Next Steps	What is planned next, what the customer can expect, and the next part of the work.
Dependencies	Things needed from the customer, supplier, internal team, third party or another source.
Milestones	Key stages, baseline dates, forecast dates, actual dates, milestone status and progress percentage.
Evidence / Images	Visual proof of progress, condition, issues, milestone state or completion.

How teams should use the structure

A company does not need to fill every section for every Status File. The value is that the structure exists when needed. Some operational fields and internal notes may help the team manage the work but should not be assumed to be customer-facing.

Screenshot placeholder REPLACE_WITH_STATUS_FILE_WORKSPACE_SECTIONS_SCREENSHOT_URL

Controlled transparency

StatusAngel is designed so a company can maintain structured update content without automatically showing every internal detail to the customer.

Customer-facing logic

show useful customer-facing information
avoid showing internal-only content
avoid showing rows intentionally excluded from the report
avoid displaying empty sections where there is nothing useful to show

Why it matters

Teams often need to record supplier concerns, internal dependency notes, owner comments, sensitive risks or operational context. The customer report should contain selected report-ready detail, not every internal management note.

Key buyer value: StatusAngel helps a company become more transparent without losing control over what is actually sent externally.

Screenshot placeholder REPLACE_WITH_INCLUDE_EXCLUDE_INTERNAL_ONLY_SCREENSHOT_URL

Recipients and evidence/images

StatusAngel separates who receives the update from the Status File content itself, and supports image-based evidence where visual proof strengthens the report.

Recipients

Companies can maintain recipients and link them to the Status Files they should receive. The same recipient can be reused where appropriate, and each Status File can have its own recipient list.

end customers and client contacts
project stakeholders and management contacts
observers, approvers or other relevant recipients

Evidence / Images

StatusAngel currently focuses on controlled image evidence such as photos and screenshots. Images can help customers see progress, condition, issues, milestones or completion rather than only reading about them.

completed work, current progress and site/product condition
screenshot, milestone, issue and completion evidence
selected images included in the report where suitable

Image format guidance: For report/PDF output, users should rely on JPG, JPEG and PNG. HEIC, HEIF and WEBP should not be assumed to embed cleanly inside the PDF report. Where enabled, those files may be accessible through recipient dashboard or download flows, but StatusAngel should not be presented as broad document storage.

Screenshot placeholder REPLACE_WITH_RECIPIENTS_AND_IMAGE_EVIDENCE_SCREENSHOT_URL

Preview, readiness, polished email and PDF snapshot

Before a customer update is sent, StatusAngel gives the company a way to check the report basis and produce a professional output.

Capability	What it does	Why it matters
Readiness checking	Helps confirm the main reporting elements are in place: Status File details, recipients, reportable content, evidence and send readiness.	Reduces rushed, incomplete or inconsistent customer updates.
Report preview	Lets the company review the current report basis before the update is sent.	Supports controlled, deliberate reporting rather than informal last-minute emails.
Polished email	Gives recipients clear update context in a branded email.	Provides a readable first impression and a quick summary of the update.
PDF report	Acts as the formal point-in-time report snapshot and durable record of what was generated or sent.	Customers can save, forward, review or keep the PDF as a record.

Operating principle: The Status File is the live working record. Each generated report/PDF is a point-in-time snapshot of the selected report position.

Screenshot placeholder REPLACE_WITH_REPORT_PREVIEW_READINESS_EMAIL_PDF_SCREENSHOT_URL

Report history, manual sends and send behaviour

Customer reporting is not only about sending an update. It is also about knowing what was sent, when it was sent and who received it.

Report and send history can include

report runs and generated PDF snapshots
send events, recipients and sent status
failed, skipped or suppressed sends
report metadata, sender/reply-to details and linked Status File
manual or scheduled send basis

Manual and scheduled sending

Manual sending is useful when the team wants to review and send only when ready. Scheduled sending is useful when the business wants a repeatable reporting rhythm for customers or stakeholders.

Send behaviour	Meaning
Send always	Send on schedule even if little or no change exists, supporting a consistent customer communication rhythm.
Send only if changed	Send only where the Status File has changed in a meaningful way since the last report.
Skip and log	Skip the send when there is no material update, but keep a record that the scheduled point was reached.
Manual only	Keep automated sending off and send updates only when manually chosen.
Hold for approval	Reserved/future/configurable workflow. It should not be treated as the main live self-service workflow unless specifically enabled.

Screenshot placeholder REPLACE_WITH_REPORT_AND_SEND_HISTORY_SCREENSHOT_URL

Scheduling, tenant defaults, inheritance and timezones

Scheduling gives the business a repeatable reporting rhythm while still allowing practical exceptions for specific Status Files.

Schedule patterns

manual only
daily or weekdays
weekly or fortnightly
monthly or last day of month
chosen local time, timezone and relevant schedule pattern

Tenant default and inherited schedules

A company can define a default reporting pattern and allow new Status Files to inherit it. Individual Status Files can be adjusted, overridden, paused or disabled where allowed.

Timezone-aware scheduling

StatusAngel supports timezone capture and schedule display so reporting times can be understood in the relevant local timezone. The practical goal is clear: when a company says an update should go out at 9:00am in its chosen timezone, the timing should be stored and processed reliably.

Screenshot placeholder REPLACE_WITH_SCHEDULE_DEFAULTS_AND_TIMEZONE_SCREENSHOT_URL

Tenant users, roles, plan limits and operational controls

StatusAngel is intended to operate as a business reporting tool, not only as a single-user utility.

Tenant users and roles

A tenant can invite internal users into its company account and control what they can do based on role and permissions.

tenant administration and settings
Status File management and content contribution
image/evidence management, recipient management and report sending
schedule management, review-only or limited visibility

Plans and controls

Plans control available capability and usage. This keeps the product commercially controlled and technically stable.

active Status File and tenant user limits
recipients per Status File and media/image limits
scheduled-send availability and report/send limits
recipient access/feedback, branding or private deployment options where enabled

Screenshot placeholder REPLACE_WITH_TENANT_USERS_ROLES_PLAN_LIMITS_SCREENSHOT_URL

Recipient access, fit, boundaries and commercial value

StatusAngel is a focused customer status/progress reporting capability. Its value is the reporting discipline behind the update.

Recipient dashboard-lite / feedback where enabled

A recipient may receive the normal update email and PDF, and where enabled, a secure time-limited link to view update context, access the PDF, review available images/downloads or leave simple feedback. This is controlled and configurable, not an open public portal and not a requirement for every recipient.

Where StatusAngel fits

StatusAngel may suit custom manufacturers, boat builders, fit-out companies, construction and maintenance providers, professional services firms, consultants, agencies, implementation teams, repair/service businesses, premium delivery teams and internal service teams reporting to stakeholders.

What it is

scheduled customer status/progress reporting software
a Status File-based reporting capability
a practical project/status tracking layer
a way to send polished updates and keep durable report/send history

What it is not

not a full enterprise project-management suite
not a CRM, helpdesk, ticketing system or document management system
not a full client portal by default
not heavy PM software

Create the Status File Maintain the update Choose what the customer sees Add recipients and evidence Preview the report Send manually or on schedule Keep the history

Why this matters: StatusAngel helps companies answer customer questions more consistently: what progressed, what is next, what risks or issues exist, what dependencies remain, whether milestones or forecast dates moved, what evidence supports the update, who received the report and what was sent previously.

Private/custom deployments: Where a company needs stronger branding, domain control, access rules, reporting controls or support arrangements, private/custom deployment discussions can be handled through Platform Foundry’s apply form.

Screenshot placeholder REPLACE_WITH_END_TO_END_REPORTING_DISCIPLINE_FLOW_SCREENSHOT_URL

Capability in one sentence

StatusAngel helps companies maintain Status Files, select customer-ready update content, add recipients and evidence, preview the report, send polished customer updates manually or on schedule, and keep a durable record of what was sent.

Create your company account View plans See how it works