SpreadSpace is a multiplayer spreading workspace. Analysts, credit officers and reviewers work one board at the same time, and the policy, the templates and the memo format they share are set once for everyone.
Up to twenty five analysts work one spread at the same time, with live cursors, selections and drags. A colleague's move lands on your screen as it happens, and every save is kept as a restorable revision, so nothing is lost to a wrong click.
A comment thread pins to a visual or to a bare point on the canvas, and prose can link to a source line. The conversation stays attached to the figure it is about, on the loan that wrote it, and never travels into a template.
A credit officer sets the add-backs the institution allows, and every analyst's spread follows. The memo format is a shared company template, and a ratio one analyst builds is there for the teammate reviewing the same deal. A new hire opens the same policy and the same layouts on their first loan.
A spread on SpreadSpace is a shared canvas, not a file passed between inboxes. Two analysts at different zoom levels see each other's cursor over the same card, a drag by one moves the card for both, and the board saves as they go. Everyone on the loan opens the same spread from its shared library.
Review happens in place. A reviewer pins a comment to the card in question, the analyst answers under it, and the figure both are looking at opens its source line for either of them. When the spread is finalized, the reviewer sees what the analyst changed beside a copy built from the documents alone.
The institution's credit policy lives in one place. A credit officer configures the add-backs for a tax basis and a book basis, and every spread applies them. When the policy changes, one edit reaches every analyst, and a loan that needs an exception gets its own configuration without touching the policy.
Spread templates carry a layout to every loan of that type, and the memo your committee reads is rebuilt once as a company template. Comments, placed pictures and source links stay on the loan that made them, so a template never carries one borrower's detail into another's file.
Six roles scope what each person can do. Underwriters move work without touching members or billing, supervisors assign analysts to borrowers, auditors read the logs and nothing else, and developers manage keys and webhooks. Access to a loan's files follows the people assigned to it rather than a title.
Every analyst action lands in an append only log that records who acted, what changed, when, and the before and after values. An edit to a figure records its label, the column and both states, and a revert is its own row. A mistake from last week comes out with one undo from the log, and the undo is logged too. The history is kept for up to seven years.
Up to twenty five. Each sees the others' cursors, selections and drags, and every save is kept as a revision.
On the loan, pinned to the visual or the point on the canvas they are about. They never travel with a template.
Yes. Finalizing freezes the spread into a snapshot with a machine built twin beside it, and every edit is on the log with its before and after values.
A credit officer, once, as a workspace admin or through the API. Every analyst's spread applies it, and a loan that needs an exception gets its own configuration.
Every action lands in an append only log that records who, what, when and the before and after values. It is kept for up to seven years, with one click undo from the log.
Yes. Presence, comments and templates run inside the frame the same way, keyed by the user identifier your system passes.