Product Capabilities

A practical capability for scheduled customer progress and status reporting.

StatusAngel gives companies a structured way to manage Status Files, maintain lightweight project/status information, decide what should appear in customer-facing reports, and send professional progress updates to clients on a chosen schedule.

Create your company account View feature summary See how it works

Status File engine Manage one controlled record for each project, job, build, order, case or service item.

Flexible reporting depth Use short updates or deeper progress, risks, issues, dependencies, milestones and image evidence.

Client visibility control Choose what appears in the customer report and what remains internal.

Scheduled delivery Send manually or automate customer reports on a weekly, fortnightly, monthly or configured schedule.

1. Status File foundation

The Status File is the central operating record.

Each customer-facing item can have its own Status File. That Status File holds the core position, report context, dates, forecast movement, expected outcome, acceptance notes and the structured update sections used for customer reporting.

Status File name and summary

Record the main subject of the update, such as a customer build, order, project, service item, implementation, repair, matter or client file.

Original expected outcome

Define what the work is expected to deliver so future updates have a clear starting point and intended outcome.

Acceptance notes

Capture useful notes around completion, customer expectations, acceptance, review points or final delivery understanding.

Overall status

Track whether the Status File is on track, at risk, delayed, overdue, complete, paused or facing major issues.

Baseline and forecast dates

Maintain the original target date, current forecast date and actual completion date where applicable.

↗

Forecast change reason

Explain why the forecast moved, helping the company communicate date changes more professionally.

2. Lightweight PM/status sections

Structured enough to support the work, light enough to remain practical.

StatusAngel provides practical status sections that help companies manage the current position. These sections can be filled out lightly or in more detail, depending on the customer, project, job or reporting need.

Progress to date

What has been completed, what has moved forward, what has changed, and what current position should be communicated.

Risks

Future uncertainties that may affect delivery, timing, cost, quality, customer expectations or confidence.

Issues

Current problems, blockers or concerns that are already affecting the work and may need explanation.

Next steps

What will happen next, what the team intends to do, and what the customer should expect in the next period.

Dependencies

Things needed from the customer, suppliers, third parties, internal teams, approvals or external events.

Milestones

Key stages, baseline dates, current forecast dates, actual dates, progress percentage and milestone status.

Designed for flexible detail.

A company can use the structure lightly for a concise monthly update, or more fully for stronger project/status visibility. The product supports both styles without trying to become a heavy enterprise project-management suite.

3. Visibility and transparency controls

Control what appears in the customer report.

Some information is useful internally but should not always appear in the client-facing report. StatusAngel supports a controlled reporting model so companies can decide which rows are included in the report and which are kept internal.

Include or exclude individual progress rows.
Include or exclude risks and issues from the customer-facing report.
Keep selected next steps or dependencies internal where needed.
Choose which milestones appear in the report.
Control which images, screenshots, drawings or supporting files are reportable.
Use internal-only flags to preserve working notes or sensitive operational detail.

Customer-facing choice

Transparency can be increased or reduced.

For some client relationships, high transparency is valuable: progress, risks, issues, dependencies, milestone movement and images can all be shown. For other relationships, a more concise report may be better. The company controls the reporting depth.

Capture more than you show.

StatusAngel can help teams maintain a richer internal position while still producing a focused, professional customer update.

4. Scheduled sending

Customer reports can go out at the same chosen time.

Scheduling is central to the StatusAngel value. A company can update its Status Files during the week or month, then have the report sent manually or automatically at the configured reporting point.

NOW

Manual send now

Generate and send the customer update when the team is ready.

Weekly or fortnightly schedules

Choose a day and reporting rhythm for repeat updates.

Monthly schedules

Send updates on a chosen day of the month or use last-day-of-month style reporting.

⏸

Pause or disable

Pause or disable schedules where a Status File should stop sending automated updates.

↻

Tenant default schedules

Configure a default schedule that new Status Files can inherit, while allowing individual overrides.

✓

Send governance

Use controlled sending behaviour, recipient eligibility and report history to reduce accidental or unmanaged sends.

No-excuse reporting rhythm.

If a company wants customers updated at the same time each month, StatusAngel helps turn that into an operating rhythm rather than a manual habit that gets forgotten.

5. Recipients and client contacts

Reusable recipients linked to the right Status Files.

Recipients are the customer contacts, client stakeholders, buyers or external people who receive the update. StatusAngel treats recipients as reusable tenant-level contacts and links them to the Status Files they should receive.

Create reusable recipient/contact records.
Link recipients to one or many Status Files.
Set recipient role, primary recipient flag and include-in-send status.
Mark recipients as do-not-send where needed.
Support recipient suppression and future bounce/complaint handling.
Optionally group contacts through external client organisations.

6. Client organisation grouping

Group work by the tenant’s own client/customer organisation.

Where useful, a tenant can group Status Files and recipients around the external client organisation. This helps companies that manage multiple projects, jobs, builds or service items for the same client.

Tenant customer is not the same as client organisation.

The tenant company uses StatusAngel. The client organisation is the tenant’s own customer or client, used to group Status Files and recipient contacts.

7. Reports, email and evidence

Generate professional updates and preserve what was sent.

StatusAngel’s reporting capability is designed around both communication and proof. The customer receives the update, and the company keeps the generated report and send history as a record.

Branded HTML email

Send a professional email overview that identifies the Status File, customer/company, report title, status and forecast position.

PDF

PDF report attachment

Attach the generated report as a formal snapshot of the update position.

IMG

Images and evidence

Add photos, screenshots, drawings or supporting files where visual proof helps explain the update.

Report history

Keep generated report records so the company can review what was created and sent.

Report media snapshot

Preserve which media items were included in a generated report, with caption and file metadata.

Delivery logging

Track notification events and per-recipient delivery rows so sending activity remains visible.

8. Configuration and plans

Designed for SaaS plans, private deployments and future branding control.

StatusAngel is designed to support a central StatusAngel.com SaaS model and future private/custom deployments. Configuration and plan controls can influence branding, report behaviour, sending limits, media limits, user limits, schedules and feature availability.

Plan and entitlement readiness.
Feature/configuration controls.
Branding and email identity configuration.
Report and media limits.
Private/custom deployment readiness.
Future custom-domain support.

9. Operational control

Built with history, governance and future hardening in mind.

StatusAngel is not just a form and an email button. The architecture preserves report runs, notification events, recipient delivery records, schedule state, forecast history, media references and operational status fields.

Designed to become commercially serious.

The first product loop can stay simple for users, while the underlying model supports stronger plan control, admin oversight, retention policy, delivery tracking and private deployment needs.

Capability boundary

What StatusAngel is, and what it is not trying to be.

StatusAngel is focused on customer-facing status reporting, delivery transparency and scheduled progress communication. It is intentionally lighter than full enterprise project-management software.

What it is

Scheduled customer status reporting software.
A Status File-based progress reporting capability.
A lightweight project/status control layer.
A customer progress update and report history tool.
A configurable SaaS capability for many industries.

What it is not

Not a full Microsoft Project, Primavera, Jira or Asana replacement.
Not a full CRM.
Not a full helpdesk or ticketing system in Gen 1.
Not a heavy collaboration portal by default.
Not an AI-first product that depends on AI to work.

Product capability in one line.

StatusAngel helps companies maintain Status Files, use lightweight project/status tools, choose what customers see, and send professional customer progress/status reports automatically on schedule.

Create your company account View features View plans